Server upgraded 2008 to 2012 SAN Headquarters app server log folder issue

Hello, 

 You set the log directory at installation.  Typically on a network share.   

 The log directoy you referenced looks to be the old log file directory after a SANHQ upgrade. 

 It asks if you want to archive the current log directory. 

  So it's just reading the old data files, hence the "Read Only" mode.  Since you are not connecting that client to an active SANHQ server instance. 

 Regards, 

Don 

 

Don, 

I did reinstall the SANHQ app on the active server instance a few days ago but the client only - I don't recall being asked to archive the then current log directory. Makes sense it would be in RO mode as you stated since I pointed to a network share of old log files. 

I attempted to reinstall the SAN HQ server and client but receive the following error: Thoughts? 

__________________________________________________________________________________________________________

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.FormatException: Input string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at Installer.Utilities.LogicManager.UpdateWebServiceSettings(String webServiceHostName, String webServicePort, Byte[] certificateHash)
at Installer.WizardForm.MoveToNextRetreiveStep()
at Installer.InstallStepTcpIpSettings.buttonOK_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4110.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
SANHQInstall
Assembly Version: 3.3.1002.8844
Win32 Version: 3.3.1002.8844
CodeBase: file:///C:/Users/MILTEN~1/AppData/Local/Temp/SANHQInstall.exe
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4110.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4110.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3761.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4110.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3761.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3761.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
EqualLogic.General
Assembly Version: 3.3.1002.8844
Win32 Version: 3.3.1002.8844
CodeBase: file:///C:/Users/MILTEN~1/AppData/Local/Temp/SANHQInstall.exe
----------------------------------------
System.Management
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3761.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
EqualLogic.Monitor.Common
Assembly Version: 3.3.1002.8844
Win32 Version: 3.3.1002.8844
CodeBase: file:///C:/Users/MILTEN~1/AppData/Local/Temp/SANHQInstall.exe
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

__________________________________________________________________________________________________________________
EDIT:

Google hit: RE: SANHQ 3.1 Install Problems
I used Process Monitor to identify the registry key it was checking for the version on install. I found that it was looking at the following key.

HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client\Version

Mine was 4.6.00081. I looked on a computer that only had 4.5 and the version was 4.5.51209. I plugged in the 4.5.x version value, ran the setup then changed it back to the 4.6.x value after it was finished. Worked like a charm.

 

___________________________________________________________________________________________________________

FYI: I had to install .net 4.7x a few days ago because Server Manager would not launch - seems a Google hit says SAN HQ 3.x only installs with 4.5 installed. 

Thanks, 

Milty 

 

Hello, 

 I am glad you found a work around.   It also sounds like you might not be running the current version of SANHQ, v3.4. 

 The dependency comes from MS, not specifically SANHQ.  The version of NET when the application was built needs to be installed at runtime.  

 Regards, 

Don 

 

Don, 

Its not really a workaround for me. I am concerned that uninstalling .net 4.7 and consequentially causing issues with Server Manager launching and other feature issues is not acceptable. 

Does ver 3.4 require the down level .net software to install?

Your correct, I'm not running ver 3.4 I did logon to the Dell site with my IT directors credentials attempted to download 3.4 but was notified - unauthorized - is there an alternate method/repository to download the upgrade?

Thanks, 

Bob 

Hello Bob, 

 Re: SANHQ.   No.  There is no alternate site to download SANHQ.  The support contract on the array maintains your license to download newer versions of EQL array firmware and the bundled software that goes with it.  Like SANHQ,  HIT/ME etc..   

Re: .NET.  You should not have to remove 4.7 to install the lower revision .NET framework.  MS allows multiple versions to be installed for this very reason.  

https://knowledgebase.progress.com/articles/Article/P140431

Regards,

Don 

 

I performed a full uninstall of the SAN HQ app (.net framework 4.5 and 4.7 are installed) and re-installed it successfully. I ran the add group wizard and two of my Sans are now added but the third one has a connection established message and its polling the group data but it eventually times out. I'm positive the IP address is correct I assume its have trouble with the snmp community name.

So, I attempted a Putty connection to the SAN using ssh and telnet but both give me connection refused. I assume I could directly connect a cable to the SAN. Any thoughts on why I am getting a connection refused message via Putty. Or any other reason the Add group wizard is  timing out? 

Thanks, 

Bob

 

Hello, 

 That sounds more like a network issue.  Firewall?  

  I would connect via the serial port and make sure that third group is actually online and healthy. 

 Regards, 

Don 

 

Cool! 

 Love an easy fix!! 

 Take care. 

Don