EM and VBR integration fails after upgrade to V13.1

[miyu.masuda]

After upgrading EM and VBR to V13.1, data collection from VBR failed with the following message:
> The length parameter passed to the LEFT or SUBSTRING function is invalid. Warning: Null value is eliminated by an aggregate or other SET operation. The statement has been terminated.
Both EM and VBR are running on Windows.

Removing the EM-VBR integration and re-registering it results in the same failure.
Checking VeeamBES.log reveals the following errors:
> Error (1) CertificateValidation Trusted certificates list is empty
> Error (1) CertificateValidation Remote certificate 'xxxx' is not trusted
The certificate should be trusted upon VBR re-registration, yet this error persists.
The default VBR certificate is being used.

I attempted to add the VBR certificate to the Trusted Root Certification Authorities store on the EM Windows server, but it had no effect.
Are there any known instances of this issue occurring?

（Case # 08191454）

Regards,

[david.domask]

Hi miyu.masuda,

Please continue with Support, as we cannot perform troubleshooting over the forums as noted in the forum rules and when you create a topic.

The errors you posted about certificates I think are not relevant to the first error you posted, as first error is 100% from the underlying database engine, so sounds like a query is failing.

So please continue with Support, as a review of the debug logs will be required.

I am aware of at least one issue which returns the initial error though, please tell if you have any vSphere items on 9.1 (vCenter / ESXi host), and if so please be sure to mention it in the case.

[miyu.masuda]

Thank you for your reply.
After consulting with support, we learned that there is a known bug in EM (Microsoft SQL Server only) when integrated with VCF 9.1.

This is not publicly documented information. Since we had already upgraded to VCF 9.1, we were unable to roll back Veeam to version 12, and consequently could not prevent EM from becoming unusable.
Since we use EM to provide SSBP to our customers, this is a very difficult situation.
We request that you consider releasing a patch.
In addition, we would like you to publish information about this bug in the Knowledge Base.

Regards,

[david.domask]

Happy to advise.

Good to know it's a known issue; if it's an urgent issue, you can request escalation on your case to see if a hotfix is feasible. Please keep in mind that it may not be feasible to deliver a hotfix on a given version, so please be prepared that the issue may only be fixed in an upcoming release.

Looking at the issue internally, looks like it's slated for resolution in a 13.1 release, but this is subject to change, so best to discuss with Support on the case.