This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Couple of issues upgrading to installshield 2008
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Apr 14, 2008
02:30 PM
Couple of issues upgrading to installshield 2008
I have just recently upgraded my Installscript MSI Project from Installshield X to Installshield 2008; everything seemed to work very well with Installshield X. Now that I've upgraded, when I go to install the project, the install appears to hang when registering the type libraries, however when looking at the log file, it hangs on the ISComponentServiceInstall function, and then after about an hour and 37 minutes, the rest of the log after ISComponentServiceInstall is created:
MSI (s) (74:2C) [22:04:40:303]: Executing op: CustomActionSchedule(Action=ISComponentServiceInstall,ActionType=3073,Source=BinaryData,Target=ISComponentServiceInstall,CustomActionData=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\~18.tmp;C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\~19.tmp)
MSI (s) (74:2C) [22:04:40:381]: Creating MSIHANDLE (55753) of type 790536 for thread 1580
MSI (s) (74:3C) [22:04:40:381]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI73.tmp, Entrypoint: ISComponentServiceInstall
MSI (s) (74!CC) [22:04:40:616]: Creating MSIHANDLE (55754) of type 790531 for thread 2764
MSI (s) (74!CC) [22:04:40:616]: Closing MSIHANDLE (55754) of type 790531 for thread 2764
MSI (s) (74!CC) [22:04:40:631]: Creating MSIHANDLE (55755) of type 790531 for thread 2764
MSI (s) (74!CC) [22:04:40:631]: Closing MSIHANDLE (55755) of type 790531 for thread 2764
MSI (s) (74!CC) [22:04:40:631]: Creating MSIHANDLE (55756) of type 790531 for thread 2764
MSI (s) (74!CC) [22:04:40:631]: Closing MSIHANDLE (55756) of type 790531 for thread 2764
MSI (s) (74!CC) [22:04:40:631]: Creating MSIHANDLE (55757) of type 790531 for thread 2764
MSI (s) (74!CC) [22:04:40:631]: Closing MSIHANDLE (55757) of type 790531 for thread 2764
MSI (s) (74!CC) [22:04:40:647]: Creating MSIHANDLE (55758) of type 790531 for thread 2764
MSI (s) (74!CC) [22:04:40:647]: Closing MSIHANDLE (55758) of type 790531 for thread 2764
MSI (s) (74!CC) [23:41:02:141]: Creating MSIHANDLE (55759) of type 790531 for thread 2764
MSI (s) (74!CC) [23:41:02:157]: Closing MSIHANDLE (55759) of type 790531 for thread 2764
MSI (s) (74!CC) [23:41:02:157]: Creating MSIHANDLE (55760) of type 790531 for thread 2764
MSI (s) (74!CC) [23:41:02:157]: Closing MSIHANDLE (55760) of type 790531 for thread 2764
Basically after the build continues past the hour and a half hang, the COM package is installed and seems to work okay. When the build is hanging at this step, even if I click Cancel, it still hangs and finishes the step after the hour and a half. Very weird, specially since there aren't any errors that pop up or are logged; nor does component services log any error when its logging is turned on. Also there are no errors in the event viewer.
Another odd thing is that the Installshield property values I set in my OnFirstUIBefore installscript function, which are set properly and can even be accessed later on within that function, somehow get reset to their defaults when I try to access them later in a separate function called after the client piece is installed (the function I call in the Client feature's OnInstalled property). I'm not sure if this has something to do with separate threads doing the install or what.
Does anyone have any ideas on either issue above? I'm really stuck on this one and it has been frustrating since there is no error message or anything to point me in a certain direction.
MSI (s) (74:2C) [22:04:40:303]: Executing op: CustomActionSchedule(Action=ISComponentServiceInstall,ActionType=3073,Source=BinaryData,Target=ISComponentServiceInstall,CustomActionData=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\~18.tmp;C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\~19.tmp)
MSI (s) (74:2C) [22:04:40:381]: Creating MSIHANDLE (55753) of type 790536 for thread 1580
MSI (s) (74:3C) [22:04:40:381]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI73.tmp, Entrypoint: ISComponentServiceInstall
MSI (s) (74!CC) [22:04:40:616]: Creating MSIHANDLE (55754) of type 790531 for thread 2764
MSI (s) (74!CC) [22:04:40:616]: Closing MSIHANDLE (55754) of type 790531 for thread 2764
MSI (s) (74!CC) [22:04:40:631]: Creating MSIHANDLE (55755) of type 790531 for thread 2764
MSI (s) (74!CC) [22:04:40:631]: Closing MSIHANDLE (55755) of type 790531 for thread 2764
MSI (s) (74!CC) [22:04:40:631]: Creating MSIHANDLE (55756) of type 790531 for thread 2764
MSI (s) (74!CC) [22:04:40:631]: Closing MSIHANDLE (55756) of type 790531 for thread 2764
MSI (s) (74!CC) [22:04:40:631]: Creating MSIHANDLE (55757) of type 790531 for thread 2764
MSI (s) (74!CC) [22:04:40:631]: Closing MSIHANDLE (55757) of type 790531 for thread 2764
MSI (s) (74!CC) [22:04:40:647]: Creating MSIHANDLE (55758) of type 790531 for thread 2764
MSI (s) (74!CC) [22:04:40:647]: Closing MSIHANDLE (55758) of type 790531 for thread 2764
MSI (s) (74!CC) [23:41:02:141]: Creating MSIHANDLE (55759) of type 790531 for thread 2764
MSI (s) (74!CC) [23:41:02:157]: Closing MSIHANDLE (55759) of type 790531 for thread 2764
MSI (s) (74!CC) [23:41:02:157]: Creating MSIHANDLE (55760) of type 790531 for thread 2764
MSI (s) (74!CC) [23:41:02:157]: Closing MSIHANDLE (55760) of type 790531 for thread 2764
Basically after the build continues past the hour and a half hang, the COM package is installed and seems to work okay. When the build is hanging at this step, even if I click Cancel, it still hangs and finishes the step after the hour and a half. Very weird, specially since there aren't any errors that pop up or are logged; nor does component services log any error when its logging is turned on. Also there are no errors in the event viewer.
Another odd thing is that the Installshield property values I set in my OnFirstUIBefore installscript function, which are set properly and can even be accessed later on within that function, somehow get reset to their defaults when I try to access them later in a separate function called after the client piece is installed (the function I call in the Client feature's OnInstalled property). I'm not sure if this has something to do with separate threads doing the install or what.
Does anyone have any ideas on either issue above? I'm really stuck on this one and it has been frustrating since there is no error message or anything to point me in a certain direction.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
May 27, 2008
11:36 AM
I upgraded InstallShieldX to 2008 and had the same problems. Everything was working great in X, back to the drawing board in 2008. If I understood the documentation correctly IS2008 no longer uses IDriver and the events cannot access the propeties or only have access to the original value.
I changed my InstallScript functions called in OnInstalled and similiar events to custom actions: I modified the code to export prototype and added them to the Custom Action list, immediate execution. I inserted them after InstallFinalize and they seem to be working again. This may not be the best way to do it but I needed to get the installer working ASAP.
The documentation said to change them to Defered Execution in System Context but you have to pass all the properties in CustomActionData and parse them back out, use the registry to pass parameters or some other method to get the modified properties.
I found the following links after much searching. It was for InstallShield12 but helped me out.
http://community.installshield.com/showthread.php?t=169870
http://community.installshield.com/showthread.php?t=167564
I changed my InstallScript functions called in OnInstalled and similiar events to custom actions: I modified the code to export prototype and added them to the Custom Action list, immediate execution. I inserted them after InstallFinalize and they seem to be working again. This may not be the best way to do it but I needed to get the installer working ASAP.
The documentation said to change them to Defered Execution in System Context but you have to pass all the properties in CustomActionData and parse them back out, use the registry to pass parameters or some other method to get the modified properties.
I found the following links after much searching. It was for InstallShield12 but helped me out.
http://community.installshield.com/showthread.php?t=169870
http://community.installshield.com/showthread.php?t=167564
