Introducing the all-new TIBCO Community site!

For current users, please click "Sign In" to reset your password and access the enhanced features. If you're a first-time visitor, we extend a warm welcome—click "Sign Up" to become a part of the TIBCO Community!

If you're seeking alternative community sites, explore ibi, Jaspersoft, and Spotfire.

Jump to content

Unable to connect to CRM - "Unsecured or incorrectly secured fault was received..."


Manoj Chaurasia

Recommended Posts

Hello -

Starting today, our Scribe Insight server can no longer connect to CRM 2016 Online. When an integration attempts to run, it errors off and returns the following message: " An unsecured or incorrectly secured fault was received from the other party."

We use O365 and CRM 2016 Online.

I've verified that the account being used to make the connect is active, not locked out, and generally " ok" . I've also tried my own account (I am a system administrator in CRM) and it fails as well.

I upgraded one of our Scribe servers to the latest Insight version, but this did not help. I don't know if the problem is Scribe, O365, CRM, or internal to my company.

I've attached a screen shot of the error I see in Scribe.

Below is a partial trace log I pulled from Scribe:

[09/13/2016 08:40:52.487][0x0298] Getting Registry Settings

[09/13/2016 08:40:52.487][0x0298] 09/13/2016 08:40:52 (Adapter for Dynamics CRM) +Connect

[09/13/2016 08:40:52.487][0x0298] 09/13/2016 08:40:52 (Adapter for Dynamics CRM) Connect using current credentials

[09/13/2016 08:40:52.487][0x0298] 09/13/2016 08:40:52 (Adapter for Dynamics CRM) org: orgb7f10520

[09/13/2016 08:40:52.487][0x0298] 09/13/2016 08:40:52 (Adapter for Dynamics CRM) svr: https://disco.crm.dynamics.com/

[09/13/2016 08:40:52.487][0x0298] 09/13/2016 08:40:52 (Adapter for Dynamics CRM) domain:

[09/13/2016 08:40:52.487][0x0298] 09/13/2016 08:40:52 (Adapter for Dynamics CRM) userId: scribe_import@lord.com

[09/13/2016 08:40:52.487][0x0298] 09/13/2016 08:40:52 (Adapter for Dynamics CRM) Home Realm URI:

[09/13/2016 08:40:53.769]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.AuthenticateTokenWithACSForCrm(AuthenticationCredentials authenticationCredentials, Uri appliesTo, Uri acsEndpoint)

at Microsoft.Xrm.Sdk.Client.ServiceConfiguration`1.AuthenticateOnlineFederationInternal(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.

[09/13/2016 08:40:53.769]ERROR!

Error Number: 0x00000380 (896)

Native Error: 0x00000000 (0)

Source: System.ServiceModel.FaultException: ACS10002: An error occurred while processing the SOAP body. ACS50000: There was an error issuing a token. ACS50001: Relying party with identifier 'https://disco.crm.dynamics.com/' was not found.

Trace ID: 3395a202-45c3-488e-940b-ec6780c3d864

Timestamp: 2016-09-13 12:40:53Z

Description: ACS10002: An error occurred while processing the SOAP body. ACS50000: There was an error issuing a token. ACS50001: Relying party with identifier 'https://disco.crm.dynamics.com/' was not found.

Trace ID: 3395a202-45c3-488e-940b-ec6780c3d864

Timestamp: 2016-09-13 12:40:53Z

[09/13/2016 08:40:53.769]ERROR!

Error Number: 0x00000380 (896)

Native Error: 0x00000000 (0)

Source: Scribe.AdapterBase.Publisher.UnableToConnectException: Unable to connect to Microsoft Dynamics CRM using your current settings.

Please verify they are correct.

Posted by Bryan F. on Sep 13 2016 3:47PM { U4822 , F8 , T4605 , C13324 }

Link to comment
Share on other sites

  • 1 month later...

Have a look at one of these articles:

http://www.dynamicscrmpros.com/scribe-fails-connect-microsoft-dynamics-c...

 

http://www.dynamicscrmpros.com/solve-error-id3242-security-token-not-aut...

 

If for some reason your CRM org was moved or upgraded you may have been sent to a new crm url. Open Settings -> Customizations -> Developer Resources and see if the url has changed. I had one a few weeks back that went from https://disco.crm.dynamics.com to https://disco.crm9.dynamics.com

changing that setting in scribe fixed my issue.

 

I hope one of those solutions helps!

 

-Josh

Link to comment
Share on other sites

  • 2 weeks later...
  • 2 years later...
×
×
  • Create New...