No replies to this topic

[Mon]

If you get the error “Provider can not be found, It may not be properly installed” when you click "Test Connection" in AccuSQL, then that means AccuSQL is unable to connect to your SQL Server. The most obvious thing of course is to make sure you have typed the correct information in the connection information boxes. If yes, try the following:

(1) There is a test you can do to check if the failed connection error is caused by AccuSQL or the connection of the client computer to the SQL Server. This test is done outside of AccuSQL. If it fails, then AccuSQL will NOT be able to connect to your SQL Server and the problem is outside of the AccuSQL software:


1. Create a text file on desktop and name it
test.UDL
(Windows will prompt you about the extension. Answer "Yes" to keep it as UDL).

2. Double click the test.UDL file. A dialog box would open. On 'provider' tab select "SQL Native Client"

3. On Connection tab enter whatever you have entered in your AccuSQL database location Setup and then click 'Test Connection'.


(2) Make sure you have done the following at the SQL Server side:


1. Enable the sa and enable the SQL server authentication. These are disabled by default.


2. The firewall on the server could block access to the SQL Server. You will need to add the following as exceptions to your firewall blocking:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlservr.exe
C:\Program Files\Microsoft SQL Server\90\Shared\sqlbrowser.exe
Alternatively you could add the port instead (1433).

3. Turn on the SQL Browser on the server using SQL server configuration and set its startup to automatic if you are shutting down the server.


(3) For more details, see this Microsoft Knowledge Base article on configuring SQL Server 2005 to allow remote connections:

http://support.microsoft.com/kb/914277


NOTE: SQL Server configuration, Windows, and network issues are beyond the scope of AccuSQL support. We are providing the above information to help you with the setup of the SQL Server. If the above does not help and you still need assistance, please contact your SQL Server DBA or network administrator. If you do not have a SQL Server DBA or network administrator, we can hire a third party specialist for you for a fee. Contact us for more details.