Error Installing Vault Server version 4.1.4.18402

[mark4262]

I get an error saying that it is not a valid windows install.
(see attachment)

I don't get this same error with v. 4.1.3.18336

[Beth]

Did you download it from our site directly to the machine where it will be installed, or did you copy it across a network share? I've seen MSIs that are copied inside of a network sometimes refuse to run.

[mark4262]

Thanks for your response, Beth.

Yes, I copied it straight to the machine where it will be installed. I did exactly the same thing with the previous version 4.1.3 and it installs just fine. I would just install the previous version, but I don't want to have to re-release all my validation documention to go back a version.

[mark4262]

More information:
MSI.dll version: 3.1.4000.3959

2 attached installion logs:
install txt : version 4.1.4
install_old.txt : version 4.1.3

[Beth]

Yes, I copied it straight to the machine where it will be installed.

Can you connect with your server and pull it down directly and run it that way?

I don't know what the root cause with some MSIs and copying, but I know it's not something particular to our installer. It was over a year ago that I read something about this occurring with MSIs sometimes in general.

[mark4262]

nope ... same error however I try it ....

Clearly something changed with your installer between the 4.1.4 version and the 4.1.3 version.
Any idea what the difference is?

I am using Windows Server 2003 ....

Thanks for you help in resolving this.
Mark

[Beth]

I'm checking into what the installer changes are. In the meantime, this Microsoft article might give some insight: http://support.microsoft.com/kb/295823. If we upgraded our installer, but your msi settings are old, I could see where that could cause this. What happens if you try their recommendation before installing?

[mark4262]

This is a new install on a new server, so the windows installer does not have an old settings.
I have installed the 4.1.3 version for now ... can't spend anymore time messing with the newest one.
Please let me know if you discover what might be wrong.
Mark

[Beth]

After checking with the developers I found there was no change with the installer. Next time you try installing you might want to have some msi installer logging. You can run it from the command line with the msiexec command with the /log switch.

If you would like a little closer assistance, you send send an email to support at sourcegear.com (attn: Beth ) with a link to this forum thread.

[mark4262]

Beth,
If you look back about 5 posts, I have already done what you suggested about the logging and attached the log files. Please refer to the attachments on that email.
Thanks,
Mark

[mskrobul]

Is the 4.1.4 installer package that doesn't work located at the same folder on disk as the 4.1.3 package? If not try moving it to that location. Or just try re-downloading the package from our site to a different location on disk and try installing from there. It sounds weird but sometimes the location of the .msi on disk matters.

I am really now sure why 4.1.3 works and the other doesn't. The installer itself hasn't changed at all (other than the version number and product code of course - other than that the source is identical). Your problem seems like some sort of permissions issue.

Make sure that the SYSTEM account has full access to the following folders:

Source directory - The directory where the .msi is located

Temp directory - The temporary directory where Windows Installer stores its temporary files (for example, c:\temp). To determine where the temporary files are stored, check the %TEMP%
and %TMP% environment variables.

Target directory - The directory to where Vault is being installed