1

I had an InstallShield 2011 project (A) that installs a service, and copied this project to use for another project (B) that installs a different service.

During uninstall, it seems like if either (A) or (B) is installed, the service uninstalls and is removed from the Services list. However, if BOTH (A) and (B), then (B) is not being removed from the Services list on uninstall. The actual files are being deleted, so when I right click to Start the service, it says that the file could not be found.

I updated the Product Code and Upgrade Code on the General Information page of the project, and updated the Key Name in Setup Design - Advanced Settings - Services - [My Service] when copying the InstallShield project.

Are there any other shared items that could be affecting the uninstall?

jkh
  • 3,618
  • 8
  • 38
  • 66

1 Answers1

1

The component GUIDs could be shared too. This is most likely the source of your problems. As a practice, you should NEVER copy a project and use to create a setup project for another similar product, this is the easiest way to miss updating some GUIDs that must be unique and have your packages behave incorrectly.

I don't know if InstallShield has the option, other tools do have it, but the recommended method is to create a project template from the first one (A), then create a new project from that template, case in which IS should make sure that you get new unique GUIDs for all sensitive areas from the package.

Bogdan Mitrache
  • 10,536
  • 19
  • 34
  • When saving the InstallShield project as a template and creating a new project from a template, the Product/Upgrade codes change, but the Component Codes remain the same. Do they need to be unique across multiple projects? – jkh Jan 16 '14 at 14:01
  • Component GUIDs should be unique too. If you want to have certain files shared between both application and have the some GUIDs for the components a better option would be to build a merge module and add that merge module in both project. But, if the projects are considered to build packages completely separate then you should have unique GUIDs for the components. – Bogdan Mitrache Jan 16 '14 at 14:09