Offise 2k install on XP

I'm having problems loading Office 2000 on Win XP Pro

MSI (c) (90:2C): Note: 1: 2755 2: 995 3: \\fileserver\disk1\data1.msi
DEBUG: Error 2755: Server returned unexpected error 995 attempting to install package \\fileserver\disk1\data1.msi.
Internal Error 2755: Please contact product support for assistance.
MSI (c) (90:2C): Product: Microsoft Office 2000 Premium -- Internal Error 2755: Please contact product support for assistance.

Searching MSKB I found several articles relating to error 2755, but they refer to error 1632 (not 955) which is to do with permissions.

Occasionally I get message box referring to oleaut32.dll.

I'd be grateful for any assistance.

This corporate Office 2K premium setup has been used successfully on Win 9X, NT4 (SP6) and W2K (all service packs)

Thanks

Did you see this mskb? Did you try copying the contents of the cd to the hard drive and installing from there?

Thanks NooNoo

I've seen this, but I'll go back thorugh it again - can't do any harm!

I've just done a network installation to a W2k machine (as a check) which has completed OK.

I'll post back - but any other help very welcome.

Tried the procedures in the article NooNoo posted.

Unfortunately no fix

Any other help would be gratefully received!.... I'm nearly at the point of purchasing Office XP, but part of our Group is a Training Company, and all our ECDL people are working on the Office 2000 tutorials!!!

Thanks for reading

I've now been through all the available (well, as far as I can devise search queries!) articles at MS, and some other sites that Dell recommended (not a great deal of use)

I cannot find any specific references to the problem I am encountering.

I tried installing the Office suite on an "out of the box" XP machine, not networked, install from CD Rom, AV disabled, still won't install

I have managed to get the program running, but BY DOING SOMETHING I WOULD NEVER RECOMMEND TO ANY OTHER CONTRIBUTOR/USER

Logged on as administrator, install runs until message INSTALLER TERMINATED PREMATURELY. Running a verbose log shows the error previously submitted

At this point in other Windows O/S, the machine would always re-boot (by request, not automatic). With the error message window on screen on these XP machines, no option to re-boot through ctrl/alt/del, so switch off!!! AS I SAY, THIS IS NOT RECOMMENDED

On re-start, office apps are available, BUT

The windows installer still sees the installtion as "in progress", so when a User launches a programm, set-up runs. By cancelling this, User can access programs.

Clearly this is not acceptable long-term.

So, I'm still looking for any pointers/help

Thanks for input so far.

After some two weeks of research I have finally resolved my problem. I am posting this in case any one else should encounter this difficulty

I am unsure as to which of the following parts of the equation actuall cause the problem

Windows XP SP1 (OEM Install, IE6)
Dell 2350
Office 2000 Premium from 1999

It appears that the installer was terminating prematurely becuse it was hanging on accessing the MS Web Component mswoc.dll. This only became evident as the file could not be deleted, (even after re-boot) and msiexec was running. Terminate msiexec, and file deletable

Downloaded upgrade to this file from MS owcupd.exe (it comes with an Office XP file too, so this problem could exist in Office XP). It is supposed to be a security patch

Copied new msowc.dll to administrative installation point, re-install to client, and programmes install correctly

On launch, Access 2000 appears to not have VBA6.dll available and does not run correctly

Install SP1 (Office 2000) and all welll.

My thanks to NooNoo for the contribution too.

Dear Lord... that is some fix you have there. Have you emailed microsoft about it? I think you deserve some sort of award for that!

Just a thought, it is possible that the hanging on mswoc.dll is because XP "knows" the file is wrong but has no error procedure for it?

What version IE/Service Pack level was on the machine?

Thanks, NooNoo

It had occured to me that there might be a checksum mis-match on reading the dll. However, The installer package (data1.msi) would, I think, cover that, not the XP installer. I've seen many posts on newsgropus where contributors say there are no compatibility problems with XP/Office 2k

I haven't mailed MS, simply because it didn't occur to me to do so. And because I was extremely pleased late last night when the install completed! Having posed the question, I'm not sure how I would submit this. Curiously, XP didn't generate the usual "Do you want to send details to MS" option on install fail.

I also find it curious that the msiexec setup .txt files referred to other files (oleaut32.dll) as encountering errors, but not the msowc.dll file.

I can now integrate more machines into the network, and have (reasonably) happy users. Of course, you'll probably know that most machines need a User upgrade!

Thanks for your reply, NooNoo. I read about you having a toothache (and YaKnow scored some points as a result, he says!), hope that's gone now.

Finally, I appreciate the selfless way you offer help to complete strangers (viz your posts total) - I'm not being sentimental! Doesn't happen too often in the big bad world. I hope you are motivated to keep it up!

All the best.