Re: Win2K3 Client / Win2K3 & 2K SQL Server DBNETLIB Problem!

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Teddy Smith (teddy_at_smith.com)
Date: 09/13/04 

Date: Tue, 14 Sep 2004 09:29:49 +0930

Hi Uri,

Thanks for your help.

When you say checked the permission issue do you mean the UID and PWD that I
am using in the connection string / DSN?. I have checked these a few times
and they all seem ok, but because the problem is random and the script
actually works most of the time, I assume they must be right?.

I also tried increasing the time out value and this seems to have no impact
at all on the problem.

I have also found some other people having similar problems such as this
one:
http://www.mcse.ms/message747245.html

but there are many more on google with the same problem.

My advice to anyone reading this would be not to upgrade their client side
servers to windows 2003 unless they have fully tested their app under load
as these problems did not show up in initial testing but under a bit of load
they seem to appear quite quickly. I am sure it has something to do with the
Windows 2003 client server, and maybe network ports or some kind of security
setting that allows it to run initially (and even retrieves some of the data
from SQL) but eventually throws this error.

Thanks again for all your help.

"Uri Dimant" <urid@iscar.co.il> wrote in message
news:eaZRSWWmEHA.3104@TK2MSFTNGP10.phx.gbl...
> Teddy
> Strange, have you checked a permission issue when it run on WIN2003
server?.
> Try to increase a timeout value in the connection string.
>
>
> "Teddy Smith" <teddy@smith.com> wrote in message
> news:ci3hjb$2kj$1@perki.connect.com.au...
> > Hi all,
> >
> > I am having a major problem with a simple application that queries a
> > database.
> >
> > Firstly we have SQL2000 SP3a running on a Windows 2003 Server with all
the
> > latest patches and updates. Windows 2003 is running the shipped MDAC 2.8
> and
> > I've run the component checker to make sure there is no problems with
the
> > installation, all is ok. The server is configured ONLY for TCP/IP, and
> > TCP/IP is also selected on the client server DSN and all the tests work
> > fine. ODBCPING also works fine so I'm sure connectivity is ok.
> >
> > The client is a Windows 2003 Standard Server with the same configuration
> as
> > above. The Client Server runs a small VB application which connects to
the
> > database via a system DSN we have setup and pulls some records from it
to
> a
> > file and then closes the connection, very very simple.
> >
> > The problem is that when this application runs (about every 10 minutes)
it
> > will randomly give the following error:
> >
> > Run-time error '-2147467259 (80004005)':
> > [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist
or
> > access denied
> >
> > I have noticed that it is more likely to give this error when the number
> of
> > rows it returns is over about 1500. I have watched it running using
> > netstat -an, and it creates many connections to the database server on
> port
> > 1433, it certainly seems to be working initially without any problems at
> > all.
> >
> > Now the tricky thing is that the exact same application running the
exact
> > same code against the exact same database server (but this time the
client
> > is running on a Windows 2000 machine) will run this all day without a
> > problem, so it seems to be directly related to the client server running
> > windows 2003.
> >
> > I have also read posts from other people with the same issue but no one
> > seems to have a solution. The problem is not with the network as I have
> run
> > many tests, traces and so on and everything is 100%, no dropped packets
> > etc.. I've also tried using the IP address instead of names for the DSN
> > etc... and nothing seems to fix it. I am certain there is something on
> this
> > windows 2003 server that causes the problem as the client on win2k
against
> > the same win2k3/sql2k server runs fne everytime.
> >
> > I am wondering if anyone has seen this or knows a real solution?. I am
> > starting to think that windows 2003 is trying to be smart and closing
TCP
> > ports or something when it should'nt be (ie whats this enhanced security
> > browser stuff?) and this is causing a connection failure. From the
> > netstat -an all seems ok, and in fact it seems to be the same behaviour
as
> > the win2k server in this way, but the win2k server will complete fine
> where
> > the 2003 will throw an error after about a minute or so of running the
> > query.
> >
> > I have also seen the following error on the new server as well:
> >
> > Run-time Error '-2147467259 (80004005)':
> > [Microsoft][ODBC SQL Server Driver] Timeout expired
> >
> > The error code is the same as the one above, so it does seem to be
> related.
> >
> > Thanks for any help, Regards.
> >
> >
>
>

Relevant Pages

  • Re: Win2K3 Client / Win2K3 & 2K SQL Server DBNETLIB Problem!
    ... Windows 2003 client server, and maybe network ports or some kind of security ... > Try to increase a timeout value in the connection string. ... >> I've run the component checker to make sure there is no problems with ...
    (microsoft.public.sqlserver.server)
  • Re: Win2K3 Client / Win2K3 & 2K SQL Server DBNETLIB Problem!
    ... Windows 2003 client server, and maybe network ports or some kind of security ... > Try to increase a timeout value in the connection string. ... >> I've run the component checker to make sure there is no problems with ...
    (microsoft.public.sqlserver.clients)
  • Re: Win2K3 Client / Win2K3 & 2K SQL Server DBNETLIB Problem!
    ... Windows 2003 client server, and maybe network ports or some kind of security ... > Try to increase a timeout value in the connection string. ... >> I've run the component checker to make sure there is no problems with ...
    (microsoft.public.sqlserver.connect)
  • Re: hangs up on send/receive
    ... IE is set to "always dial my default connection" and there ... >Jeff wrote: ... >> connection to the internet hangs up immediately when OE ... >> system file checker of Win98 and it found no problems ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)