我一次又一次地遇到 LoadOperation 失败的情况
我不知道为什么，有时加载操作成功，有时不成功。是因为同时发出了很多（6-7）个请求吗？所有 get 查询偶尔都会失败。这是错误之一：-
Webpage error details
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; InfoPath.2; Tablet PC 2.0; .NET4.0C; .NET4.0E)
Timestamp: Wed, 16 Mar 2011 03:22:10 UTC
Message: Unhandled Error in Silverlight Application
Code: 4004
Category: ManagedRuntimeError
Message: System.ServiceModel.DomainServices.Client.DomainOperationException: Load operation failed for query 'GetSiteTerms'. The remote server returned an error: NotFound. ---> System.ServiceModel.CommunicationException: The remote server returned an error: NotFound. ---> System.Net.WebException: The remote server returned an error: NotFound. ---> System.Net.WebException: The remote server returned an error: NotFound.
at System.Net.Browser.BrowserHttpWebRequest.InternalEndGetResponse(IAsyncResult asyncResult)
at System.Net.Browser.BrowserHttpWebRequest.<>c__DisplayClass5.<EndGetResponse>b__4(Object sendState)
at System.Net.Browser.AsyncHelper.<>c__DisplayClass2.<BeginOnUI>b__0(Object sendState)
--- End of inner exception stack trace ---
at System.Net.Browser.AsyncHelper.BeginOnUI(SendOrPostCallback beginMethod, Object state)
at System.Net.Browser.BrowserHttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelAsyncRequest.CompleteGetResponse(IAsyncResult result)
--- End of inner exception stack trace ---
at System.ServiceModel.DomainServices.Client.WebDomainClient`1.EndQueryCore(IAsyncResult asyncResult)
at System.ServiceModel.DomainServices.Client.DomainClient.EndQuery(IAsyncResult asyncResult)
at System.ServiceModel.DomainServices.Client.DomainContext.CompleteLoad(IAsyncResult asyncResult)
--- End of inner exception stack trace ---
at System.ServiceModel.DomainServices.Client.OperationBase.Complete(Exception error)
at System.ServiceModel.DomainServices.Client.LoadOperation.Complete(Exception error)
at System.ServiceModel.DomainServices.Client.DomainContext.CompleteLoad(IAsyncResult asyncResult)
at System.ServiceModel.DomainServices.Client.DomainContext.<>c__DisplayClass1b.<Load>b__17(Object )
Line: 76
Char: 13
Code: 0
URI: http://localhost:9090/Default.aspx
Ria 服务不稳定还是我需要对 Sql 服务器的设置进行一些更改？
提前致谢 ：）
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
“未找到”异常在“一般保护错误”之后在无帮助方面排名第二。可能有很多问题都隐藏在那个坚不可摧的“未找到”堡垒后面。
这种情况最常发生，因为 WCF 服务调用返回 HTTP 结果 4xx 或 5xx。那么，Silverlight产生的异常对调试问题没有丝毫帮助。但您不需要 Silverlight 来帮助 - 毕竟问题是服务器端的。如果启动 Fiddler，您将能够看到 Silverlight 客户端和服务器之间的流量。在那里，您还可以看到确切的服务器响应以及确切的异常消息和堆栈跟踪。
尝试使用 “如何永久消除 Silverlight 的 WCF 服务调用“未找到”错误”，使 Silverlight 错误更容易接受。
The "Not found" exception wins second place in unhelpfulness after "General Protection Fault". It could be a number of problems all getting stashed behind that impenetrable "Not found" fortress.
It happens most often because a WCF service call returned an HTTP result 4xx or 5xx. Then, the exception generated by Silverlight does not help in the slightest to debug the problem. But you don't need Silverlight here to help - the problem is server-side after all. If you fire up Fiddler, you'll be able to see the traffic between the Silverlight client and the server. There, you'll also be able to see the exact server response with the exact exception message and stack trace.
Try using the tips in "How to Permanently Banish Silverlight’s “Not Found” Error for WCF Service Calls" to make the Silverlight errors more palatable.
我与这个错误斗争了两天并找出问题所在......
默认情况下，当您尝试加载数据源时，它只能处理 64K 数据......当您找不到时，这意味着大小大于 64k......尝试复制表，将行数减少到10-15（刚刚测试）并尝试执行应用程序，它会正常工作......
I was fighting with this error for 2 days and figured out whats the issue is....
By default when you try to load the datasource it can handle only 64K data....when you get not found which means the size is greater than 64k......try replicating the table, bring down the number of rows to 10-15(just testing) and try execute the app it will work fine......