Incorrect Replica Counters in Monthly Cloud Connect License Usage Report

KB ID:
3004
Product:
Veeam Cloud Connect
Version:
9.4 Update 4b
Published:
Last Modified:
2019-09-20

Challenge

Automated monthly license usage reports generated by Veeam Cloud Connect display an unexpected number of replicated VMs and licensed instances. At the same time, Get-VBRCloudTenant -Name "TenantName" PowerShell cmdlet returns proper numbers.

Cause

Miscalculations are caused by a bug in the stored procedure.

Solution

  1. Download archive with u4b_FIX_Licensing.Reporting.CC.GetInstancesInfo.sql file, extract and copy it to the SQL server, which hosts the Veeam Cloud Connect database or any other machine that can connect to the SQL instance in question.
  2. Connect to the SQL instance by using Microsoft SQL Studio. When connecting, please provide valid credentials with full permissions.
  3. Find your Veeam Cloud Connect database (its default name is VeeamBackup). Right-click it and select New Query.
  4. Open file u4b_FIX_Licensing.Reporting.CC.GetInstancesInfo.sql by using the text editor, copy all its content and paste it to the query window from step 3.
  5. Run the query by clicking Execute or pressing F5. Make sure that the query is executed successfully.
User-added image

More Information

[[DOWNLOAD|DOWNLOAD SCRIPT|https://storage.veeam.com/Fix_187183_fc067577f8.zip]]

MD5 for Fix_187183_fc067577f8.zip: 024ba03459d46e3c9be6b59d40066868
SHA-1 for Fix_187183_fc067577f8.zip: 302af86b05b6bfc25e532db4f69045e7d6e41732

Should you have any questions, contact Veeam Support.
 

Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.

OK

Rate the quality of this KB article: 
5 out of 5 based on 4 ratings

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.

Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text:

Submit