Failed to connect to Veeam Backup and Replication server

[axiomcrs]

Veeam B&R has been starting fine for several weeks. So it is not an install issue. Using the default port of 9392. No other svc is using port 9392 by checking with netstat -a -b -o. It is running on Windows Server 2019. This is the only application running on this server. I have not changed the pwd or the server name. Veeam B&R version is 10.0.1.4854. Did not see any errors in the logs at c:\programdata\veeam. The full error msg is: https://i.gyazo.com/d0f948715fca2d107c7 ... 43b1f7.png

In the App logs from the Windows Event Viewer only this:
Service cannot be started. System.OperationCanceledException: The operation was canceled.
at Veeam.Backup.DBCreator.BackupDatabaseDeployer.CanDeploy(IDatabaseVersion databaseVersion)
at Veeam.Backup.DBCreator.BackupDatabaseDeployer.DatabaseDeploy(List`1 inDeployChangedOptions)
at Veeam.Backup.DBCreator.BackupDatabaseDeployer.Deploy()
at Veeam.Backup.DBManager.SqlRetryableInitializer.Init()
at Veeam.Backup.Service.CVbServiceImpl..ctor(CVbEnvironment env, CTerminationMediator terminator)
at Veeam.Backup.Service.CVeeamBackupSvc.OnStart(String[] args)
at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

I did read about a possible db lock causing the issue. However, did not find a useful fix (the only fix I saw related to updating the db version iirc).

Any suggestions on fixing the issue?

[Mildur]

You can find the reason for the not started service in the veeam log files in this location:
C:\programdata\veeam\backup

Each service has its own log file.
If a service will not start, you will find the reason there. It looks like your veeam Backup Service is not running.

If not, use open a support request.

[Dima P.]

Hello axiomcrs,

As Fabian mentioned we need the detailed debug logs to identify the root cases, so please raise a support case and share the case ID with us. Cheers!

[axiomcrs]

Do you know which log file it would be in that dir.? Or does it depend on the failure? I just tried to start the Veeam B&R console today and I noticed that only certain log files in that dir. have today's date and time of the attempt on starting the console (3). None of these files have an error in them (the files are Svc.VeeamInstaller.log, Svc.VeeamInstallerDll.log, and Svc.Transport.log, which seems to be files unrelated to starting the console).

[Mildur]

Most likely C:\programdata\veeam\backup\svc.VeeamBackup.log.

Are all of your veeam services are started? I bet with you for a beer, that your service „Veeam Backup Service“ is not running on the server, that you are trying to connect your veeam console.

Veeam Backup Service is the one which is connecting to your sql database.
If this service is not running, your veeam console cannot connect to your veeam installation.

[Dima P.]

Unfortunately cant advise on logs analysis, but support team should know that for sure. By the way, have you tried to telnet vbrhostname over 9392 to make sure that nothing is blocking the connection? Did I get it right that both console and VBR are installed on the same machine? Thanks!

[axiomcrs]

I would assume that when trying to start the console and it fails for my issue, that the log file c:\programdata\veeam\backup\svc.veeambackup.log would have the same date and time as the failed attempt. But it does not. That log file has not updated with the latest failure. It has as its latest update a date of 2 days ago. Yes, the console and VBR are on the same server. I would assume that it wouldn't matter (in terms of starting the console) if the telnet to the server over port 9392 worked or not.

Here's a screenshot of the svcs: https://i.gyazo.com/c761f3c2c933cff3fd0 ... 6a1f42.png

VeeamBackupSvc will not start (I would assume that the other stopped svcs don't matter when trying to start the console).

So it appears that there is another log file that contains the reason why the console won't start.

Does it matter if the svc SQLAgent$VEEAMSQL2016 is stopped? If it should be started, mine will not start manually.

[Mildur]

Ignore the console error. The console is not the error here. Your veeam backup service is the error. It must be in a running state. Your console will not help you to get it running.

Again: ignore your console error, concentrate on why your backup service is not running.
Please ask support to help you.
As a service provider, you have surely a maintenance contract for your rental license.

It‘s like:
You have to start your computer, before you can run microsoft word.
If your computer isn’t started, you will not search the logs for word errors because you cannot use your word application. the requirements are not fulfilled.

[axiomcrs]

Thanks for that. When starting the VeeamBackupSvc manually, it says starting for about 2 minutes and then it goes back to Stopped. In the Windows logs for Application there is an error corresponding to the time I tried to start the svc manually. It is:

Code: Select all

Service cannot be started. System.OperationCanceledException: The operation was canceled.
   at Veeam.Backup.DBCreator.BackupDatabaseDeployer.CanDeploy(IDatabaseVersion databaseVersion)
   at Veeam.Backup.DBCreator.BackupDatabaseDeployer.DatabaseDeploy(List`1 inDeployChangedOptions)
   at Veeam.Backup.DBCreator.BackupDatabaseDeployer.Deploy()
   at Veeam.Backup.DBManager.SqlRetryableInitializer.Init()
   at Veeam.Backup.Service.CVbServiceImpl..ctor(CVbEnvironment env, CTerminationMediator terminator)
   at Veeam.Backup.Service.CVeeamBackupSvc.OnStart(String[] args)
   at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

Which seems not to be very useful info.

In the System logs there is:
The Veeam Backup Service service terminated with the following error:
An exception occurred in the service when handling the control request.

Also, not very useful.

In c:\ProgramData\Veeam\Backup\Svc.VeeamBackup.log there is this entry corresponding to the start time:

Code: Select all

[05.01.2021 10:33:12] <04> Info     [DB|ERROR] Failed to connect to server . (Microsoft.SqlServer.Management.Common.ConnectionFailureException)
[05.01.2021 10:33:12] <04> Info     [DB|ERROR]    at Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()
[05.01.2021 10:33:12] <04> Info     [DB|ERROR]    at Veeam.Backup.DBCreator.DatabaseConnector.Connect(DatabaseConnectorOptions options)
[05.01.2021 10:33:12] <04> Info     [DB|ERROR] A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (System.Data.SqlClient.SqlException)
[05.01.2021 10:33:12] <04> Info     [DB|ERROR]    at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, DbConnectionPool pool, String accessToken, Boolean applyTransientFaultHandling, SqlAuthenticationProviderManager sqlAuthProviderManager)
[05.01.2021 10:33:12] <04> Info     [DB|ERROR]    at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
[05.01.2021 10:33:12] <04> Info     [DB|ERROR]    at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)
[05.01.2021 10:33:12] <04> Info     [DB|ERROR]    at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
[05.01.2021 10:33:12] <04> Info     [DB|ERROR]    at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
[05.01.2021 10:33:12] <04> Info     [DB|ERROR]    at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
[05.01.2021 10:33:12] <04> Info     [DB|ERROR]    at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
[05.01.2021 10:33:12] <04> Info     [DB|ERROR]    at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
[05.01.2021 10:33:12] <04> Info     [DB|ERROR]    at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
[05.01.2021 10:33:12] <04> Info     [DB|ERROR]    at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
[05.01.2021 10:33:12] <04> Info     [DB|ERROR]    at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
[05.01.2021 10:33:12] <04> Info     [DB|ERROR]    at System.Data.SqlClient.SqlConnection.Open()
[05.01.2021 10:33:12] <04> Info     [DB|ERROR]    at Microsoft.SqlServer.Management.Common.ConnectionManager.InternalConnect(WindowsIdentity impersonatedIdentity)
[05.01.2021 10:33:12] <04> Info     [DB|ERROR]    at Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()
[05.01.2021 10:33:12] <04> Info     [DB|ERROR] The system cannot find the file specified (System.ComponentModel.Win32Exception)
[05.01.2021 10:33:12] <04> Info     [DB] Disconnecting from SQL Server (ServerInstance=[SERVER1\VEEAMSQL2016])
[05.01.2021 10:33:12] <04> Info     [DB] Connection is terminated
[05.01.2021 10:33:12] <04> Info     [DB|ERROR] Unable to connect to SQL Server SERVER1\VEEAMSQL2016. A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Veeam.Backup.DBCreator.DatabaseException)
[05.01.2021 10:33:12] <04> Info     [DB|ERROR]    at Veeam.Backup.DBCreator.BackupDatabaseDeployer.InternalCanDeploy(IDatabaseVersion databaseVersion)
[05.01.2021 10:33:12] <04> Info     [DB|ERROR]    at Veeam.Backup.DBCreator.BackupDatabaseDeployer.CanDeploy(IDatabaseVersion databaseVersion)
[05.01.2021 10:33:12] <04> Info     [DB|ERROR] The operation was canceled. (System.OperationCanceledException)
[05.01.2021 10:33:12] <04> Info     [DB|ERROR]    at Veeam.Backup.DBCreator.BackupDatabaseDeployer.CanDeploy(IDatabaseVersion databaseVersion)
[05.01.2021 10:33:12] <04> Info     [DB|ERROR]    at Veeam.Backup.DBCreator.BackupDatabaseDeployer.DatabaseDeploy(List`1 inDeployChangedOptions)
[05.01.2021 10:33:12] <04> Info     [DB|ERROR]    at Veeam.Backup.DBCreator.BackupDatabaseDeployer.Deploy()
[05.01.2021 10:33:12] <04> Error    The operation was canceled. (System.OperationCanceledException)
[05.01.2021 10:33:12] <04> Error       at Veeam.Backup.DBCreator.BackupDatabaseDeployer.CanDeploy(IDatabaseVersion databaseVersion)
[05.01.2021 10:33:12] <04> Error       at Veeam.Backup.DBCreator.BackupDatabaseDeployer.DatabaseDeploy(List`1 inDeployChangedOptions)
[05.01.2021 10:33:12] <04> Error       at Veeam.Backup.DBCreator.BackupDatabaseDeployer.Deploy()
[05.01.2021 10:33:12] <04> Error       at Veeam.Backup.DBManager.SqlRetryableInitializer.Init()
[05.01.2021 10:33:12] <06> Info     Stop service status tracking.
[05.01.2021 10:33:12] <04> Error    Failed to start service.
[05.01.2021 10:33:12] <04> Error    The operation was canceled. (System.OperationCanceledException)
[05.01.2021 10:33:12] <04> Error       at Veeam.Backup.DBCreator.BackupDatabaseDeployer.CanDeploy(IDatabaseVersion databaseVersion)
[05.01.2021 10:33:12] <04> Error       at Veeam.Backup.DBCreator.BackupDatabaseDeployer.DatabaseDeploy(List`1 inDeployChangedOptions)
[05.01.2021 10:33:12] <04> Error       at Veeam.Backup.DBCreator.BackupDatabaseDeployer.Deploy()
[05.01.2021 10:33:12] <04> Error       at Veeam.Backup.DBManager.SqlRetryableInitializer.Init()
[05.01.2021 10:33:12] <04> Error       at Veeam.Backup.Service.CVbServiceImpl..ctor(CVbEnvironment env, CTerminationMediator terminator)
[05.01.2021 10:33:12] <04> Error       at Veeam.Backup.Service.CVeeamBackupSvc.OnStart(String[] args)
[05.01.2021 10:33:12] <04> Info         Unregistering TCP client channel [cat_tcp]
[05.01.2021 10:33:12] <04> Info         Channel successfully unregistered
[05.01.2021 10:33:12] <04> Info     Unregistering TCP server channel [bstcp]. Port: [9392]
[05.01.2021 10:33:12] <04> Info     Channel successfully unregistered
[05.01.2021 10:33:12] <04> Info     [WinDesktop] Closing desktop 'VeeamBackupServiceDesktop'
[05.01.2021 10:33:12] <01> Error    The operation was canceled. (System.OperationCanceledException)
[05.01.2021 10:33:12] <01> Error       at Veeam.Backup.DBCreator.BackupDatabaseDeployer.CanDeploy(IDatabaseVersion databaseVersion)
[05.01.2021 10:33:12] <01> Error       at Veeam.Backup.DBCreator.BackupDatabaseDeployer.DatabaseDeploy(List`1 inDeployChangedOptions)
[05.01.2021 10:33:12] <01> Error       at Veeam.Backup.DBCreator.BackupDatabaseDeployer.Deploy()
[05.01.2021 10:33:12] <01> Error       at Veeam.Backup.DBManager.SqlRetryableInitializer.Init()
[05.01.2021 10:33:12] <01> Error       at Veeam.Backup.Service.CVbServiceImpl..ctor(CVbEnvironment env, CTerminationMediator terminator)
[05.01.2021 10:33:12] <01> Error       at Veeam.Backup.Service.CVeeamBackupSvc.OnStart(String[] args)
[05.01.2021 10:33:12] <01> Error       at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)
[05.01.2021 10:33:12] <01> Error    --- End of stack trace from previous location where exception was thrown ---
[05.01.2021 10:33:12] <01> Error       at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
[05.01.2021 10:33:12] <01> Error       at System.ServiceProcess.ServiceBase.Run(ServiceBase[] services)
[05.01.2021 10:33:12] <01> Error       at Veeam.Backup.Service.Program.Main(String[] args)

I noticed that the service SQLAgent$VEEAMSQL2016 is not started, should it be? When I try to manually start it I get:
https://i.gyazo.com/c69a3f361c9a3945c53 ... e67b97.png

[Mildur]

The sql agent service should not be needed here.
Please open a service request, your sql instance is not reachable.

<04> Info [DB|ERROR] Unable to connect to SQL Server SERVER1\VEEAMSQL2016. A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

It not allowed to post log files here in the R&D forum:

veeam-backup-replication-f2/rules-of-po ... -t755.html

Second thing, for each technical issue, you have to post the case ID here. This are the rules

[axiomcrs]

Case id is 04526502.