J
J.G.
I am attempting to use SQL Server 2000 for my session state management
with an ASP .NET 2.0 application. When I attempt to run the
application, I get the following error:
Named Pipes Provider, error: 40
and it states that perhaps the database is not configured to allow
remote connections (it is).
I tried using TCP/IP instead of named pipes, and its still not working.
The kicker is that we have an ASP 1.1 application that works just fine
on that cluster. When I attempt to run my .NET 2.0 application from a
development machine (not our QA cluster) it also works fine!
Any suggestions out there?
Thanks
with an ASP .NET 2.0 application. When I attempt to run the
application, I get the following error:
Named Pipes Provider, error: 40
and it states that perhaps the database is not configured to allow
remote connections (it is).
I tried using TCP/IP instead of named pipes, and its still not working.
The kicker is that we have an ASP 1.1 application that works just fine
on that cluster. When I attempt to run my .NET 2.0 application from a
development machine (not our QA cluster) it also works fine!
Any suggestions out there?
Thanks