Office 2000 - no longer working correctly

[wvgirl64]

We are running Office 2000 on 7 W2K Citrix servers. Just recently we began experiencing problems with the Office suite on one server. For example, when opening a database from a desktop shortcut, the message appears "This file does not have a program associated with it for performing this action". If we start Access, and then open the database, the message appears "An error occurred and this feature is no longer functioning properly". Here's the catch - when I log on as administrator and open the same databases, I get no errors. Clearly, a permissions problem, but where do I check? I have even given full control to a particular user, but the errors still appear. I have uninstalled and installed Office, no help, maybe worse. This as I said just started happening, was not a problem from the beginning. We are experiencing problems with the other apps in Office as well, such as Excel. Access seems to be the worst.
Very frustrating, all help appreciated. Thanks

 

[mlrtime718]

I had the same problem after updating to Office SR-2. If you don't have it download regmon from

http://www.sysinternals.com/ntw2k/source/regmon.shtml

Wheon monitoring it creates a huge list so I would advise to do it when no one is on the server. Start monitoring and recreate the error. Stop monitoring and go through the list looking for ACCESSDENIED errors. It will tell you which key in the registry is giving you the problems. For some reason the MS update corrupted the permissions on the key. I added Everyone with Full Control and it fixed the problem.

 

[Illuvatar]

Something must have happened before on the server that causes these problems. Have you tried to find out if there where changes on the system that are possible for these errors ? If so, can you update us. It might help a lot.

 

[wvgirl64]

I believe that our problems occurred before we applied SP2 to Office, however we applied the service pack in hopes of correcting the problem. Now we have issues with all the email security.
But back to the original problem, we did run the network monitor with some assistance from our support group and ended up modifying the permissions in the registry, Everyone, Full Control. This seems to have fixed it.