Skip to main content

Notifications

Community site session details

Community site session details

Session Id :
Microsoft Dynamics 365 | Integration, Dataverse...
Answered

XRMToolbox connections to On-Premise CRM16/9 Failing after KB5049993

(3) ShareShare
ReportReport
Posted on by 957
We have a couple of legacy On-Premise CRM boxes for supporting CRM2016 and CRM9.1
Since the end of January both these instances cannot be connected to via the XRMToolbox, or our own utilities that use AD or connection strings to authenticate.

Access via the standard web browser remains unaffected, and both platforms are using the simpler HTTP and standard port of 5555.

Our investigations have linked this problem to the arrival of KB5049993 on Windows Server 2016 and KB5050048 on Windows Server 2012.
If we force the removal of these patches the XRMToolbox and our data transfer utilities start to function again.

Does anybody know what is in these patches that makes this a problem for coded access.
What do we have to change to coexist with these patches.

For those interest in the underlying error, here is the logged output provided by the XRMToolbox:
 
Any suggestions and advice greatfuly received.
 
 
Microsoft.Xrm.Tooling.Connector.CrmServiceClient          Verbose          16         10/02/2025 10:19:57  Initialize CRM connection Started - AuthType: AD
Microsoft.Xrm.Tooling.Connector.CrmServiceClient          Information    8          10/02/2025 10:19:57  Discovery URI is = http://CRM2:5555/XRMServices/2011/Discovery.svc
Microsoft.Xrm.Tooling.Connector.CrmServiceClient          Information    8          10/02/2025 10:19:57  DiscoverOrganizations - Initializing Discovery Server Object with http://CRM2:5555/XRMServices/2011/Discovery.svc
Microsoft.Xrm.Tooling.Connector.CrmServiceClient          Verbose          16         10/02/2025 10:19:57  DiscoverOrganizations - attempting to connect to CRM server @ http://CRM2:5555/XRMServices/2011/Discovery.svc
Microsoft.Xrm.Tooling.Connector.CrmServiceClient          Verbose          16         10/02/2025 10:19:57  DiscoverOrganizations - created CRM server proxy configuration for http://CRM2:5555/XRMServices/2011/Discovery.svc - duration: 00:00:00.1630079
Microsoft.Xrm.Tooling.Connector.CrmServiceClient          Verbose          16         10/02/2025 10:19:57  DiscoverOrganizations - proxy requiring authentication type : ActiveDirectory
Microsoft.Xrm.Tooling.Connector.CrmServiceClient          Verbose          16         10/02/2025 10:19:57  DiscoverOrganizations - service proxy created - total create duration: 00:00:00.1672464
Microsoft.Xrm.Tooling.Connector.CrmServiceClient          Error    2          10/02/2025 10:19:57  ERROR REQUESTING ORGS FROM THE DISCOVERY SERVER
Microsoft.Xrm.Tooling.Connector.CrmServiceClient          Error    2          10/02/2025 10:19:57  ERROR REQUESTING ORGS FROM THE DISCOVERY SERVER
Source : Not Provided
Method           : Not Provided
Date    : 10/02/2025
Time    : 10:19:57
Error    : ERROR REQUESTING ORGS FROM THE DISCOVERY SERVER
Stack Trace     : Not Provided
======================================================================================================================

Microsoft.Xrm.Tooling.Connector.CrmServiceClient          Error    2          10/02/2025 10:19:57  Source : mscorlib
Method           : HandleReturnMessage
Date    : 10/02/2025
Time    : 10:19:57
Error    : The caller was not authenticated by the service.
Stack Trace     : Server stack trace:
   at System.ServiceModel.Security.IssuanceTokenProviderBase`1.DoNegotiation(TimeSpan timeout)
   at System.ServiceModel.Security.SspiNegotiationTokenProvider.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Security.WrapperSecurityCommunicationObject.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Security.CommunicationObjectSecurityTokenProvider.Open(TimeSpan timeout)
   at System.ServiceModel.Security.SymmetricSecurityProtocol.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Security.WrapperSecurityCommunicationObject.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.SecurityChannelFactory`1.ClientSecurityChannel`1.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.CallOpenOnce.System.ServiceModel.Channels.ServiceChannel.ICallOnce.Call(ServiceChannel channel, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)
   at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(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.Xrm.Sdk.Discovery.IDiscoveryService.Execute(DiscoveryRequest request)
   at Microsoft.Xrm.Sdk.Client.DiscoveryServiceProxy.Execute(DiscoveryRequest request)
   at Microsoft.Xrm.Tooling.Connector.CrmWebSvc.DiscoverOrganizations(Uri discoveryServiceUri, Uri homeRealmUri, ClientCredentials clientCredentials, ClientCredentials deviceCredentials, CrmLogEntry logSink)
======================================================================================================================
Inner Exception Level 1         :
Source : System.ServiceModel
Method           : ThrowIfNegotiationFault
Date    : 10/02/2025
Time    : 10:19:57
Error    : The request for security token could not be satisfied because authentication failed.
Stack Trace     : at System.ServiceModel.Security.SecurityUtils.ThrowIfNegotiationFault(Message message, EndpointAddress target)
   at System.ServiceModel.Security.SspiNegotiationTokenProvider.GetNextOutgoingMessageBody(Message incomingMessage, SspiNegotiationTokenProviderState sspiState)
======================================================================================================================

Microsoft.Xrm.Tooling.Connector.CrmServiceClient          Error    2          10/02/2025 10:19:57  Unable to login to Dynamics CRM, Error was : The caller was not authenticated by the service.
Source : mscorlib
Method           : HandleReturnMessage
Date    : 10/02/2025
Time    : 10:19:57
Error    : The caller was not authenticated by the service.
Stack Trace     : Server stack trace:
   at System.ServiceModel.Security.IssuanceTokenProviderBase`1.DoNegotiation(TimeSpan timeout)
   at System.ServiceModel.Security.SspiNegotiationTokenProvider.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Security.WrapperSecurityCommunicationObject.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Security.CommunicationObjectSecurityTokenProvider.Open(TimeSpan timeout)
   at System.ServiceModel.Security.SymmetricSecurityProtocol.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Security.WrapperSecurityCommunicationObject.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.SecurityChannelFactory`1.ClientSecurityChannel`1.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.CallOpenOnce.System.ServiceModel.Channels.ServiceChannel.ICallOnce.Call(ServiceChannel channel, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)
   at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(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.Xrm.Sdk.Discovery.IDiscoveryService.Execute(DiscoveryRequest request)
   at Microsoft.Xrm.Sdk.Client.DiscoveryServiceProxy.Execute(DiscoveryRequest request)
   at Microsoft.Xrm.Tooling.Connector.CrmWebSvc.DiscoverOrganizations(Uri discoveryServiceUri, Uri homeRealmUri, ClientCredentials clientCredentials, ClientCredentials deviceCredentials, CrmLogEntry logSink)
   at Microsoft.Xrm.Tooling.Connector.CrmWebSvc.DiscoverOrganizations(Uri discoveryServiceUri, Uri homeRealmUri, NetworkCredential networkCredential, CrmLogEntry logSink)
   at Microsoft.Xrm.Tooling.Connector.CrmWebSvc.InitCRM2011Service()
======================================================================================================================
Inner Exception Level 1         :
Source : System.ServiceModel
Method           : ThrowIfNegotiationFault
Date    : 10/02/2025
Time    : 10:19:57
Error    : The request for security token could not be satisfied because authentication failed.
Stack Trace     : at System.ServiceModel.Security.SecurityUtils.ThrowIfNegotiationFault(Message message, EndpointAddress target)
   at System.ServiceModel.Security.SspiNegotiationTokenProvider.GetNextOutgoingMessageBody(Message incomingMessage, SspiNegotiationTokenProviderState sspiState)
======================================================================================================================

Microsoft.Xrm.Tooling.Connector.CrmServiceClient          Error    2          10/02/2025 10:19:57  Unable to Login to Dynamics CRM
Microsoft.Xrm.Tooling.Connector.CrmServiceClient          Error    2          10/02/2025 10:19:57  Unable to Login to Dynamics CRM
Source : Not Provided
Method           : Not Provided
Date    : 10/02/2025
Time    : 10:19:57
Error    : Unable to Login to Dynamics CRM
Stack Trace     : Not Provided
======================================================================================================================

 
Categories:
  • rgx91 Profile Picture
    2 on at
    XRMToolbox connections to On-Premise CRM16/9 Failing after KB5049993
    Hello @Steve Le Monnier, can you describe who did you find out which update was the offending one?
    We have the same issue right now, and we theoretically updated all servers (dc controller as well) to the latest windows update.
     
  • Verified answer
    Steve Le Monnier Profile Picture
    957 on at
    XRMToolbox connections to On-Premise CRM16/9 Failing after KB5049993
    We've finally worked out what was causing our problem.
     
    The KB5049993 existed on the CRM server and the client server but not on the Domain Controller.
    Once this KB was installed on all the key boxes the problem disappeared just as quickly as it appeared.
     
    We don't know what it does exactly to the authentication handshake, but it seems only patching some servers and not all is significant.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

🌸 Community Spring Festival 2025 Challenge Winners! 🌸

Congratulations to all our community participants!

Adis Hodzic – Community Spotlight

We are honored to recognize Adis Hodzic as our May 2025 Community…

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
Siv Sagar Profile Picture

Siv Sagar 149 Super User 2025 Season 1

#2
Muhammad Shahzad Shafique Profile Picture

Muhammad Shahzad Sh... 61 Most Valuable Professional

#3
Daivat Vartak (v-9davar) Profile Picture

Daivat Vartak (v-9d... 53 Super User 2025 Season 1

Overall leaderboard

Product updates

Dynamics 365 release plans