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 2Check out the latest updates and new features of Dynamics 365 released from October 2022 through March 2023
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
We have a production environment running dynamics 4 r21. Recently, the CRM admins tried to add a user and received the error: 'The current user id could not be determined'. This lead to the admins noticing that the user exists in the org db but not in the MSCRM_Config db.
When a CRM admin attempts to add the user, they receive 'domain name already exists'.
Has anyone seen this before? Or does anyone have an idea how to resolve such an issue?
One way this can happen is if the organisation was imported into CRM, but the user was not mapped during the import process.
The supported way to resolve this is to disable and delete the organisation, then reimport and makes sure all users are mapped.
A quicker, but unsupported, way would be to change the domainname attribute of the user in the org db to some other value, then add the user
NOTE: THIS IS UNSUPPORTED
You may also delete the user record from within the _MSCRM database.
Try to restore _MSCONFIG DB with latest copy and run repair to avoid other issues, let me know if this helps please.
Business Applications communities