The SQL Server Database Connection is Refused

Error Message

No connection could be made because the target machine actively refused it. or 10061

Error Example

Failed to connect database and Error: (pyodbc.OperationalError) ('08001', '[08001] [Microsoft][ODBC Driver 17 for SQL Server]TCP Provider: No connection could be made because the target machine actively refused it.\r\n (10061) (SQLDriverConnect); [08001] [Microsoft][ODBC Driver 17 for SQL Server]Login timeout expired (0); [08001] [Microsoft][ODBC Driver 17 for SQL Server]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. (10061)')

Note: The \r\n characters in the example are present in the exported message and were not removed or replaced with spaces.

Meaning

The adapter could not connect to SQL Server because the target refused the connection. A stopped SQL Server service is one possible cause. Reference information about the Microsoft error 10061.

Login timeout expired does not by itself prove that the username or password is incorrect. Network connection and authentication failures occur at different stages. Microsoft connection troubleshooting.

Possible Causes

The SQL Server service may be stopped, restarting, or unavailable.
The configured server, instance, or port may be incorrect or may have changed.
SQL Server may not be accepting the required network connections.
A network or access rule may be preventing the approved connection.

Recommended Resolution

Check whether TRACKER or its database is undergoing maintenance or experiencing a known outage.

Ask your ERP administrator or database administrator to confirm that SQL Server is running and accepting connections at the approved server address and port.

If connection settings recently changed, contact Textura Support and your ERP administrator or ERP consultants to verify the integration configuration and approved network access.

After service or connectivity resumes, wait for Textura to retry.

Caution: Do not disable firewalls, expose the database publicly, or change credentials solely because of this message. Only authorized administrators should make technical changes.

Last Published Friday, October 23, 2026