[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

I have an application that was programmed in Classic ASP VB Script and used to connect to Access.  I'm trying to change the connection string to connect to our new SQL Server 2005 development server (within the network, then eventually to our production server outside the network). So far, no luck connecting to the Development server. I keep getting this error:

Microsoft OLE DB Provider for SQL Server error '80004005'
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
/catalog/admin/connect.asp, line 12

I have no idea if TCP/IP is set up on the machine nor do I know how to check. I've also tried using the IP address as the Data Source instead of the machine name, but get the same error.

Right now we are stuck with Classic ASP (will be converting to C# and .NET in a while, but not for now). Is there a better way to connect in classic ASP than I am using? What am I doing wrong?
set Conn = Server.CreateObject("ADODB.Connection")
Conn.Open "PROVIDER=SQLOLEDB; Data Source=AUDCMS01; Initial Catalog=ruUtility; Persist Security Info=True; Network=OURNETWORK; User ID=user; password=pass" 
set rsMAX = Server.CreateObject("ADODB.Recordset")
SQL = "SELECT Max(ID) AS MaxOfID FROM programsOfStudyDetails;"
rsMAX.Open SQL, Conn
maxID = rsMAX("MaxOfID")

if maxID <> "" then
	Response.Write "Connected! MAX ID=" & maxID
	Response.Write "Not Connected"
end if

Set rsMAX = Nothing
Set Conn = Nothing %>

Open in new window

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Raja Jegan RSQL Server DBA & Architect, EE Solution GuideCommented:
>> [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

Make sure that

* Servername and other information provided in your Connection credentials are correct
* SQL Server Service is up and running
* SQL Server Browser Service is up and running if you have multiple instances
* Remote connections are enabled properly in the server.
* You have applied latest Service packs for SQL Server and Windows OS.

Also check these links out:
vcbertiniAuthor Commented:
All of this has been verified, except how do I check to see that Remote connections are enabled properly in the server? Where do I go for that?
Om PrakashCommented:
Can you connect to SQL server using the information provided in the connection string?
Database ruUtility;
User ID=user;
Cloud Class® Course: Microsoft Office 2010

This course will introduce you to the interfaces and features of Microsoft Office 2010 Word, Excel, PowerPoint, Outlook, and Access. You will learn about the features that are shared between all products in the Office suite, as well as the new features that are product specific.

Raja Jegan RSQL Server DBA & Architect, EE Solution GuideCommented:
Check whether remote connections are enabled properly as mentioned here:


Also check out other possible connection strings here:


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
vcbertiniAuthor Commented:
I would assume I am connecting, but cannot find the SQL Server instance. Not sure why access would be denied because the login information works when I'm actually on the server.
vcbertiniAuthor Commented:

@rrjegan17 - I followed the instructions in the first article all the way up to the Windows Firewall, and as it turns out, Windows Firewall is not running, so not sure what to do with that. Tested my connection again and still receiving the same error.
vcbertiniAuthor Commented:
This was not the final solution, but lead me to investigate the firewall more closely on our test server with our Network Admin. I was finally able to point directly to our production server and get a successful connection. So the problem is not yet solved, but pretty much narrowed down to being a firewall setting issue. Our Network Admin will investigate further.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2005

From novice to tech pro — start learning today.