Repackaging Cisco CRS Historical Reports
I am trying to repackage Cisco CRS Historical Reports using Installer Design Studio (the application is in an installshield executable format). I repackage into .msi format then run against my clean image. I logoff from the account that installed the package then logon under another account (w/ user or admin rights). The windows installer kicks off right away when logging in. The following messages are posted in event viewer under application:
Event ID: 1001
Source: msiInstaller
Event ID: 1001
Source: MsiInstaller
Detection of product '{AA497A6E-1996-4655-98AD-675A97962961}', feature 'MainFeature' failed during request for component '{7C2B93E9-B927-4786-9720-576833BA943E}'
Event ID: 1004
Source: MsiInstaller
Detection of product '{AA497A6E-1996-4655-98AD-675A97962961}', feature 'MainFeature', component '{79A6468D-4CF3-45E8-9F91-9FFDC8364486}' failed. The resource 'HKEY_CURRENT_USER\Software\Scriptlogic\InstallerDesignStudio\Save\' does not exist.
I tried to use Active Setup to add these components silently but Windows Installer runs anyway. Is there from running as soon as the user logs in but it still runs anyway. Is there anyway I can prevent this from happening, maybe by just having Windows Installer run when someone double clicks on the application icon? By the way the component {79A6468D-4CF3-45E8-9F91-9FFDC8364486} has shortcuts that point to the main program executable, launchHRC.exe. Thank you.
-Dan
Event ID: 1001
Source: msiInstaller
Event ID: 1001
Source: MsiInstaller
Detection of product '{AA497A6E-1996-4655-98AD-675A97962961}', feature 'MainFeature' failed during request for component '{7C2B93E9-B927-4786-9720-576833BA943E}'
Event ID: 1004
Source: MsiInstaller
Detection of product '{AA497A6E-1996-4655-98AD-675A97962961}', feature 'MainFeature', component '{79A6468D-4CF3-45E8-9F91-9FFDC8364486}' failed. The resource 'HKEY_CURRENT_USER\Software\Scriptlogic\InstallerDesignStudio\Save\' does not exist.
I tried to use Active Setup to add these components silently but Windows Installer runs anyway. Is there from running as soon as the user logs in but it still runs anyway. Is there anyway I can prevent this from happening, maybe by just having Windows Installer run when someone double clicks on the application icon? By the way the component {79A6468D-4CF3-45E8-9F91-9FFDC8364486} has shortcuts that point to the main program executable, launchHRC.exe. Thank you.
-Dan
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
nheim
18 years ago
Hi Dan,
seems to me, that you got a mess with the user setting here. You have User Settings in the main feature, which tries to install the hole app each time. Also check, if the components key-regkey exists.
Please read the following:
http://itninja.com/question/distribution-message21
http://www.ewall.org/index.php?module=ContentExpress&func=print&ceid=23
Regards, Nick
seems to me, that you got a mess with the user setting here. You have User Settings in the main feature, which tries to install the hole app each time. Also check, if the components key-regkey exists.
Please read the following:
http://itninja.com/question/distribution-message21
http://www.ewall.org/index.php?module=ContentExpress&func=print&ceid=23
Regards, Nick
Posted by:
danr29
18 years ago
Yeah the problem is that the shortcuts to launch the installation have the launchHRC.exe file as their filepath and then there's another component that has a shortcut (an installshield uninstall file) the has the HKCU registry value as it's keypath. Can I just move these 2 components over to the Current User feature as discussed in the 2 articles you posted above and will everything work ok then? Or do the shortcuts that launch the application have to have this registry value as it's keypath?
Posted by:
nheim
18 years ago
Hi dan,
the shortcuts will not be a problem, as long as they are not mixed up in wrong component.
That means, you should look at it from the component level.
A component must not have entries for machine AND user context.
A component with a shortcut for the Desktop or the StartMenu can't have a keypath to the HKCU which is users context, because the shortcuts could go to AllUsers Profile (that's machine context) or the Current Users Profile (that's users context). This depends on the ALLUSERS property.
Such shortcuts should be put to the same component as the exe-file and the key pointing also to the exe.
An shortcut for unistall should be threated with the same rules. But wait a minute! What is this shortcut good for? You most likely don't need that anymore, because uninstall is done trough Windows Installer now! Just delete it!
Regards, Nick
the shortcuts will not be a problem, as long as they are not mixed up in wrong component.
That means, you should look at it from the component level.
A component must not have entries for machine AND user context.
A component with a shortcut for the Desktop or the StartMenu can't have a keypath to the HKCU which is users context, because the shortcuts could go to AllUsers Profile (that's machine context) or the Current Users Profile (that's users context). This depends on the ALLUSERS property.
Such shortcuts should be put to the same component as the exe-file and the key pointing also to the exe.
An shortcut for unistall should be threated with the same rules. But wait a minute! What is this shortcut good for? You most likely don't need that anymore, because uninstall is done trough Windows Installer now! Just delete it!
Regards, Nick
Posted by:
danr29
18 years ago
Yeah I know that shortcut points to the Installshield uninstaller. I have removed that shortcut and I realized after moving over my per-user components to the new feature they still pointed to the feature they were originally part of. So after pointing them to the CurrentUser feature and advertising the shortcuts the application worked great!
Thanks for all of your help.
-Dan
Thanks for all of your help.
-Dan
Posted by:
nheim
18 years ago
Hi dan,
good to read, that it worked out for you.
Keep packaging. :-)
Regards, Nick
good to read, that it worked out for you.
Keep packaging. :-)
Regards, Nick
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.