Data migration troubleshooting

This message may be due to:

• If mandatory updates need to be installed. To check if mandatory updates are required, on the Start menu, point to Microsoft Dynamics CRM Online, and then click Update. If updates are not automatically installed, no updates are available.

  No mandatory updates have yet been released.

If the Data Migration Manager cannot synchronize customizations during the sign-in process, it shows this error. This problem may occur if customizations have been made, but not published in Microsoft Dynamics CRM Online.

To work around the problem, try closing Data Migration Manager, and then publish the customization in Microsoft Dynamics CRM Online. Restart Data Migration Manager.

If the error message still occurs, uninstall and reinstall Data Migration Manager.

Data Migration Manager can only work with one Microsoft Dynamics CRM Online server.

To work around this, if you need to migrate data to another instance of Microsoft Dynamics CRM Online, you must uninstall and reinstall Data Migration Manager.

Caution

Any data maps you have created for migrations will be deleted when you uninstall and reinstall. If you need to use an existing data map with the other server, be sure to export the data map, prior to uninstalling Data Migration Manager.

This problem occurs if the server isn't available.

First, make sure you can access the Microsoft Dynamics CRM Online server from Internet Explorer. If prompted for your account name and password, be sure to check the Remember my password check box. If you are using Microsoft Vista, you will also need to store the credential type to use for this server. For more information, see the Microsoft Dynamics CRM Online Help topic, "Install and Run the Data Migration Manager."

To work around this problem:

1. Install Data Migration Manager. Do not click Sign In yet.
2. Go to the C:\Program Files\Microsoft Dynamics CRM OnlineData Migration Manager\DMClient\ConfigWizard folder, and double-click Microsoft.Crm.DMClient.Config.exe.
3. Configure Data Migration Manager specifying the remote instance of SQL Server.
4. Execute the following procedure on the remote instance of SQL Server:

   USE [master]

   GO EXEC xp_instance_regwrite N'HKEY_LOCAL_MACHINE', N'Software\Microsoft\MSSQLServer\MSSQLServer', N'LoginMode', REG_DWORD, 2

   GO

   ALTER LOGIN sa ENABLE ;

   GO ALTER LOGIN sa WITH PASSWORD = '<password>' ;

   GO

   Replace <password> with a strong password.

5. Share a folder on the machine, on which you are running Data Migration Manager. Give full-access permissions to the user who is running Data Migration Manager. Give read permissions to 'Everyone.'
6. On the client machine, start regedit. Navigate to HKLM\SOFTWARE\Microsoft\Data Migration Wizard.
7. Define a registry key of type String named "ShareForRemoteSQL."
8. Populate this key with the name of the share created. This should be just the name of the share and nothing else. For example, if machine is mypc and share is myshare, then the UNC path for the share is \\mypc\myshare and registry key must be populated with "myshare."
9. Open the registry key "Database." Modify the connection string to:

   "Provider=SQLOLEDB;Data Source=<SQLSERVER>;Initial Catalog=MSCRM_MIGRATION;User ID=sa;Password=

   <password>;Trusted_Connection=False

   In the above statement, replace <SQLSERVER> with the the name of the instance of SQL Server and <password> with the password chosen in step 4 above.

10. Start Data Migration Manager. Click Sign In.

    Warning

Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system and Microsoft Dynamics CRM Online. We cannot guarantee that these problems can be solved. Modify the registry at your own risk.

Comma-separated values (CSV) files can contain Unicode text. However, the files cannot contain the ASCII control sequences (first 19 ASCII characters) such as:

• Null
• Line feed
• Carriage return

The most common cause of special characters is a source system that stores multiple lines of data in one attribute, and uses a line-feed or carriage-return character in the middle of the attribute. For example, your source system might store the entire address, including both the street address and city in one line, using a line feed between the street address, and city, so that it appears correctly in the source application. When this data is exported to Microsoft Office Excel or to a .csv file, the line feed is included.

Control characters typically look like small rectangles when viewed in Notepad or Microsoft Office Word, and as a question mark in a box when viewed in Excel. They are hard to remove with Excel and Word, as you cannot search for them. To thoroughly check your files, you will need to use a tool such as a hex editor to search for, and remove, control codes in the output. Hex editors are available for free download from many Web sites. In the hex editor output, look in the hexadecimal output for 0A (line feed), 0D (carriage return), and 00 (null), and remove them.

For a complete list of control codes, see ASCII Control Codes.

Microsoft Office Excel doesn't display rows with blank data, so if you look at your .csv files with Excel, you will not see empty rows at the end.

To remove empty rows at the end of a .csv file, open it in Notepad.

No. There can only be one .csv file with records for each record type.

If your record has a status of Published, it cannot be migrated. Articles must have a status value of Draft or Unapproved to be migrated. After migrating the articles, use Microsoft Dynamics CRM Online to change the status of the articles.

No. The top-level parent business unit is created automatically when you set up Microsoft Dynamics CRM Online using the name of the organization you specified during setup. When you migrate business units, you can migrate only business units that are under this top-level business unit. Multiple levels of hierarchy are possible.

Because of the timing by which Data Migration Manager creates a custom entity, it cannot migrate data to the Records Created On attribute.

To work around this limitation, create the custom entity using the Customization area of Microsoft Dynamics CRM Online, and then migrate data to the custom entity.

When the list of files is changed, the whole set of files is reparsed, and custom attribute mappings have not yet been stored.

If you change a file after you map custom attributes in a custom entity, you will need to remap the custom attributes.

You must have an ObjectTypeCode column in your .csv file, with a value of 1 if the address is related to an account record, or 2 if the address is related to a contact record.

If you do not have this column, add it to your .csv file.

The Quantity Selling option is not customizable in Microsoft Dynamics CRM Online, so if your data has customized values in this column in your .csv file, it will not be migrated.

To work around this problem, you will need to do one of the following procedures:

• Manually edit the data map for the migration to map the customized drop-down list (picklist) values in your price list items .csv file to valid Microsoft Dynamics CRM Online integer values. The three valid values are 1 (No Control), 2 (Whole), and 3 (Whole and Fractional).
• Edit your price list items .csv file and change the custom values to valid Microsoft Dynamics CRM Online values.

If a unit references another unit, you will receive an error, and the unit will not migrate.

To work around this problem, enter any Unit Group data directly into Microsoft Dynamics CRM Online before migrating unit data.

Data Migration Manager does not migrate users. The users.csv file is used to map source users to Microsoft Dynamics CRM Online users.

If a user listed in this file is not already a Microsoft Dynamics CRM Online user, Data Migration Manager will prompt you to either create the user or map the user to a different user. For each new user, you will be prompted to create the user. The following fields will be prepopulated on the New User page if you have them in your users.csv file:

• Domain Logon Name
• First Name
• Last Name

You must manually enter any other user data after you finish the migration.

There are several reasons this error might occur:

• The specified domain name for a user might be incorrect.

  Verify that the domain names are correct.

• Required columns might be missing.

  You must include the Domain Logon Name, First Name, and Last Name columns.

• If you have more users in your file than you have licenses for Microsoft Dynamics CRM Online, you will get this error message.

  You will need to reduce the number of users you are creating, or purchase additional licenses prior to migrating data.

Data Migration Manager cannot migrate data into many-to-many relationships. It can only migrate data into one-to-many or many-to-one relationships.

The Status attribute is considered a drop-down list (picklist) attribute, so you must have a <PickListMap> section in the data map for this attribute.

This mapping cannot be created in the Data Migration Manager. It must be created manually in the data map. For more information, see the help topic "Status and Status Reason Attributes."

If you have an invalid value in the Status column, you will see this error, even if the invalid value is not -1.

Look in your source data to see what value you have in this column. To determine valid Status values, see Default values of Status and Status Reason attributes.

You cannot use a transformation to populate an owner column. When Data Migration Manager maps owners, it does not search in transformation maps.

To work around this problem, edit your source data prior to migrating it so that no transformations are required for owner columns.

If a custom attribute is not created the first time you run an Express-mode migration, all data in this attribute will be ignored when you reuse the data map from this migration for another Express-mode migration.

To work around this problem, when you start Data Migration Manager using the data map, use Standard mode, so that you can specify creating a new attribute again.

Data Migration Manager uses one input for both the database logical name and the display name, therefore the database logical name must use ASCII characters.

To work around this problem, after you migrate your data, use the Customization area of Microsoft Dynamics CRM Online to change the display name.

If a column name is too long, a new custom attribute cannot be created.

To work around this problem, edit your data map to shorten attribute names to 160, or fewer, characters.

Data is migrated during the Data Upload stage of data migration. If you get to this page, click Next, and get any errors related to network problems, check in Microsoft Dynamics CRM Online to see if the records have been migrated. For example, if your migration included accounts and contacts, check in the Accounts and Contacts areas to see if the new records appear.

If they have not yet been migrated, open Data Migration Manager again, and migrate the data. If this migration is available for re-use, it will show up on the first page where you select how to start the migration.

Data Migration Manager loads customizations when it is first started, but does not check afterward. If you run a migration after making customizations in Microsoft Dynamics CRM Online, you will receive data upload errors for all rows: "An error has occurred. For more information, contact your system administrator."

To work around this, if you customize attributes or entities in Microsoft Dynamics CRM Online between migrations, always stop and restart Data Migration Manager.

If the error specifically refers to a missing relationship or state information, the record was migrated, and you should delete it, fix the error, and migrate it again. Or, you can manually update the relationship or state in Microsoft Dynamics CRM Online.

If the error does not refer to a missing relationship or state information, the record was not migrated, and you should fix the error and migrate the record again.

File names are case sensitive. In your data map, verify that the <SourceEntityName> in the <EntityMap> has the same capitalization as the file name.

If you have a value that is too long in a parameter, such as SourceName, Name, or SourceEntityName, you will receive this error. The log file will show a "Generic SQL error."

To work around this problem, shorten parameter names in the data map to 160, or fewer, characters.

The day offset must be specified in the range of -1 to 6, rather than 1 to 8.

Change the day offset in the transformation mapping.

If you have more than one mapping for a source column, and one of those mappings includes transformation mapping, you need to open the data map and review the XML.

Data Migration Manager stores all the migrated data in the MSCRM_Migration database on the server on which Data Migration Manager is installed.

After you have established that the data is correct in Microsoft Dynamics CRM Online, you might want to delete the migration data on the local computer to save disk space, and for data security.

Do not delete a migration, locally, if you want to later delete it from the Microsoft Dynamics CRM Online server. The migration must still exist on the local computer to delete the migrated records from the server.

If Data Migration Manager is able to run a bulk-deletion job on the Microsoft Dynamics CRM Online server, and that job is complete, it reports back to Data Migration Manager that the deletion has a status of Completed. However, if the bulk-deletion job finishes with errors, Data Migration Manager still reports that the job was complete.

To ensure that all data has been deleted, check the status of the bulk-deletion job on the Microsoft Dynamics CRM Online server. To do this, click Settings, click Data Management, and then click Bulk Record Deletion.

Yes, when you use Data Migration Manager to delete migrated data, all migrated records are deleted, even if a record has been changed after you migrated the data.

If the migration created a custom Microsoft Dynamics CRM Online entity, and if this entity has been deleted from Microsoft Dynamics CRM Online, you will get this error when you try to delete the migrated records by using Data Migration Manager. Note that the status of the bulk-deletion job will show up as Completed, even though the data cannot be deleted.

To work around this problem, delete the migrated records in Microsoft Dynamics CRM Online rather than by using Data Migration Manager.

Bulk Deletion Completed: the job is complete. Completed: the job no longer exists on the server.

You can turn on tracing on the computer running Data Migration Manager.

To turn on trace on the computer running Data Migration Manager, in the registry, change the value of the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Data Migration Wizard\TraceEnabled registry key to 1. The trace log will be stored in the c:\Documents and Settings\user_profile\Application Data\Microsoft\MSCRM\Traces folder.

Remember to turn off tracing after you have determined the problem, as trace logs can fill up your hard disk.

Trace logs are large, and if you leave tracing on, your disk will be filled up with the logs. If the disk is full, you will get this error message.

To fix this problem, turn off tracing, and remove any unneeded trace-log files.To turn off tracing on the computer running Data Migration Manager, in the registry, change the value of the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Data Migration Wizard\TraceEnabled registry key to 0.

Warning

Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system and Microsoft Dynamics CRM Online. We cannot guarantee that these problems can be solved. Modify the registry at your own risk.