Runtime error on Comparing Project Versions

[EmiW]

I just loaded MS Project Standard 2003, SP2 on my computer. Previously, I'd
been using Project Standard 2003 SP1, without any issues.

Now, when I launch the compare feature, it starts to run and then I get an
error "Runtime error 1101, The value is not valid". I click ok and get
another error, "Runtime error 440: Automation error". I click ok and it says
"An error occurred in the COM Add-in named: Compare Project Versions, error
#440; Automation error; Please restart Project to restart the COM add-in."

I've restarted, but I get the same errors.

I'd appreciate any help/insight anyone can provide.

Thanks,
Emi

 

[John]

I just loaded MS Project Standard 2003, SP2 on my computer. Previously, I'd
been using Project Standard 2003 SP1, without any issues.

Now, when I launch the compare feature, it starts to run and then I get an
error "Runtime error 1101, The value is not valid". I click ok and get
another error, "Runtime error 440: Automation error". I click ok and it says
"An error occurred in the COM Add-in named: Compare Project Versions, error
#440; Automation error; Please restart Project to restart the COM add-in."

I've restarted, but I get the same errors.

I'd appreciate any help/insight anyone can provide.

Thanks,
Emi

EmiW,
It's been a while since I played with the compare utility. Your issue
has been raised a few times over the last couple of years and at one
time I listed several things to be aware of when using that utility. I
can put a finger on that list now, but you might like to try a search on
this newsgroup using the search words "Compare" and look for "John" as
the author. Perhaps there will be some helpful hints in those postings.

If nothing there helps, post back and we will see what else can be done.

John
Project MVP

 

[EmiW]

Thanks, John.

I searched the earlier posts, but didn't find anything that worked.

I have fooled around with it more and have determined that the error is
specific to the files I'm comparing (so it's not a global MS Project SP2
issue for me. I can compare other files, and I did a test and compared newly
created files).

The 'bad' file in question is a 600+ task project that I cut/pasted from
other files to create. I went back to the original file (that I first created
from cutting/pasting from other sources) and I see that there's a problem
from the get go. Short of retyping from scratch (gasp!) the entire thing, any
suggestions for debugging the potentially corrupt file?

Appreciate any suggestions.

Emi

 

[John]

Thanks, John.

I searched the earlier posts, but didn't find anything that worked.

I have fooled around with it more and have determined that the error is
specific to the files I'm comparing (so it's not a global MS Project SP2
issue for me. I can compare other files, and I did a test and compared newly
created files).

The 'bad' file in question is a 600+ task project that I cut/pasted from
other files to create. I went back to the original file (that I first created
from cutting/pasting from other sources) and I see that there's a problem
from the get go. Short of retyping from scratch (gasp!) the entire thing, any
suggestions for debugging the potentially corrupt file?

Appreciate any suggestions.

Emi

Emi,
The way the compare utility works is by indexing through the Unique IDs
of both files. That means both files must be of the same origin. You
mention that you created the file using copy & paste from other files.
OK, that's one file, the compare utility requires two files. Where did
the other file come from?

It is possible the file is corrupt but what makes you think so? There
are ways to clear corruption from a Project file, but those methods may
not preserve the Unique ID, therefore rendering the compare utility
useless.

What are you really trying to accomplish? In other words, what is your
end goal? Maybe there are other ways to get there.

John
Project MVP

 

[EmiW]

Hi John,
I created the original file in August. Since then, each week I make changes
to some tasks, changing percent complete, or due dates, etc, and I "save as"
and make a new version each week.

What I wanted to do was compare one of the earlier versions to one of the
later versions using the compare feature, and am getting the errors I
mentioned earlier. I know there might be other ways to see changes, but I am
wondering why this isn't working. (I have other files that I change monthly,
and I am able to do the compare with them and it works.)

Thanks,
Emi

 

[John]

Hi John,
I created the original file in August. Since then, each week I make changes
to some tasks, changing percent complete, or due dates, etc, and I "save as"
and make a new version each week.

What I wanted to do was compare one of the earlier versions to one of the
later versions using the compare feature, and am getting the errors I
mentioned earlier. I know there might be other ways to see changes, but I am
wondering why this isn't working. (I have other files that I change monthly,
and I am able to do the compare with them and it works.)

Thanks,
Emi

EmiW,
OK, so it sounds like the files you are trying to compare do indeed have
the same heritage (i.e. same source), so the compare utility should
work. For this type of problem it is a little difficult to find out what
may be happening without actually having the files to test. If you are
willing to e-mail them to me, when I get some time I can run some tests.
If you send the files, send the original and any of the later versions.
Also tell me exactly which fields you want to compare. My e-mail is
below.

John
Project MVP
jensenj6atatcomcastdotdotnet
(remove obvious redundancies)