NameMapping fie got corrupt

I have also faced the same issue.

and could not get any resolution.. :(

that is sad :(, anyways thanks Prachi

Hi Ali,



To help us investigate the problem, please send us the target .tcNM file.

Thanks Lexi,

have done that.

Hi Lexi,

Got the id of my request M0089350 from your support team.

I like to mention what i have done before NameMapping file got corrupt.

I have deleted some redundant/non required mapped objects and mapped some new objects.

Then checked the NameMapping file to CVS.

Hi Ali,



Thank you for the details. We've received your message. Currently, we are investigating the situation. Let's continue our conversation via e-mail.

Hi,



This problem has been resolved through Support. Since other users may face the same problem, I will post the results here:



The .tcNM file can be corrupted if its encoding was changed. In Ali's particular case, the target .tcNM file has been saved in the Unicode format when the file has been checked in to CVS, and the file became unreadable for TestComplete. To avoid this kind of problem, please make sure that the encoding stays unchanged.



To be sure that the encoding is OK, check whether the .tcNM file encoding is the same as specified in the file itself. You need to check the following line in the .tcNM file:



<?xml version="1.0" encoding="UTF-8" standalone="no"?>

I had same problem and here is repsonse and solution from SmartBear :

The cause of the problem is that the characters from the
second part of the ASCII table in Name Mapping properties corrupt the Name
Mapping file when migrating to TestComplete 9.

 

To get rid of the problem, our developers gave me the
steps below and I followed them to restore your Name Mapping file:

1. Open the Name Mapping file via Notepad (I used
Notepad++ - you can find it here: http://notepad-plus-plus.org/).

2. Find the following string: "Error: get
property" (without quotes).

3. Delete all characters after the "Error: get
property" string and before "/>.

4. Repeat steps 2 and 3 until you replace all wrong
characters.

 

So, if you face the same problem again, please follow the
steps above.