locked
Issue with CRM Adapter 5.5.0 - At least one security token in the message could not be validated. RRS feed

  • Question

  • We are currently using Scribe Insight 7.7.0.43481 with the CRM Adapter 5.5.0.40736.

    We are able to connect to our production CRM and database using the older CRM Adapter 2011 (5.4.1)... but when using the newer adapter we get the following error:

    [04/21/2014 09:30:49.060]ERROR!
       Error Number:  0x00000380 (896)
       Native Error:  0x00000000 (0)
       Source:        System.ServiceModel.Security.MessageSecurityException: An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail.

    Server stack trace:
       at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.ProcessReply(Message reply, SecurityProtocolCorrelationState correlationState, TimeSpan timeout)
       at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout)
       at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
       at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

    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 Microsoft.IdentityModel.Protocols.WSTrust.IWSTrustContract.Issue(Message message)
       at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst, RequestSecurityTokenResponse& rstr)
       at Microsoft.Xrm.Sdk.Client.ServiceConfiguration`1.Issue(AuthenticationCredentials authenticationCredentials)
       at Microsoft.Xrm.Sdk.Client.ServiceConfiguration`1.AuthenticateInternal(AuthenticationCredentials authenticationCredentials)
       at Microsoft.Xrm.Sdk.Client.ServiceConfiguration`1.AuthenticateFederationInternal(AuthenticationCredentials authenticationCredentials)
       at Microsoft.Xrm.Sdk.Client.ServiceConfiguration`1.Authenticate(AuthenticationCredentials authenticationCredentials)
       at Microsoft.Xrm.Sdk.Client.DiscoveryServiceConfiguration.Authenticate(AuthenticationCredentials authenticationCredentials)
       at Scribe.Adapter.Crm.Authentication.Crm2011.ServerConnection.GetDiscoverServiceProxy()
       at Scribe.Adapter.Crm.Authentication.Crm2011.ServerConnection.GetOrganizationAddress(Uri discoveryServiceUri, String organizationName)
       at Scribe.Adapter.Crm.Authentication.Crm2011.ServerConnection.GetServerConfiguration(AuthenticationDefinition authenticationDefinition)
       at Scribe.Adapter.Crm.Authentication.Crm2011.Crm2011ServiceProvider.GetOrganizationService(AuthenticationDefinition authenticationDefinition)
       at Scribe.DynamicsCrm5.Adapter.CrmDatabase.ConnectionMgr.Connect(CrmCredentials credentials)
       at Scribe.DynamicsCrm5.Adapter.CrmDatabase.CrmService.CrmServiceMgr50.Connect(CrmCredentials currentCRMCredentials)
       Description:   An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail.

    [04/21/2014 09:30:49.060]ERROR!
       Error Number:  0x00000380 (896)
       Native Error:  0x00000000 (0)
       Source:        System.ServiceModel.FaultException: At least one security token in the message could not be validated.
       Description:   At least one security token in the message could not be validated.

    Does anyone know how to fix this?  We would rather use the updated driver, as it has fixes for issues we have encountered.

    Thanks!

    -Joe B.

    Tuesday, April 22, 2014 6:09 PM