This article explains the cause and several solutions to the BACKTRACK problem that prevents the client workstation from locating SQL database on launch.
When the BACKTRACK client workstation (using SQL) opens, it attempts to connect to the SQL database. If it cannot, it will generate an error message.
There can be several reasons it cannot connect. They include:
- SQL Server service instance is disabled (#1 below)
- SQL Server Protocols not configured correctly (#2 below)
- SQL Server name not identified correctly in btwdata.ini file (#3 below)
Solutions depend on the reason listed above.
1. SQL Server Service Instance Is Disabled or Stopped
Need to enable and run the SQL Server service for that instance. This needs to be done on the computer/server running the SQL Server database.
2. SQL Server Protocols Not Configured Correctly
Protocols that control connections to SQL Server may need to be changed to allow BACKTRACK to connect. This can be done via SQL Configuration or SQL Management Studio. The settings must be changed on the computer/server running the SQL Server database.
3. SQL Server Name Not Identified Correctly In The Btwdata.ini File (Using “Local” Instead of Server Name)
The btwdata.ini file my contain and invalid or incorrect name for the SQL Server. A common error is that the file contains “local” as the server name (e.g. using “(local)\<BACKTRACK SQL server instance name>” instead of “<Windows server name\BACKTRACK SQL server instance name>”) from the btwdata.ini file. If this is the problem, changing it to the actual server name or IP address will correct the problem.
- Changing the btwdata.ini file – KBA-01098-Q6F3D4
- Set SQL Protocols for BACKTRACK Clients to Connect to Database – KBA-01101-B5S9H8