The recycle bin on C: is corrupted

On one of the windows systems, the following error message popped up every other time.

In order to fix the issue, a command prompt was launched as an administrator and the following command was run.

rd /s /q C:\$Recycle.bin

NetApp system manager fails to launch

hmm...

This morning I had an issue with system manager 3.1.2. The application failed to launch. No error , no prompts and just fails to launch.

I would recommend the following steps:

1) Check if browser is compatible (read release notes).

2) If you have system manager installed on a DFM server then it is best to uninstall it from the DFM server and use a different server for system manager.

3) Verify you have the right java version installed (uninstall older versions of Java)

4) Add http://127.0.0.1 to the local  intranet zone sites

5) Following the two KBs below:

• https://library.netapp.com/ecmdocs/ECMLP2602644/html/frameset.html  (refer Unable to launch System Manager) 
• https://kb.netapp.com/app/answers/answer_view/a_id/1006756/loc/en_US

network access message the page cannot be displayed [ NetApp unified manager ]

Hmm...

If you were trying to access NetApp products like unified manager and you receive the following error then you can try accessing the unified manager using IP address:

'network access message the page cannot be displayed'

I believe these errors are caused by slow DNS responses.

NetApp system Manager 500 Connection has been shutdown

If you encounter the following error on system manager then  this is an issue caused by the requirements of the latest java JRE.

To fix the issue, you need to enable TLS on the NetApp controller. Options TLS is the command.
You will also need to enable TLS V2.

500 Connection has been shutdown:
javax.net.ssl.SSLHandsakeException: Server chose SSLv3, but that protocol version is not enabled or not supported by the client.

filer_A> options tls
tls.enable on 

VSC errors: Current vCenter Server context is unknown' a and '"The hostname:port# cannot be resolved"

Issue 1: 

Hmm.... The VSC 6.2.1 of mine was reporting the following error. The way to fix the issue was to reboot the server that is running VSC. Ha ha ha ha. 


faultCode : Server.Processing

faultString:'java.lang.RuntimeExeption : Current vCenter Server context is unknown'

faultDetail:'null'


If you know what causes the issue then please leave a comment. 



Issue 2:

"The hostname:port# cannot be resolved" 

To resolve this issue,
1)   login to the VSC server  and edit the file java.security at the following path: 

2) Reduce the limit of accepted RSA keySize by modifying the option jdk.certpath.disabledAlgorithms:

--

jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 512

--

3) Register the VSC again and restart the server.