Related to Office 2003 SP2?

[mszablocky]

I had the same difficulties with this Service Pack everyone else is
reporting, but I'm seeing Application warnings in the Event Viewer that are
new to me. Does anyone know if the're related to the new Service Pack? If
so, is there a way to eliminate them? There is no information on them yet in
the Knowledge Base.

Here is the text of some these messages:

Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1004
Date: 10/1/2005
Time: 5:28:59 AM
User: NT AUTHORITY\NETWORK SERVICE
Computer: IBM-49D233600C8
Description:
Detection of product '{91120409-6000-11D3-8CFE-0150048383C9}', feature
'ProductFiles', component '{66CD2C91-2A15-4DA4-BBD2-5EC1075F3C0E}' failed.
The resource 'HKEY_CLASSES_ROOT\.pip\' does not exist.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1001
Date: 9/30/2005
Time: 9:48:39 PM
User: NT AUTHORITY\NETWORK SERVICE
Computer: IBM-49D233600C8
Description:
Detection of product '{91120409-6000-11D3-8CFE-0150048383C9}', feature
'WORDFiles' failed during request for component
'{1EBDE4BC-9A51-4630-B541-2561FA45CCC5}'

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

 

[drgarner]

I spent several days researching this same exact problem on my Citrix
server and finally figured out a fix! (BTW, these errors pre-date
Service Pack 2 to Office 2003.) In my particular situation my server
previously had Office 2000 Premium and I recently upgraded to Office
2003 Professional - that is when these event log entries started. The
fix is to log in as a different user with local admin rights and delete
the UsrClass.dat file in the profile for the user that this error is
logged with. The path is c:\documents and settings\<userid>\local
settings\application data\microsoft\windows

On my Terminal Server I simply did a search on usrclass.dat in
c:\documents and settings\ and then deleted every file found. Note
that to prevent a locked file error you must have just rebooted and
that no user can be logged on. Apparently there is some profile info
in this file related to the old Office installation that is causing
these errors.

Hopefully this will help someone out there - I spent many days
researching this.

Good Luck,
Dave Garner