Print Page | Close Window

Database Setup Issues on New Server

Printed From: LogSat Software
Category: Spam Filter ISP
Forum Name: Spam Filter ISP Support
Forum Description: General support for Spam Filter ISP
Printed Date: 19 January 2019 at 12:25pm

Topic: Database Setup Issues on New Server
Posted By: bdaniels
Subject: Database Setup Issues on New Server
Date Posted: 28 July 2009 at 10:34pm
I am in the process of migrating my Spam Filter installation from a virtual machine to a physical server.   I currently have 2 servers connected to a single database cluster on the backend.   I have installed a 3rd server and want to pre-configure it before I retire one of the virtual servers.   However, when I configure the Database setup on the new server, I get the following error when tesing the DB string:
Test connection failed because of an error in initializing provider.
[DBNETLIB]ConnectionOpen (Connect()).]SQL Server does not exist or access denied
I am using the exact same string as the other servers and it works fine on them.  I can telnet to the SQL port from the new server, so the server is reachable, and the login works for the other 2 servers I have configured.   Are there any other configuration changes that need to be made on the new server?

Posted By: LogSat
Date Posted: 29 July 2009 at 4:43pm
For the connection string, are you using a .UDL file (Microsoft Universal Data Link), or are you specifying the actual full OLEDB/ODBC string with its parameters?

If using a .UDL file (the recommended method), if you double-click this file and click on "Test Connection", are you able to connect successfully?

If you're using a full connection string, what provider are you using? In addition, can you make sure that on the client (SpamFilter's server), using the SQL Server Client Network Utility (%system32%\cliconfg.exe), you have "TCP/IP" as an enabled protocol, and that it is first in the list of enabled protocols?

Also, when you say that you can telnet into the SQL port, you are referring to port 1433, correct? 

Roberto Franceschetti" rel="nofollow - LogSat Software" rel="nofollow - Spam Filter ISP

Posted By: bdaniels
Date Posted: 30 July 2009 at 12:32am

I figured it out, we are using a non standard port for our SQL server.   For some reason the Alias we have configured in SQL Server Client Utility was not actually working.  

I bypassed it by putting a comma and the port number after the server name in the connection string.
Thanks for the reply

Print Page | Close Window