Sys Mgr 3.0RC1 - Unable to load storage information from the configuration file

[gcaley]

Hi all,

I've an 8.2 2-node vsim, and I installed System Manager 3.0RC1, under Windows 7 with 64-bit JRE7.

When I start system manager, i add my cluster to the inventory and then double click to login.

I then get a popup saying 'Unable to load storage information from the configuration file' The details of which are below.

Any ideas, I have tried what is suggested below, but still not working? Thanks.

==ERROR==

java.lang.Throwable

==TIME==

2013-06-30 10:00:25,565

==MESSAGE==

Unable to load storage information from the configuration file.

==DETAILS==

Storage information is not available in configuration file or OnCommand System Manager configuration file is corrupted.

==CORRECTIVE ACTION==

Do the following: <Br> Refresh inventory page <Br> Delete the storage systems and add again <Br> Open the storage management console

==LOCATION==

Location is not specified.

==BROWSER INFO==

App Name: Microsoft Internet Explorer

App Version: 4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/6.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.3; .NET4.0C; .NET4.0E)

App Codename: Mozilla

User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/6.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.3; .NET4.0C; .NET4.0E)

Platform: Win32

Cookie Enabled: true

[valcour24]

Did you get an answer to this? I'm having the same problem.

[gcaley]

not yet.

[ASWINIKUMAR_REDDY]

Please let me know are you able to coonect the array trough telnet/ssh ?

if yes, try to uninstall the OSCM and reinstall it and add the array agin.

check the #options http

array001> options http

httpd.access                 legacy

httpd.admin.access           host=All,

httpd.admin.enable           on

httpd.admin.hostsequiv.enable off

httpd.admin.max_connections  512

httpd.admin.ssl.enable       on

httpd.admin.top-page.authentication on

httpd.autoindex.enable       off

httpd.enable                 on

and also check the ssl configuration.

[yuvaraju]

1. Install this “Microsoft Hot Fix”  and try again http://support.microsoft.com/kb/2750841

If this does not solve this issue, do let us know.

[korns]

I've got this problem happening on a Win7 system and it is not being fixed by any of the suggested notes in this community I can see. I'm running on the NetApp corp Win7 image as a VM under Fusion on a Mac. FWIW, SysMan 3.0 for OS X is working fine. It developed the same problem but using the Java control panel to clear cache (Delete Temporary Files ...) seemed to clear the problem for it.

However, on the Win7 SysMan 3 I have tried:

   - was originally running 3.0RC1, tried Java Control Panel Delete Temporary files ... no affect

   - un-installed SysMan 3.0RC1

   - downloaded and installed SysMan 3.0 ... same problem, no affect

   - tried to clear Java cache ... no affect

   - applied MicroSoft http://support.microsoft.com/kb/2750841 , rebooted ... no affect

Is there some small hidden file I could delete and get rid of this situation?

[korns]

About an hour after my post above I figured out my problem (sort of). This was a Win7 system running under VMware Fusion. Fusion has a feature setting that lets the guest VM share certain classes of folders with host machine (OS X). I normally have a specific folder I share with the host (VMshare in my case, see below) I had recently enabled sharing of 'Documents' and 'Desktop' and 'Downloads' also. I believe something about the interaction of sharing the 'Documents' folders (or Libraries in Win7 terms) was causing the problem. Below is a screen shot of the Fusion Sharing Setup window ... the orange circle highlighting the options I turned off which cleared up my problem. I turned off both Desktop and Documents sharing but I think 'Documents' was causing the problem.

[kborovik]

Thank you very much for the solution!

[nigelmullings]

This worked for me - Taken from the 3.1.1 Release Notes...

Unable to launch System Manager

You cannot launch System Manager if either the configuration file or keystore file is corrupted.

Sometimes, after launching System Manager, you cannot manage storage systems because of the

configuration file being corrupted.

After restoring the files, you can launch the System Manager application and manage storage

systems. However, any changes made at the application level in the preceding session might not be

saved. These changes are specific to your input on the home page in System Manager. For example,

storage system credentials might not always be stored after restoring the files. Therefore, you have to

reenter the credentials after launching System Manager.

Workaround

• Restoring the

.config file:

1. Close System Manager.

2.Ensure no Java processes related to System Manager are running.

3.Navigate to the configuration file location:

◦Default location in Windows: C:\Users\user_name\NetApp\SystemManager

◦Default location in Linux: /root/Netapp/SystemManager

4.Copy the contents of SystemManagerBackup.config to SystemManager.config.

• Re-creating the .ks file:

1.Close System Manager.

2.Ensure no Java processes related to System Manager are running.

3.Navigate to the keystore file location:

*Default location in Windows: C:\Users\user_name\NetApp\SystemManager

◦Default location in Linux: /root/Netapp/SystemManager

4.Delete SystemManager.ks.

Subsequently, when you launch System Manager, a new SystemManager.ks file is automatically generated.

[lwangnetapp]

I have recently encountered all kinds of problem after my W7 workstation was patched with MS security updates and java 8 (java is nasty, isn't it?) regarding to NetApp SystemManager 3.1.2 (SM312).

First, the error is "500 Connection Refused"", then "HTTP XML Authentica​tion failed from x.x.x.x (DFM server) on Netapp controller", and last the KS file corruption.

I tried to remove java 8, then remove and re-install Java (jre-7u65) and SM312; did not work.

Of course, you have to install jre-7u65 and SM.

Next, recovere the SM.config file from C:\Users\myusername\NetApp\SystemManager using SMBackup.config, simply deleted the SM.config file then recreate the file using backup (you know how to do this, don't yuo?); deleted the KS file. This restored my previous connections to my filers,great, one step closer.

Next, putty to the filers (controllers) and run this command: "options tls.enable on", bingo, my SM back to work.

Thanks, guys. Good Luck.

[etlhpboise · Accepted solution]

I had the same issue on a 2012R2 install.  To fix the issue I just added "http://127.0.0.1" to the local intranet zone sites.

[Glenco26421]

Adding 127.0.0.1 to the extranet site is what fixed our issue.  Thank you for posting the solution

[Balbir_Singh_BS]

I Was getting error " Unable to load the storage systems as the configuration file of OnCommand System Manager is corrupted. For more information, see the following section in the Release Notes: Unable to Launch System Manager."   Adding 127.0.0.1 to intranet zone resolved my issue too.

[ahmada]

you are the best man alive!