Thursday 4 November 2021

Commvault webconsole is in accessible - It looks like something went wrong

 



It was a lovely sunny morning and the weather was fine , UNTIL.....the Commvault webconsole reported the above error. 


The usual troubleshooting step was :

1) Restart the tomcat services. That didn't work.

2) The next pro :-) step is to restart stop Commvault (CV) services, restart IIS (iisreset /noforce) and then start CV services. That didn't work. 


The webconsole.log was reporting invalid reponse returned :503 error. What was interesting was that the webserver.log was not touched for a while. The event log errors showed that W3WP.exe process was crashing. 


SOLUTION: 

As documented in the following link, the new Cylance agents that were deployed on the Commserve was responsible for the W3WP.exe process crashes. The following exclusions were added to Commserve and the issue was resolved. 

\Windows\SysWOW64\inetsrv\w3wp.exe
\Windows\System32\inetsrv\w3wp.exe

https://docs.microsoft.com/en-us/answers/questions/590694/net-runtime-errors-iis.html

No comments:

Post a Comment

Commvault : DR backup to cloud fails to run

 The Commvault DR backup to cloud (an option within Control Panel of Commvault console) was reporting failures.  The CVCloudService.log repo...