install office 2003
in [Microsoft Office]
|
Prev: sku113.cab
Next: cplexe
From: doug_semler on 16 Feb 2006 11:42 I ran into the same problem, and I *THINK* that the problem has to do with either the user that installed the program no longer being an adminsistrator or that the user that installed it no longer exists. I managed to fix this by changing the permissions on the local machine properties for these keys. I got rid of all my event logs (for the 1004 id, 1001 id, and the HHCTRL 1904 id) and the Windows Installer dialog by doing the following: ***WARNING*** Standard Microsoft disclaimer regarding registry editing here. You can seriously F*** UP your computer if you F*** UP the registry. I take ABSOLUTELY POSITIVELY NO responsiblity for any problems you experience if you F*** this up! 1) Log on to the computer as an administrator. 2) Start regedit 3) Navigate to the HKEY_LOCAL_MACHINE\Software\Classes\Software key. 4) Right click on the key and open the Permissions... dialog. 5) Click on the Advanced button 6) Click on the "Replace permission entries on all child objects..." check box. 7) Click Apply 8) Close out all windows, log off, and log on as a restricted user. 9) Cross your fingers and start the office app. Doug Semler MCAD for .NET kevin wrote: > Hi! i'm experiencing the same problem would like to know if you have found > the solution? thks :) > > Regards > kevin > > "Phill" wrote: > > > Hi Mary, > > > > Thank you for your reply, unfortunately the fix you offered did not resolve > > the problem. We have turned off the "Windows Installer" service and this > > allows us to at least use the application without being prompted for the > > install. > > > > Does anyone know what office is doing when the install message "Please wait > > while windows configures Microsoft office 2003" runs, we have tried to run > > filemon and regmon to capture where it falls over from actually completing > > its task but could not pin it down > > > > Thanks again > > > > Phill > > > > "Mary Sauer" wrote: > > > > > Windows Installer-related event IDs are logged in the Application log when you start > > > an Office program > > > http://support.microsoft.com/kb/911682/en-us > > > > > > -- > > > Mary Sauer MSFT MVP > > > http://office.microsoft.com/ > > > http://msauer.mvps.org/ > > > news://msnews.microsoft.com > > > "Phill" <Phill(a)discussions.microsoft.com> wrote in message > > > news:1CAF9DE3-A87A-477E-A9E9-69FEECF6A50A(a)microsoft.com... > > > > Hi, > > > > > > > > We are experiencing an issue with Office 2003 pro. Office installs and runs > > > > perfectly with our admin account. We have an application which when launched > > > > as a user (non-admin) tries to initiate the "please wait while windows > > > > configures Microsoft office 2003, it will run through its things and then > > > > carry on to the normal screen. The trouble is it will do this every time we > > > > run the app. > > > > > > > > MSIinstaller generates events 1004 and 1001. > > > > > > > > Event 1004 looks like this: > > > > > > > > Detection of product '{90110409-6000-11D3-8CFE-0150048383C9}', feature > > > > 'ProductNonBootFiles', component '{FCF764E4-903B-4085-8E15-49FE7986986E}' > > > > failed. The resource > > > > 'HKEY_CLASSES_ROOT\SOFTWARE\Microsoft\MasterAggregatorForIPP\MSDAIPP\ServerCacheLocation' > > > > does not exist. > > > > > > > > Event 1001 looks like this: > > > > > > > > Detection of product '{90110409-6000-11D3-8CFE-0150048383C9}', feature > > > > 'ProductNonBootFiles' failed during request for component > > > > '{22056900-C842-11D1-A0DD-00A0C9054277}' > > > > > > > > If we give the user account admin rights it is fine. We have removed and > > > > re-added Office numerous times using "run all from my computer" but it still > > > > wants to do something when the program is launched > > > > > > > > Thank you for your time > > > > > > > > Regards > > > > > > > > Phill > > > > > > > > > > > > >
From: Phill on 16 Feb 2006 18:36
Hi, The solution (workaround) we have used is to simply turn off the windows installer service, it does not solve the problem though, I am still searching for the elusive fix I will try your fix Doug to see if that can sort us out, I will let you know if it works Much appreciated Phill "doug_semler(a)wideopenwest.com" wrote: > > I ran into the same problem, and I *THINK* that the problem has to do > with either the user that installed the program no longer being an > adminsistrator or that the user that installed it no longer exists. I > managed to fix this by changing the permissions on the local machine > properties for these keys. I got rid of all my event logs (for the > 1004 id, 1001 id, and the HHCTRL 1904 id) and the Windows Installer > dialog by doing the following: > > ***WARNING*** > Standard Microsoft disclaimer regarding registry editing here. You can > seriously F*** UP your computer if you F*** UP the registry. I take > ABSOLUTELY POSITIVELY NO responsiblity for any problems you experience > if you F*** this up! > > 1) Log on to the computer as an administrator. > 2) Start regedit > 3) Navigate to the HKEY_LOCAL_MACHINE\Software\Classes\Software key. > 4) Right click on the key and open the Permissions... dialog. > 5) Click on the Advanced button > 6) Click on the "Replace permission entries on all child objects..." > check box. > 7) Click Apply > 8) Close out all windows, log off, and log on as a restricted user. > 9) Cross your fingers and start the office app. > > Doug Semler > MCAD for .NET > > kevin wrote: > > Hi! i'm experiencing the same problem would like to know if you have found > > the solution? thks :) > > > > Regards > > kevin > > > > "Phill" wrote: > > > > > Hi Mary, > > > > > > Thank you for your reply, unfortunately the fix you offered did not resolve > > > the problem. We have turned off the "Windows Installer" service and this > > > allows us to at least use the application without being prompted for the > > > install. > > > > > > Does anyone know what office is doing when the install message "Please wait > > > while windows configures Microsoft office 2003" runs, we have tried to run > > > filemon and regmon to capture where it falls over from actually completing > > > its task but could not pin it down > > > > > > Thanks again > > > > > > Phill > > > > > > "Mary Sauer" wrote: > > > > > > > Windows Installer-related event IDs are logged in the Application log when you start > > > > an Office program > > > > http://support.microsoft.com/kb/911682/en-us > > > > > > > > -- > > > > Mary Sauer MSFT MVP > > > > http://office.microsoft.com/ > > > > http://msauer.mvps.org/ > > > > news://msnews.microsoft.com > > > > "Phill" <Phill(a)discussions.microsoft.com> wrote in message > > > > news:1CAF9DE3-A87A-477E-A9E9-69FEECF6A50A(a)microsoft.com... > > > > > Hi, > > > > > > > > > > We are experiencing an issue with Office 2003 pro. Office installs and runs > > > > > perfectly with our admin account. We have an application which when launched > > > > > as a user (non-admin) tries to initiate the "please wait while windows > > > > > configures Microsoft office 2003, it will run through its things and then > > > > > carry on to the normal screen. The trouble is it will do this every time we > > > > > run the app. > > > > > > > > > > MSIinstaller generates events 1004 and 1001. > > > > > > > > > > Event 1004 looks like this: > > > > > > > > > > Detection of product '{90110409-6000-11D3-8CFE-0150048383C9}', feature > > > > > 'ProductNonBootFiles', component '{FCF764E4-903B-4085-8E15-49FE7986986E}' > > > > > failed. The resource > > > > > 'HKEY_CLASSES_ROOT\SOFTWARE\Microsoft\MasterAggregatorForIPP\MSDAIPP\ServerCacheLocation' > > > > > does not exist. > > > > > > > > > > Event 1001 looks like this: > > > > > > > > > > Detection of product '{90110409-6000-11D3-8CFE-0150048383C9}', feature > > > > > 'ProductNonBootFiles' failed during request for component > > > > > '{22056900-C842-11D1-A0DD-00A0C9054277}' > > > > > > > > > > If we give the user account admin rights it is fine. We have removed and > > > > > re-added Office numerous times using "run all from my computer" but it still > > > > > wants to do something when the program is launched > > > > > > > > > > Thank you for your time > > > > > > > > > > Regards > > > > > > > > > > Phill > > > > > > > > > > > > > > > > > > > |