Office 2003 Issue

[Guest]

Hello everybody,

I have this scenario :
1 Server SBS 2000 , configured as domain controller, DNS, DHCP and Terminal
server in Application mode. Everything was working well until I had to
upgrade Office 2000 to Office 2003 Pro.

Now the problem is that domain users (accessing the server in TS) receive
error opening Excel (class non registered, vb errors), Outlook (script error
298), Access (the application don't start). For administrators (or users
temporary promoted to administrator) everything works fine.

I've checked the Knowledge Base for every error and tested the relative
resolution but with no success... I've already verified NTFS permission... I
tryed to remove every office application and reinstall... tryed without
office service pack, then with sp1 and sp2... tryed to remove addins
(acrobat...)...

Any idea ???? Thank you...

Diego

 

[Vera Noest [MVP]]

Was the server in install mode when you installed Office 2003?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___

 

[Guest]

Hi, Vera

First of all thanks for your help... yes... install mode...
I always installed from add/remove programs in control panel...
Years ago, when I installed Office 2000, I had to create the .mst file with
the ORK tools... with Office 2003 I followed a Knowledge Base article that
say that this time the transform file was not necessary... this is correct ?

Bye

Diego

 

[Vera Noest [MVP]]

Yes, that's correct, Office 2003 doesn't need a mst file anymore.
Did you first uninstall Office 2000 and then a fresh install of
Office 2003, or did you do an upgrade?

You could try to use RegMon to find on which registry keys the
users need more permissions, but in your case, I would be hesitant
to take this approach, since it seems that the whole installation
of Office has problems.

This is also your Domain Controller, isn't it? I assume that you
know that running TS on a DC is *not* recommended (it's not even
possible anymore on SBS2003), and I don't know which additional
problems this might cause on your SBS2000 DC.

That said, give RegMon and maybe also FileMon a try. Download them
from http://www.sysinternals.com/.
Run them as administrator on the console (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.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___

 

[Guest]

I first tryed an upgrade... when the problems begun (instantaneously), I
completely removed office and reinstalled...

I know... a DC on a TS is horrible... but this is an acquired customer, so
the initial network design was not made by me... I acquired the customer
after installing a new member server with ISA... I'm MCP on ISA...

Great idea !!! tomorrow I will try "regmon" and "filemon"... I'll post the
results...

Thank you very much !!!

Diego

 

[Guest]

Vera, you are the BEST !!!!!

It was a registry issue... using "regmon" I found the guilty keys...
The problem was in some (12) subkeys under :
HKEY_CLASSES_ROOT\TypeLib
HKEY_CLASSES_ROOT\Interface
with access permission only for Administrators and SYSTEM...

Now everything works fine...
Thank you VERY VERY MUCH !!!

Diego

 

[Vera Noest [MVP]]

Thanks, Diego, I'm glad that the problem is solved!
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
*----------- Please reply in newsgroup -------------*