Re: Irritating SQL 2000/2005 connection problem
- From: "Shawn B." <leabre@xxxxxxxx>
- Date: Fri, 12 May 2006 15:57:23 -0700
One thing to look into ...shot in the dark....the TCP Provider is
mentioned...if you are authenticating to the server with something other
than
SQL server logins it may be the "network library" being used. Named pipes
may
be needed, depending on your environment....or something along this line.
We are authenticating via SQL login accounts. This works correctly with
Named Pipes (even though we have them disabled on our servers). In
production, Named Pipes is not an option, we're using a vlan between the web
servers and the sql servers, so it has to be TCP/IP.
Further, when we try the exact same code in VS.NET 2003 (framework 1.1) it
works fine.
However, we'll look into authentication and try to rule that out. Thanks.
Thanks,
Shawn
.
- References:
- Irritating SQL 2000/2005 connection problem
- From: Shawn B.
- Irritating SQL 2000/2005 connection problem
- Prev by Date: Re: How to BeginTransmit with two TabeAdapter method
- Next by Date: Provider Tracing
- Previous by thread: Irritating SQL 2000/2005 connection problem
- Next by thread: Re: Irritating SQL 2000/2005 connection problem
- Index(es):
Relevant Pages
|
Loading
