Skip to main content
Question

Invalid Name Character

S

Veeam B&R version 12.2.0.334

Having backup jobs fail because of this error

Example: 

Error: Invalid name character in 'ApplicationProcessingEnၡblm$'. The 'ၡ' character, hexadecimal value 0x1061, cannot be included in a name.

 

The occurrence is random. The errant character is random. The job affected seems to be random as well.

Was able to keep this from happening with a weekly reboot of the backup server, but now that is not working.

Can sometimes get the job to succeed by Rebooting the server and restarting the job

 

This all started with the upgrade to 12.2 from 12.1.

 

    5 comments

    E
    Forum|alt.badge.img
    • eblack
    • Experienced User
    • 45 comments
    • March 12, 2025

    Assuming there isn’t any strange characters in the jobs or job settings. I’d attempt the following, 

     

    Clone one of the offending jobs and see that clone reacts in the same way. 

     

    Flush the config cache. (Will stop functional until services are restarted)

    net stop VeeamBackupSvc
    net stop VeeamBrokerSvc
    net stop VeeamCatalogSvc
    net stop VeeamEnterpriseManagerSvc
     

    Delete or move contents of C:\ProgramData\Veeam\Backup\Config\Cache\

    net start VeeamBackupSvc
    net start VeeamBrokerSvc
    net start VeeamCatalogSvc
    net start VeeamEnterpriseManagerSvc

     

    Check DB for table issues - (Best to work with Support on this one) You’d want to look for this or similar. WHERE name LIKE '%ApplicationProcessingEn%'

     

    Upgrade to 12.3 - 

     


     

     

    matheusgiovanini
    Dynamic
    2 people like this
    • matheusgiovanini
      matheusgiovanini
    • Dynamic
      Dynamic
    matheusgiovanini
    Forum|alt.badge.img+5
    eblack wrote:

    Assuming there isn’t any strange characters in the jobs or job settings. I’d attempt the following, 

     

    Clone one of the offending jobs and see that clone reacts in the same way. 

     

    Flush the config cache. (Will stop functional until services are restarted)

    net stop VeeamBackupSvc
    net stop VeeamBrokerSvc
    net stop VeeamCatalogSvc
    net stop VeeamEnterpriseManagerSvc
     

    Delete or move contents of C:\ProgramData\Veeam\Backup\Config\Cache\

    net start VeeamBackupSvc
    net start VeeamBrokerSvc
    net start VeeamCatalogSvc
    net start VeeamEnterpriseManagerSvc

     

    Check DB for table issues - (Best to work with Support on this one) You’d want to look for this or similar. WHERE name LIKE '%ApplicationProcessingEn%'

     

    Upgrade to 12.3 - 

     


     

     

     

    I agree. Try all of that and let us know if your jobs run successfully after that.

    Matheus Giovanini | Senior Backup & Data Protection Analyst
    D
    Forum|alt.badge.img+3
    • ddomask
    • Comes here often
    • 106 comments
    • March 13, 2025
    eblack wrote:

    Assuming there isn’t any strange characters in the jobs or job settings. I’d attempt the following, 

     

    Clone one of the offending jobs and see that clone reacts in the same way. 

     

    Flush the config cache. (Will stop functional until services are restarted)

    net stop VeeamBackupSvc
    net stop VeeamBrokerSvc
    net stop VeeamCatalogSvc
    net stop VeeamEnterpriseManagerSvc
     

    Delete or move contents of C:\ProgramData\Veeam\Backup\Config\Cache\

    net start VeeamBackupSvc
    net start VeeamBrokerSvc
    net start VeeamCatalogSvc
    net start VeeamEnterpriseManagerSvc

     

    Check DB for table issues - (Best to work with Support on this one) You’d want to look for this or similar. WHERE name LIKE '%ApplicationProcessingEn%'

     

    Upgrade to 12.3 - 

     


     

     

    Hi, please don’t do any of these steps. They are potentially risky and unsupported.

    The issue itself is a bit unclear -- it’s XML parsing error for sure which makes me think the VBM file or the GuestInfo XML in the configuration database got corrupted.

    Regardless, please do not use advices found online regarding the VBM file or database for this error, these errors require Veeam Support to review to avoid further complications. (Depending on the backup environment and what features are used (primarily capacity tier), deleting the VBM may cause further issues)

    It’s best to open a Support Case and let Support guide the investigation.

    0x0D 0x0A
    Tommy O'Shea
    1 person likes this
    • Tommy O'Shea
      Tommy O'Shea
    Tommy O'Shea
    Forum|alt.badge.img+3
    • Tommy O'Shea
    • Experienced User
    • 48 comments
    • March 13, 2025

    ​@ddomask That’s a very good point. Generally when a case requires doing anything with the database, either delving into it or making modifications, that is my limit. It would be best to open a case, upload logs and a copy of the database.

    Tommy O’Shea, VMCE, VMCE-SP, VMCA
    E
    Forum|alt.badge.img
    • eblack
    • Experienced User
    • 45 comments
    • March 17, 2025
    ddomask wrote:
    eblack wrote:

    Assuming there isn’t any strange characters in the jobs or job settings. I’d attempt the following, 

     

    Clone one of the offending jobs and see that clone reacts in the same way. 

     

    Flush the config cache. (Will stop functional until services are restarted)

    net stop VeeamBackupSvc
    net stop VeeamBrokerSvc
    net stop VeeamCatalogSvc
    net stop VeeamEnterpriseManagerSvc
     

    Delete or move contents of C:\ProgramData\Veeam\Backup\Config\Cache\

    net start VeeamBackupSvc
    net start VeeamBrokerSvc
    net start VeeamCatalogSvc
    net start VeeamEnterpriseManagerSvc

     

    Check DB for table issues - (Best to work with Support on this one) You’d want to look for this or similar. WHERE name LIKE '%ApplicationProcessingEn%'

     

    Upgrade to 12.3 - 

     


     

     

    Hi, please don’t do any of these steps. They are potentially risky and unsupported.

    The issue itself is a bit unclear -- it’s XML parsing error for sure which makes me think the VBM file or the GuestInfo XML in the configuration database got corrupted.

    Regardless, please do not use advices found online regarding the VBM file or database for this error, these errors require Veeam Support to review to avoid further complications. (Depending on the backup environment and what features are used (primarily capacity tier), deleting the VBM may cause further issues)

    It’s best to open a Support Case and let Support guide the investigation.

     

    The only real risk is the DB, which I said, would be best to engage support.

    Comment


    Terms & Conditions