This topic contains top known issues for V11 based on their criticality or the number of support cases they generate.
#1: "Access denied" when logging into Veeam ONE Web Client after the upgrade
Symptoms: The following error appears in the application log.
Code: Select all
IISMANAGER_MODULE_INITIALIZATION_THREW_EXCEPTION
The Initialize method for module "Microsoft.Web.Management.Arr.ArrModule, Microsoft.Web.Management.Arr.Client, Version=7.2.4.0, Culture=neutral, PublicKeyToken=tokenID" of type "ApplicationRequestRouting" threw an exception.
Exception:System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Web.Management.WebFarmClient, Version=7.1.2.0, Culture=neutral, PublicKeyToken=tokenID' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.Web.Management.WebFarmClient, Version=7.1.2.0, Culture=neutral, PublicKeyToken=tokenID'
at Microsoft.Web.Management.Arr.ArrModule.Initialize(IServiceProvider serviceProvider, ModuleInfo moduleInfo)
at Microsoft.Web.Management.Client.Connection.Initialize(WebManagementInfo webManagementInfo)Status: While we are collecting additional data about the issue, please contact our customer support for assistance with correcting the IIS authentication as it fixes the issue.
#2: Veeam ONE Reporting Service fails to start after the upgrade
Symptoms: During the upgrade, the "Failed to install extension modules" error appears. After the upgrade, Veeam ONE Reporting Service does not start.
Cause: This happens due to an issue with the report migration procedures. Issue ID 302130.
Status: Please, contact our customer support for applying a hotfix.
#3: Veeam ONE Reporting Service fails to start after the upgrade
Symptoms: If lightweight pooling is enabled on the underlying SQL server, the following error appears in the upgrade log.
Code: Select all
2021-00-00 00:00:00.0000 [ERR] 0x0670 - 9t - 1c PackInstaller - - - - - - - : ResourcePack installation failed
System.Data.SqlClient.SqlException: Common language runtime (CLR) execution is not supported under lightweight pooling. Disable one of two options: "clr enabled" or "lightweight pooling".Cause: Unable to upgrade the report packages because enabled lightweight pooling does not allow using CLR types. Issue ID 301085.
Status: The current workaround is to disable the lightweight pooling on the SQL server. We are planning to address this issue in the next Veeam ONE versions.
#4: Frequent connection attempts to the configured SMTP server after the upgrade
Symptoms: Veeam ONE attempts to connect to the configured SMTP server every 10 seconds.
Cause: Issue in the communication logic. Issue ID 302303.
Status: Fixed in V11a.
#5: Notification email delivery issues after the upgrade
Symptoms: Veeam ONE fails to deliver some scheduled reports and alarm notifications. When re-configuring the SMTP server settings, Veeam ONE throws an error "Invalid format string" upon saving the settings.
Cause: Syntax issue in the verbose-level logging of the communication with an SMTP server. Issue ID 303163.
Status: Fixed in V11a
#6: High CPU usage on Veeam ONE server after the upgrade
Symptoms: Veeam ONE server has started consuming way more CPU after the upgrade.
Cause: Most of the opened cases we've seen had different nature. Some of them have been related to a lack of CPU resources, some to improperly configured Veeam ONE Agent. We are still investigating a few of the cases.
Status: Please, contact our customer support to provide us with additional information.