Hello everyone,
The company I work for has WCF Web Services hosted on Windows Azure in a medium sized webrole with two instances. We call the services from a WPF Application. 99.9% of the time the calls from the client application to the WCF Web Services work correctly, but every once in a while trying to call a web service method returns the following exception:
Source
mscorlib
Message
There was no endpoint listening at
https://website/ServiceName.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
StackTrace
Server stack trace:
at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout)
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.SendRequest(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at ApplicationName.ServiceName.IServiceName.WebServiceMethodName(Guid sessionToken)
at ApplicationName.WindowName.ClientApplicationMethodName(Object sender, DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
TargetSite
Void HandleReturnMessage(System.Runtime.Remoting.Messaging.IMessage, System.Runtime.Remoting.Messaging.IMessage)
Source
System
Message
The remote name could not be resolved: 'website' (website where web services are hosted, same as "website" fromThere was no endpoint listening at
https://website/ServiceName.svc above)
StackTrace
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at System.Net.HttpWebRequest.GetRequestStream()
at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
TargetSite
System.IO.Stream GetRequestStream(System.Net.TransportContext ByRef)
Although the exceptions are very rare, I've personally replicated this when running the client application on my 64-bit Windows 7 machine and its Windows XP Virtual Machine. Our customers have seen this occur when running the client application on Windows Vista & Windows XP machines.
The exceptions have occured in across multiple web services and methods, for both normal and async calls.
I find these exceptions confusing because normally a "no endpoint listening" exception occurs when trying to get the configuration right, but in this case the configuration is correct and the web services usually work great. Because the exceptions are so rare it's difficult to replicate. Also, since we're hosting the services on a medium sized Azure webrole with two instances (and we're not all that busy), I don't think it's a case of the web services being overloaded.
I checked the Azure IIS logs for the date and time when I replicated this exception but couldn't find anything of interest. (if the client is saying it couldn't resolve the name where the web services are hosted then I'm guessing the request didn't make it through to Azure and thus didn't appear in the IIS logs...)
I originally posted about this in the WCF forms but they sent me over here. Is there anything in either the WCF or Azure configurations I should check? Is there any more information I can provide you guys?
Thanks for the help,
ZenkeiRich