Discussion Locked

Office 2000 Setup Problems

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hello All,
I have an NT 4.0 SP6a system that will not allow Office 2000 to install. I've searched Technet, viewed the logs, tried reinstalling Office 97 then Office 2K, tried reinstalling SP6a and then Office 2K, all to no avail. The error I'm receiving is Windows Installer error 2328 (Error getting file version info for file) and it kicks me out of the installation. Below is an excerpt from a log I created in verbose mode. I have the whole log if someone needs it.

MSI (c) (0A:05): Transforming table CustomAction.

Internal Error 2826: Please contact product support for assistance.
Internal Error 2898: Please contact product support for assistance.
Action 9:44:38: UserInfo. Dialog created
Internal Error 2328: Please contact product support for assistance.
Action ended 9:44:49: UserInfo. Return value 3.
MSI (c) (0A:05): Doing action: FatalError
Action start 9:44:49: FatalError.
MSI (c) (0A:05): Transforming table CustomAction.

Action 9:44:49: FatalError. Dialog created
Action ended 9:44:52: FatalError. Return value 2.
Action ended 9:44:52: INSTALL. Return value 3.

Anyone know how I can determine the file that O2K setup cannot get the version information for? Or, anyone know a workaround for this issue? Thanks!

The errors 2826 and 2898 are standard errors according to TechNet article Q230879, plus the dialog I'm getting during setup references error 2328.

Arlo McCalla
arlo.mccalla@afpc.randolph.af.mil

11 replies

by dmiles

I think that SP6a may be your problem,uninstall service pack and reinstall service pack 5,then run Office 2k install,If this works,you will need to install office sp1a,then upgrade back to sp6a,the service pack may have updated files that office does not recognize.hope this helps

by arlo mccalla

Thanks for the response. We have over 2500 systems all running SP6a and they accepted the load without a problem. This one system has some additional software that isn't on most of our systems, I just need to determine which file(s) are causing the problem but have been unable to do so.

by mantvydas

I think a bad CD may be your problem. Try installing on a different system. If it fails, return your CD for a replacement.

by arlo mccalla

Hi Mantvis, thanks for your quick reply. I am installing from a network share that we used to install over 2500 systems with, all without this error. We have installed clients since then, so it's something on this particular client. I just need amethod for determining the problem file(s).

by grantcom

I suspect an installer problem or installer upgrade problem. See the following KB Article
Q219423
I had similar problems (but with win98)and had to download and install the latest installer from MS. Don't know about NT though. The cited article also has some diagnostics for NT
I persoanlly think it may be a speed issue (setup times out.) Try loading Office CABS to the drive first and run setup from there...this will remove timing issues from the diagnostic loop.

Installer InfoQ229819

by grantcom

Also see Q200116...NT Office Setup Troubleshooter...gives some good tips and advice on NT Office setup.

by arlo mccalla

Thanks for all the info, still not working though. Below is a snippet from the Office 2K setup log, the Windows Installer was installed successfully. I did try to install the one I downloaded separately from Microsoft, and that installation ran fine but the Office 2K install still bombed at the same spot.

>C:\WINNT\System32\msiexec.exe is >version 1.10.1029.1
>Windows installer upgrade >succeeded.

Arlo

by grantcom

Arlo...check out this link
http://msdn.microsoft.com/library/psdk/msi/pref_7bll.htm

This will give you command line switchs in regard to version. It apears that the "a" switch will cause a complete re-write regardless of version...may help if there is a version determination failure.

Also see this link:

http://msdn.microsoft.com/library/psdk/msi/aref_1wo5.htm

Look over this carefully and you will find valuable TOC links in regard to file library, log file interpretation etc. From reading the article it appears that a verbose log may be a little more difficult to interpret than regular diagnostic.

Also, from what I read it may be better to uninstall all prior versions and then attempt the 2000 install...removing will eliminate most version determination problems.

Wayne

by arlo mccalla

Thanks for the tip, all I had to do was Uninstall 97 (I then ran the Office 97 Eraser utility) and Office 2000 installed successfully after that.

This discussion is closed to new replies.