Resolve Veeam ONE “The specified property cannot be found” and License Mismatch Errors During upgrade

This article discusses how to resolve Veeam ONE “The specified property cannot be found” and License Mismatch Errors. Veeam Data Platform (VDP) is an end-to-end data recovery platform designed to provide immutable, high-performance backups and direct to object storage at any scale. Please see Azure Virtual Desktop: How to set Up Azure Virtual Desktop Insights Monitoring [Part 03], Azure Virtual Desktop: Connect to Session Hosts Using Entra ID [Part 04], and Azure Virtual Desktop: Autoscaling Implementing and Monitoring Session Hosts [Part 05],

VDP optimizes moving or copying backups between different storage types, preserving data reduction with intelligent backup data migration. Veeam Data Platform includes the following Veeam products: Veeam Backup & Replication, Veeam ONE, and Veeam Recovery Orchestrator.

When managing enterprise backup environments, keeping monitoring components in sync with your backup core is crucial. During infrastructure upgrades, specifically when introducing Veeam Data Platform (VDP) v13 alongside an existing Veeam ONE v12 instance. You will encounter distinct schema and licensing errors as shown in the image below.

You will find a similar “trial license error” discussed. You can expand the configuration issues for more detailed information as shown below. Also, since the core object cannot be licensed and properly queried, the dependent data collection tasks can also start to fail as shown below.

Please see Azure Virtual Desktop: How to set Up Azure Virtual Desktop Insights Monitoring [Part 03], How to fix Update Error 0x800f0831 in Windows or Windows Server, and Azure Virtual Desktop: How to set Up Azure Virtual Desktop Insights Monitoring [Part 03].

Understanding the Root Cause

Veeam enforces a strict top-down operational rule as we have seen with Veeam Backup for Enterprise Manager and Veeam Recovery Orchestrator which are part of the VDP suite. Veeam ONE must always be at the same version or newer than the Veeam Backup & Replication server it monitors.

Applying a VDP v13 license file directly to a Veeam ONE v12 instance causes a license schema failure as we have seen above. Veeam ONE v12’s license parser does not recognize the internal XML/schema structure of a v13 key. This is why it throws “The specified property cannot be found” and flags the license as incompatible until you upgrade the Veeam ONE software to v13 which we will be doing very shortly.

To reproduce this error, head over to the Veeam Customer Portal to download your NFR license as shown below.

NFR license has been downloaded.

From the Hamburger Menu in Veeam ONE, navigate to License

Click on Install License. See how to replace Veeam Recovery Orchestrator License, and how to license Veeam Enterprise Manager and Add VBR Servers.

Select the recently downloaded NRF. Here is how you can get yours too “how to apply and install Veeam NFR License“.

As you can see, the specified property cannot be found.

This is because, Veeam license files (.lic) contain encrypted metadata, product flags, and object parameters specific to their major product generation.

• License Parsing Failure: Veeam ONE v12’s licensing module is designed to parse v12-generation license schemas. When presented with a VDP v13 key containing updated fields, the v12 client cannot map the parameters and throws an unhandled property error.

Veeam ONE must be upgraded to v13 first so that its licensing engine can correctly parse, accept, and validate the VDP v13 key.

Please see Azure Virtual Desktop: Deploy host pools and session hosts in the Azure [Part 01], Azure Virtual Desktop: Manage Azure Virtual Desktop host pools and session hosts using the Azure portal [Part 02], and Disaster Recovery Test Checklist: What to Capture Before You Start.

Upgrade Veeam ONE 12 to 13

A Veeam Data Platform 13 NFR license from my test isn’t compatible with Veeam ONE 12 license installed as discussed above. Therefore, an upgrade to v13 is necessary.

To do this, please, see how to upgrade Veeam One from v12 to v13, and how to upgrade Veeam ONE to v12.1. As you can see below, we have successfully upgraded our Veeam ONE instance to v13.

Proceed and install the license again using the steps discussed above. As you can see now, there are no more errors and compatibility issue is no longer present.

Note: Once the core binary matches the database schema, data collection threads resume writing performance cache to disk without throwing UI exceptions.

As you can see below, upgrading Veeam ONE to version 13 and applying the VDP v13 NFR license returns the infrastructure to full health. Now the VM Jobs Status pie chart and Top Repository Servers by Used Space bar charts update cleanly.

As shown below, I am resolving the one of the warnings by clearing the configuration issue counter in the top banner. This will bring the entire monitoring environment back to a healthy all green status.

I hope you found this article on “Resolve Veeam ONE “The specified property cannot be found” and License Mismatch Errors During upgrade” very useful. Please feel free to leave a comment below.