/build/static/layout/Breadcrumb_cap_w.png

creating an upgrade package with services

HI!

I'm trying to craete an upgrade package in wise package studio 4.61 and I'm experiencing the following error:

When I first install the original package, a service is started. If I run my update, this service is removed during the step "RemoveExistingProducts".

I even made a test upgrade package that was an excact copy of the original package. The only thing I changed was the version of the application and I added the upgrade information. Even in this case the service is removed when I run the update. Any sugestions why?

Thanks,
Hendria

---- Addition ----

I've found out some more about this issue:

The original installation uses several custom action to handle services. Rather stupid, since the ServiceControl has not been used to do this. Anyway, one of these custom actions deletes the service, when condition REMOVE~="ALL" is true. Apparaently, this condition is also true when RemoveExistingProducts is executed, and during this Action, custom actions of the previous install are also executed. During the Action RemoveExistingProducts, the service is dleted and this is most likely caused by this custom action.

When I remove this custom action from the original application, the service is not removed. However, I'm not allowed to do this, since the original package needs te remain unchanged. I'll have to find a workaround. Suggestions are still very welcome.

Hendria

0 Comments   [ + ] Show comments

Answers (0)

Be the first to answer this question

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ