Missing Reference

[consul]

I'm stuck with a weird problem at the moment. I have a bunch of Word templates which have
references to another common template located on a network share.
The reference is set up using UNC notation, like \\server\path\to\folder\mycommontemplate.dot
All worked fine with this setup for years, but about a week ago one user got a problem.
When he opens any template containing a reference to the mycommontemplate.dot, he gets "Can't access macro storage" error.
He can't add a reference to the template from any new documents either.
He can open the mycommontemplate.dot directly with no problem.
If I copy the mycommontemplate into the same folder as the original, he can add the reference to the copy, but not the original template.
He does not have any problems opening other templates referring to this copy.

So it seems like he has a corrupted copy of the mycommontemplate somewhere, but I can't find traces of this corrupted copy.
I cleared all user's temp files I could find and checked that there is no mycommontemplate in the Word's search path
(Tools/Options/File Locations), but the problem still persists.

Does anybody has a clue what to check next?

System info:
Windows XP with all service packs
Word 2003 (11.8227.8221) SP3
The user does not have admin rights to his workstation
The user has read only rights to the network folder where the templates are.

 

[That Guy]

I'm stuck with a weird problem at the moment. I have a bunch of Word templates which have
references to another common template located on a network share.
The reference is set up using UNC notation, like \\server\path\to\folder\mycommontemplate.dot
All worked fine with this setup for years, but about a week ago one user got a problem.
When he opens any template containing a reference to the mycommontemplate..dot, he gets "Can't access macro storage" error.
He can't add a reference to the template from any new documents either.
He can open the mycommontemplate.dot directly with no problem.
If I copy the mycommontemplate into the same folder as the original, he can add the reference to the copy, but not the original template.
He does not have any problems opening other templates referring to this copy.

So it seems like he has a corrupted copy of the mycommontemplate somewhere, but I can't find traces of this corrupted copy.
I cleared all user's temp files I could find and checked that there is nomycommontemplate in the Word's search path
(Tools/Options/File Locations), but the problem still persists.

Does anybody has a clue what to check next?

System info:
Windows XP with all service packs
Word 2003 (11.8227.8221) SP3
The user does not have admin rights to his workstation
The user has read only rights to the network folder where the templates are.

This is a wild guess, but if the user has read only rights to the
drive and the template is not read only, then the macro would not have
the rights when launched by him to use the network drive and affect
changes to itself.

So while it runs by default in debug mode where it can make changes it
could not save them. I ran into a similar problem before and making
the template read-only solved it for me.

good luck.

 

[consul]

This is a wild guess, but if the user has read only rights to the
drive and the template is not read only, then the macro would not have
the rights when launched by him to use the network drive and affect
changes to itself.

So while it runs by default in debug mode where it can make changes it
could not save them. I ran into a similar problem before and making
the template read-only solved it for me.

good luck.

I don't think this is the case. The templates are stored in a read only location, but the resulting documents not.
The macro code is digitally signed and no self-modifying changes are allowed. And only one user is affected.
The weird thing is that when I open the reference dialog I see "MISSING: my_correct_vba_project_name_here" with the correct path
to the mycommontemplate.dot! As I said, the user can open the common template directly, but for referencing templates
it is invisible.