I am really hoping that someone out there has seen the following and can come to the rescue!!!

My client is upgrading from MS Office 2000 to MS Office 2003, Office has been configured to use Local Installation Source and is using a transform generated using the custom installation wizard.

I am able to deploy MS Office 2003 using SMS 2003 (pointing to LIS and executing PRO11.MSI and appropriate transform) and the upgrade takes place as expected without any issues.

The users have local profiles on the workstation. If a user launches MS Office 2003 using a PC that already has a (pre Office 2003 profile for them) present then all office apps attempt to self repair. See Event log entry below:

Detection of product '{90110409-6000-11D3-8CFE-0150048383C9}', feature 'OfficeUserData', component '{C9AF9050-C8BE-11D1-9C67-0000F81F1B38}' failed. The resource 'HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Common\UserData' does not exist.

Followed by:

Product: Microsoft Office Professional Edition 2003 -- Configuration failed.

If a user that has not already created a (pre office 2003 profile) launches any Office 2003 product the application self-repairs itself and works perfectly.

In order to 'work around' this issue users profiles can be reset (rename NTUSER.DAT) and allow it to be recreated however this is far from an ideal situation as there are other things to think about when reseting profiles (favourites, desktop items, app settings etc)

Has anyone else encountered this issue, and if so how did they get around it.

Please, Please, Please somebody come to my rescue!!!!
0 Comments   [ - ] Hide Comments


Please log in to comment

There are no answers at this time
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity