RG028 – Fixing a Automation Manager agent uninstall issue

By Max Ranzau


Here’s a rare problem that I’ve stumbled uppon a couple of times. I reported earlier how to clean out the ID of the agent earlier in this post. However, in my lab environment I had recently been messing around with my Agents machines (no, I did not treat them very nice). Anyway lo and behold – something broke. When trying to push-deploy the Wisdom Agent to the target machine, I got the following error every time:

Let me just repeat it in clear text for the search engines: 58% Failed to uninstall Agent (1612 – The installation source for this product is not available – Verify that the source exists and that you can access it.)

It would appear that I litteraly managed to render my Wisdom Agent FUBAR. In other words, the Wisdom Agent normally uninstalls nice and clean, but this is a special situation.

The way I managed to fix the situation was to clean out all the gunk in the registry that had anything remotely to do with the Wisdom Agent, as the errormessage indicates that something is pointing somewhere wrong. To spare you the hassle of searching yourself, below is an overview of the keys I nuked:

  • HKCR\Installer\Products\65EF6217F775DC24E91B3D4EFBEDAFA9 (delete this key and all subkeys)
  • HKLM\ControlSet002\Services\RESWAS (delete this key and all subkeys)
  • HKLM\ControlSet002\Enum\Root\LEGACY_RESWAS /s  (btw, this one couldn’t be deleted as it was locked. Doesn’t seem to matter in the end though)
  • HKCR\TypeLib\{354A5F15-E707-4A54-B09E-FE3219D4DFF9} (delete this key and all subkeys)
  • HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Folders (delete only the two following values:)

“C:\\Program Files\\RES Wisdom\\Agent\\”=””

“C:\\Program Files\\RES Wisdom\\”=””

  • HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\65EF6217F775DC24E91B3D4EFBEDAFA9 (delete this key and all subkeys)
  • HKLM\SOFTWARE\RES\Wisdom (delete this key and all subkeys)
  • HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WUID\Default
  • Finally, delete all the files located below %programfiles%\RES Wisdom\Agent and reboot.

Now it may very well be that only one of the above are necessary to fix the problem,  nevertheless rest assured your target machine has been cleansed for all the Install registry keys. Next time I deployed the agent from the Wisdom Console everything went swimmingly.

Finally – I’d love to have provided you with a buildingblock to fix these registrysettings, but it doesn’t really fly when you think about it: There’s no way it’s ever going to run in the first place, when the agent is broke :-)

No Comments

No comments yet.

RSS feed for comments on this post.

Leave a comment

You must be logged in to post a comment.