CRM 2011错误:通信对象不能用于通信,因为它处于Faulted状态

时间:2014-03-31 12:21:26

标签: c# web-services dynamics-crm-2011

我的CRM组织出现此错误,所有插件都停止工作。 到目前为止,他们一直没有遇到问题。重新启动服务和机器似乎没有帮助。 今天早上我正在使用一个新的插件,当它停止工作时,我意识到其他的不再工作了。我尝试停用并删除新插件但无济于事。 这是跟踪:

[2014-03-31 13:59:28.211] Process:Microsoft.Crm.Sandbox.HostService |Organization:00000000-0000-0000-0000-000000000000 |Thread:   13 |Category: Sandbox |User: 00000000-0000-0000-0000-000000000000 |Level: Warning |ReqId:  | SandboxClientBase`1.Stop  ilOffset = 0xD
>System.ServiceModel.CommunicationObjectFaultedException: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

Server stack trace: 
   at System.ServiceModel.Channels.CommunicationObject.Close(TimeSpan timeout)

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 System.ServiceModel.ICommunicationObject.Close()
   at Microsoft.Crm.Sandbox.SandboxClientBase`1.Stop()
[2014-03-31 14:08:37.953] Process:Microsoft.Crm.Sandbox.HostService |Organization:00000000-0000-0000-0000-000000000000 |Thread:   15 |Category: Sandbox |User: 00000000-0000-0000-0000-000000000000 |Level: Warning |ReqId:  | SandboxErrorHandler.HandleError  ilOffset = 0xE
>System.ServiceModel.CommunicationException: There was an error reading from the pipe: Unrecognized error 109 (0x6d). ---> System.IO.IOException: The write operation failed, see inner exception. ---> System.ServiceModel.CommunicationException: There was an error reading from the pipe: Unrecognized error 109 (0x6d). ---> System.IO.PipeException: There was an error reading from the pipe: Unrecognized error 109 (0x6d).
   at System.ServiceModel.Channels.PipeConnection.OnAsyncReadComplete(Boolean haveResult, Int32 error, Int32 numBytes)
   --- End of inner exception stack trace ---
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.ConnectionStream.ReadAsyncResult.End(IAsyncResult result)
   at System.Net.FixedSizeReader.ReadCallback(IAsyncResult transportResult)
   --- End of inner exception stack trace ---
   at System.Net.Security.NegotiateStream.EndRead(IAsyncResult asyncResult)
   at System.ServiceModel.Channels.StreamConnection.EndRead()
   --- End of inner exception stack trace ---
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.FramingDuplexSessionChannel.TryReceiveAsyncResult.End(IAsyncResult result, Message& message)
   at System.ServiceModel.Dispatcher.DuplexChannelBinder.EndTryReceive(IAsyncResult result, RequestContext& requestContext)
   at System.ServiceModel.Dispatcher.ErrorHandlingReceiver.EndTryReceive(IAsyncResult result, RequestContext& requestContext)
# CRM Tracing Version 2.0
# LocalTime: 2014-03-31 14:09:22.932
# Categories: *:Warning
# CallStackOn: No
# ComputerName: KASUMIACC
# CRMVersion: 5.0.9910.0014

更新1

有一个插件调用了WS,因此Pipe的错误是由于这个原因造成的。我停用了该插件,现在服务启动时出现的错误是:

[2014-03-31 14:46:51.239] Process:Microsoft.Crm.Sandbox.HostService |Organization:00000000-0000-0000-0000-000000000000 |Thread:   11 |Category: Sandbox |User: 00000000-0000-0000-0000-000000000000 |Level: Warning |ReqId:  | SandboxClientBase`1.Stop  ilOffset = 0xD
>System.ServiceModel.CommunicationObjectFaultedException: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.
Server stack trace: 
   at System.ServiceModel.Channels.CommunicationObject.Close(TimeSpan timeout)
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 System.ServiceModel.ICommunicationObject.Close()
   at Microsoft.Crm.Sandbox.SandboxClientBase`1.Stop()

更新2

我使用Powershell为MSCRMSandboxService设置SPN

setspn -A MSCRMSandboxService/localhost ACCOUNTNAME

并用

验证
setspn -L AccountName

一切似乎都没问题,但它没有帮助。

有什么想法吗?

0 个答案:

没有答案