troubleshooting Question

WCF connection Problem

Avatar of socom1985
socom1985 asked on
WCFWeb ServersMicrosoft IIS Web Server
3 Comments1 Solution1530 ViewsLast Modified:
Im trying to connect to a Webservice on a remote machine but I always get the same error I cant find the place where I could change the FQDN. I Replaced localhost in the whole project with the real external url. But still it gives me the .local domain in the error.. :(
Here is the error

Error: Cannot obtain Metadata from http://domain.com/SaaSManager/SaaSManager.Service.svc?wsdl If this is a Windows (R) Communication Foundation service to which you have access, please check that you have enabled metadata publishing at the specified address.  For help enabling metadata publishing, please refer to the MSDN documentation at http://go.microsoft.com/fwlink/?LinkId=65455.WS-Metadata Exchange Error    URI: http://domain.com/SaaSManager/SaaSManager.Service.svc?wsdl    Metadata contains a reference that cannot be resolved: 'http://domain.com/SaaSManager/SaaSManager.Service.svc?wsdl'.    <?xml version="1.0" encoding="utf-16"?><Fault xmlns="http://www.w3.org/2003/05/soap-envelope"><Code><Value>Sender</Value><Subcode><Value xmlns:a="http://schemas.xmlsoap.org/ws/2005/02/sc">a:BadContextToken</Value></Subcode></Code><Reason><Text xml:lang="en-US">The message could not be processed. This is most likely because the action 'http://schemas.xmlsoap.org/ws/2004/09/transfer/Get' is incorrect or because the message contains an invalid or expired security context token or because there is a mismatch between bindings. The security context token would be invalid if the service aborted the channel due to inactivity. To prevent the service from aborting idle sessions prematurely increase the Receive timeout on the service endpoint's binding.</Text></Reason></Fault>HTTP GET Error    URI: http://domain.com/SaaSManager/SaaSManager.Service.svc?wsdl    The document was understood, but it could not be processed.  - The WSDL document contains links that could not be resolved.  - There was an error downloading 'http://domain.local/SaaSManager/SaaSManager.Service.svc?xsd=xsd0'.  - The remote name could not be resolved: 'domain.local'

help please
ASKER CERTIFIED SOLUTION
David Johnson, CD
The More I know, the more I don't know
Join our community to see this answer!
Unlock 1 Answer and 3 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 3 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros