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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

MS Dynamics CRM 2015 Install Issue - Action Microsoft.Crm.Setup.Server.SetSandboxServicePrincipalNameAction failed

(0) ShareShare
ReportReport
Posted on by 15

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:

/Begin 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

---------------------------

/End Error

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.

*This post is locked for comments

I have the same question (0)
  • bcaspar Profile Picture
    on at

    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.

  • Community Member Profile Picture
    on at

    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

  • Community Member Profile Picture
    on at

    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!

  • Inogic Profile Picture
    682 on at

    This type of issue is occurred because the user selected for service does not have appropriate permission in DC. You can try following points.

     

    1. Give appropriate permission to service account user.
    2. For now you can ignore the error and run the SETSPN command manually after the installation.

    Thanks,

    Sam

  • Community Member Profile Picture
    on at

    Thanks, I figured out the proper command syntax for you SetSPN.  I appreciate the help.

  • Community Member Profile Picture
    on at

    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 < >.

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…

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