Recently there were a couple of network changes done at our client’s side which we weren’t aware of and ultimately it led to a downtime for CRM application. Users were not able to log-in to CRM and instead were getting an error which read as
CrmException: Failed to get priv user group information. k = 1b3b9610-36e3-e111-8aef-0050568b60d0 privUserGroupId: 47cbacdc-081f-4457-850f-bc66ef3a2137, localSystemAdGuid: 0005972b-bd43-4de4-8364-51f4b3ef27a8, Exception: System.Runtime.InteropServices.COMException: The server is not operational.
Upon researching a bit, it was clear that the issue was somehow related to Domain Controller which was not able to route any of the user requests thus none of users were able to get authenticated and get into the system. This is how we managed to fix it.
There is a registry key that we can apply for the Preferred Domain Controller on the CRM web server and then do a quick restart of the server and hopefully the CRM should be up and running successfully.
- Go to Run >> regedit
- Once Registry Editor is opened, Navigate to HKLM\Software\Microsoft\MSCRM
- Add a new String value that is named PreferredDc
- Specify the domain controller that you want. Typically, this is the closest domain controller.
- If you are unaware of what the domain controller is then open Command Prompt and type ‘echo %LOGONSERVER%’ (without the quotes). This should give you the current DC. Copy this value and paste it into the PreferredDc setting.
- Restart the CRM server and you should be good to go.
PS: Just in case it still fails, do a restart for all of the CRM services and try refreshing the CRM App Pool and do a IISRESET, finally a restart of the CRM Website.
This should fix the problem for most of you but just in case the above doesn’t help you at all, do let me know in comments below and I can try fixing it up for you.