Common TRACKER Connection Issues

This section explains common TRACKER health-check errors, their possible causes, and recommended actions.

If the connection does not recover, contact Textura Support, your ERP administrator, or your ERP consultants. Provide:

The complete error message through the approved support channel.
The organization ID and adapter name: TRACKER.
The date and time of the error, including the time zone.
Whether the error is continuing or recurring.
Any known maintenance, outage, or recent integration change.
Note: Contact support promptly if the error is not listed or affects time-sensitive work.

Select the error type for details.

The SQL Server Database Connection is Refused

General Guidance for End Users

If you see one of these errors, it does not necessarily mean you did something wrong. In most cases, the issue is related to configuration, authentication, permissions, connectivity, service availability, or backend ERP setup.

Next Steps

Capture the error message exactly as shown.
Note the approximate date and time.
Share the organization ID and any related transaction details if available.
Contact Textura Support, your ERP administrator, or your ERP consultants for investigation and resolution.

The SQL Server Database Connection is Refused

Next Topic: The SQL Server Database Connection is Refused