Greetings,

I'm having difficulty creating an MSI based install for Crystal Reports Viewer 11. The source file is a crveiwerxi.exe, which passes arguments on to a setup.exe and msi in a temp directory durring uncompression. I have managed to extract the msi and files with an admin install. However when trying to run the MSI it tells me I must run this from setup.exe.

I've read this seemingly related posting with solution here: http://itninja.com/question/install-string-for-crystal-reports-xi but the proporty for ProductLanguage is not -1, it is 1, and changing it to 1034 does not solve the issue. Setting a proporty for ISSETUPDRIVEN=1 does not work either, and there is no custom action that I can see with my limited experience that is driving this.

It's a simple app, just need it to install with all defaults silently, but we can not use the included setup.exe due to environment restrictions.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Run the install with a verbose log: you should see which Custom Action is testing which property and causing the install to bail.
Answered 12/05/2007 by: VBScab
Red Belt

Please log in to comment
0
sometimes with runtimes you can manipulate the setup.exe with INI or command line entries and get it to run silently that way.
Answered 12/05/2007 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
You will have to forgive me. It appears when calling /qn from a cmd line it does not prompt this error. I had been using /qb. All is well, thank you.
Answered 12/05/2007 by: Jahya
Senior Yellow Belt

Please log in to comment
0
we can not use the included setup.exe due to environment restrictions.So this was rubbish, then?
Answered 12/05/2007 by: VBScab
Red Belt

Please log in to comment
0
Uhm no. And why would you be a jerk besides?

I passed the /qn to the extracted MSI. The original compressed executable passed commands to a setup.exe in a temp folder upon uncompression. If you run the original exe as "crveiwerxi.exe /a" it passes it to the temp folder setup.exe and runs an admin install, extracting the msi and files.

Once I had that, it prompts "please run from setup.exe in parent blah" error message when trying to run manually non-silent, or with /qb, and the standard Installshield tricks listed above did not work. Running that extracted msi with /qn installed fine without the "please run from setup.exe in parent blah" message.

We use CA Software Delivery Option, and our policy dictates using an MSI unless absolutely needed. Hence a restriction, not a ban.
Answered 12/05/2007 by: Jahya
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity