Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Error - DBNETLIB ConnectionOpen Connect SQL Server does not exist or access denied

1,292 views
Skip to first unread message

Don

unread,
Jan 6, 2004, 6:01:25 PM1/6/04
to
Hi,

I have an urgent matter that I need assistance with if any are able to help. I have been getting an error message intermittently and with a recent surge in traffic on our web site the error is occurring much more frequently, but the error is still intermittent:

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

The error occurs randomly and it is from an ASP application accessing a SQL2K database. IIS and SQL2K are on separate machines both running Windows 2003 Server.

The Web server has Dual 2.66 Ghz processors with 2GIGs RAM, SCSI drives. The SQL box has a single 2.66 Ghz processor with 1GIG RAM.

Here is the connection string I am using:
strConnString = "Provider=SQLOLEDB;Data Source=xxx.xxx.xxx.xxx;Network Library=DBMSSOCN;Initial Catalog=dbname;User ID=username;Password=password"

We already have setup an alias for the sql server. Have tried moving the databases to a new machine. We have also replaced the network cards in both machines and verified that connectivity is good. But the error persists.

Any ideas how to resolve this?

Thanks in advance!

dFunk

unread,
Jan 7, 2004, 2:20:34 PM1/7/04
to
I am having the exact same problem on a very similar setup (Two
Win2k3, single CPU boxes.) I've been scouring the message boards and
am currently looking at connection pooling as a culprit based on other
discussions.

These servers have very little traffic, so I don't think it is a
typical timeout problem, and the application works perfectly on dozens
of other insallations, so it isn't with the code.

Since it happens once every other day or so, troubleshooting is very
difficult.

Don Galbraith

unread,
Jan 7, 2004, 3:22:11 PM1/7/04
to

What have you read about connection pooling? Can you direct me to some
information?

In case you haven't seen it yet there is an MS KB article on this error
but it didn't do the trick for us.

http://support.microsoft.com/?id=328306


*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

dFunk

unread,
Jan 8, 2004, 9:45:50 AM1/8/04
to
Here's the thread that I found about connection pooling:

http://groups.google.com/groups?hl=en&lr=&ie=UTF8&oe=UTF8&threadm=02aa01c3a3c1%2410c334f0%24a101280a%40phx.gbl&rnum=1&prev=/groups%3Fhl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3DUTF8%26scoring%3Dd%26selm%3D02aa01c3a3c1%252410c334f0%2524a101280a%2540phx.gbl

From what I could understand, it sounded like what may be happening.
But the bad news is I turned off connection pooling and still got the
error last night.

I've seen a few other threads mentioning similar problems, but no
solutions.

I have GOT to get this fixed so I'll keep searching and trying things.

Paul Bowley

unread,
Jan 30, 2004, 10:25:04 AM1/30/04
to
Don <requir...@hotmail.com> wrote in message news:<62EF312C-D654-485A...@microsoft.com>...

Did you manage to track down the source of this error? I am having
similar problems but with a ColdFusion application. Once the error
occurs, which is about twice a day, I have to restart the ColdFusion
server to clear it. It seems to be related to memory usage by the
ColdFusion server; once this reaches about 150 MB, the error starts
occurring.

mkiv_eurotrash

unread,
Feb 13, 2004, 2:31:41 PM2/13/04
to

Hey,

Has anyone found a solution to this problem. I'm having the same issue.
Very random occurrances of the error followed by some server timeouts.
The thing is though, I know other people are not experiencing any
problems because sales have been through the roof. Any info or even a
finger in the right direction would help soooo much. Thanks!

Joel


mkiv_eurotrash
------------------------------------------------------------------------
Posted via http://www.mcse.ms
------------------------------------------------------------------------
View this thread: http://www.mcse.ms/message252185.html



berdy

unread,
Feb 23, 2004, 6:38:17 AM2/23/04
to

I am have exactly the same problem and my set up is very similar to
yours.

Unfortunately I cannot offer a solution but this has been happening to
me EVER SINCE I upgraded to W2003. I too have changed servers for my
SQL2K DB last week and had no success. The error message only seems to
appear when useage is high, ie not just me!! My very weak, guessed
theory is that it is something to do with the set up in W2003. I am
going to put my system back onto a W2K box today and see if it solves
the problem.

I will let you know if I have any success. What I can say is that in
November when this started happening there was next to nothing on the
internet about it and now there is this thread and one or too more,
which I find slightly comforting.

=?Utf-8?B?RG9u?= wrote:
> *Hi,

> Thanks in advance! *

--
berdy

nl_bennie

unread,
Mar 4, 2004, 6:27:16 AM3/4/04
to

Hi,
I have the simular problem has there been a solution yet?
Please let me know.
Thanks in advance,
Bennie.

--
nl_bennie

mrgray

unread,
Mar 5, 2004, 3:51:07 AM3/5/04
to
Hi,

I've just tried to go from IIS4 to IIS6 for one server, access to DB SQL7 under NT4, same problem...
no solution for the moment... going back to IIS4.

DELL hardware ?

Al Degutis

unread,
Mar 19, 2004, 7:51:30 AM3/19/04
to
We had the same problem on a 2003 server running client software that makes
an ODBC connection to a 2003 server running the DB. It would randomly drop
it's connection with:

Unexpected error: [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL
Server does not exist or access denied.

After reading this thread, our short-term fix was to downgrade the 2003
server client to Windows 2000. We're testing the resolution listed in the
following KB doc on a separate 2003 server and for the now the error seems
to be gone. It might be the workaround.

http://support.microsoft.com/default.aspx?kbid=315159

Al

"nl_bennie" <nl_benni...@mail.mcse.ms> wrote in message
news:nl_benni...@mail.mcse.ms...

David Russell

unread,
Mar 30, 2004, 8:50:38 AM3/30/04
to

Hi,

We are having very similar problems. We recently upgraded all our
hardware and OS's from a W2K environment. Our SQL server is SQL 2000
enterprise running on Windows 2003 enterprise. The hardware is Dell 6650
quad Xeon processors. We have recently been advised by Microsoft to
disable the hyperthreading capability with Xeons, which gave us 8
logical processors, and this seems to have made a small improvement.
This is particularly annoying as we only upgraded our Windows 2003 so
that we could take advantage of multiple CPU's and memory of 8g

Your last note said you were going back to W2K and maybe that is what we
will do as well.

Al Degutis

unread,
Mar 30, 2004, 9:46:04 AM3/30/04
to
David,

If you didn't see my post on this issue, here's what we found:


We had the same problem on a 2003 server running client software that makes
an ODBC connection to a 2003 server running the DB. It would randomly drop
it's connection with:

Unexpected error: [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL
Server does not exist or access denied.

After reading this thread, our short-term fix was to downgrade the 2003
server client to Windows 2000. We're testing the resolution listed in the
following KB doc on a separate 2003 server and for the now the error seems
to be gone. It might be the workaround.

http://support.microsoft.com/default.aspx?kbid=315159

Al

"David Russell" <d...@aardsoft.net> wrote in message
news:%23vK883l...@TK2MSFTNGP11.phx.gbl...

0 new messages