Backup Service not starting after upgrade v12 -> v12.1

[Refruit]

Hello there,

Case # 07072049

We have upgraded our environment with 1 Enterprise Manager and 3 Veeam Servers from v12 to latest v12.1 today.

- EM with remote MSSQL DB went fine
- 1 Veeam Server with local MSSQL DB went fine

The other 2 Veeam Servers (1 with remote MSSQLDB and 1 with local MSSQL DB) Installation went through but the Backup Service itself refuses to start.
Event Manager entry is the following:

Code: Select all

Service cannot be started. System.NullReferenceException: Object reference not set to an instance of an object. at Veeam.Backup.ServiceLib.CRemoteInvokeServiceHolder.DisposeInternal()
at Veeam.Backup.ServiceLib.CRemoteInvokeServiceHolder..ctor(Int32 port, CVbServiceManagers managers, CBackupServerCertificateManager vbrCertificateManager)    
at Veeam.Backup.ServiceLib.CVbServiceImpl.InitSslServerChannel(CVbServiceManagers mngrs, CDisposableList disposableObjects)    at Veeam.Backup.ServiceLib.CVbServiceImpl..ctor(CVbEnvironment env, CTerminationMediator terminator)    
at Veeam.Backup.Service.CVeeamBackupSvc.OnStart(String[] args)    at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

Support currently assume some certificate issue and suggests deleting the Veeam Certificates. Should those be re-created automatically?
After doing so and repairing the Installation, certificates are still missing and Backup Service won't start with the same error.

Did anybody came across this issue?

[Refruit]

So we found a workaround, as Veeam doesn't like our internal certificate (which worked for v12 flawlessly) with v12.1 anymore.
Tha'ts surprising as in the documentation (https://helpcenter.veeam.com/docs/backu ... ml?ver=120) at the bottom it sais:

Page updated 10/10/2023
Page content applies to build 12.1.1.56

No issues when using a self signed certificate

[khisamserv]

Hi there,
I'm experiensing same issue. Did you jusy delete certs from Certificate manager?

[david.domask]

Hi khisamserv,

The case from the topic was resolved after an upgrade to latest build and checking on a few other environmental items, so I'm not sure that any such solutions will apply necessarily to your situation.

It's best to open a Support Case and allow Veeam Support time to review the behavior you're seeing. Be sure to include logs for Support to review. (Use the 3rd radio button, select the Veeam Server itself to begin with, and export logs)