Unable to Update previous version
There's no update option in my TP installer. What should I do to upgrade?
Upgrading TargetProcess is easy. All you need to do is run setup.exe, hit “Next” a couple times, and enjoy your coffee while the installer does the job.
However, it might seem a bit more tricky if for some reason you don’t see the “update previous version” option, and the system is about to install a new instance of TargetProcess. Let’s see how to troubleshoot this.
To upgrade correctly, the system should know some details about the current installation, e.g. the current version, the path, etc. TargetProcess stores that information in registry. If you happened to have moved the TargetProcess app just by copying the files to another location, AND no registry information has been moved (and it just can’t be moved that way), the installer will get stuck.
See how to move the application correctly from one server to another in this article:How to move Targetprocess from one server to another
If you’re facing the “no upgrade option” issue right now, one of the ways to resolve it is to let the installer run elsewhere, then restore the database ( the old version ) and re-run the installer to update the database.
However, in some cases this is not possible, and you’d need to update the registry on your server. Run the regedit program and go to:
HKEY_LOCAL_MACHINESOFTWAREWow6432NodeTargetProcessTargetProcess2 ( for 32-bit systems skip the “Wow6432Node” part of the path)
If you have access to the old server, you can export the properties to a .reg file and then run it on the new server. Before running the reg file, please edit it and make sure the values are correct there.
Here’s how your registry should look before you run the upgrade:
|iissrv||the name of the Web Site at IIS|
|path||the location where the application files are stored|
|version||the build number you’ve had before the upgrade|
|vfolder||IIS virtual folder. If you install TargetProcess to the root of the web site, the key should be left blank|
Make sure that all the information is valid before running the upgrade. In general, updating the registry manually is a risky approach.If you specify the wrong data, e.g. an incorrect virtual directory, the installer will try to create a new one and this might break the current installation.