Jon,
Please review this KB, and see if it applies to your case :
http://support.microsoft.com/default...b;en-us;315159
If your ASP.NET worker process is running under the ASPNET account,
and your SQL server is using named pipes to receive connections,
there's a bug for the .Net Framework 1.1 and ASP.NET 1.1 :
the ASPNET account cannot establish a named pipes connection to the
SQL server, unless you do one of these two things :
1. Turn on impersonation for your ASP.NET application.
2. Use TCP/IP instead of the named pipes protocol to connect to the db.
To use TCP/IP, add "Network Library =dbmssocn" to your connection string.
"User ID=sa;Password= Password;Initia l Catalog=Shepher dRepository;Dat a
Source=server;C onnect Timeout=120;Net work Library =dbmssocn"
If you use impersonation you don't have to do that, but remember
that the Application's user will be changed to IUSR_Machinenam e
( That's why using impersonation works,
because it doesn't use the ASPNET account any more ).
Juan T. Llibre, ASP.NET MVP
ASP.NET FAQ :
http://asp.net.do/faq/
ASPNETFAQ.COM :
http://www.aspnetfaq.com/
Foros de ASP.NET en Español :
http://asp.net.do/foros/
=============== =============== ========
"Jon Delano" <jd*****@hotmai l.com> wrote in message
news:8Z******** ************@co mcast.com...
Will do .. thanks ... and did a watch on that too :-D
I appreciate all your assistance.
Thank you
"Greg Burns" <bl*******@news groups.nospam> wrote in message
news:ub******** ******@TK2MSFTN GP09.phx.gbl... Try some of these trouble shooting things.
http://support.microsoft.com/kb/827422
I would also verify with a watch that the value being read from the web.config is what
you think it is.
Greg
"Jon Delano" <jd*****@hotmai l.com> wrote in message
news:ta******** *************** *******@comcast .com... In VS 2003 ... I had changed the catch to catch ex as exception ...
Then put a break point in that section ... when it stopped there ... I did a quick
watch on ex ...
"Greg Burns" <bl*******@news groups.nospam> wrote in message
news:uM******** ********@TK2MSF TNGP12.phx.gbl. ..
You say you are getting "sql server does not exist or access denied", but I don't see
where you are recording the error in your catch statement. How can you tell what the
error is from the code you posted?
Try
...
Catch ex as exception
trace.warn(ex.t ostring)
...
Finally
...
End Try
Change your catch to something like that. You could, of course, put a breakpoint on
the catch statement itself and take a look ex's value.
Greg
"Jon Delano" <jd*****@hotmai l.com> wrote in message
news:ZO******** ************@co mcast.com...
> Oh yeah ... the server that sql server 2000 is running on is Windows 2000
>
> "Greg Burns" <bl*******@news groups.nospam> wrote in message
> news:Oi******** ********@TK2MSF TNGP10.phx.gbl. ..
>> Sorry for the bad grammar. :^) Let's try that again.
>>
>> Is this a web app? What does your connection string look like? Are you connecting
>> to SQL using integrated security? Is it trying to use your local ASPNET account?
>>
>> "Greg Burns" <bl*******@news groups.nospam> wrote in message
>> news:OK******** ********@TK2MSF TNGP12.phx.gbl. ..
>>> Is this a web app? What is does your connection string look like? Are you
>>> connection to SQL using integrated security? Is it using trying to use your local
>>> ASPNET account?
