error 5981 (macro storage) on TS

[tiny68]

Have just configured a windows 2000 server as a terminal server and hav
word97 running successfully on all clients. Error occurs when trying t
execute a macro under user privledges. Under admin privledges the macr
runs fine. The macro once worked under user privledges before the serve
upgrade so its not that the macro doesnt support user access.

So far I have tried renaming normal.dot, re-registering vbe.dll, loggi
everyone on under admin then off again, running winword.exe /r an
nothing...

any help would be greatly appreciated :

 

[Uniqa]

Hi tiny68,

have you checked (when logged in as a user) if the references set in the
macro file are all OK? (Open *.dot - Open VBE Editor [ALT]+[F11] - Under
Tools select References).
Maybe there is a reference to another macro file, ocx, dll .... to which
access is denied for normal users.

Hope this helps!

 

[tiny68]

I get the same error when I attempt to open the VB editor and then onc
it opens I get "project unavailable" when I click on any of the thre
macros present. Tools-references is greayed out too.

But it was something I hadnt tried :

 

[tiny68]

Im an idiot! I could copy those macros to a less complicated environmen
and do this... oh but then if vb editor doesnt start its probably
problem with vb and not the macro...

hmmmm... perplexing..

 

[Uniqa]

It appears to me that you just started MS Word and not actually opened the
macro file (the *.dot file(s) in the word startup directory)? That's when you
normally would get the "project unavailable" message. If not..... than this
is only getting weirder ;-)
Maybe there are some AutoExec macro's which could cause the problem?

 

[JB]

Im an idiot! I could copy those macros to a less complicated environment
and do this... oh but then if vb editor doesnt start its probably a
problem with vb and not the macro...

hmmmm... perplexing...

Where have you stored the macros? Is this a place where normal users
have folder access rights? Maybe the macros are trying to store the
WRL###.TMP file somewhere they have no access to?

J