Skip to main content
Solved

Orchestrator Error, Veeam One Monitoring Service cannot access its database

S
Forum|alt.badge.img+1

Orchestrator Error, Veeam One Monitoring Service cannot access its database.

Initially got the error, “The embedded Veeam Backup and Replication server is not Healthy, state = Communication Error”.

So digging more into the issue showed the error above. When I ran VeeamOne client, it said it cannot connect to the Veeam One server.

I noticed at the top of the client it shows Community Edition

This is weird, why would it say Community Edition, if VRO is showing a valid license

 

I ran the Veeam One setting utility and was able to connect successfully

 

 

I opened a ticket to Veeam support and we have been going back and forth for almost 2 weeks now and no results yet.

 

Hoping you folks can give me ideas where to go next.

Best answer by spider32

Apparently, the DBs got corrupted. I had to restore the 3 DBs being used by the Orchestrator, the VeeamBackup, VeeamOne, and VRO from a certain date. Have restored full VMs of the DB server from dates when the Orchestrator was working but did not work so not sure why that did not work.

View original
    Chris.Childerhose
    1 person likes this
    • Chris.Childerhose
      Chris.Childerhose
    Did this topic help you find an answer to your question?

    4 comments

    Chris.Childerhose
    Forum|alt.badge.img+21
    • Chris.Childerhose
    • Veeam Legend, Veeam Vanguard
    • 9320 comments
    • April 18, 2025

    I would suggest continuing with support as that is the best way to resolve the issue.

    Chris Childerhose - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | VUG Canada Leader | vExpert 6* | Toronto VMUG Leader | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
    Iams3le
    S
    2 people like this
    • Iams3le
      Iams3le
    • S
      spider32
    waqasali
    Forum|alt.badge.img+4
    • waqasali
    • Influencer
    • 338 comments
    • April 20, 2025

    Hi ​@spider32 Make sure the server can talk to the SQL database in addition to kindly check if any AV or FW is blocking the Veeam services and make sure ports like 1433 SQL and 9392 Veeam must be open.

    Waqas Ali
    S
    1 person likes this
    • S
      spider32
    Marcel.K
    Forum|alt.badge.img+9
    • Marcel.K
    • Veeam Legend
    • 256 comments
    • April 21, 2025

    Hi spider32,

    i had this problem with version 12.2….. on Veeam One as well and via support case they suggested to upgrade to 12.3.0… So after upgrade it well  run.

    Error appears suddenly and base on technician they saw that service is crashing randomly. So upgrade fixed the problem. VBR is not need to upgrade - i am still on 12.2.0.334.

    Marcel Kačmár | VCSP Partner 2022 | VMCE 2024 | VMCA 2024 |
    S
    1 person likes this
    • S
      spider32
    S
    Forum|alt.badge.img+1
    • spider32
    • Author
    • Influencer
    • 97 comments
    • Answer
    • May 12, 2025

    Apparently, the DBs got corrupted. I had to restore the 3 DBs being used by the Orchestrator, the VeeamBackup, VeeamOne, and VRO from a certain date. Have restored full VMs of the DB server from dates when the Orchestrator was working but did not work so not sure why that did not work.

    Chris.Childerhose
    Marcel.K
    2 people like this
    • Chris.Childerhose
      Chris.Childerhose
    • Marcel.K
      Marcel.K

    Comment


    Terms & ConditionsAccessibility statement