Migrated SQL Database - Administration service process failed to create a database connection.

Dan Zabinski 191 Reputation points
2021-09-30T18:52:10.47+00:00

We just migrated our SCCM database to new SQL servers (remote system, configured as an Always On Availability Group).

For the most part everything has gone smoothly, however in the component logs for the SMS_REST_PROVIDER I'm getting the error "Administration service process failed to create a database connection." constantly.

For readability, I'm putting the error message I'm seeing in the AdminService.log in the bottom of this thread. I already know the server hosting the Administration Service has permissions to connect to SQL, and all the other servers and services seem to be connecting just fine.

I don't see anywhere that specifies which SQL server it's trying to connect to. So I'm wondering if the Administration Service didn't update it's connection string to the new servers with everything else, but I can't find a way to validate or update it.

We don't use the Administration Service yet, however it is in our plans to switch to this soon for console connections, so I'm trying to get this sorted out.

AdminService.log error: 

Exception during request processing.
System.Data.SqlClient.SqlException (0x80131904): 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: TCP Provider, error: 0 - The wait operation timed out.) ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out
   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)
   at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
   at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)
   at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
   at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
   at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
   at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
   at System.Data.SqlClient.SqlConnection.Open()
   at Microsoft.ConfigurationManager.AdminService.Data.SCCMDataSql..ctor(IList`1 allEntityTypes, IServiceConfig serviceConfig, ILogger logger)
   at Microsoft.ConfigurationManager.AdminService.DbContextMiddleware.<Invoke>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.ConfigurationManager.AdminService.RequestLoggingMiddleware.<Invoke>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.ConfigurationManager.AdminService.ThrottlingMiddleware.<Invoke>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Owin.Host.HttpListener.OwinHttpListener.<ProcessRequestAsync>d__5.MoveNext()
ClientConnectionId:00000000-0000-0000-0000-000000000000
Error Number:258,State:0,Class:20
SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
12,666 questions
0 comments
Accepted answer
  1. Dan Zabinski 191 Reputation points
    2021-10-01T13:39:08.473+00:00

    This turned out to be a generic network communications issue with the SQL server. We had a firewall rule blocking incoming SQL connections (1433) from that server to our new SQL servers.

    I thought that the logs had shown this working previously but I was mistaken. Once we opened that port all of the errors for this server were resolved.

    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Amandayou-MSFT 11,046 Reputation points
    2021-10-01T03:12:10.24+00:00

    Hi @Dan Zabinski ，

    According to your description, all the other servers and services seem to be connecting just fine, not all of the red line is mistake.

    As long as it does not affect the operation of sccm, we could ignore this red line. Please check if any error on the side of cnsole, if not, we could use sccm normally.

    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments