c# - WCF Service Discovery has stopped working via WCF Test Client and via Visual Studio -
having spent around 3 days , losing of hair i'm calling out the wonderful stackoverflow community!
we've got bunch of wcf web services on dedicated windows server 2008 r2 running iis7.5. xamlx, svc, asmx.
we've been running these services fair few years no problem. of sudden we're finding of our apps (web / console etc) failing call them. if explicitly reference wsdl (appending ?wsdl call example http://server:8000/app/app.svc?wsdl
) we're sorted , works again.
problem doesn't explain happened on server caused of our services stop working.
when try call services using wcftestclient
error: cannot obtain metadata
http://server:8081/app/app.svc
if windows (r) communication foundation service have access, please check have enabled metadata publishing @ specified address. enabling metadata publishing, please refer msdn documentation @ http://go.microsoft.com/fwlink/?linkid=65455.ws-metadata exchange error uri:http://server:8081/app/app.svc
metadata contains reference cannot resolved: 'http://server:8081/app/app.svc
'. content type application/soap+xml; charset=utf-8 not supported servicehttp://server:8081/app/app.svc
. client , service bindings may mismatched. remote server returned error: (415) cannot process message because content type 'application/soap+xml; charset=utf-8' not expected type 'text/xml; charset=utf-8'..http error uri:http://server:8081/app/app.svc
html document not contain web service discovery information.
i'll happily go through , implement more detailed publishing information our web.config files. no problem @ all! want understand has happened server has caused discovery of these services fail.
also, we've not run windows updates on here since april 2013 (we've since updated , restarted , it's had no effect)
the applications mix of .net 2 , including 4.5 , discovery failing on of them. have mirror of server use testing exact same setup , discovery of these services not fail.
any appreciated!
wow took quite while fix found out issue - new relic's .net agent. after removing had no problems.
Comments
Post a Comment