Error loading line #31 (while dereferencing <GUID>)

Dre' · Post by **Dre'** » Mon Jul 13, 2009 3:43 am

I am getting this error intermittently on multiple install scripts, and it is driving me crazy! First time I succeeded in getting rid of it by renaming the backup of the .mpr file, but then the next project also wouldn't open, which is in a totally different folder. This time however, my quick fix won't work.....

Basically I'm stumped by the message because it does not provide enough info to deal with it:

Line number would be much more helpful when combined with a filename.

Listing possible causes, or advised ways to proceed would be helpful too.

For the exact GUID, see the screenshot. I'm hoping anyone more knowledgeable has an insight to share.

Thanks in advance,

Dre'

File Attached:

errror.jpg

MichaelNesmith · Post by **MichaelNesmith** » Mon Jul 13, 2009 5:25 am

This is very serious script corruption - causes could be varied, such as failing hard disks, OS crashes, manual manipulation of script files, or source control file merges.

Dre' · Post by **Dre'** » Mon Jul 13, 2009 5:31 am

I'll check the disks then, because the only thing I did to the scripts was to store them in one session, then check them into WinCVS, later take them out of WinCVS again, and attempt to open them. Are you aware of any conflict between WinCVS and InstallAware?

I'll let you know about the CHKDSK......

Dre' · Post by **Dre'** » Mon Jul 13, 2009 5:40 am

Checked both partitions of the disk, but none reported any error.

Is there any document that might give me some insight into the structure of the InstallAware sourcefiles, so I may attempt a recovery in a more knowledgeable manner?

Thanks for the help so far, it does give me new ideas.

Dré

MichaelNesmith · Post by **MichaelNesmith** » Mon Jul 13, 2009 5:44 am

If you do a merge in ANY source control system, unless that source control system is VERY smart, it will probably corrupt your script files. The only fix is to roll back to an older, uncorrupted version.

BTW: Once a script becomes corrupt like this, we do not have automated or manual tools to revive it. Do not merge using automated tools that don't know what they're doing.

Dre' · Post by **Dre'** » Mon Jul 13, 2009 5:50 am

Thanks for the clear answer, albeit a little late. But don't worry, I probably have myself to blame, for failing to RTFM..... (It is in the manual, is it?)

Thanks for the quick reply anyway.

Dré

Dre' · Post by **Dre'** » Mon Jul 13, 2009 6:10 am

And thanks for the tip of retrieving an older version.
I managed to rescue almost everything......