I had the same problem when upgrading from HRMS 2014 to 2015. I had a problem when just trying to upgrade w/o uninstalling the 2014 versions. So had to uninstall and reinstall the client. I found it would never remove the HRMS Client from the list. So went ahead an installed over the top of it. All seemed to go ok. It resolved the problem I ran into by just installing upgrade w/o uninstalling first and it's running fine. You may have to restart the install once or twice but it completes the install just fine. It is pointing to the new 2015 folders on the application server so presume it would point to your new server as well. If you haven't tried that yet, it's worth a shot.

Thank you for the suggestion. I will try it tomorrow and post my results here.

Good answer Roger. I too (in supporting the product) have noticed add/remove doesn’t quite do the trick all the time. The strange thing the mere existence of it in add/remove is not necessarily an impediment to the process of installing FROM a new location. If you get backed into a corner on not being able to remove the software the following steps will likely bear the most fruit.

1. remove associated key from the registry.

start/run/regedit

highlight hkey_localmachine

go to edit, find and enter hrms client

keep hitting f3 until you see an entry that looks like this.

remove the entire parent container for this.

2. then find a folder called

C:\Program Files (x86)\Sage\Sage HRMS Client

and delete it.

This should be good enough to make the computer forget it had a client on it even though there are still several places on the machine where it will still kind-of reside. If all else fails, support is your friend.

Hello,

Roger's idea may have worked when upgrading the program, but it did not work in my case when changing the SQL server. However, the good news is that John's instructions completely worked. Thank you so much for your help, You are a life saver!

Hello,

Roger's idea may have worked when upgrading the program, but it did not work in my case when changing the SQL server. However, the good news is that John's instructions completely worked. Thank you so much for your help, You are a life saver!