error: SQL Server does not exist or access denied. (Article # 246)
View products that this article applies to.
Problem:
The following behaviour was observed in Microsoft SQL Server 2005 (MSSQL 2005)
In fcClient, in console_left.asp, the following error can appear:
SQL Server does not exist or access denied.
This error happens when the console left queries the database using an ADO connection, in order to retrieve the count of items in the wipbins and queues, and is unable to connect to the database.
Note that the fcClient application did start and initialize properly (meaning that it could connect to the database), and the console and console_main pages displayed properly.
fcClient uses a direct ADO connection for retrieving wipbin and queue counts, as opposed to using the fcSDK, which is why the main application can connect to the database, but the code that gets the wipbin and queue counts cannot.
Resolution:
The resolution is to enable TCP/IP as a protocol for SQL Server.
Start - Programs - Microsoft SQL Server 2005 - Configuration Tools - SQL Server Configuration Manager
Expand the SQL Server 2005 Network Configuration node in the treeview
Click on Protocols for MSSQLSERVER
In the right pane, enable TCP/IP
In order for this to take effect, SQL Server must be re-started
From within the Configuration Manager, click on SQL Server 2005 Services
Click on SQL Server
Click the Restart button (or right-click and choose Restart)
Applies To: