.net webservice錯誤

Question

我正在Silverlight中製作一個帶有服務的程序。 一切工作正常，但當我昨天開始我的程序時，我得到這個錯誤：CommunicationException是未處理的用戶代碼，遠程服務器返回了一個錯誤：NotFound 我的代碼以前工作過，我沒有做任何更改。 不知道這可能是什麼？以及如何解決它。

{System.Net.WebException: The remote server returned an error: NotFound. ---> System.Net.WebException: The remote server returned an error: NotFound. 
    bij System.Net.Browser.BrowserHttpWebRequest.InternalEndGetResponse(IAsyncResult asyncResult) 
    bij System.Net.Browser.BrowserHttpWebRequest.<>c__DisplayClass5.<EndGetResponse>b__4(Object sendState) 
    bij System.Net.Browser.AsyncHelper.<>c__DisplayClass2.<BeginOnUI>b__0(Object sendState) 
    --- Einde van intern uitzonderingsstackpad --- 
    bij System.Net.Browser.AsyncHelper.BeginOnUI(SendOrPostCallback beginMethod, Object state) 
    bij System.Net.Browser.BrowserHttpWebRequest.EndGetResponse(IAsyncResult asyncResult) 
    bij System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelAsyncRequest.CompleteGetResponse(IAsyncResult result)} 

Stacktrace: 
    bij System.ServiceModel.AsyncResult.End[TAsyncResult](IAsyncResult result) 
    bij System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result) 
    bij System.ServiceModel.ClientBase`1.ChannelBase`1.EndInvoke(String methodName, Object[] args, IAsyncResult result) 
    bij BiljartHandicap.UserValidationWebServiceReference.UserValidationWebServiceClient.UserValidationWebServiceClientChannel.EndValidateUsername(IAsyncResult result) 
    bij BiljartHandicap.UserValidationWebServiceReference.UserValidationWebServiceClient.BiljartHandicap.UserValidationWebServiceReference.UserValidationWebService.EndValidateUsername(IAsyncResult result) 
    bij BiljartHandicap.UserValidationWebServiceReference.UserValidationWebServiceClient.OnEndValidateUsername(IAsyncResult result) 
    bij System.ServiceModel.ClientBase`1.OnAsyncCallCompleted(IAsyncResult result) 

Answer 1

摘自a previous SO answer of mine：

'NotFound' is a generic error message that could mean just about anything.
...snip...
In any case, something i have found invaluable for tracking this sort of issue is the Service Trace Viewer tool from Microsoft. Read all about it right here , all it takes is some simple changes to your web.config to enable the logging.