Veeam Agent for Microsoft Windows fails to start

[Sicherdat]

Veeam support case ID: 04511804

Hello,
the following errors occur in the Windows Application Event Log Viewer when VeeamEndpointBackupSvc is starting:

Code: Select all

Log Name:      Application
Source:        SQLLocalDB 11.0
Date:          24/11/2020 09:19:03
Event ID:      528
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      LOCALCOMPUTER
Description:
Windows API call WaitForMultipleObjects returned error code: 575. Windows system error message is: {Application Error}
The application was unable to start correctly (0x%lx). Click OK to close the application.

Reported at line: 3621.

This event appears twice.

Code: Select all

Log Name:      Application
Source:        VeeamEndpointBackupSvc
Date:          24/11/2020 09:19:03
Event ID:      0
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      LOCALCOMPUTER
Description:
Service cannot be started. System.Exception: Error occurred during LocalDB instance startup: SQL Server process failed to start.

   at Veeam.Common.CSqlLocalDb.ThrowLocalDbException(Int32 errorCode, String function)
   at Veeam.Common.CSqlLocalDb.CreateInstance(String instanceName)
   at Veeam.EndPoint.CEndPointServiceImpl.PrepareSqlInstanceImpl(ISqlLocalDbAccessProvider sqlLocalDbAccessProvider, DatabaseFile databaseFile, Boolean recreateDatabase, Boolean reattachDatabase)
   at Veeam.EndPoint.CEndPointServiceImpl.PrepareSqlInstance(DatabaseFile databaseFile, ISqlLocalDbAccessProvider sqlLocalDbAccessProvider)
   at Veeam.EndPoint.CEndPointServiceImpl.InitDb(DatabaseFile databaseFile)
   at Veeam.EndPoint.CEndPointServiceImpl..ctor(CVbOptions options, CTerminationMediator terminator, CExternalEventHelper externalEventHelper)
   at Veeam.EndPoint.EndPointService.OnStart(String[] args)
   at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

It's a computer running Windows 10 (Version 1909), the service is configured to log on as Local System account.
Re-installing as well as disabling the firewall did not resolve this issue.

Any help is appreciated.

[Vitaliy S.]

Hi,

It's hard to say what went wrong here, but you can give this solution a try. If it does not help, then continue working with our support team.

Thanks!

[Sicherdat]

Hello and thanks for your suggestion - unfortunately it did not help in my case, I'm getting the same errors again.

[nitramd]

@Sicherdat,

If this machine is attached to an MS domain, try adding a service account and password to the Veeam Agent service - the account will need to have Domain Admin privileges.

If this machine is not attached to a domain then create a local account & password with Admin privilege and add it to the Veeam service.

Once the service account & password have been added you'll need to restart the Veeam service. But be forewarned, once the service has been restarted you'll probably need to recreate the backup job.

I have ~6-8 machines that have this issue, but I have another 15 or so machines that do not exhibit the issue. Very perplexing and vexing.

Can you post back your results?

Hope this helps.

[Sicherdat]

Thank you very much nitramd, this workaround solved it.

To enhance the perplexity of this I can say that my computer is a domain member, the service started now using a local user account with admin rights.

[nitramd]

Glad to hear that it worked for you.

[dwrandolph]

Security comment: Domain Admin accounts should be kept very restricted and only used to actually administer the domain, not for local issues on a member machine! This was working for you because of an old default GPO that added the Domain Admins global group to your Administrators local group. Many sites remove this as part of their hardening procedures.

A larger deployment might want to use a domain account as the "service account" on member machines for tracking and accountability, but such an account does not needed elevated privileges at the domain level.