Skip to main content
N
nafonsoalonso1-Visitor
1-Visitor
November 3, 2015
Question

Error when loading Web Services references with Visual Studio 2015

  • November 3, 2015
  • 1 reply
  • 2411 views

Hi,

I'm trying to create a proxy client for web services on following address (integrityserver is my server) to extend Integrity.

http://integrityserver:7001/webservices/10/2/Integrity/?wsdl

However I'm getting the following problem on getting data definition (mex):

There was an error downloading 'http://integrityserver:7001/webservices/10/2/Integrity/?wsdl/$metadata'.

The request failed with HTTP status 405: Method Not Allowed.

Metadata contains a reference that cannot be resolved: 'http://integrityserver:7001/webservices/10/2/Integrity/?wsdl'.

The content type text/xml;charset=UTF-8 of the response message does not match the content type of the binding (application/soap+xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 392 bytes of the response were: '<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'><env:Header></env:Header><env:Body><env:Fault xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'><faultcode>env:Client</faultcode><faultstring>Endpoint {http://webservice.mks.com/10/2/Integrity}Integrity_10_2Port does not contain operation meta data for empty soap body</faultstring></env:Fault></env:Body></env:Envelope>'.

The remote server returned an error: (500) Internal Server Error.

If the service is defined in the current solution, try building the solution and adding the service reference again.

I'm not sure if this is due to something I'm doing wrong, because I've been able to successfully creating proxy clients for two other WebServices;

http://integrityserver:7001/webservices/2009/Generic/?wsdl

and

http://integrityserver‌:7001/webservices/2009/7/Source/?wsdl

Any leak? any help will be appreciated

    1 reply

    K
    KaelLizak16-Pearl
    16-Pearl
    December 29, 2015

    Hello nafonsoalonso‌,

    '400' series messages are server side messages. '405' in this case likely means something wasn't constructed correctly in the Request URI.  Reading into this a little further, the "(500) Internal Server Error" suggests that the best place to dig further into this would be the server logs.  In this case, it would probably be the web server part of the logs as opposed to the Integrity server logs.

    If you haven't already, please contact PTC Integrity Lifecycle Management Support, making a reference to this post.  I suspect this is going take some very specific digging to find the root cause.

    Regards,
    Kael

    Terms & ConditionsAccessibility statement