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
- :
- Major Upgrade, change of INSTALLDIR and Installer CA = Error 1001
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
Oct 18, 2012
05:06 AM
Major Upgrade, change of INSTALLDIR and Installer CA = Error 1001
We are having issues with the following scenario:
We have a product which we have changed the default installdir on. We have added a major upgrade item for the previous version (and verified that this new version is executed as a major upgrade in MSI Validator). The project contains several Installer dlls (Installer Class), and we are experiencing Error 1001 during upgrade.
In the log we find the following:
Action 11:51:35: _70AFA579B2F851B352EC17A9F23A00AB.install.
MSI (s) (78:C8) [11:51:35:517]: Executing op: CustomActionSchedule(Action=_70AFA579B2F851B352EC17A9F23A00AB.install,ActionType=3073,Source=BinaryData,Target=ManagedInstall,CustomActionData=/installtype=notransaction /action=install /LogFile= /allusers=1 "C:\Program Files (x86)\Company\ML\CA-Install-OML.dll" "C:\Users\Admin\AppData\Local\Temp\{6B750DCC-0B02-41CC-B39C-77ED2A434794}\_isconfig.xml")
MSI (s) (78:D8) [11:51:35:532]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI3119.tmp, Entrypoint: ManagedInstall
Error 1001.
MSI (s) (78!20) [11:52:50:939]:
MSI (s) (78:D8) [11:52:50:939]: Leaked MSIHANDLE (128) of type 790531 for thread 2336
MSI (s) (78:D8) [11:52:50:939]: Note: 1: 2769 2: _70AFA579B2F851B352EC17A9F23A00AB.install 3: 1
Info 2769.Custom Action _70AFA579B2F851B352EC17A9F23A00AB.install did not close 1 MSIHANDLEs.
CustomAction _70AFA579B2F851B352EC17A9F23A00AB.install returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 11:52:50: InstallFinalize. Return value 3.
The Installer CA runs perfectly when just installing. If we try to disabling this CA, the error just occur at the next Installer CA
Using process monitor we found that MSI attempted to access the previous InstallState file.
Anyone have any idea of why this is happening and can share some wisdom about this matter?
We have a product which we have changed the default installdir on. We have added a major upgrade item for the previous version (and verified that this new version is executed as a major upgrade in MSI Validator). The project contains several Installer dlls (Installer Class), and we are experiencing Error 1001 during upgrade.
In the log we find the following:
Action 11:51:35: _70AFA579B2F851B352EC17A9F23A00AB.install.
MSI (s) (78:C8) [11:51:35:517]: Executing op: CustomActionSchedule(Action=_70AFA579B2F851B352EC17A9F23A00AB.install,ActionType=3073,Source=BinaryData,Target=ManagedInstall,CustomActionData=/installtype=notransaction /action=install /LogFile= /allusers=1 "C:\Program Files (x86)\Company\ML\CA-Install-OML.dll" "C:\Users\Admin\AppData\Local\Temp\{6B750DCC-0B02-41CC-B39C-77ED2A434794}\_isconfig.xml")
MSI (s) (78:D8) [11:51:35:532]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI3119.tmp, Entrypoint: ManagedInstall
Error 1001.
MSI (s) (78!20) [11:52:50:939]:
MSI (s) (78:D8) [11:52:50:939]: Leaked MSIHANDLE (128) of type 790531 for thread 2336
MSI (s) (78:D8) [11:52:50:939]: Note: 1: 2769 2: _70AFA579B2F851B352EC17A9F23A00AB.install 3: 1
Info 2769.Custom Action _70AFA579B2F851B352EC17A9F23A00AB.install did not close 1 MSIHANDLEs.
CustomAction _70AFA579B2F851B352EC17A9F23A00AB.install returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 11:52:50: InstallFinalize. Return value 3.
The Installer CA runs perfectly when just installing. If we try to disabling this CA, the error just occur at the next Installer CA
Using process monitor we found that MSI attempted to access the previous InstallState file.
Anyone have any idea of why this is happening and can share some wisdom about this matter?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Nov 02, 2012
04:03 AM
did you check this
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)