Re: SQLConnect

I would guess though that your test machine doesn't get the
same traffic and the same activity as the production server.
So it really isn't odd to have issues in one environment and
not the other even with the same configurations.
The first one...locking or blocking issues could do that,
UMS issues, a lot of things. You need to be monitoring the
server to see what's going on when this happens.

The second one...a lot of things. Refer to the following for
more information:
Potential causes of the "SQL Server does not exist or access
denied" error message
http://support.microsoft.com/?id=328306

The third one is not an error. That's an informational
message which can be ignored. You'd need to handle
informational messages in your app.

-Sue

On Fri, 1 Sep 2006 08:20:22 -0500, "Weston Fryatt"
<wfryatt@xxxxxxxxx> wrote:

Environment:
Windows 2003 Enterprise Server (Production Server)
SQL Server 2000 Standard Edition (with Service Pack 4 installed)

Windows 2003 Enterprise Server (Test Server)
SQL Server 2000 Enterprise (with Service Pack 4 installed)


I'm getting three different ODBC error:

>> Error At:Login: SQLConnect
SQL RC:-1
State:HYT00
SQL Error:[Microsoft][ODBC SQL Server Driver]Timeout expired
SQL Native Error Code:0

>> Error At:Login: SQLConnect
SQL RC:-1
State:08001
SQL Error:[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server
does not exist or access denied.
SQL Native Error Code:17

>> Error At:Login: SQLConnect
SQL RC:-1
State:01000
SQL Error:[Microsoft][ODBC SQL Server Driver][SQL Server]Changed
database context to 'CDMS8'.
SQL Native Error Code:5701


These error are on our production server only, on my test server which is
the same configuration, I don't get any of these ODBC errors. In both cases
the SQL Server is "local" to both machines. So their no possibility of
network traffic, Firewalls, bad cables, etc.

I've already check and the ODBC System DSN is set to use "local host" as the
name of the server to connect to, We use "Mixed Mode" and login as the "sa"
account. Also the default database is set to the correct named database.

What would cause these errors?

Thanks,
Weston Fryatt
Sr. Software Engineer
The SSI Group, Inc.




.

Relevant Pages

  • RE: Fulltext failure on a 2 node cluster
    ... Server full-text search resource online: "SQL Cluster Resource 'Full Text' ...
    (microsoft.public.sqlserver.clustering)
  • Re: HELP PLEASE ~ ???
    ... You mentioned that it went ahead and added a SQL ... SQL Server 2000 database for all my data. ... find the connectionString in the newly recreated SQLExpress database. ... The connection string specifies a local Sql Server Express instance ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Multi-Channel Raid VS SAN Storage
    ... A 5~6 years old server is a very old server. ... As I mentioned, the server is one node in a cluster environment, and SQL is ... We actually are running RAID 1+0 and our aplication is definately more ... needs it's own SAN device, or at least a dedicated IO channel on the SAN. ...
    (microsoft.public.sqlserver.setup)
  • Re: Multi-Channel Raid VS SAN Storage
    ... A 5~6 years old server is a very old server. ... As I mentioned, the server is one node in a cluster environment, and SQL is ... We actually are running RAID 1+0 and our aplication is definately more ... needs it's own SAN device, or at least a dedicated IO channel on the SAN. ...
    (microsoft.public.sqlserver.setup)
  • RE: How do I get back to base SQL server on my SBS 2003 server?
    ... After you uninstall SQL 2005, the instance which you upgraded will not go ... Uninstall and then reinstall ISA server. ... Uninstall and then reinstall the Monitoring component. ... Tools to Maintenance, change Monitoring component to Install, and then ...
    (microsoft.public.windows.server.sbs)
Loading