ASP .NET Session State : Named Pipes Provider, error: 40

Discussion in 'ASP .Net' started by J.G., Mar 9, 2006.

  1. J.G.

    J.G. Guest

    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
    J.G., Mar 9, 2006
    #1
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. piyush
    Replies:
    0
    Views:
    1,844
    piyush
    Jul 14, 2004
  2. Jeff Smythe
    Replies:
    3
    Views:
    1,239
    Jeff Smythe
    Jan 2, 2004
  3. xz
    Replies:
    0
    Views:
    858
  4. jnickfl1
    Replies:
    0
    Views:
    582
    jnickfl1
    Sep 18, 2006
  5. archana
    Replies:
    0
    Views:
    341
    archana
    Mar 13, 2007
Loading...

Share This Page