Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I am attempting to install MS Dynamics CRM 2015 on a new 2012 R2 server that I have set up, but during the installation I am receiving the following error:
Microsoft Dynamics CRM Setup
Action Microsoft.Crm.Setup.Server.SetSandboxServicePrincipalNameAction failed.
There was a problem setting the service principal name (SPN) for service MSCRMSandboxService with user account "ServiceAccountName". The reason was: Checking domain DC="DomainName",DC=local
Abort Retry Ignore
I have read through the requirements for the Sandbox Processing Service account, here, and made sure that the service account has the necessary permissions. The only part that was confusing me is the line that reads "Folder read and write permission on the Trace, by default located under \Program Files\Microsoft Dynamics CRM\Trace, and user account %AppData%folders on the local computer." This reads to me like the service account needs access to its own %AppData% folder, which it has. The only thing I changed from that page was for the command "SETSPN –a MSCRMSandboxService/<ComputerName> <service account>", I changed -a to -s because it looks like -a has been deprecated from Server 2012.
I can't seem to find anything else that points to a resolution for this issue.
I was encountering the same error and took a look at the SETSPN command. It wasn't even finding my service account at first, which led me to believe it was a networking issue.
I have a DC and a separate VM for SQL and CRM. I turned off the external switch and was able to execute SETSPN successfully, then continued the CRM process and it worked fine.
I realize this may be an environment-specific solution, but I hope it helps.
My experience is that CRM setup automatically creates the needed SPNs for you. So I would recommend installing CRM with newly created service accounts which don't have SPN set already. After you run setup, you can check each account to see wether setup has created the SPNs for you, by using commands like this:
setspn -l hosting\sandboxaccount1
In my case CRM setup automatically created SPNs for the Sandbox service and the Async service. You can always add SPNs if needed after setup
I ran into the same error while installing CRM 2016. Can you clarify the set SPN command. The two service that failed were the Sandbox and Asynchronous. Can you give an example of each command please? Let just say server name is crmserver, domain is crmdomain, users are crmsand and crmasync.
Thank you in advance for your help!
This type of issue is occurred because the user selected for service does not have appropriate permission in DC. You can try following points.
Thanks, I figured out the proper command syntax for you SetSPN. I appreciate the help.
For anyone else having this problem, if you're on Windows Server 2012 R2 and CRM 2015 or CRM 2016 the command to use is as follows:
setspn -s http/MSCRMSandboxService <Domain\User>
setspn -s http/MSCRMAsyncService <Domain\User>
just replace the <Domain\User> with your domain and service account name minus the < >.
Business Applications communities