macro signature revoked or expired

[Lil Miss Norti]

this message appears whenever I open Microsoft Word. We have had this issue
before and I was able to rectify it by searching through the newsgroups on
Microsoft.com hwoever I cannot seem to find it this time.

Can someone please help me, it's driving me mad!!

 

[Jay Freedman]

On Tue, 7 Dec 2004 16:25:08 -0800, "Lil Miss Norti" <Lil Miss

this message appears whenever I open Microsoft Word. We have had this issue
before and I was able to rectify it by searching through the newsgroups on
Microsoft.com hwoever I cannot seem to find it this time.

Can someone please help me, it's driving me mad!!

It sounds like a variation of the "Compile Error in Hidden Module"
problem caused by a bad add-in, described in section 4 of
http://www.word.mvps.org/FAQs/AppErrors/ProbsOpeningWord.htm. The
procedure for removing it should be the same.

 

[Lil Miss Norti]

Jay,

Thanks for your prompt reply however this information does not seem like the
correct course of action that was taken last time this occured.

When I start work I get the signature revoked or expired message and it also
says that because we run at the High Security level, macros will be disabled.
When you click 'ok' it then says 'The macros in the project are disabled,
please refer to the online help documentation on how to enable macros.' This
error is repeated when you close the application as well.

It seems to only be affecting Word at the moment, but it is still rather
annoying to say the least.

Is there any other way you could assist me?

Regards,
Lil Miss Norti

 

[Suzanne S. Barnhill]

This is almost certainly coming from an add-in. If you change your macro
security to Medium, you will get a message allowing you to enable the macros
and perhaps trust the author. At least you'll get some information on what
add-in the message is coming from. Alternatively, you can try removing each
add-in in turn till you find out which one is causing the problem.

 

[Lil Miss Norti]

Thank you Suzanne for your reply, however all but the first suggestion are
not able to be implemented. These errors occur if i'm opening Microsoft Word
with a new document or existing one and there's not option to 'trust the
author'. Other than reducing our macro security level there seems to be no
solution.

I distinctly remember that this was a problem that we rectified on another
machine some time ago shortly after changing to XP and Office 2003. However
I cannot seem to find the exact procedure in which to fix it.

 

[Suzanne S. Barnhill]

Add-ins load whenever you start Word, no matter how you start it. If you
change your macro security, you will have the option to enable the macros
the *next* time you start Word. You *must* reduce macro security to Medium
to be given this option. There is no danger in reducing macro security to
Medium provided you choose not to enable macros you do not trust. You can
also cut down on a lot of messages by checking the box for "Trust all
installed templates and add-ins" on the Trusted Sources tab of Tools | Macro
| Security. This will cover all templates and add-ins in Word's user
templates, workgroup templates, and Startup folders; unfortunately, this
trust does not extend to the Office Startup folder, where some add-ins are
saved.

I would strongly recommend that instead of trying to remember how you solved
this problem in the past, you consider the suggestions given to you with
regard to proven ways of solving the problem in the present.