Issue uninstalling IMan 3.0 and installing IMan 3.2 (4 replies)
Note: According to Windows Programs and Features, Realisable IMan is not listed as installed but the behavior of the IMan 3.2 installer indicates that it detects a previous installation.
Hi Jon,
This situation can be a result of the windows installer attempting and failing a repair, this is usually caused by a tracked install file being deleted.
It's tough for me to tell what state the install is in. You may be able to re-install by deleting the IMan services using the SC DELETE command from the command prompt. Be careful with theis cpmmand and be sure you're comfortable with using it.
If you are unable to install following service deletion please drop us an email land we'll see if we can get you fixed.
I am having the exact same issue, just going from 2.0 to 3.0. Can you tell me the exact language for the command? Is it SC DELETE followed by the name of the service?
Dane, you do not want to delete the services using a command.
You want them deleted through by uninstalling the software.
If you get this error use the attached script to reinstalling any missing service(s) then uninstall.
I’m having issues uninstalling the existing IMan installation on my server. I had forgot that I had already installed IMan on the server when I tried installing IMan 3.2. The previous installation was 3.0. I remember now that you have to stop the IMan services in the IMan panel before uninstalling IMan but didn't do so this time around unfortunately. When I tried to install IMan 3.2, the installer prompted me to first stop Realisable services and processes before continuing. I did stop those using the task manager and used third party software to remove all IMan files and registry items from that server. When I try to do a fresh install of IMan 3.2, I’m given these errors: (listed in screenshots attached).
I’m not sure where the .msi installer is finding traces of the previous install. Those file paths that the errors mention above didn’t exist before I ran the installer so they must have been created during this installation before the error occurs.