could not open macro storage

[makkinje.ingrid]

Hello all,
I have created a template in MS Word with VBA macros and installed this
on several PCs.
These macros did not cause any problem for three months, but now on one
of the PCs it gives error messages:
for example: nr 5981Could not open macro storage.

The debugger stopped (stops) at several lines in the code, for example
Application.UserAddress = "Company name" & Chr(13) & _

I have changed this to
Application.UserAddress = "Company name" & vbNewLine &_


After changing this, the debugger does not stop at this line anymore
but stops at a next line:
ActiveDocument.Envelope.DefaultSize = "DL"

This code does not cause any problem on the other machines that have
these macros installed and also not when logging on as a different user
on the same PC as where the problem appears.

I have tried the recommendations from KB from Microsoft:
1. Renaming the normal.dot
2. Increasing hard disk space
3. For reinstalling or repairing the VBE6.dll, I have created a new
user profile for that specific user, did not help. I have removed and
reinstalled MS Office, did not help.


Hope someone can help me
Ingrid

 

[Jezebel]

The message means that the template is corrupt. Discard it and re-install a
good copy.

 

[makkinje.ingrid]

I did that but it did not help. And I don't think the template is
corrupt, because when a different user on that same PC creates a
document based on this template there is no problem.



Jezebel schreef:

 

[Russ]

5981 Could not open macro storage.
Message below.

I did that but it did not help. And I don't think the template is
corrupt, because when a different user on that same PC creates a
document based on this template there is no problem.



Jezebel schreef:

One possible reason for that error message:

I would also get this message when I logged onto a computer that I did not
have high enough permissions to actually own any new documents that I tried
to create and run macros on. You'll get that message with a document, if
when you go into the Visual Basic Editor and look at the "This Document"
properties pane and not be able to change the "UserControl" property from
"False" to "True" by double-clicking on the "False" word. Then you don't
have "ownership" of the document.

A file brought from another computer might work for me, if at the time it
was created it's creator had high enough permissions, but no new documents
create by me would work until I had higher permissions on that particular
computer or obtained a "Roaming" versus "Local" high-permission password for
that particular network. Talk to your IT Administrator for a possible
solution.