Can't install/upgrade to SAN HQ v2.5 - Unexpected error -
I get this error after I tried upgrading and doing a fresh install of SAN HQ v2.5 on my SAN HQ server; but have no problem installing SAN HQ v2.2 The install seems to work fine, and when I try to open the SAN HQ client I receive the above error.
I just built a new server and installed the new SAN HQ Server v2.5, and right when it finishes installing, I get the same above error.
No, I only have NET 4.0 installed. I first tried the upgrade on my original SAN HQ server, and received the error above. I then tried to unintall and reinstall; installing 2.5 on a fresh copy, received the same error.
So just for fun, I built a new server today from scratch; Server 2008 R2. Imediatly after adding it to the domain, I installed SAN HQ 2.5, the install went through, and when it tried to automactilly open SAN HQ client, I got the same error, which really supprised me.
I tried Java 6 Update 31, 36, 37; still no luck, getting the exact same error as above.
I appreciate all the tips everybody, keep them coming and lets see if we can solve this one together. I am out here in Afghanistan right now, so I have all the time in the world to try to fix this issue.
I removed everything that even mentioned SAN HQ in the registry; and folders; reinstalled, still got the same problem.
Now my question is, what program installs the path C:\Cygwin\buildarea , as my old server I tried to upgrade and the new server that I did a fresh install did not have the Cygwin path that the error refers to?
I ran into this exact same issue. Ended up renaming the 'Equallogic' folder (or you can delete) under program files and also the Registry folder. After this I attempted a re-install and was able to get past the prompt. If you have a case open with EQL I might be able to dig up a case# to reference for you.
napalmer7
9 Posts
1444
1
Posted January 3rd, 2013 13:00
Crowlaw, can you verify if your systems are configured for FIPS compliancy? The easiest way to check this is to look at this registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy\Enabled
If this entry is set to 1 then I would recommend you try temporarily changing it to 0 to see if that lets you launch the SANHQ Client.