I am working on an MSI provided by For The Record. http://www.fortherecord.com/page.asp?PageID=243 The msi has been set to require that you run setup.exe and not the msi directly. I have worked past that part and I can get the msi to install most of the way until it fails after it installs a service and tries to start that service. I opened the msi in orca and looked at the service control table and noticed that the event for the service was set to 1. I changed it to 2 and now the msi will complete the install without any errors but if you manually try to start the service it fails. Is there a way to disect the setup.exe to see what it is doing?

Any ideas? I'm starting to really get annoyed with vendors who provide programs packaged in an msi but require you to run setup.exe to install the program. [:@] It seems it's becoming a fad. Also the setup.exe does not support any type of silent install. I hate the idea of having to repackage an msi.

Thanks
Joe
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
Does the System Event Log give any additional information as to why the service failed to start ? Events from the Service Control Manager (if there are any) may help you.

Also, you could try the following. Install the application using the legacy installer (setup.exe) and inspect the following key in using regedit

[font="Courier New"]HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\<Name of Service>

Next, on another clean machine, install the application using just the MSI (use the one where you amended the service control table to allow the install to complete) and inspect the same registry key.

The registry value "Start" under this key will probably be different when you compare the two, but any other differences are what really are of interest here.

Check the ImagePath value under the above key and make sure whichever file is set in this value actually exists on the system following the second installation outlined above.


Regards,

Spartacus
Answered 07/04/2006 by: spartacus
Black Belt

Please log in to comment
0
I checked in the registry where you suggested and discovered that there is a whole key missing. Adding the missing key does not appear to fix the problem. Who knows what else could be missing.[:'(]

Playing with this app I have discovered what I think is an install script msi. I would like to find some more information on what this means. But it looks like these are not true MSIs and cannot be installed as such since the logic is contained within the setup.exe?

Thanks
Joe
Answered 07/05/2006 by: joedown
Second Degree Brown Belt

Please log in to comment
0
Hi joe,
this is an Installshield9 MSI. You where on the right track, it requires ISScript9.Msi as prerequisite. But be aware of the problems that arise with the install of this type of MSI's. Please search around this forum to get feeling for this.
Regards, Nick
Answered 07/06/2006 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
I've been doing some reading about these ISScript files but it hasn't really been clear to me what the best practice is for making these install silently. Doing a snapshot does not seem to be the right method. Following the article here http://support.installshield.com/kb/view.asp?articleid=Q108166 does not work for this application although it has worked in the past for other programs that required an isscriptX.msi to install. BTW this one uses isscript1150.msi.
Answered 07/11/2006 by: joedown
Second Degree Brown Belt

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