09/25/2009 3544 views
Hi guys,

I'm having an issue with one of the packages I'm working on. Long story short it's an in-house app that's supposed to install a service called Toledo Transfer to monitor a scale. Whilst installing the package on a clean machine poses no problem at all, an upgrade of previous versions causes the Installer to hang at a certain point. I mean no more movement, logging stops. At this time a Toledo Transfer service seems to start, however, instead of being linked to T-Automatique.exe, as it should be, it's linked to a process called MSI##.tmp (the #'s are random characters).

At this point I have to manually kill that erroneous MSI##.tmp process for the installation to continue. The loggings seems to "catch up" when I do and the installer continues to a succesful completion. In the end the service does get installed and started up. When I go look at the log I see the time gap occurs in an action called UninstallTAutomatique, which is not one of my Custom Actions. Is this linked to the service manipulations perhaps?

I know I could probably replace the Installshield Service stuff by calling SC.exe or something, but I want to figure this out, I'm stubborn that way.

So to recap

InstallShield 2009
NT Service Install function (on the component that contains the .exe)
logging stops (at UnregisterComPlus)
I kill the MSI##.tmp process
Logging catches up and install finishes.

Hope you guys can help, if you need extra info, please ask.

0 Comments   [ + ] Show comments


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

All Answers

Ok, just had a bit of a discovery

It would seem the UninstallTAutomatique action stems from the uninstall of one of the old MSI's for that application... Not from my package. Gotta love having to update "legacy" MSI's (as in made by my predecessors...)

that's a whole day I'll never get back...[:@]


Answered 09/25/2009 by: pjgeutjens
Red Belt