Dynamics crm 新安装后未启动工作流_Dynamics Crm

Dynamics crm 新安装后未启动工作流

dynamics-crm

Dynamics crm 新安装后未启动工作流,dynamics-crm,Dynamics Crm,我刚刚安装了Dynamics CRM 4.0。除了工作流之外，它工作得很好。他们不会启动。我打开了跟踪，似乎有一个IO错误。服务器是使用IFD和SSL设置的。在内部或外部访问它时没有问题。以下是跟踪： # CRM Tracing Version 2.0 # LocalTime: 2010-06-08 11:34:58.2 # Categories: # CallStackOn: No # ComputerName: FOX-CRM1 # CRMVersion: 4.0.7333.2741 # D

我刚刚安装了Dynamics CRM 4.0。除了工作流之外，它工作得很好。他们不会启动。我打开了跟踪，似乎有一个IO错误。服务器是使用IFD和SSL设置的。在内部或外部访问它时没有问题。以下是跟踪：

# CRM Tracing Version 2.0
# LocalTime: 2010-06-08 11:34:58.2
# Categories:
# CallStackOn: No
# ComputerName: FOX-CRM1
# CRMVersion: 4.0.7333.2741
# DeploymentType: OnPremise
# ScaleGroup:
# ServerRole: AppServer, AsyncService, DiscoveryService, WebService, ApiServer, HelpServer, DeploymentService

[2010-06-08 11:34:58.2] Process:CrmAsyncService |Organization:821a137e-7191-49a4-86cc-69101e2b6d20 |Thread:   24 |Category: Platform.Async |User: 00000000-0000-0000-0000-000000000000 |Level: Error | AsyncOperationCommand.Execute
>Exception while trying to execute AsyncOperationId: {DF68F483-2C73-DF11-9A34-18A9053B7B38} AsyncOperationType: 1 - System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: The handshake failed due to an unexpected packet format.
   at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
   at System.Net.TlsStream.CallProcessAuthentication(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
   at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.ConnectStream.WriteHeaders(Boolean async)
   --- End of inner exception stack trace ---
   at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
   at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Microsoft.Crm.SdkTypeProxy.CrmService.Retrieve(String entityName, Guid id, ColumnSetBase columnSet)
   at Microsoft.Crm.Asynchronous.SdkTypeProxyCrmServiceWrapper.Retrieve(String entityName, Guid id, ColumnSetBase columnSet)
   at Microsoft.Crm.Asynchronous.SdkPluginDescriptionProvider.GetPluginTypeDescription(Guid pluginTypeId, IOrganizationContext context)
   at Microsoft.Crm.Caching.PluginTypeCacheLoader.LoadCacheData(Guid key, IOrganizationContext context)
   at Microsoft.Crm.Caching.CrmMultiOrgCache`2.CreateEntry(TKey key, IOrganizationContext context)
   at Microsoft.Crm.Caching.CrmSharedMultiOrgCache`2.LookupEntry(TKey key, IOrganizationContext context)
   at Microsoft.Crm.Caching.PluginTypeCache.LookupEntry(Guid pluginTypeId, IOrganizationContext context)
   at Microsoft.Crm.Asynchronous.AsyncOperationCommand.GetPluginType(Guid pluginTypeId)
   at Microsoft.Crm.Asynchronous.EventOperation.InternalExecute(AsyncEvent asyncEvent)
   at Microsoft.Crm.Asynchronous.AsyncOperationCommand.Execute(AsyncEvent asyncEvent)

我唯一尝试更新部署表中的AsyncSdkRootDomain行以匹配ADSdkRootDomain和ADApplicationRootDomain值的操作。它是空白的。这似乎不起作用

经过进一步研究，我认为这可能是因为异步服务无法使用SSL访问SDK web服务。如果这是正确的，那么如何配置CRM服务器以实现内部和外部（IFD）安全访问，并且仍然允许异步服务访问网站

谢谢你的帮助

我把这件事弄明白了……大部分时间。这与内部用户和外部用户（通过IFD）通过SSL保护CRM站点有关

这个解决方案并不理想，但很接近。网站是用证书设置的，但它允许非安全连接。使用IFD部署工具，内部和外部访问都使用HTTPS。我们有一个用于内部访问的DNS条目，因此它与证书匹配（我们不使用机器名）。AsynchSdkRootDomain为空（在DeploymentProperties数据库中）。这表明它应该使用环回IP（127.0.0.1）。注册表项ServerURL设置为机器名+端口作为路径（）。并且LocalSdkPort设置为443。这没有什么意义，但它正在发挥作用。

我已经弄明白了……大部分时间。这与内部用户和外部用户（通过IFD）通过SSL保护CRM站点有关