Macro Expired (Word 2003)

Topic

New Reply

Sure as anything I am going to leave something out of this post but please forgive me.
Yesterday I went into word 2003 and received a dialog box that Macros had expired, I changed the security level down to medium and was able to identify the culprits, Each one coming up as an individual file. These were namely Click Books cb.dot and WOPR 2003 wopr_ui.dot. If I remove everything from the C:Program FilesMicrosoft OfficeOFFICE11STARTUP folder word starts perfectly.
I have read Microsoft’s kb822645 and am totally unsure as to what to do, what appeals most is to reset word to default settings (towards the end of the article), I reinstalled ClickBook but no positives from that action, I have also downloaded the latest version of cb.dot but no fix.
I have deleted normal.dot again no happiness, an opinion would be appreciated.

Reply | Quote

Replies

The problem is caused by add-ins, not by Normal.dot, so there’s no need to delete Normal.dot.
The makers of add-ins often “sign” their macros with a digital certificate; if you indicate once that you trust the certificate, you can run the macros without being prompted, and even if macro security is set to High.

For security (and commercial) reasons, digital certificates expire after a while, and this causes your problems.
The WOPR utilities aren’t being updated any more, so you won’t get a new version, and you won’t be able to run the old version under High security any more.
The Blue Squirrel Knowledge Base claims that ClickBook 11 has been signed with a new certificate; the certificate for ClickBook 10 and before has expired and won’t be renewed.

Reply | Quote

Thanks Hansv,
The trouble is I do not get the choice to say I accept approve the Macro, the attached graphic is from security set to medium.
If I approve to run I have to do it every time I run word

Reply | Quote

I’m afraid that you’re stuck with having to enable macros every time you start Word if you want to keep on using the WOPR utilities. The alternative would be to set macro security to Low. This is not recommended by Microsoft, on the other hand I haven’t heard about macro viruses for a long time now…

Reply | Quote

The answer you gave for post 742521 works like a treat for me, thanks again.
Ted

Reply | Quote