Re: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
From: Joel (jjimenez1984_at_yahoo.com)
Date: 06/28/04
- Next message: Chris Wilkins: "Re: Login failed for user '(null)'"
- Previous message: Lou Arnold: "Re: When will port 445 be used by SQL Server?"
- In reply to: MUTU: "Re: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied."
- Next in thread: Lou Arnold: "Re: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied."
- Reply: Lou Arnold: "Re: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied."
- Messages sorted by: [ date ] [ thread ]
Date: 28 Jun 2004 07:54:29 -0700
We're having the same problems, except with WScript since moving a
server over to Windows 2003 Server. We are connecting to SQL Server 7
on a local network, specifying TCP/IP in the connection string.
The connection failure is intermittent, but is most easily reproduced
by performing a loop where connections are opened and closed. That
will pretty much guarantee that the error will occur at some random
spot in the loop. Sometimes it fails on the first try, sometimes on
the 415th try. It seems to be completely random.
We have eliminated network issues as a possibility by isolating the
servers onto their own switch and have been able to mitigate the
problem by re-using database connections rather than opening new ones.
Probably we will open a ticket with MS soon.
If anybody has info on a fix, it would help us out tremendously to
hear about it.
Pseudo code to reproduce issue...
-------------------------------
begin loop
open database connection
execute a sql statement
close database connection
destroy connection
end loop
-------------------------------
MUTU <MUTU.18f155@mail.mcse.ms> wrote in message news:<MUTU.18f155@mail.mcse.ms>...
> same here... I optimised the scripts to reduce the number of queries and
> I've managed to reduce the number of errors, but I haven't been able to
> eliminate them.
>
> Windows 2000 used to work fine, but Windows 2003 on upgraded hardware
> and with a tenth of the number of queries (or less) gives problems.
>
> Sometimes the problem occurs when I'm trying to get a recordset, and
> sometimes it occurs when I'm connecting to the SQL Server 2000 DB.
- Next message: Chris Wilkins: "Re: Login failed for user '(null)'"
- Previous message: Lou Arnold: "Re: When will port 445 be used by SQL Server?"
- In reply to: MUTU: "Re: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied."
- Next in thread: Lou Arnold: "Re: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied."
- Reply: Lou Arnold: "Re: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|