Error message since installing Pub 2k3 in XP system

[Colonel Blip]

Here is an original message posted in the directaccess newsgroup for
Publisher. They've sent me here for help.

"I keep getting the following message when I open any of my templates in
Pub2k3. It generally takes a few minutes before the message pops up.

"You have modified a signed project. You do not have the correct key to sign
this project. The signature will be discarded"

I click ok, and then get:

"The VBA project could not be digitally signed because the certificate is
invalid. The digital signature was removed."

I've not done anything to change anything in the template. I do have vba
code I created in it.

This problem started after I installed xp pro and reinstalled publisher.
I've run selfcert to create a certificate but that didn't help. Ideas?"

As an experiment I deleted all of the code and the message disappeared. They
said I need to change the VBA code, which doesn't 'compute' with me, yet.
Here is my reply:

"I'm missing something here. The following are facts:

I've been using Pub 2k3 since it released.
I've been using these very same codes in it since it released; no changes
made to the code.
I've been using the same certificates since I installed Pub 2k3 and began
using it
I've run it successfully with this arrangement under w2k and no messages
Now I get the messages and the only change made is it is running under XP
Pro.
I do not understand why I need to change the code? Is there some code that
works under w2k that doesn't under XP. If so, it is first I've heard of it."

Maybe I need to change code but first I've heard of such a thing wth any of
my office 2k3 apps.

Anyone here know what is causing this problem and how to fix it? I can post
the code that has worked for a year if that helps.

 

[Ed Bennett]

This problem started after I installed xp pro and reinstalled
publisher. I've run selfcert to create a certificate but that didn't
help. Ideas?"

I'm almost the only regular round these parts who has experience with Pub
VBA (feel free to jump in if you feel I'm excluding you), and I have not
done any certification of any projects - so I'm kind of shooting in the dark
here!

Do you have the old certificate/key that you had on the previous
installation?

Are you able to re-certify the project with a new certificate/key from
SelfCert?

Are you able to remove the signing altogether and start over?

This problem appears not to be related to your code, but rather the code
signing that you used on it, so modifying your code to work with Windows XP
is not the issue.

I think making modifications to your code was recommended so that Publisher
might be able to re-certify the project with a new certificate.