In your Web Console under Reports > eDiscovery Exception Report you are able to create a reports to identify possible issues in the indexing process.
Bug:
If you try to create such a eDiscovery Exception Report and you click on a search engine you will see a greyed our form with a moving progress circle and after a timeout interval (~20seconds) you get an error message 3011,Search Engine service is down and a note that the CommVault Search Engine may not running. But CommVault Search Engine is up and running fine.
The root cause is that the Commvault Web Server installed on a different machine cannot connect to the CommVault Search Engine as the Windows Firewall is blocking the connection. Commvault missed to add the C:\Program Files\CommVault\Simpana\CIServer\bin\tomcat6.exe executable to the firewall exceptions.
Solution:
Add an additional and undocumented firewall exception manually to the system and you are done.
netsh advfirewall firewall add rule name="CommVault_Process_1_CIServer_Tomcat6 / C:\Program Files\CommVault\Simpana\CIServer\bin\tomcat6.exe" dir=in action=allow program="C:\Program Files\CommVault\Simpana\CIServer\bin\tomcat6.exe" enable=yes
Add for the reason that solr search offers it's internal admin interface on this port I strongly suggest to open it only for your Commvault Webserver machine and not every machine on your network.
netsh advfirewall firewall add rule name="CommVault_Process_1_CIServer_Tomcat6 / C:\Program Files\CommVault\Simpana\CIServer\bin\tomcat6.exe" dir=in action=allow program="C:\Program Files\CommVault\Simpana\CIServer\bin\tomcat6.exe" enable=yes remoteip=192.168.x.x
History:
- 2015/12/16: Bug report filed at Commvault Support.