HPE 3PAR SRA upgrade from 6.1 to 6.5 failed with an Error - "Error1001.InstallUtilLib.dll:Unknown error"

I was working on upgrading HPE 3PAR SRA from 6.1.0 to 6.5 on VMware SRM 6.1 which was installed on Windows 2012 server. It was supposed to be straight forward process. Uninstall old SRA and install new SRA using the .msi file. That's it!

When I logged into SRM server (windows 2012) to uninstall the HEP 3PAR SRA old version (6.1.0.170) using control panel - uninstall program feature. HPE 3PAR SRA did not show up in the program list in programs and features.

I tried to install the SRA 6.5 directly but it failed with an error - Error1001.InstallUtilLib.dll:Unknown error.

Ok, so I thought of installing the 6.1 version. When I tried that it said the product is already installed on this server.

Then I started digging into it more. I deleted all the entries that had HPE 3PAR 6.1.0.170 from registry, rebooted the SRM server - tried to install the SRA 6.5 - same error -Error1001.InstallUtilLib.dll:Unknown error.

Then I started looking out for Error1001.InstallUtilLib.dll:Unknown error. There were few solutions - some of them said its related to .net frame work.

As per 3PAR SRA documentation that I read initially, it mentioned that .net framework is not needed if the SRM server is on 2012, which was in my case. But just to play around I installed the .net framework on the SRM server, rebooted the server and tried the SRA install again. And viola! I was able to install the SRA successfully this time. When I read the 'read me' file that showed up after completing the successful install - the first prerequisite was to have the .net framework.

So to conclude,

For HPE 3PAR SRA 6.5 - .net framework is needed while installing SRA 6.5. You won't be able to install the SRA 6.5 without .net framework.

For HPE 3PAR SRA 6.1 - With SRA 6.1, even if you don't have the .net framework installed on the SRM server, the SRA will get installed successfully but it won't show up in program and features in control panel.

Comments

Guest Introspection(GI) NSX Appliance gets Deleted Automatically after vCenter Disconnect

I was working in an environment where NSX was configured with Trend micro deep security in VDI environment to protect VDI desktops. We had 2 vCenters setup in that way and one of the vCenter is showing some odd symptoms. We are seeing some weird actions with NSX manager in one vCenter. So, I lose the connection to the vCenter from fat client, web client is still fine and doesn’t kick me off. In the process, the Guest Introspection appliance or GI VMs (appliance managed by NSX) from some random hosts were getting deleted automatically - from the cluster that was protected with NSX. When I checked the windows logs (as vCenter was on windows server) this is what I saw - I opened a case with VMware support - They reviewed the NSX logs and came to conclusion that this is not the NSX issue but it's vCenter that is deleting those VMs. vCenter gets disconnected for few seconds, then connects back. It doesn't recognizes those GI VMs and starts de...

How to Check Up Time of ESXi Host or Virtual Machine from vCenter Server

To check up time of ESXi host from vCenter server - Logon to vCenter Server - If using C# (fat) client - click on cluster - on right side pane click on Hosts - select the up time option by right clicking on the header. The column will be added at the end. You can drag and drop column to place it in your view. If using HTML client - click on cluster - on right side pane click on Hosts - select the up time attribute from show/hide column by clicking on the header If using web (Flash) client - click on cluster - on right side pane click on related objects - hosts - right click on the header to show/hide column - click on up time attribute Similarly, you can check the up time for a virtual machine by clicking on the virtual machine tab instead of host tab, but only caveat is vCenter gives you up time of a virtual machine according to reboots performed from the vCenter. So, rather than rebooting server fr...

VMWare ESXi Host showing Up Time as 0 second

I have seen this more on 5.5 ESXi hosts but the host shows the up time as 0 seconds and CPU and Memory percentage as 0% Easiest way to resolve this is to put the host in maintenance mode and then restart the management agents on the ESXi hosts. #esxcli services.sh restart But to be more cleaner I prefer to put host in maintenance mode and reboot the host to get the clean state.

Virtualization Blog

Search This Blog