Export (0) Print
Expand All

ClearQuest Migration Report Messages

The ClearQuest Migration Report has an Errors section and a Warnings section. A Critical Error section is added if a fatal error stops migration or analysis. The report file is generated when you analyze a ClearQuest database, and when you migrate a ClearQuest database. The report file is created in the same folder from where the converter is run. This topic explains the messages that appear in these sections. For more information about how to troubleshoot the errors listed, see Troubleshooting ClearQuest Converter.

Summary

The summary section lists details about the command that was just run; analyze or migrate. Details include whether the command succeeded, how many errors occurred, how many work items were migrated, and other information. If problems occur, review this section to make sure that the converter was running as expected. For example, verify that the identified Team Foundation Server is correct.

Critical Error

If analysis or migration is interrupted by a critical error, this section is included in the report and provides a description of the error that caused analysis or migration to fail. For more information, see ClearQuest Critical Migration Errors.

Errors

If you have errors during analysis, it means that you will not be able to successfully migrate any work items. If you have errors during migration, it means that some work items were not migrated.

Non-critical errors do not stop the migration process. The converter will continue to run and some work items will not migrate successfully. The IDs of work items that were not migrated successfully are listed in this error section. The work items that did get migrated successfully are usable. You could choose to ignore the work items that were not migrated and start using the migrated work items.

For more information, see ClearQuest Migration Errors.

Warnings

This section contains information about the loss of information or modification of information because data in ClearQuest cannot be migrated to Team Foundation for a known reason. During analysis, the converter warns about this potential loss of information. Sometimes, you can either take some action to prevent the information loss, or you can choose to accept the information loss and run the converter anyway.

Each warning message gives a brief description of the issues that were found during migration or analysis, and contains a link to a document that contains details about the warning.

Data Loss Warnings

The following list shows the data loss warnings that the converter may experience during migration or analysis:

  • Skipping link creation for work item '{0}' as duplicate of work item type '{1}', which is not in the migration list.

    This means that the linked work item was not migrated because it was of a work item type which is not under migration. The result is that you would not see the linked work item in Team Foundation Server. The migrated work item is still usable.

  • Changing field '{0}' attribute from Read-only to Editable.

    The read-only attribute of a field was changed to editable. You may want to reset the read-only property after migration. To do that you will have to modify the work item type and use the witimport utility to import the work item type into Team Foundation Server. For more information, see witimport.

  • Not migrating the Hooks behavior for Field '{0}'.

    Hooks are not supported by Team Foundation Server. There is no work around. This is a limitation of the converter.

  • Unable to resolve following user names: {0}.

    During migration, the converter tries to resolve the display names of the user aliases present in user fields in your ClearQuest database. Some of the aliases may not be valid user accounts in Windows. This causes the display name resolution to fail. This warning is informational and no corrective action is required.

  • Entity '{0}' will not be converted as it is not connected with the base entity '{1}'.

    The converter migrates a base entity, the entity on which you based your migration query, and other entities to which the base entity refers. It does not migrate any other entity. This warning typically occurs when you modify the schema map file to include some additional work item types for migration. Instead of trying to migrate all work items at the same time, you should schedule different converter runs to migrate unrelated work item types.

  • The work item '{0}' of type '{1}' contains a reference to itself in field '{2}'. Team Foundation does not support relating a work item to itself.

    Team Foundation does not support self-reference. This warning indicates that the converter detected a case of self-reference in ClearQuest and that it could not migrate that work item. There is no work around. This is a limitation of the converter.

  • Using: '{0}' instead of: '{1}' for: '{2}'.

    The default value for a field was used instead of the value read from the ClearQuest database. This occurs only when the value read from ClearQuest is not acceptable in Team Foundation. For more information about default values, see Field Map Files, Value Map, and Default Values.

  • Work item '{0}' is already migrated.

    This warning is informational and no action is necessary. This warning typically occurs when you restart the converter after fixing a problem. The converter does not re-migrate work items.

  • Work item type '{0}' cannot be created because it already exists on your Team Foundation Server.

    The converter creates a work item type on Team Foundation Server only when the type does not already exist on Team Foundation Server. If you want to use the work item type that already exists on Team Foundation Server, you can safely ignore this warning. If you want to use a different work item type, you must use the witimport utility to import the new work item type. For more information, see witimport.

  • The '{0}' field is of the type 'User List'. The converter is converting it to a 'Simple String' field because Team Foundation does not support multi-value fields.

    Multi-value fields are not supported in Team Foundation. To migrate these fields, the converter changes each instance of the multi-value field into a comma separated list.

Other Warnings

The following is another warning that the converter may experience during migration or analysis:

  • Cannot edit field '{0}' as is a internal core field in Team Foundation work item tracking system.

    This warning indicates that you are using an internal Team Foundation Server field in the mapping file, but that the core field cannot be modified by the converter. The result is that Team Foundation Server defined rules would set the field value instead of the values the converter tries to set based on the values in ClearQuest. An example is the Changed Date field. Changed Date is always set by Team Foundation Server to the date when a particular change occurs regardless of what values the converter specifies.

See Also

Community Additions

ADD
Show:
© 2014 Microsoft