JoeBrewski
New Member
- Joined
- Jul 4, 2012
- Messages
- 315
Generating path to Hotspot <20.8201, -23.41602, 90.6708>
Waiting for path request to finish...
Generating path to Hotspot <20.8201, -23.41602, 90.6708>
Waiting for path request to finish...
Generating path to Hotspot <20.8201, -23.41602, 90.6708>
Waiting for path request to finish...
Nav callback called.
Can't get path from server.
There was no endpoint listening at http://178.33.63.45:8723/PathService.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
Server stack trace:
at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
at System.ServiceModel.Channels.ServiceChannel*****.InvokeEndService(IMethodCallMessage methodCall, *****OperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannel*****.Invoke(IMessage message)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.Real*****.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.Real*****.PrivateInvoke(MessageData& msgData, Int32 type)
at Buddy.Navigation.NavServiceReference.IPathService.EndGetPath(IAsyncResult result)
at Buddy.Navigation.NavServiceReference.PathServiceClient.EndGetPath(IAsyncResult result)
at Buddy.Navigation.DefaultNavigationProvider.(IAsyncResult )
Generating path to Hotspot <20.8201, -23.41602, 90.6708>
Waiting for path request to finish...
Waiting for path request to finish...
Generating path to Hotspot <20.8201, -23.41602, 90.6708>
Waiting for path request to finish...
Generating path to Hotspot <20.8201, -23.41602, 90.6708>
Waiting for path request to finish...
Nav callback called.
Can't get path from server.
There was no endpoint listening at http://178.33.63.45:8723/PathService.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
Server stack trace:
at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
at System.ServiceModel.Channels.ServiceChannel*****.InvokeEndService(IMethodCallMessage methodCall, *****OperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannel*****.Invoke(IMessage message)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.Real*****.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.Real*****.PrivateInvoke(MessageData& msgData, Int32 type)
at Buddy.Navigation.NavServiceReference.IPathService.EndGetPath(IAsyncResult result)
at Buddy.Navigation.NavServiceReference.PathServiceClient.EndGetPath(IAsyncResult result)
at Buddy.Navigation.DefaultNavigationProvider.(IAsyncResult )
Generating path to Hotspot <20.8201, -23.41602, 90.6708>
Waiting for path request to finish...