Software Deployment

The CA producing that message is OnCheckSilentInstall. Condition that one out, too.

The WPS debugger is part of WPS and, as far as I'm aware, not available as a separate component [sic]. If you have WPS, load up the MSI into the editor and click the 'Debug' button which is tucked down on the bottom right-hand side of the page, or press Ctrl+E.

Note that, whilst mostly useful, this is another classic, bug-ridden piece of software from Wise. If you cancel an "installation" while it's running in the debugger, 9 times out of 10 it will hang the user-level MSIEXEC.EXE process. You'll have to kill it with Task Manager/Process Explorer.

Running the MSI through WPS's debugger, it seems that the offending CA is ISVerifyScriptingRuntime. Conditioning-out that CA allowed the MSI to proceed past the offending message.

Be aware, though, that because the rest of the package was built in "lazy IS packager" mode, it will still require the necessary IS driver/engine (v8) to be pre-installed.

In this case, you didn't look to whom the reply was directed.

search for ISSETUPDRIVEN it's been covered loads of times

You need to add this public property to your msi (via a transform obviously)

there may also be a custom action called onsilentinstall (that may not be the correct name as I'm just trying to recall it from my little brain) which needs removing or conditioned to never run

Hi,

I know about ISSETUPDRIVEN property and I have set its value as 1. It allows me to run msi but now msi is running silently without showing any dialogues.

There was a custom action named onchecksilentinstall..I even removed that still msi is running silently....any suggestions pleae....thanks

Any other suggestions pls...

in all probability there won't be any dialogs in the msi.

The dialogs will be spawned by the setup.exe and this will pass any info gathered to the msi.
You need to work out what the exe passes to the msi and set them in your transform.

what's the app?

Some stubs are set up to accept a switch so that additional arguments can be passed to MSIExec. That switch is normally '/V' so it might be worth trying something like: setup /V"/L*V %temp%\MyLog.log". The log which hopefully results will contain the complete command line which was passed to MSIExec.

ORIGINAL: timmsie

in all probability there won't be any dialogs in the msi.

The dialogs will be spawned by the setup.exe and this will pass any info gathered to the msi.
You need to work out what the exe passes to the msi and set them in your transform.

what's the app?



App is Northgate Iclipse 4.42

Anyone...any more suggestions....how can I run msi non silently....

Are there any dialogs in the MSI?

ORIGINAL: VBScab

Are there any dialogs in the MSI?


No, looks like there are not dialogs, in MSI :(

How to proceed to create package in this scenario...as there are no dialogues in MSI?

ISS file creation --- This doesn't looks very promising..

Using MSI --- how?

Post the MSI to SendUit.com or similar. I'll try and take a look at it: we'll be here all week otherwise...

Thanks, I am uploading it now....

ORIGINAL: VBScab

Post the MSI to SendUit.com or similar


I have uploaded the setup.exe which extracts msi in temp location.

Also I have uploaded the extracted msi.

Iclipse MSI -->
http://www.megaupload.com/?d=F6FABF47

Iclipse Setup.exe
http://www.megaupload.com/?d=3RS2LFH0

Please take a look and let me know your comments.

Hi Ian,

Did you a chance to take a look at it?

pls suggest...THANKS

ruddy hell! are you alright? have you had a bump on the head? [:D]

ruddy hell! are you alright? have you had a bump on the head? [:D]


WHAT DID I DO?

ORIGINAL: VBScab

Running the MSI through WPS's debugger, it seems that the offending CA is ISVerifyScriptingRuntime. Conditioning-out that CA allowed the MSI to proceed past the offending message.

Be aware, though, that because the rest of the package was built in "lazy IS packager" mode, it will still require the necessary IS driver/engine (v8) to be pre-installed.



Hi Ian,

I removed the custom action, after that tried to run the msi and got the message as " To run a silent install you must either specify a response file or override this event (onMsiSilentInstall()) and provide your own implementation. setup will now end"

Yes, looks like this is installscript msi.

I have few queries, probably you can answer as you have the source media now...

1. How to package in this scenario? to create an ISS file or take a snapshot of this one.
2. can you point me to WPS debugger, I had used it years back but not recently

Many Thanks.....

ORIGINAL: VBScab

In this case, you didn't look to whom the reply was directed.


I mistakenly rated this post....

Anyway...he replied to my mail...thats why i thought the reply is directed to me

Anyway...he replied to my mail...thats why i thought the reply is directed to me Check the tiny print in the extreme right-hand side of each post. It says "(in reply to [whoever the reply is to])".

Check the tiny print in the extreme right-hand side of each post. It says "(in reply to [whoever the reply is to])".


got it....

Thanks for all your advise...

can you put light on the question of 'How to repackage this application"...what would be the best way to go........

The best way to go to re-package? Don't.

You will enter a whole new world of pain by re-packaging any install which is already an MSI. You're almost there. Keep going.

I am creating an iss file... with the help of ISS file, I can run setup.exe silently with the customizations...

Finally as we have to deliver this package in MSI format, I will call this setup.exe as a cutom action after install finalize, in my msi..

let me know your expert comments....

You already have my comments. Whether or not you choose to follow the advice therein is up to you.

Please can you suggest whether creating an ISS file is correct approach?

IMV, no, it isn't.

Condition-out the 2 CAs as discussed and re-test.

definately something going on! you should have flipped by now [;)]

What is IMV...

I have tried what you have suggested...and then msi run silently...that is fine....

but now there is a small issue, as I had told you earlier, there are no dialogues in MSI and as part of cutomizations, I have to supply some data on different dialogues as per the users requirement....

Now ..how do I do this if I try to create transform for this msi.....

http://www.acronymfinder.com/Slang/IMV.html there are no dialogues in MSI and as part of cutomizations, I have to supply some data on different dialoguesSurely part one of that sentence precludes any possible action on the second?

What customisations do you need? Obviously, you'll remove the LaunchCondition and probably change the REBOOT property to R but what else is there to customise?

if you run setup.exe....there are various options that comes as part of installation....like server name, database name and few other things,....which are displayed in different dialogues.....

As I said back in post 5, you need to identify which properties these dialogs change and add the required values to your transform

ORIGINAL: djain3

if you run setup.exe....there are various options that comes as part of installation....like server name, database name and few other things,....which are displayed in different dialogues.....


In which case you should try and capture the changes made to your system when you run the original setup.exe after you have installed your MSI using a lightweight capture tool such as PictureTaker or InCntrl. But first you will need to temporarily change the ProductCode GUID in your MSI before you install it otherwise the second (setup.exe) will think that the product is already installed and will show the Modify/Remove dialog which is not what you want.

To summarize,

1) Edit your MSI and note the value of the original ProductCode property then change it to a new GUID.
2) Install your MSI
3) Run a 'before' snapshot using a capture tool
4) Install the original setup.exe responding to dialogs as needed
5) Run an 'after' snapshot using the capture tool
6) Examine the snapshot clearing anything that is obviously junk
7) Edit your MSI and revert the ProductCode property to the value noted at step 1
8) Create a transform and incorporate the relevant changes picked up in the snapshot. Don't forget to add any LaunchConditions and REBOOT property changes if you need them.


Regards,

Spartacus

you will need to temporarily change the ProductCode GUID in your MSIIt's much quicker - and safer - to rename the relevant entry in the registry's Uninstall tree.

As to the dialogs, the set-up stub must be passing information to the MSI, unless it's installing stuff outside of that, in which case a lightweight snapshot tool is the way to go. I apologise: I was under the impression that all packagers routinely run MSI-extracting stubs after installing just the MSI in order to determine if the stub is behaving that way. I guess that what ASSUME does, right?