The following are examples of error messages you might find in the log file. Specific details may differ for your designs/diffs but you can apply these to troubleshooting concepts for your specific scenarios.

•Error message:

FATAL - ImExCustomLookupTables.import: caused exception importing custom lookup table=LOOK1UP.xml com.mitratech.teamconnect.foundation.TCException: Cannot delete YDetailLookupItem because it still has 4 EProjDetailObjeValues referencing it

a.To locate the corresponding *.XML source file, from your diff path, navigate to:

diff\Lookup Tables\Custom\LOOK1UP.xml

where diff is the path to the diff

If the issue were in a system lookup table, you could find the *.XML file in diff\Lookup Tables\System\LOOK1UP.xml

b.If you open the source *.XML file, the first line should end like:

"opcode="delete"

This is the command that tries to delete lookup table items.

c.It is recommended to rename the *.XML file (like *.XML.old) so the DMT will skip the file during import but you can later track changes that might need to be made manually.

•Error message:

FATAL - ImExCategory.import: exception unmarshalling.Please enter a unique name.

com.mitratech.teamconnect.foundation.TCException: Please enter a unique name.

a.To locate the corresponding *.XML source file, look in the dmt.log file at the events just above (before) the FATAL message. A sample excerpt follows:

DEBUG - ImExCategory.importCategory: key=OTHE

DEBUG - ImExCategory.importCategory: itemKey=PR01_OTHE, opCode=insert

DEBUG - ImExCategory.importCategory: inserting category for itemKey=PR01_OTHE, parent=PR01

DEBUG - ImExCategory.importCategory: inserting category for itemName=OTHER, key=OTHE, order=0

b.The first four characters of the itemKey, PRO1_OTHE, or PRO1, indicates the object for which a duplicate category was found.

c.From your diff path, navigate to:

diff\Object Definitions\PRO1\categories.xml

where diff is the path to the diff

d.Open the categories.xml file and search for "PR01_OTHE"

For example, the context could look like:

<Category displayOrder="" name="Other" treePosition="PR01_OTHE" isActive="true" opcode="insert" />

e.Generally you must verify that you do not create a category that already exists in the target instance. It is recommended to comment out the corresponding line from the categories.xml file so DMT will skip insertion of the duplicate category.

•Error message:

FATAL - ImExCustomFields.import: caused exception for filename=PR01_0112.xml

com.mitratech.teamconnect.foundation.TCException: Cannot delete Detail Field because it still has 1 EProjDetailTextValue referencing it

a.To locate the corresponding *.XML source file, from your diff path, navigate to:

diff\Object Definitions\PRO1\Custom Fields\PR01_0112.xml

where diff is the path to the diff

b.If you open the source *.XML file, the first line should end like:

opcode="delete"

This is the command that tries to delete the detail field.

c.It is recommended to rename the *.XML file like *.XML.old so the DMT will skip the file during import but you can track changes that might need to be made manually.