This topic contains all Update 4 regressions which resulted in 3 or more support cases created.
Last updated: April 1st
#1: Veeam ONE cannot connect to the database after the upgrade to Update 4
Symptoms: Veeam ONE Monitor client shows configuration issue “SQL Server connection failure”. Monitoring is not available.
Cause: The issue is caused by the incorrect “InstallationDate” value format in the Veeam ONE database.
Status: Hotfix is available through support.
#2: Unable to upgrade Veeam ONE to Update 4 due to the error message
Symptoms: The error message during the upgrade “The error during the upgrade to U4: Error 1327. Invalid Drive V:\”.
Cause: Performance cache folder is not available or the old removable drive is not available.
Status: Make sure that the folder location is correct by checking the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam ONE Monitor\Service\DiskPerfCachePath. Besides, please check that there is no removable device available in the Disk Management snap-in.
#3: Cannot install license file after upgrade to U4
Symptoms: The Veeam ONE Monitor client says, “Unable to load license: License signature is invalid”.
Cause: The root certificate is not installed on the Veeam ONE server to validate the license file.
Status: To fix the issue, install “VeriSign Universal Root Certification Authority” and “Thawte Timestamping CA” certificate on the Veeam ONE server. KB2157
#4: Performance data cannot be collected from the SCVMM server and its objects
Symptoms: Veeam ONE 9.5 Update 4 cannot obtain performance data from the SCVMM server due to the error message in the logs: Unable to cast object of type 'PerfHelperAPI.MoRef' to type 'PerfHelperAPI.IPerfQuerySpecByTime'.
Cause: The issue occurs when some of the Hyper-V infrastructure objects were excluded from the monitoring.
Status: Contact Veeam Support to get the hotfix.
#5: High CPU usage on the Veeam Backup&Replication 9.5 Update 3/3a/4 server after upgrading Veeam ONE to Update 4
Symptoms: High CPU usage on backup server after upgrading Veeam ONE to U4.
Cause: One of the WMI queries from the Veeam ONE server causes the issue.
Status: Install Veeam Backup&Replication 9.5 Update 4a to solve the issue.
#6: Updating to U4 error: Subquery returned more than 1 value
Symptoms: Updating process fails with the mentioned error.
Cause: Two or more alarms have the same internal number.
Status: Contact Veeam Support to get the solution.
#7: Object Properties Collection Task status: Failed to retrieve empty storage controller list for Hyper-V host
Symptoms: Object Properties Collection Task returned error or warning with this message in the session details.
Cause: The issue caused by the Microsoft Windows Management Instrumentation design.
Status: Contact Veeam Support to get the workaround.
#8: Business View grouping expression raise an error “invalid expression” if the length is longer than 25 rows
Symptoms: Grouping expression doesn’t work and the editor highlights the expression with red with the mentioned error.
Cause: The issue occurs when you use long grouping expressions.
Status: Contact Veeam Support to get the hotfix.
#9: Unable to install update 4 due to foreign key error
Symptoms: The following error message appears during the upgrade to Update 4: “The ALTER TABLE statement conflicted with the FOREIGN KEY constraint "FK_ObjectProperty_Object". The conflict occurred in database "VeeamOne", table "reporter.Object", column 'ID'”.
Cause: The Veeam ONE database contains invalid links.
Status: Contact Veeam Support to get a hotfix.
#10: Provided license does not allow monitoring Veeam Backup&Replication server
Symptoms: Provided license does not allow monitoring Veeam Backup&Replication server.
Cause: The license file for the Veeam Backup&Replication installation does not contain “Monitoring: Yes” field.
Status: Check license compatibility table, obtain new license if needed.
#11: High load on the Veeam ONE SQL server after upgrading to Update 4
Symptoms: The CPU usage is getting high after the upgrade to Update 4.
Cause: “CheckUntrustedConstraints” operation causes high CPU load.
Status: Contact Veeam Support to get the hotfix.
#12: Failed to download clients.xml from the vCenter server after upgrading to U4
Symptoms: vCenter cannot be monitored due to the error message “Failed to download clients.xml file from https://IPaddress/client/clients.xml”.
Cause: Non-default port is used for the vCenter connection.
Status: Contact Veeam Support to get the hotfix.
#13: Enabled FIPS preventing data collection from the Veeam Backup & Replication server
Symptoms: The data cannot be collected from the Veeam Backup & Replication server if FIPS is enabled.
Cause: WMI calls to Backup servers are not compliant with FIPS.
Status: Contact Veeam Support to get the solution.
#14: Veeam ONE is trying to connect to deleted hosts
Symptoms: Windows Event viewer indicates multiple DistributedCOM events “DCOM was unable to communicate with the computer” against Veeam ONE application.
Cause: Veeam ONE is trying to connect to already deleted hosts from the monitoring.
Status: Contact Veeam Support to get the hotfix.
#15: Veeam ONE raises “Guest Disk Space” alarm with the Error status instead of Warning
Symptoms: Veeam ONE raises “Guest Disk Space” alarm with the Error status instead of Warning.
Cause: The alarm rule has been changed incorrectly during the upgrade to Update 4.
Status: Contact Veeam Support to get the hotfix.
#16: Veeam ONE cannot collect data from the Enterprise Manager and its objects
Symptoms: Veeam ONE cannot obtain any data from the Enterprise Manager and its objects.
Cause: The special symbol in the password “;” causes the issue.
Status: Contact Veeam Support to get the hotfix or change the password to a new one which does not contain the symbol “;”.
#17: When you do Export Business View objects in the Veeam ONE Monitor client, the exported file does not contain Categories names
Symptoms: When you do Export list of Virtual Machines from the Business View tab in the Veeam ONE Monitor client, exported file does not contain Categories names.
Cause: Bug with the Export function.
Status: Contact Veeam Support to get the hotfix.
#18: Veeam ONE Agent could not be deployed during the upgrade
Symptoms: Veeam ONE installation fails with the error message that the Veeam ONE Agent service could not be deployed on the Veeam Backup & Replication server.
Cause: The port 2805 is closed on the backup server or the account does not have enough permissions to install the Agent service.
Status: Check the port status and the permissions for the account. Deploy Veeam ONE Agent service manually from the ISO file or contact Veeam Support for further assistance.
-
- Veteran
- Posts: 7328
- Liked: 781 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
- Contact:
Who is online
Users browsing this forum: No registered users and 7 guests