Operating Dynamics 365 Customer Engagement (on-premises) (on-premises)

As you administer Dynamics 365 Customer Engagement (on-premises), you’ll want to guarantee availability for your users by monitoring server status and performance, troubleshooting issues, and planning for disaster recovery.

Ongoing maintenance of Dynamics 365 Customer Engagement (on-premises) includes operations such as updating, customizing, monitoring, and relocating or reconfiguring Dynamics 365 Server and required or optional technologies such as SQL Server and SharePoint.

Caution

Operations that require intensive database transactions cannot be run concurrently. This includes the following operations:

• Language pack provisioning
• Importing a solution
• Publishing customizations
• Database updates (Customer Engagement (on-premises) only)
• Solution update operations (Dynamics 365 for Customer Engagement only)

Known issues operating Dynamics 365 Customer Engagement (on-premises)

Plugin failure or Dynamics 365 API call to sandbox service failure

If there is a plugin failure on a plugin registered on sandbox mode, the following exception might be logged:

Message: System.ServiceModel.Security.SecurityNegotiationException: A call to SSPI failed, see inner exception. ---> System.Security.Authentication.AuthenticationException: A call to SSPI failed, see inner exception. ---> System.ComponentModel.Win32Exception: The target principal name is incorrect --- End of inner exception stack trace --- at System.Net.Security.NegoState.StartSendAuthResetSignal(LazyAsyncResult lazyResult, Byte[] message, Exception exception) at System.Net.Security.NegoState.StartSendBlob(Byte[] message, LazyAsyncResult lazyResult)

Event Viewer might record this event when the issue occurs:

The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server SVC.[REDACTED - Sandbox Service Account]. The target name used was host/[REDACTED Destination Server]. This indicates that the target server failed to decrypt the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target service is using. Ensure that the target SPN is only registered on the account used by the server. This error can also happen if the target service account password is different than what is configured on the Kerberos Key Distribution Center for that target service. Ensure that the service on the server and the KDC are both configured to use the same password. If the server name isn't fully qualified, and the target domain ([REDACTED CX DOMAIN]) is different from the client domain ([REDACTED CX DOMAIN]), check if there are identically named server accounts in these two domains, or use the fully qualified name to identify the server

This issue occurs when there are two or more Windows servers running the Dynamics 365 Customer Engagement full server role in the deployment. This issue only occurs with Dynamics 365 Customer Engagement (on-premises), version 9.1.

To work around this issue, do one of the following.

• Split full server roles (recommended):
  • If you have multiple servers running the full server role deployed in a server farm, separate the roles by deploying as front end and back end within the farm. More information: Install Dynamics 365 Server Front End Server and Back End Server roles
• Configure the following service accounts to use the same password (not recommended):
  • IIS application pool identity account(w3wp)
  • Asynchronous Processing Service account

Note

After implementing this work around you may continue to receive events in Event Viewer related to this issue. You can identify these events when the call stack includes the keyword Isandboxhost.ping. This is a known issue and when this occurs, the events can be ignored.