9 replies to this topic

[tadigiacomo]

I am having a problem with the silent install of Actuate e.Reporting Server. When I recorded the setup it ended with a SdFinishReboot dialog. However, we've had problems where the Actuate silent install failed with a ResultCode of -3. When I installed on the failed machine interactively, the Actuate setup was ending with a MessageBox stating that installation was successful, not the SdFinishReboot dialog. I am figuring that this caused the failure. For some reason the configurations of all our lab and test machines is such that Actuate requires the reboot. Obviously, this is not the case everywhere else.

Is there any way around this? I don't know of any way to tell Setup.exe that it may encounter one OR the other. Any ideas?? Thanks!

Tom D.
Lucent Technologies

[Taco Bell]

You basically need to combine the reboot & non-reboot results into one common setup.iss, so you get the best of both worlds. IS will automatically use what it needs and ignore any extra data, thereby covering both scenarios.

[Perotin]

TacoBell, does that work? I never thought this would do ...

I thought the iss files had to describe the dialog order like

CODE

[{C7B15526-3E6B-11D6-8EF3-00065B663C82}-DlgOrder] Dlg0={C7B15526-3E6B-11D6-8EF3-00065B663C82}-SdLicense-0 Count=3 Dlg1={C7B15526-3E6B-11D6-8EF3-00065B663C82}-SdAskDestPath-0 Dlg2={C7B15526-3E6B-11D6-8EF3-00065B663C82}-SdAskOptions-0

How do I write an iss file that has two dialogs Dlgx?

The problem occured at our place with Acrobat Reader and I found that the AcrobatReader installation wanted to replace some system files and therefore asked for a reboot.

Tom, you can look for the WINDIR\wininit.ini file (in Win9x, NT uses some registry keys) when your setup wants to reboot to find out, what files are being replaced (if you cannot see into the cab/msi file ).
Now you have to provide two iss files (with and without reboot dialog).
Then you check the user's system for files to be updated and use an iss file with the appropriate ending ...

[Taco Bell]

Yes Perotin, believe me, it does work as long as your silent installation is using IS 6 and not IS 3.

Also, the ISS file does describe the order of the dialogues, but if a particular one doesn't come up, then it doesn't complain. Just make sure each Dlgx entry is unique, and that the correct number is reflected in the count.

Just think of as it as a file containing the ordering of all the possible dialogues for a setup instead of looking at it on a case-by-case basis. Of course when you automatically record/generate an ISS file, it can only write out what it sees, but if you take the sum of all the things, then you can cover all your bases.

CODE

[InstallShield Silent] Version=v6.00.000 File=Response File [File Transfer] OverwrittenReadOnly=NoToAll [{02E7DB6A-B120-11D4-A3F4-00C04F606097}-DlgOrder] Dlg0={02E7DB6A-B120-11D4-A3F4-00C04F606097}-SdWelcome-0 Count=8 Dlg1={02E7DB6A-B120-11D4-A3F4-00C04F606097}-SdLicense-0 Dlg2={02E7DB6A-B120-11D4-A3F4-00C04F606097}-SdAskDestPath-0 Dlg3={02E7DB6A-B120-11D4-A3F4-00C04F606097}-SdComponentTree-0 Dlg4={02E7DB6A-B120-11D4-A3F4-00C04F606097}-SdSelectFolder-0 Dlg5={02E7DB6A-B120-11D4-A3F4-00C04F606097}-SdStartCopy-0 Dlg6={02E7DB6A-B120-11D4-A3F4-00C04F606097}-File Transfer Dlg7={02E7DB6A-B120-11D4-A3F4-00C04F606097}-SdFinishReboot-0 [{02E7DB6A-B120-11D4-A3F4-00C04F606097}-SdWelcome-0] Result=1 [{02E7DB6A-B120-11D4-A3F4-00C04F606097}-SdLicense-0] Result=1 [{02E7DB6A-B120-11D4-A3F4-00C04F606097}-SdAskDestPath-0] szDir=C:\Program Files\Canary Labs Result=1 [{02E7DB6A-B120-11D4-A3F4-00C04F606097}-SdComponentTree-0] szDir=C:\Program Files\Canary Labs\Trend Link Viewer Program Files-type=string Viewer Program Files-count=3 Viewer Program Files-0=Viewer Program Files\Think & Do Licensing Viewer Program Files-1=Viewer Program Files\Resource English Component-type=string Component-count=4 Component-0=Viewer Program Files Component-1=Demo DataSource Component-2=OPC DataSource Component-3=Think & Do DataSource Result=1 [{02E7DB6A-B120-11D4-A3F4-00C04F606097}-SdSelectFolder-0] szFolder=Canary Trending Result=1 [{02E7DB6A-B120-11D4-A3F4-00C04F606097}-SdStartCopy-0] Result=1 [Application] Name=Canary Trend Link ActiveX Control Version=5.2.5 Company=Canary Labs Lang=0009 [{02E7DB6A-B120-11D4-A3F4-00C04F606097}-File Transfer] ReadOnlyFile=YesToAll SharedFile=YesToAll [{02E7DB6A-B120-11D4-A3F4-00C04F606097}-SdFinishReboot-0] Result=1 BootOption=0 [{02E7DB6A-B120-11D4-A3F4-00C04F606097}-SdFinish-0] Result=1 bOpt1=1 bOpt2=0

For example, the File Transfer information is something I added later to handle some additional prompts which occurred in the field. It's rare to experience those dialogues, but if you don't encounter them, then it just skips/ignores it.

Also, at the bottom there you can see I have sections to handle both a regular finish and a reboot finish. However, I noticed that for the dialog order I don't reflect both possibilities. Believe me, it still works though. For curiousity's sake, I'll double check specifically referencing both though since I've received a new version of this 3rd-party software, so I need to re-create this ISS file anyway.

[tadigiacomo]

Perotin,

Thanks! I was thinking that I might have to go that route. Do you know where in the registry it keeps the files that need replaced?

TacoBell,

I'd like to avoid shipping two .iss files. How exactly do you add that extra info to the .iss file?

Thanks to both of you for your help!

Tom D.

[tadigiacomo]

TacoBell,

Thanks! Ignore my previous post - I think we posted at about the same time.

I will try that and let you know how it goes. Thanks again!

Tom D.

[Taco Bell]

For NT-based OSes, that registry location is the following:
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations

But you may also want to check:
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx

P.S. Yeah, I noticed that tadigiacomo, so I was planning on just igorning part of it.

Edited by TacoBell00, 03 July 2003 - 15:34.

[tadigiacomo]

TaceBell,

Thanks so much! Your replies have been very helpful.

But, I got another somewhat-related question. I am also writing out password info to this same .iss file, and if a particular password is NO password (null), it breaks. The name-vlaue pair ends up pwd= (as opposed to pwd=abc123), and the silent install fails with a -3 result code. My question is, how to a pass an empty password (or string) via the .iss file, or, how can I encrypt my value before writing it out so that it will be properly decrypted by the silent install? I am currently setting an encrypt password flag to 0. When I recorded the .iss with an empty password entered it encrypted it and place the value properly. Any ideas? Thanks!

Tom D.

[Taco Bell]

Yeah, I've tried to use null before in an ISS file for something else and it got equally confused.

I'm not sure, but maybe try pwd="" or just removing that line/section from the ISS to keep it the default of null.

[tadigiacomo]

Thanks! I'll give it a try.