Normal.dot Permissions Issue

[Chris]

I have a terminal server on a w2k3 server with Office Professional 2k3. I am
having an issue with normal.dot that I cannot seem to fix. When a domain user
attempts to use word you periodically get this error " Word cannot open the
existing (Normal.dot). It appears to happen at random and I cannot pin down
what the cause might be. I have done everything I could find out there to
correct this but it keeps coming back. I have deleted the template, the data
files, the reg keys uninstalled and reinstalled (through add and remove).
Someone on another board suggested that it's a permissions issue and
suggested that I post the question here. I have logged on as the local admin
and did not receive the error and quickly logged off and on as a domain admin
and the error was present. This is why the poster on the other board
suggested that it be a permissions issue.

Thanks for any suggestions.
Chris

 

[Jeremy]

I'm not too sure on this one, but check to make sure there isn't an orphined
normal.dot file in the users templates. Make sure the user doesn't have
another session open with word or outlook open. I read somewhere that someone
fixed this problem by doing a chkdsk /r becuase word was trying to write the
normal.dot to a bad sector fo the hard drive.
Good Luck,
Jeremy

"Chris" wrote:

> I have a terminal server on a w2k3 server with Office Professional 2k3. I am
> having an issue with normal.dot that I cannot seem to fix. When a domain user
> attempts to use word you periodically get this error " Word cannot open the
> existing (Normal.dot). It appears to happen at random and I cannot pin down
> what the cause might be. I have done everything I could find out there to
> correct this but it keeps coming back. I have deleted the template, the data
> files, the reg keys uninstalled and reinstalled (through add and remove).
> Someone on another board suggested that it's a permissions issue and
> suggested that I post the question here. I have logged on as the local admin
> and did not receive the error and quickly logged off and on as a domain admin
> and the error was present. This is why the poster on the other board
> suggested that it be a permissions issue.
>
> Thanks for any suggestions.
> Chris