VM manager upgrade failed and can install again - Critical

Usage and Config
1

Hi i aḿ using the bigfix 9.5.8.38 on windows server 2016.

The default vm manager was not working, so i tried do upgrade with the fixlet upgrade vm manager 9.2.18.0, the fixlet erased the original vmmanager and failed to install the new one.

After that i tried to install with the instalation fixlet and it keeps failing. It fails before the download.

Is it possible to reintall throught the original fixlet? I tried but the files don´t exist to download anymore.

Any one can help, tomorow our company will be audited.

Thanks

2

Download links of the installation fixlet are working, can you screenshot the action info, to see which line of the action script is failing? Please double check the free disk space on the target computer as well.

You can also try to run the uninstall fixlet, in case some references of the VM manager are preventing the installation to succeed.

3

it fails with exit code 32, i attached the action but it is big

action failed
action failed861×607 155 KB

the uninstall fixlet is grayed out

thanks

4

IMHO the “BES Client\LMT\VMMAN” folder is being used by some process, probably the VM manager service itself. Check if the service “IBM VM Manager Data Collector” still exists: if it does, stop it. If it doesn’t, check if prunsrv.exe is running on the server and kill it eventually. Then, re-run the fixlet.

1 Like
5

it worked thanks a lot.