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,
-
miyu.masuda
- Service Provider
- Posts: 49
- Liked: 4 times
- Joined: Mar 17, 2023 12:25 pm
- Full Name: miyu masuda
- Contact:
-
david.domask
- Product Manager
- Posts: 3857
- Liked: 936 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: EM and VBR integration fails after upgrade to V13.1
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.
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.
David Domask | Product Management: Principal Analyst
Who is online
Users browsing this forum: DatatoSecure, Google [Bot] and 282 guests