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.