Re: ODBC Connect Failed SQLState 08001 SQL 2005

Tech-Archive recommends: Speed Up your PC by fixing your registry

The new SQLNativeClient interface is an OLE DB interface, not ODBC, but it should not matter.
Have you bumped up the Connection Timeout keyword in the ConnectionString?
Frankly, I have seen this behavior on old IBM networks that were heavily loaded. Depending on the security configuration, it might be an overloaded Domain Controller or a server too busy to respond....
I'm also of the opinion that an architecture that depends on long-wire connectivity needs to build in network issue management--I would expect plenty of problems as the length of wire increases and the number of bridges, routers and switches increases.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------

"Sandy Wood" <sandy.wood@xxxxxxxxxx> wrote in message news:80CA99FF-8E97-4DA0-A923-0BB7400B167A@xxxxxxxxxxxxxxxx
We're working to get our remote clients connected via ODBC to a new SQL 2005
server. Our programmers have a Powerbuilder executable that connects to the
database. Clients that are on the local, high-speed lan can connect in a few
seconds, however remote, T1 clients can take over 120 seconds to connect. The
error they get is

SQL Native Client - Unable to complete login process due to delay in opening
server connection.

I'm thinking it's a pure network issue, but I'd like to make sure I'm not
missing anything on the SQL Server side to maximize the connection time. Has
anyone seen this issue before?
--
Sandy Wood
Orange County District Attorney

.

Relevant Pages

  • Re: Error "SQL Server does not allow remote connections"
    ... The application could not connect to the sql server db. ... network is blocking the connection. ... SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 ... integratedSecurity, SqlConnection owningObject) +737554 ...
    (microsoft.public.dotnet.framework.aspnet)
  • connecting to Oracle from ASP.NET 2.0 ?
    ... I am able to access 9i and 10g Oracle DBs from other clients on my pc ... An error has occurred while establishing a connection to the server. ... When connecting to SQL Server 2005, this failure may be caused by the ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Connection from remote computer to network SQL Server
    ... There is no firewall on the W2K machine acting as the SQL server. ... I tried making the SQL machine a "trusted" on the router. ... connection works. ... To find the IP address of your computer inside the network, ...
    (microsoft.public.access.adp.sqlserver)
  • ADO.net Orcas Samples Install Problem
    ... An error has occurred while establishing a connection to the server. ... When connecting to SQL Server 2005, this failure may be caused by the ... SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, ... or am I better off with a full SQL Server install. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: OpenDataSource SQL Server xpress problem
    ... I tried your suggestions with some success. ... I tried setting up the .odc file through the Word Mail Merge wizard as ... If I work through the dialog to connect and then click the 'Test Connection' ... but I suspect it's because until recently most SQL Server ...
    (microsoft.public.word.mailmerge.fields)