Step-by-Step Microsoft CRM 1.2 Migration to CRM 3.0 – Part II

As discussed in my previous blog entry, lets now take a peek at some of the issues you might encounter whilst CRM 1.2 Migration to CRM 3.0.


1. Importing “Mapping.xml” and “Deployment.xml” XML files might fail on the new test server with error: “An error occurred during mapping the computer accounts – the mapping failed”. To resolve this error, open import.log for more details. There is a KB article which discusses about hot fix but that might not help. More information on

The reason you get this error is due to the fact that the computer names of the TEST CRM Server, GUID and SID are not updated (newguid=”<update manually>“, newname=”<update manually>“, newsid=”<update manually>“.) and during the import process it attempts to reuse and eventually it fails with an error occurred during the mapping of computer accounts. The mapping failed. Exception of type System.Exception was thrown (SDTransform).

To resolve this, open “Deployment.xml” in notepad (Make a copy of that before you actually edit). Watch for word-wrap and search for the following tag (<mapping type=”computer);

<mapping type=”computer role=” dbname=” oldguid=”{206e4599-8fa2-4e37-b893-6791f81b6369} newguid=”<update manually> oldname=”CN=CRM-PRODUCTION,CN=Computers,DC=DOMAIN,DC=com newname=”<update manually> oldsid=”S-1-5-21-622582695-539100016-4190993944-1640 newsid=”<update manually> />

Note that the XML file says to update the newguid=”<update manually>“, newname=”<update manually>“, newsid=”<update manually>of the new CRM TEST Server.

You have the newname of the TEST CRM Server. Now, the task is to get the newguid & newsid. This is achieved by using ADSIEDIT & GETSID.exe.


  1. Install ADSIEDIT from Windows Server 2003 Support Tools.
  2. Launch ADSIEDIT.msc and browse through Domain – DC=DOMAIN,DC=COM – CN=COMPUTERS – CN=TEST-CRM-SERVER-NAME.
  3. Right click CN=TEST-CRM-SERVER-NAME, Click on Properties – Double Click on Attribute: objectGUID and copy the hexadecimal value and you have to paste in the deployment.xml file newguid=”<Paste objectGUID>.

GETSID – Get Security ID

You can identify the SID by using GetSID.exe. Getsid.exe is a simple tool that returns the SIDs for two user accounts that you specify and tells you whether the accounts’ SIDs match. You must provide two account names. If you want to determine the SID for only one account, the simplest solution is to specify the same account twice.

  1. Install GETSID from Windows XP SP2 Support Tools.
  2. The syntax for Getsid.exe is – getsid \\server1 account \\server2 account. For instance; CMD: getsid \\TEST-CRM-SERVER-NAME administrator \\TEST-CRM-SERVER-NAME administrator
  3. Copy the SID to paste in the deployment.xml file newsid=”<update manually>

Now, simply paste the above values in the deployment.xml file as explained above. Run RedeployWizard.exe again and the import should be successful.

In the next blog entry, we will see some more issues with related to “Deployment.xml” file. Stay tuned!

One thought on “Step-by-Step Microsoft CRM 1.2 Migration to CRM 3.0 – Part II

Leave a Reply

Your email address will not be published. Required fields are marked *