/build/static/layout/Breadcrumb_cap_w.png

Office XP MSI problem

I have made a MSI package which uses an MST file. This works fine and will also work as a 'lights out' distribution.

The problem is that the other day I imaged some other machines and logged on them as an associated user, about 6 packages installed correctly (snappshots) but for some reason Office didnt even try to install. Straight away it came back with the old faithful "Install failed. MSI returned error code: 1612"

I have re-imaged my origional computer and logged onto that and the Office installation worked fine, I thought that because it was an MSI it would install on any type of hardware????

I have had the same problem with Adobe Reader7 and AWETT Assessing the Workplace (both snappshots) working on some workstations but not others

If anyone could shed some light on this it would be gratefully appreciated

0 Comments   [ + ] Show comments

Answers (7)

Posted by: sini 18 years ago
Orange Senior Belt
0
Create an installation log: msiexec /i Office.msi TRANSFORMS=YourTransform.MST /Liemo! C:\Office.log scroll to the bottom and look for the cause
Posted by: slb 18 years ago
Purple Belt
0
I hope the error says that the installation source location is not found?? If this is the case try to keep the msi local and then delete it after installation... Hope it makes sense.
Posted by: Total5 18 years ago
Senior Yellow Belt
0
Thanks for the reply, I have had real trouble in getting an msi.log I have just ran gpedit.msc and enabled windows installer logging.... but does not create a log file??

Could you expand a bit more on the way you are telling me to do it. What is msiexec.exe? and do I have to point to where the office msi is e.g. ZenServer\apps\msi\etc\etc..........

Thanks
Posted by: VikingLoki 18 years ago
Second Degree Brown Belt
0
Log file needs to be full path to any location with full write access. Msiexec.exe is the Windows Installer command executable. Open a command prompt and type MSIEXEC /? on a machine with Windows Installer installed.
Posted by: Total5 18 years ago
Senior Yellow Belt
0
The problem which I am having is that it returns an error code of 1612, I have enabled logging and it does produce a log when an msi has been installed but is does NOT create a log from the Office failure (I have voicewarmup in the properties of logging)

The exact same package has worked before and worked over the WAN to a different type of workstation. I have re-imaged the workstation which it was created on and tried to install again, and it is comming up with this message? as far as I know the package hasnt been touched or changed in any way?

Any ideas?????
Posted by: Total5 18 years ago
Senior Yellow Belt
0
I have tried to install the same package on my machine (not the test machine, which I keep imaging). I have logged on to my machine as the user which I use to install a certain set of programs (which includes the Office install).

Now when I click to install Office it installs a little bit and then stops, this returns an error which says
"could not launch Office XP.ZfD Distribution.ZfD (using\\..\.....\.....\.....\etc) (id=5) Access is denied"
It has also returned me a log file (which I cannot see why it failed). This never happened on the other workstation, it didnt even provide me with a log file.

Maybe this could provide more of a clue??
Posted by: craig16229 18 years ago
Third Degree Brown Belt
0
Total5,

When you say you made an .msi package for Office XP, does that mean you created an administrative installation point, or that you repackaged the original .msi into a new .msi?


Craig --<>.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ