Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Msi Installer Error?

Status
Not open for further replies.

NcCorduan

MIS
Oct 26, 2001
92
US
Running into a pretty major problem right now. We have a lot of PC's on our campus on which we have installed MS Office 2000 (also running Windows 2000), using a MSI and a MST from an administrative install point. We thought everything was fine until we did this upgrade for a user that does a lot of mail merges in Word. Her performance with this task -- undoubtedly one of the most memory-intensive operations you can do in Office -- was dismal.

So that got me started looking through her event long. And, there, I found almost endless entries in the Application log, such as the following:

Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1004
Date: 1/30/2002
Time: 3:19:37 PM
User: N/A
Computer: TSOFW
Description:
Detection of product '{00010409-78E1-11D2-B60F-006097C998E7}', feature 'WORDFiles', component '{CC29E963-7BC2-11D1-A921-00A0C91E2AA2}' failed


Followed by...

Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1001
Date: 1/30/2002
Time: 3:19:37 PM
User: N/A
Computer: TSOFW
Description:
Detection of product '{00010409-78E1-11D2-B60F-006097C998E7}', feature 'WORDFiles' failed during request for component '{CC29E963-7BC2-11D1-A921-00A0C91E2AA2}'


And then by...

Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1000
Date: 1/30/2002
Time: 3:19:37 PM
User: N/A
Computer: TSOFW
Description:
Failed to connect to server. Error: 0x80004001


So... Can anyone out there help me unwravel this one???

Thanks!!!
 
I'd try reinstalling office first.
A search of the event IDs on gives quite a bit of info, but the advice is a bit scary! To quote
"Go to HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\Components\.. registry key. Now run RegMon from Start that, pause it from watching the registry, start excel and get to the point when the error would happen, start RegMon, create the error, go to RegMon and pause it! Search in RegMon for the above registry key, it will go further down the tree and you will see the binary code in the results part of regmon, showing 'ExcelUserData', once you have found that entry, save the whole of the key to a .reg file using RegEdit and then delete the single entry within that key."
Good luck
John
 
John,

Thanks, I'll see if I'm brave enough to try that suggestion from EventID.net...

Re-installing from the CD's rather from our administrative MSI seems to take care of the problem but it's not all that more pleasant an option. A detail that I didn't mention before is that, spurred on by this finding, I started scouring the event logs of other users and found the same constant string of errors in just about every one I looked at.

As I've thought about it some more, I realized the few users who do not have the errors in their application users are all local administrators on their machines, whereas the others are only power users.

Could this be a permissions issue? Or an issue with the network connection the server from which the administrative installs were done?
 
Have you found a solution to this yet? we are having the same issue. we have done the reinstall, update to SR-2, and reg hacks!

Still nothing, i would be very interested in how this issue is overcome.
 
We had the same problem, try:
- Open a W2k session with the user who makes the DCOM calls (and in your case the identity that has installed the products)
- Run Word (and Excel)
- Close it (them)
Seems that the installation process is not really finished whent it says so...
 
I have had the same problems with Office XP SP1 on W2K SP2.

Turns out it was the permissions on C:\Winnt\Installer; make sure Authenticated Users or Everyone has at least Read & Execute access to the subdirectories.

Sorted out the problem on XP, hope it works for 2000.

 
I was just having a similar problem trying to apply SR-1 and Service Pack 3 to Access 2000 no a remote server. I finally checked where I found the answer.

Our HW guys normally remove the "Everyone" account from a server drive security list, adding our administrator accounts, but they had failed to re-add SYSTEM as an account on that drive. The drive had a directory with the installation software.

Now, my installation works like a charm!
 
I am also having fun with these errors, although my problems lie on a Citrix server, and it is only one user (at the minute) who is actually receving on screen errors such as:

Microsoft Excel can't use the AutoCorrect lists.
Microsoft Excel cannot install the necessary files due to Windows
installer error 1605. This action is only valid for products that
are currently installed.

That's just one, they vary slightly...I have the above error logs too.

Nothing I have tried so far has worked, (haven't and don't plan on touching the registry :p )

Anyone got any ideas what I could try? Is my problem down to the user? as other people (including myself) are using word and excel fine within Citrix.

Cheers
 
Also,

This is one and the main error logs on the server....

Detection of product '{00000409-78E1-11D2-B60F-006097C998E7}', feature 'OfficeUserData', component '{C9AF9050-C8BE-11D1-9C67-0000F81F1B38}' failed. The resource 'HKEY_CURRENT_USER\Software\Microsoft\Office\9.0\Common\UserData' does not exist.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top