Analysis Services – Errors when trying to add a User as a Server Admin

When trying to add a user as a Server Admin to Analysis Services, you may encounter one of the following errors:

The following system error occurred:  The trust relationship between the primary domain and the trusted domain failed.


The following system error occurred:  No mapping between account names and security IDs was done.

When you see this, you want to look for an entry in the Admin list that looks like a SID (Security Identifier) instead of the actual account name.  For example:


This emails that the account that was listed as a Server Admin was probably deleted, or if you were in a Trusted Domain scenario, the Trust may have been broken preventing the ability to resolve the SID to the account name.

If you see this, and then add a new user, when you hit on the OK button on the bottom, you will see one of the two errors above.  The first error could come up if you are in that Trust Domain Scenario and the user was from a different domain.  The second error may come up if it was just a user in the same Domain as the SSAS Service.

To get around this issue, remove the SID account and then you should be able to add the new Admin account normally.


Adam W. Saxton | Microsoft Escalation Services

Comments (10)

  1. Jenver says:

    It works. Really Helpful I tried many ways. Thanks Adam.

  2. Alexander says:

    Thanks for this, this worked for us. We had a situation in which our only SSAS admin was an SID number and it wasn't letting us add any other accounts. But, with the same login that wasn't able to add accounts I was able to remove the SID user and then was seemingly granted permission by SSAS add another. After that everything was good.

  3. Robert says:

    This is exactly what I was looking for… worked for us as well.

  4. Srinivas says:

    I haven't seen SID in the security pane but still I facing the above error when trying to add a SG.

  5. John says:

    Worked like a charm.  Thanks for the clear cut answer and screenshot.

  6. Arunkumar M says:

    Thanks a lot Adam, This simple post resolved our issue so quickly than other blogs which created confusion with much unwanted information.

  7. Karen says:

    We've had this happen with all of our valid logins from a domain including my own login. This was for the Analysis services/properties/security  list.  

    The server was set up correctly to know where to find the domain.

    In our case, I made sure we could see the domain when we click add a new user.  It would find the new user from the same domain as everyone else but give the message ' No mapping between account names and security IDs was done' when we tried to save it due to the others in the list not showing correctly.  

    Luckily a restart of analysis services resolved the issue. It would be great if SSAS ignored existing users (good or bad) when adding  a new user.

  8. Kishan says:

    It worked and was very helpful.
    Thank you very much!

  9. winson says:

    This is what exactly I was looking for.
    Thanks for the solution. You hit the nail on the spot.

Skip to main content