7 replies to this topic

[MonkeyK]

For some reason I cannot get the msi in an "Install From the Web install" Can anybody help me to figure out what I need to do?

I built an Install From The Web install (the kind that makes setup.exe, .msi, and .cab files. Setup.exe is downloaded and then when it runs it is supposed to pull down whatever it needs).

I set the "URL for your files" field to point to a directory on my test webserver: https://qa.securiana...TestWebInstall/

I get the setup.exe and launch it and get the message telling me that an upgrade will be performed, followed by setup initializing...

and then "The installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid windows installer package."

I logged the install to see what is going on and see:
=== Verbose logging started: 07/08/2004 10:54:45 Build type: SHIP UNICODE 2.00.2600.1183 Calling process: C:\WINNT\system32\MSIEXEC.EXE ===
MSI © (8C:74): Resetting cached policy values
MSI © (8C:74): Machine policy value 'Debug' is 0
MSI © (8C:74): ******* RunEngine:
******* Product: https://qa.securiana...tallProduct.msi
******* Action:
******* CommandLine: **********
MSI © (8C:74): Package path is a URL. Downloading package.
MSI © (8C:74): MainEngineThread is returning 2
=== Verbose logging stopped: 07/08/2004 10:54:46 ===



What I guess is happening is that the setup.exe is downloaded within the user's authenticated HTTP session. But then when setup.exe is launched, it has no way to authenticate to the site.

Can anybody help me out with this?


Thanks,
Mike

[Stefan Krueger]

MSI 2 runtime does not support HTTPS, only HTTP. Microsoft will add support for HTTPS MSI 3 (currently in beta)

[MonkeyK]

Aha!

Thank you Stefan, you have saved me from yet another day of bumbling around trying to figure it out.

Your MSI/InstallShield knowledge has helped me out more times than I care to count!


-Mike

[MonkeyK]

it looks as though support for HTTPS is as far as it goes, no authentication.

http://msdn.microsof...dows_041304.asp

[Stefan Krueger]

yes, it can't prompt for user name and password

[MonkeyK]

A real shame too. I'm not sure my company can put our install out on our website unsecured

With a 40meg install, an "Install From the Web" release build seemed ideal (in my install it would probably cut the download time by 90%), but without authentication, it's wasted

[Stefan Krueger]

You could ask the user to log in before they reach the download link that will start your install.

[MonkeyK]

I am able to download the setup.exe in my code with no problems. I just pass username and password in the code. Or if I use the trial update service, I am prompted when downloading setup.exe. When the setup.exe is launched, it tries to get the .MSI which fails since the connection that the setup.exe is trying to use has not been authenticated (at least I think that's why. Also, just for fun I tried seperately logging in in a web browser, but that's not good enough).

I imagine I would have the same problem when the .MSI tries to download the .CAB files

Edited by MonkeyK, 13 July 2004 - 17:42.