Office 2000 permission/rights issues, office programs close

[Guest]

I'm running Office 2000 on a Windows 2003 Terminal Server. I have 3 terminal
servers and they're all running the same configuration... They're all in the
same domain and they're all domain controllers. I'm using mandatory profiles.

1 of them has a lot of trouble with using Office programs. For example,
when users log in and they open Microsoft Word and start typing "Dear xxx,",
the program closes. if you type the comma anywhere else in the document,
it's fine...just if you use it at the beginning it crashes. in Microsoft
Excel, if you try to put a chart in, it crashes. I did install office using
the Office resource kit .MST file.

Also, if you click on File in the upper left, it opens up very slowly.
Everything works ok if you login as admin. Also, the other 2 servers have
the same configuration but are not experiencing the same issues. All the
Windows updates have been done including Office updates. I've tried to
uninstall / reinstall Office and the same problem. I've tried to change the
profile to non-mandatory and no luck.

One of the other servers that works ok for the most part, comes up with this
"Symantec Fax "error returned code from CreateNamePipe=231" ".
I ran MSCONFIG and disabled it from starting up but after I did that, all
the users are getting that message "You have changed the
configuration....blah blah blah" when they login. You can click in the box
that says "Don't show this to me again" but it still comes up every time you
login.

Here's some of the errors from event viewer:
4/8/2005 9:47:58 AM Application Error Error None 1001 N/A GSDT2 Fault bucket
70938867
4/8/2005 9:47:55 AM Application
Error Information (100) 1004 N/A GSDT2 Reporting queued error: faulting
application WINWORD.EXE, version 9.0.0.8216, faulting module MSO9.DLL,
version 9.0.0.6926, fault address 0x0026297c.
4/8/2005 9:47:54 AM Application Error Error None 1001 N/A GSDT2 Fault bucket
123592225.
4/8/2005 9:47:52 AM Application
Error Information (100) 1004 N/A GSDT2 Reporting queued error: faulting
application PlasmaCAM.exe, version 0.0.0.0, faulting module PlasmaCAM.exe,
version 0.0.0.0, fault address 0x0002ff3c.
4/8/2005 9:47:51 AM Application Error Error None 1001 N/A GSDT2 Fault bucket
70938867.
4/8/2005 9:47:42 AM Application
Error Information (100) 1004 N/A GSDT2 Reporting queued error: faulting
application WINWORD.EXE, version 9.0.0.8216, faulting module MSO9.DLL,
version 9.0.0.6926, fault address 0x0026297c.

 

[Vera Noest [MVP]]

About the Symantex Fax problem:
have you deleted the service from the All Users profile?
Or check this:
222430 - OL2000: (IMO) FaxErr: "Error return code from
CreateNamePipe=231"
http://support.microsoft.com/?kbid=222430

I am not in the least familiar with the PlasmaCAM software that
causes one of the Application errors, but after some quick reading
on www.plasmacam.com, it seems unlikely that this software is
designed with TS in mind. That doesn't necessarily mean that it
cannot work on TS, but I would be suspicious.
Note that the Application error caused by PlasmaCAM is logged at
the same minute as the first Winword application error, which lists
MSO9.dll as the faulting module.
The file version of MSO9.dll on your system (9.0.0.6926) is not
listed in Microsofts dll database, which only lists file version
9.0.0.2720. I'm not sure if this has anything to do with your
problem, but I would investigate it (compare with working server).

DLL Help Database
http://support.microsoft.com/servicedesks/fileversion/dllinfo.asp?
fr=0&sd=tech

If all this leads to nothing, I would download FileMon and RegMon
from http://www.sysinternals.com/. Run them as administrator (when
no user is connected), start a TS session as a normal user and try
to run the application.

FileMon and RegMon will show you all "access denied" errors that
occur, so that you can give your users the necessary permissions on
a file-to file or Registry subkey basis.

 

[Guest]

Yes, I did checkout that KBB on the Symantec fax and it's not under the All
Users profile... you can see it if you run MSCONFIG. The problem I have is
that I can disable it but I don't want that message to come up and say "You
have modified the configuration bla bla bla... ". The message comes up
everytime a user logs in.