Answered by:
moving mscrm 2011 from one domain to another

Question
-
i backup and restored the my xxx_mscrm db from one sql server in domain a and restored it to domain b. Delete the organization from domain b and imported it .
When i try to connect to dynamics is get a error saying
business management error you are attempting to create a user with a domain logon that does not exist select another domain logon
does anyone have any idea on how to resolve this error. What is the correct was to move a crm environment from dev_domain to prod_domain
ronTuesday, June 7, 2011 4:19 PM
Answers
-
Sounds like a user mapping problem. Remove the org and reimport it and try manually mapping the users and see if that helps. Or at least try some different method of mapping the users than you tried before. It will ask you how you want to handle the user mappings in the import wizard.
Jamie Miley
http://mileyja.blogspot.com
Linked-In Profile
Follow Me on Twitter!- Proposed as answer by Jamie MileyModerator Friday, June 8, 2012 3:00 PM
- Marked as answer by Jamie MileyModerator Monday, April 15, 2013 5:20 PM
Tuesday, June 7, 2011 5:17 PMModerator -
It wouldn't be supported. I would still try the other methods of importing first to see if anything works, but if not I would open a ticket with Microsoft before I would try an unsupported solution like modifying the tables.
Jamie Miley
http://mileyja.blogspot.com
Linked-In Profile
Follow Me on Twitter!- Proposed as answer by Jamie MileyModerator Friday, June 8, 2012 3:00 PM
- Marked as answer by Jamie MileyModerator Monday, April 15, 2013 5:20 PM
Tuesday, June 7, 2011 6:07 PMModerator -
can you ensure that the user who is doing the import / install / move is listed as a Deployment Admin in the Org before moving it. I don't know that this will help but it is worth a try.
- Proposed as answer by Jamie MileyModerator Friday, June 8, 2012 3:00 PM
- Marked as answer by Jamie MileyModerator Monday, April 15, 2013 5:20 PM
Friday, June 10, 2011 2:36 AM
All replies
-
Sounds like a user mapping problem. Remove the org and reimport it and try manually mapping the users and see if that helps. Or at least try some different method of mapping the users than you tried before. It will ask you how you want to handle the user mappings in the import wizard.
Jamie Miley
http://mileyja.blogspot.com
Linked-In Profile
Follow Me on Twitter!- Proposed as answer by Jamie MileyModerator Friday, June 8, 2012 3:00 PM
- Marked as answer by Jamie MileyModerator Monday, April 15, 2013 5:20 PM
Tuesday, June 7, 2011 5:17 PMModerator -
same issue - can the tables be edited to solve this issue ?
ronTuesday, June 7, 2011 5:56 PM -
It wouldn't be supported. I would still try the other methods of importing first to see if anything works, but if not I would open a ticket with Microsoft before I would try an unsupported solution like modifying the tables.
Jamie Miley
http://mileyja.blogspot.com
Linked-In Profile
Follow Me on Twitter!- Proposed as answer by Jamie MileyModerator Friday, June 8, 2012 3:00 PM
- Marked as answer by Jamie MileyModerator Monday, April 15, 2013 5:20 PM
Tuesday, June 7, 2011 6:07 PMModerator -
can you ensure that the user who is doing the import / install / move is listed as a Deployment Admin in the Org before moving it. I don't know that this will help but it is worth a try.
- Proposed as answer by Jamie MileyModerator Friday, June 8, 2012 3:00 PM
- Marked as answer by Jamie MileyModerator Monday, April 15, 2013 5:20 PM
Friday, June 10, 2011 2:36 AM -
Did your issue get resolved?
Jamie Miley
Check out my about.me profile!
http://mileyja.blogspot.com
Linked-In Profile
Follow Me on Twitter!Friday, June 8, 2012 3:01 PMModerator