no wsdl root element set

[former_member184588]

Hello,

I am trying to consume an .net web service. Using no security works. But now we activated SSL and user/pass authentification and i am not able anymore to generate the service. The Report RSSIDL_DESERIALIZE_DEMO shows the following error message:

-

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
-<soap:Body>
-<soap:Fault>
 <faultcode>soap:Server</faultcode>
 <faultstring>SIDL/SLIB exception</faultstring>
-<detail xmlns:slibfault="http://xml.sap.com/2005/11/esi/slib/fault/">
 <slibfault:timestamp>Thu, 18 Jul 2013 12:32:50 GMT</slibfault:timestamp>
-<slibfault:exception>
 <slibfault:text>Kein WSDL-Root-Element gesetzt</slibfault:text>
 <slibfault:positionprogram="CL_SRT_WSP_CONFIG_SIDL========CP" include="CL_SRT_WSP_CONFIG_SIDL========CM011" line="30" />
 </slibfault:exception>
 </detail>
 </soap:Fault>
 </soap:Body> 
</soap:Envelope>

But we have a root element and when I see the WSDL in the i-browser I am able to spin it up and down.

Like I told the .net WSDL changed but I cannot see which element is wrong:

<wsdl:definitions name="MasterDataService" targetNamespace="http://tempuri.org/">
    <wsp:Policy wsu:Id="basicHttpBindingEndpoint_policy">
      <wsp:ExactlyOne><wsp:All><http:NegotiateAuthentication/>
      <sp:TransportBinding><wsp:Policy><sp:TransportToken>
      <wsp:Policy>
 <sp:HttpsToken RequireClientCertificate="false"/>
</wsp:Policy>
</sp:TransportToken>
<sp:AlgorithmSuite>
<wsp:Policy>
<sp:Basic256/>
</wsp:Policy>
</sp:AlgorithmSuite>
<sp:Layout>
<wsp:Policy>
<sp:Strict/>
</wsp:Policy>
</sp:Layout>
</wsp:Policy></sp:TransportBinding>
<wsaw:UsingAddressing/>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
<wsdl:types>

When I download the WSDL and its XSD-files and exchange the policy-area of the wsdl with the old one without security. I am able to see the WSDL in the report without any problems.

Did someone ever has had a similar problem and knows how to fix it? Searching in google and the scn didn't bring new informations. I also could not find any sap notes that describe this problem. What is the element that is wrong?

Greetings, Vanessa

[former_member184588]

If I delete the sp:TransportBinding - Section... I can see the WSDL file with the mentioned report. Does it mean that sp:TransportBinding is microsoft specific and not supported by SAP?