web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Error for all Users An...
Microsoft Dynamics CRM (Archived)

Error for all Users An Error has occurred. "Try this action again. If the problem continues ..."

(0) ShareShare
ReportReport
Posted on by Community Member

ScreenHunter_5F00_04-Oct.-23-12.44.jpg

Hello,

Around Thursday last week users began reporting they could no longer log into Dynamics CRM.  You can get to our AD login page and that seems to work but the next screen shows the above message.  I have enabled tracing and it looks like there may be some sort of authentication issue, but I can think of nothing that has changed that would cause said issue.

Please trace excerpt below:

# CRM Tracing Version 2.0
# LocalTime: 2017-10-23 12:32:12.793
# Categories: 
# CallStackOn: No
# ComputerName: <removed>
# CRMVersion: 7.0.0001.0129
# DeploymentType: OnPremise
# ScaleGroup: 
# ServerRole: AppServer, AsyncService, DiscoveryService, ApiServer, HelpServer, DeploymentService, SandboxServer, DeploymentManagementTools, VssWriter, EmailConnector

[2017-10-23 12:32:12.793] Process: w3wp |Organization:00000000-0000-0000-0000-000000000000 |Thread:    8 |Category: Platform.Sdk |User: 00000000-0000-0000-0000-000000000000 |Level: Error |ReqId: 00000000-0000-0000-0000-000000000000 | TraceSource.TraceData  ilOffset = 0x68
><TraceRecord xmlns="schemas.microsoft.com/.../TraceRecord" Severity="Error"><TraceIdentifier>msdn.microsoft.com/.../System.ServiceModel.Diagnostics.ThrowingException.aspx&lt;/TraceIdentifier><Description>Throwing an exception.</Description><AppDomain>/LM/W3SVC/1/ROOT-1-131532499297304453</AppDomain><Exception><ExceptionType>System.ServiceModel.EndpointNotFoundException, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType><Message>There was no endpoint listening at net.pipe://localhost/CrmSandboxHost that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.</Message><StackTrace>   at System.ServiceModel.Channels.PipeConnectionInitiator.GetPipeName(Uri uri, IPipeTransportFactorySettings transportFactorySettings)
>   at System.ServiceModel.Channels.NamedPipeConnectionPoolRegistry.NamedPipeConnectionPool.GetPoolKey(EndpointAddress address, Uri via)
>   at System.ServiceModel.Channels.CommunicationPool`2.TakeConnection(EndpointAddress address, Uri via, TimeSpan timeout, TKey&amp;amp; key)
>   at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
>   at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.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.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
>   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
>   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
>   at System.ServiceModel.Channels.ServiceChannelProxy.ExecuteMessage(Object target, IMethodCallMessage methodCall)
>   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeChannel(IMethodCallMessage methodCall)
>   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
>   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData&amp;amp; msgData, Int32 type)
>   at System.ServiceModel.ICommunicationObject.Open()
>   at Microsoft.Crm.Sandbox.SandboxClientBase`1.Open()
>   at Microsoft.Crm.Sandbox.SandboxClientBase`1.get_Proxy()
>   at Microsoft.Crm.Sandbox.SandboxHostManager.PingSingleClient(SandboxClient pingClient, SandboxHostInfo info)
>   at Microsoft.Crm.Sandbox.SandboxHostManager.PingHostsInternal(Object stateObject)
>   at Microsoft.Crm.Sandbox.SandboxHostManager.PingHosts(Object stateObject)
>   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
>   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
>   at System.Threading.TimerQueueTimer.CallCallback()
>   at System.Threading.TimerQueueTimer.Fire()
>   at System.Threading.TimerQueue.FireNextTimers()
></StackTrace><ExceptionString>System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.pipe://localhost/CrmSandboxHost that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---&amp;gt; System.IO.PipeException: The pipe endpoint 'net.pipe://localhost/CrmSandboxHost' could not be found on your local machine. 
>   --- End of inner exception stack trace ---</ExceptionString><InnerException><ExceptionType>System.IO.PipeException, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType><Message>The pipe endpoint 'net.pipe://localhost/CrmSandboxHost' could not be found on your local machine. </Message><StackTrace>   at System.ServiceModel.Channels.PipeConnectionInitiator.GetPipeName(Uri uri, IPipeTransportFactorySettings transportFactorySettings)
>   at System.ServiceModel.Channels.NamedPipeConnectionPoolRegistry.NamedPipeConnectionPool.GetPoolKey(EndpointAddress address, Uri via)
>   at System.ServiceModel.Channels.CommunicationPool`2.TakeConnection(EndpointAddress address, Uri via, TimeSpan timeout, TKey&amp;amp; key)
>   at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
>   at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.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.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
>   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
>   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
>   at System.ServiceModel.Channels.ServiceChannelProxy.ExecuteMessage(Object target, IMethodCallMessage methodCall)
>   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeChannel(IMethodCallMessage methodCall)
>   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
>   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData&amp;amp; msgData, Int32 type)
>   at System.ServiceModel.ICommunicationObject.Open()
>   at Microsoft.Crm.Sandbox.SandboxClientBase`1.Open()
>   at Microsoft.Crm.Sandbox.SandboxClientBase`1.get_Proxy()
>   at Microsoft.Crm.Sandbox.SandboxHostManager.PingSingleClient(SandboxClient pingClient, SandboxHostInfo info)
>   at Microsoft.Crm.Sandbox.SandboxHostManager.PingHostsInternal(Object stateObject)
>   at Microsoft.Crm.Sandbox.SandboxHostManager.PingHosts(Object stateObject)
>   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
>   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
>   at System.Threading.TimerQueueTimer.CallCallback()
>   at System.Threading.TimerQueueTimer.Fire()
>   at System.Threading.TimerQueue.FireNextTimers()
></StackTrace><ExceptionString>System.IO.PipeException: The pipe endpoint 'net.pipe://localhost/CrmSandboxHost' could not be found on your local machine. </ExceptionString></InnerException></Exception></TraceRecord>
[2017-10-23 12:32:12.839] Process: w3wp |Organization:00000000-0000-0000-0000-000000000000 |Thread:    8 |Category: Platform.Sdk |User: 00000000-0000-0000-0000-000000000000 |Level: Error |ReqId: 00000000-0000-0000-0000-000000000000 | TraceSource.TraceData  ilOffset = 0x68
><TraceRecord xmlns="schemas.microsoft.com/.../TraceRecord" Severity="Error"><TraceIdentifier>msdn.microsoft.com/.../System.ServiceModel.Diagnostics.ThrowingException.aspx&lt;/TraceIdentifier><Description>Throwing an exception.</Description><AppDomain>/LM/W3SVC/1/ROOT-1-131532499297304453</AppDomain><Source>System.ServiceModel.Channels.ServiceChannel/50346327</Source><Exception><ExceptionType>System.ServiceModel.CommunicationObjectFaultedException, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType><Message>The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.</Message><StackTrace>   at System.ServiceModel.Channels.CommunicationObject.Close(TimeSpan timeout)
>   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
>   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
>   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
>   at System.ServiceModel.Channels.ServiceChannelProxy.ExecuteMessage(Object target, IMethodCallMessage methodCall)
>   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeChannel(IMethodCallMessage methodCall)
>   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
>   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData&amp;amp; msgData, Int32 type)
>   at System.ServiceModel.ICommunicationObject.Close()
>   at Microsoft.Crm.Sandbox.SandboxClientBase`1.Stop()
>   at Microsoft.Crm.Sandbox.SandboxHostManager.PingSingleClient(SandboxClient pingClient, SandboxHostInfo info)
>   at Microsoft.Crm.Sandbox.SandboxHostManager.PingHostsInternal(Object stateObject)
>   at Microsoft.Crm.Sandbox.SandboxHostManager.PingHosts(Object stateObject)
>   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
>   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
>   at System.Threading.TimerQueueTimer.CallCallback()
>   at System.Threading.TimerQueueTimer.Fire()
>   at System.Threading.TimerQueue.FireNextTimers()
></StackTrace><ExceptionString>System.ServiceModel.CommunicationObjectFaultedException: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.</ExceptionString></Exception></TraceRecord>
[2017-10-23 12:32:18.058] Process: w3wp |Organization:00000000-0000-0000-0000-000000000000 |Thread:   14 |Category: Platform.Sdk |User: 00000000-0000-0000-0000-000000000000 |Level: Error |ReqId: 30b08969-041b-4af0-80d4-da8809147bd7 | TraceSource.TraceData  ilOffset = 0x68
><TraceRecord xmlns="schemas.microsoft.com/.../TraceRecord" Severity="Error"><Description>Handled exception.</Description><AppDomain>/LM/W3SVC/1/ROOT-1-131532499297304453</AppDomain><Exception><ExceptionType>System.IdentityModel.Tokens.SecurityTokenException, System.IdentityModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType><Message>ID4175: The issuer of the security token was not recognized by the IssuerNameRegistry. To accept security tokens from this issuer, configure the IssuerNameRegistry to return a valid name for this issuer.</Message><StackTrace>   at Microsoft.IdentityModel.Tokens.Saml11.Saml11SecurityTokenHandler.CreateClaims(SamlSecurityToken samlSecurityToken)
>   at Microsoft.IdentityModel.Tokens.Saml11.Saml11SecurityTokenHandler.ValidateToken(SecurityToken token)
>   at Microsoft.IdentityModel.Tokens.SecurityTokenHandlerCollection.ValidateToken(SecurityToken token)
>   at Microsoft.IdentityModel.Web.TokenReceiver.AuthenticateToken(SecurityToken token, Boolean ensureBearerToken, String endpointUri)
>   at Microsoft.IdentityModel.Web.WSFederationAuthenticationModule.SignInWithResponseMessage(HttpRequest request)
>   at Microsoft.IdentityModel.Web.WSFederationAuthenticationModule.OnAuthenticateRequest(Object sender, EventArgs args)
>   at Microsoft.Crm.Authentication.Claims.CrmFederatedAuthenticationModule.OnAuthenticateRequest(Object sender, EventArgs args)
>   at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
>   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&amp;amp; completedSynchronously)
>   at System.Web.HttpApplication.ApplicationStepManager.ResumeSteps(Exception error)
>   at System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData)
>   at System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)
>   at System.Web.HttpRuntime.ProcessRequestNoDemand(HttpWorkerRequest wr)
>   at System.Web.Hosting.ISAPIRuntime.ProcessRequest(IntPtr ecb, Int32 iWRType)
></StackTrace><ExceptionString>System.IdentityModel.Tokens.SecurityTokenException: ID4175: The issuer of the security token was not recognized by the IssuerNameRegistry. To accept security tokens from this issuer, configure the IssuerNameRegistry to return a valid name for this issuer.</ExceptionString></Exception></TraceRecord>
[2017-10-23 12:32:18.074] Process: w3wp |Organization:00000000-0000-0000-0000-000000000000 |Thread:   14 |Category: Application |User: 00000000-0000-0000-0000-000000000000 |Level: Error |ReqId: 30b08969-041b-4af0-80d4-da8809147bd7 | ErrorInformation.LogError  ilOffset = 0x21
>MSCRM Error Report:
--------------------------------------------------------------------------------------------------------
Error: ID4175: The issuer of the security token was not recognized by the IssuerNameRegistry. To accept security tokens from this issuer, configure the IssuerNameRegistry to return a valid name for this issuer.

Error Message: ID4175: The issuer of the security token was not recognized by the IssuerNameRegistry. To accept security tokens from this issuer, configure the IssuerNameRegistry to return a valid name for this issuer.

Source File: Not available

Line Number: Not available

Request URL: <removed>/default.aspx

Stack Trace Info: [SecurityTokenException: ID4175: The issuer of the security token was not recognized by the IssuerNameRegistry. To accept security tokens from this issuer, configure the IssuerNameRegistry to return a valid name for this issuer.]
   at Microsoft.IdentityModel.Tokens.Saml11.Saml11SecurityTokenHandler.CreateClaims(SamlSecurityToken samlSecurityToken)
   at Microsoft.IdentityModel.Tokens.Saml11.Saml11SecurityTokenHandler.ValidateToken(SecurityToken token)
   at Microsoft.IdentityModel.Tokens.SecurityTokenHandlerCollection.ValidateToken(SecurityToken token)
   at Microsoft.IdentityModel.Web.TokenReceiver.AuthenticateToken(SecurityToken token, Boolean ensureBearerToken, String endpointUri)
   at Microsoft.IdentityModel.Web.WSFederationAuthenticationModule.SignInWithResponseMessage(HttpRequest request)
   at Microsoft.IdentityModel.Web.WSFederationAuthenticationModule.OnAuthenticateRequest(Object sender, EventArgs args)
   at Microsoft.Crm.Authentication.Claims.CrmFederatedAuthenticationModule.OnAuthenticateRequest(Object sender, EventArgs args)
   at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)


[2017-10-23 12:32:18.105] Process: w3wp |Organization:00000000-0000-0000-0000-000000000000 |Thread:   14 |Category: Platform |User: 00000000-0000-0000-0000-000000000000 |Level: Error |ReqId: 30b08969-041b-4af0-80d4-da8809147bd7 | ExceptionConverter.ConvertMessageAndErrorCode  ilOffset = 0x222
>System.IdentityModel.Tokens.SecurityTokenException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #B8CD5EAF: System.IdentityModel.Tokens.SecurityTokenException: ID4175: The issuer of the security token was not recognized by the IssuerNameRegistry. To accept security tokens from this issuer, configure the IssuerNameRegistry to return a valid name for this issuer.
>   at Microsoft.IdentityModel.Tokens.Saml11.Saml11SecurityTokenHandler.CreateClaims(SamlSecurityToken samlSecurityToken)
>   at Microsoft.IdentityModel.Tokens.Saml11.Saml11SecurityTokenHandler.ValidateToken(SecurityToken token)
>   at Microsoft.IdentityModel.Tokens.SecurityTokenHandlerCollection.ValidateToken(SecurityToken token)
>   at Microsoft.IdentityModel.Web.TokenReceiver.AuthenticateToken(SecurityToken token, Boolean ensureBearerToken, String endpointUri)
>   at Microsoft.IdentityModel.Web.WSFederationAuthenticationModule.SignInWithResponseMessage(HttpRequest request)
>   at Microsoft.IdentityModel.Web.WSFederationAuthenticationModule.OnAuthenticateRequest(Object sender, EventArgs args)
>   at Microsoft.Crm.Authentication.Claims.CrmFederatedAuthenticationModule.OnAuthenticateRequest(Object sender, EventArgs args)
>   at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
>   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Ivan Ficko Profile Picture
    Ivan Ficko 1,380 on at

    Did you try to restart all the CRM services on your CRM server?

  • Community Member Profile Picture
    Community Member on at

    Hello Ivan,

    Yes I restarted the CRM services first.  I then backed out any windows patches that had been recently applied and restarted the server.

    We recently renewed our godaddy wildcard cert for the server but the old cert was not set to expire until early Nov and it was still in place.  Believing this may be the issue I updated the cert in the MMC yesterday adding it to the CRM binding and in AD FS but this seems to have caused a new issue.

    The Clients see the below error now:

    ScreenHunter_5F00_06-Oct.-24-10.08.jpg

    On the server I see this error when trying to access the page

    ScreenHunter_5F00_06-Oct.-24-10.08.jpg

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans