Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Remove a files while downgrading..

Created: 05 Oct 2012 | 11 comments

I am using wise installer Editior 7.0

In this i have faced a problem serives doesnot remove while downgrade.

Steps i followed:

  • Installed lower version product.
  • Do upgrade.
  • while uninstalling downgrade process, first i remove the high version and then lower version.
  • In that some services are newly available in higher version, so those services removing process also handled in higer version only.
  • While doing the downgrade, my last uninstallation process is lower version product in that i didnot handle the services removing process.
  • So, at last those services are remain available in services list.

Please solve this.....

Advance Thanx..........

Comments 11 CommentsJump to latest comment

EdT's picture

Your posting does not make any sense. How can you uninstall a downgrade process?

Also, is your upgrade a minor or major upgrade?

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

sathish046's picture

Uninstalling in downgrade process means..

first i uninstall latest version and then older version(Reverse of upgrade installation) ...

My upgrade is major.................

EdT's picture

If you have written a major upgrade correctly then the upgrade replaces the existing installation and you should only need to uninstall the most recent version to uninstall everything. If this is not happening then the upgrade is flawed and needs to be fixed.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

piyushnasa's picture

Check if the service is still running at uninstall. You might have to kill process to remove the service.

Piyush Nasa Altiris Certified Professional (ACP)

http://msiworld.blogspot.com/

sathish046's picture

Hi Piyushnasa,

i already handled the services stop and delete process in uninstallation, but it's work's only in fresh installation not in upgrade.

EdT's picture

This further suggests that the upgrade is not written correctly.

Can your major upgrade perform a first time install of the application without the older version being present already?

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

piyushnasa's picture

Add Service Stop and Delete at install time as well in your package. This will make sure that is the service exists, it will stop and delete it. Then it will create the service again.

If this does not work, then just add Service Stop at install time as well. If the service name is different from the current one then you will have to add another entry.

Piyush Nasa Altiris Certified Professional (ACP)

http://msiworld.blogspot.com/

sathish046's picture

Hi,

i already handled the services stop and delete process in installation time, but that not working properly.

There is any way to delete the services using services name from scripting side.i.e msi script.

EdT's picture

The ServiceControl and ServiceInstall tables exist specifically to manage services. Please refer to the help file MSI.CHM to read more about the capabilities of these tables.

There is also no reason why you cannot script custom actions to handle the services and apply the appropriate conditions so that the actions only run on uninstall (or only during install)

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

piyushnasa's picture

Just before you trigger the upgrade, just check in Task manager if there is a process running related to your application/service.

I would suggest you to kill that process and then do an upgrade and see.

If it works you can place the vbs just before RemoveExistingProducts (REP). REP should be placed just before InstallInitialize action.

You can use the vbs here:

http://msiworld.blogspot.com.au/2012/03/vbscript-to-kill-process.html

Piyush Nasa Altiris Certified Professional (ACP)

http://msiworld.blogspot.com/

EdT's picture

The VBScript referenced by Piyush above will not work in a custom action, because it uses Wscript.sleep to create a delay. The Wscript.sleep method is not supported in Windows Installer's vbscript implementation, so if you want to add delays, the method using "ping" is much more reliable.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.