Dashboard > Health > Software Version report not updating

Hi ​@Ken_H ,

Kindly review the CommServe Survey Utility log file from the machine where the data is being uploaded, as well as the CVSurvey logs, to verify if the data is being successfully processed and sent to the Metrics Server.

The CVSurvey.log file on the web server contains the following:

01/20 13:34:03 INFO  "#######################################"
01/20 13:34:03 INFO  "# Begin processing metrics collection #"
01/20 13:34:03 INFO  "#######################################"
01/20 13:34:03 ERROR "__main__Failed to copy file to next metrics report server. File will be retained for retry"
Repeated 511 times. At random locations within the 511 “Failed to copy” messages are the following lines:

01/20 13:34:03 INFO  "__main__Latest file is already processed. Skip [CSS1732199722_FB7CB_E233FDD1-488F-4439-ADC2-2BE93BB391C7_915847.zip]"
Repeated 11 times with different values for the last six digits

01/20 13:34:03 ERROR "Upload Failed"
01/20 13:34:03 ERROR "File copy failed for source file D:\Program Files\Commvault\ContentStore\Reports\MetricsUpload\Upload\CSS1732233774_FB7CB_137.xml to URL [http://<CommCell_servername>/commandcenter/commandcenter/metrics/metricsUpload.do] - error code -1 "
Repeated three times for slightly different file names.

01/20 13:34:04 INFO  "__main__Reached max limit [500] for processing xml file."
01/20 13:34:04 INFO  "Calling ProcessCollectedResults..."
01/20 13:34:04 INFO  "Response received from the ProcessCollectedResultsviaAPI is : 0"
01/20 13:34:04 INFO  "Completed processing for [0] commcells from [0] successful xmls. [500] xmls failed to process."
01/20 13:34:04 INFO  "#####################################"
01/20 13:34:04 INFO  "# End processing metrics collection #"
01/20 13:34:04 INFO  "#####################################"
 

It appears I’ll need to open another support ticket. Thanks for the recommendation to check the CVSurvey.log file.

Ticket 250120-818 opened to investigate this problem.

Hi ​@Ken_H ,

Try disabling the forwarding option and upload the data directly to the Metrics Server. Verify if the reports are functioning as expected afterward.
 

1. Open the Private Metrics Reporting dialog box
2. Click the Forwarding tab
3. Configure the forwarding options
4. Disable Forwarding.
5. Re upload the data to metrics server 

Hi ​@Ken_H 

give it a try, please: https://documentation.commvault.com/additionalsetting/details?name=%22bCVGCheckDirectConnectionFirst%22&id=10749  (value 1).

Thanks for the recommendations - I’ll look into them if time permits.

CV support has recommended I upgrade from 11.34.47 to 11.36.32. I’ve gone in and downloaded the 11.36.35 latest release but when I attempt to install it, the upgrade job runs for a bit over 90 seconds and reports all clients as “Already updated”. I suspect I have larger problems than just the incorrect version on the Command Center Health Report.

I’m waiting to hear back from CV support on whether they can investigate the upgrade problem or whether I need to create a new ticket.

FYI: Ticket 250121-889 has been created to deal with the upgrade issue.

CommVault support has recommended we upgrade from 11.34.xx to 11.36.xx to resolve this issue. Unfortunately, we had a previous upgrade that required a reboot of all clients which lead to a production outage. I’m too late to get this scheduled into the production patch window which starts tomorrow evening so the upgrade will likely have to wait until the February patch weekend.

I’ve upgraded to 11.36.28 which itself broke several things the most notable of which was the loss of the Command Center interface. The issues related to the upgrade have all been resolved and I’ve been able to confirm that the upgrade did NOT resolve the issue.

I’ve attempted to follow the instructions for configuring the Private Metrics Reporting but CommVault refuses to accept the URL I enter even though it begins with https://.

Regarding the recommendation for the bCVGCheckDirectConnectionFirst setting - it’s not clear where that is supposed to be set.

Rather than guess and risk further corrupting my already unstable installation, I’ve opened 250307-528 to get the experts to investigate this problem.