Run-time Error 5981 "could not open macro storage"

[lkthompson]

One of my coworkers recently started getting these errors when opening a Word
document, and she doesn't remember changing any settings. She still has
Office 2002 and I checked the macro security settings - they are low. I also
made sure the Trust all add-ins,etc was checked. I'm thinking it might be a
corrupt template, but there's about 8 different macros listed and I don't
want to mess up her defaults and other settings. Is there a way to get rid of
those error messages?

Thanks.

 

[Jezebel]

A document (or template) has two main parts: the text part and the macro
part. The message means that there's some sort of corruption in the macro
part. of a template or add-in. Unfortunately it doesn't tell you which
template or add-in, so you'll have to investigate them individually (but
it's usually normal.dot).

 

[Russ]

Lkthompson,
See Below.

A document (or template) has two main parts: the text part and the macro
part. The message means that there's some sort of corruption in the macro
part. of a template or add-in. Unfortunately it doesn't tell you which
template or add-in, so you'll have to investigate them individually (but
it's usually normal.dot).

Does she still get the same error when she tries to record a macro of her
own? I once got these errors when I logged into a computer with a password
that didn't have high enough security like a Administrator or Power User. Is
this a new terminal that she is using, that she logs into? When my password
security level policy was bumped up, I could start recording my own macros
without that error message popping up.

 

[lkthompson]

Thanks so much, both of you. She actually doesn't record her own macros. but
we got it figured out by calling our company's Help Desk.

 

[Russ]

Lkthompson,
You would be helping others, if you would post what the solution to her
problem was. It might be specific to her situation, but others may
experience the same situation.

 

[lkthompson]

Sorry for the delay in replying..I couldn't log on to this site in awhile.
I'm not sure if this will help everyone though, because we have a
webinstallxp download site that is only available on our intranet. It is
webinstallxp.companyname.com. But anyway, you need to uninstall the "Document
Sensitivity Labeler" and then reinstall it. The Help Desk person said that
the macro codes might not have copied correctly during the upgrade, but this
corrects it and fixes the error. We have never seen the error again after
doing this.