Can not add ContentService reference in Visual Studio

After uncommenting some tags in web.config file in CWS folder, I can finally add Service Reference over HTTPS. Specifically, I can add Authentication.svc and DocumentManagement.svc to my project.

But when I try to add ContentService, I get this error:

Metadata contains a reference that cannot be resolved: 'https://myserver/les-services/ContentService.svc?wsdl'.
The WSDL document contains links that could not be resolved.
'xmime:expectedContentTypes' is a duplicate attribute name. Line 1, position 502.
Metadata contains a reference that cannot be resolved: 'https://myserver/les-services/ContentService.svc'.
Content Type application/soap+xml; charset=utf-8 was not supported by service https://myserver/les-services/ContentService.svc. The client and service bindings may be mismatched.
The remote server returned an error: (415) Cannot process the message because the content type 'application/soap+xml; charset=utf-8' was not the expected type 'multipart/related; type="application/xop+xml"'..
If the service is defined in the current solution, try building the solution and adding the service reference again.

Am I missing something in IIS or somewhere?

Find more posts tagged with

Comments

Kyle_Swidrovich

What happens when you hithttps://myserver/les-services/ContentService.svc?wsdl from a web browser?

If that’s fine, then you may need to refresh your client side proxies.

Guy_Pomerleau

Does the https config in the web.config on the server configured? by default they are not. I suggest you post your web.config file (server side)

Tiago Vilhena

Did you solve this issue?
I am having exactly the same problem.

Charles Egan

I'm having the exact same issue when updating a service reference. It's 2022. How is this not fixed yet?

I tried to get around it by creating a new project and got the following errors:

An error occurred while attempting to find services at 'https://livelink-ws-t.phillips66.net/webservices/les-services/ContentService.svc?wsdl'. Duplicate attribute found. Both 'xmime:expectedContentTypes' and 'xmime:expectedContentTypes' are from the namespace 'http://www.w3.org/2005/05/xmlmime'. Line 1, position 490.

Metadata contains a reference that cannot be resolved: 'https://livelink-ws-t.phillips66.net/webservices/les-services/ContentService.svc?xsd=xsd0'.

I then proceeded to download the xsd file and sure enough it has duplicate entries for xmime:expectedContentTypes.

Anyone manage to successfully solve this?

Clarke

Hey There,

The WSDL interface is old and not really active from OT anymore (IMHO).

The interface to use now is the REST Interface. REST is all the rage. You can use REST in C#, REST Sharp is an amazing package for C# and REST. All the C# Clients I write now are usually all REST now.

I personally have experiences the exact same issue you are having, many times. For whatever reason, C#/Visual Studio doesn't like the WSDL you are giving it, most likely because the WSDL contains errors/is broken.

From first hand experience, depending on the version, patches or CS, Visual Studio rejects the WSDL.

So besides fixing the WSDL, with more patches or whatever, the alternative is to find one that is actually working. Then consume the WSDL into your current project and then edit the .config to point back to the the system original system/the system you want to talk to.

Save this VS Project somewhere safe so you can just copy/clone it again if you need (and want to avoid these problems).

The WSDL is very static/doesn't really change very much so as long as you can find a working instance of the WSDL you can setup your Visual Studio project.

Regards,

-MC