Issue:
We had a client using Microsoft Dynamics CRM 4.0 who created a new user in Active Directory, and then created the user record in CRM.
They then realized that the user's last name was misspelled, including the domain logon, which was in the format of first name initial and last name.
They corrected the spelling in Active Directory. They then attempted to update the user record in CRM by updating the domain logon field. The updated information is pulled in from AD. However, when they attempt to save the record, they receive a dialog box with the following message:
"You are attempting to create a user with a domain logon that is already used by another user. Select another domain logon and try again."
Resolution:
The solution is to modify the CRM user record to use a domain logon that is NOT currently used for a CRM user. Once the record is saved, you can then modify it again to pull the correct domain logon from Active Directory.
Subscribe to:
Post Comments (Atom)
5 comments:
I'm experiencing this issue, but I don't really understand your resolution. Could you please give a more thorough explanation? Thanks!!
Let's say the domain logon of the CRM user is corp\mcrosse, but it should be corp\mcross. You have already updated the Active Directory account but cannot modify the CRM user record.
Edit the CRM user record and replace the corp\mcrosse with a domain logon of somebody who is NOT a CRM user. Save the record.
Edit the CRM user record again and replace the domain logon with the correct domain logon of corp\mcross.
Save the record.
Good luck doing this without using SQL i.e.
update systemuserbase
set domainname = 'corp\mcross'
where domainname = corp\mcrosse'
The active directory GUIDS for that user that are stored in the CRM Database do not change; this should fix your issue.
Re: the comment about using SQL, this is not necessary. See the more recent post that has a solution from Microsoft: http://navintmicrosoftcrm.blogspot.com/2009/01/update-to-post.html
Mike - thanks for the tip! I was banging my head against the wall with this problem and then I tried your solution. It worked great!
Post a Comment