« Previous Next »

Thread: Add .NET Users fails: No Process was on the other end of the pipe.

Last post 12-31-2008 12:28 PM by colela. 2 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (3 items)

Sort Posts:

  • 12-30-2008, 6:46 PM

    • colela
    • Not Ranked
    • Joined on 12-16-2008, 8:05 PM
    • Posts 4

    Add .NET Users fails: No Process was on the other end of the pipe.

    I just installed IIS on Windows Server 2008 (64bit)  (after first installing SQL Server 2008 with default name).

    I provisioned the SQL 2008 instance using aspnet_regsql.exe using the default name (aspnetdb). (using the 64 bit version in Framework64)

    I added a user with 'log on as process' permission (named MyUser)

    I added MyUser to the aspnetdb in SQL with max permissions

    I modified the connection string for LocalSqlSever so it reads :

    Server=localhost;Database=aspnetdb;User ID=MyUser;Password=**** (Entry Type is local)

    I modified the authentication for the default site to :Forms Authentication

    I get this error when I try to add .NET Users in IIS Manager to the default web site:

    A connection was successfully established with the Server, but then an error occurred during the login process. (provider: Shared Memory Provider, error 0 - No Process was on the other end of the pipe.)

    What do I need to do to resolve this issue?  What am I missing?

    P.S.

    SQL server 2008 has Shared Memory, Named Pipes and TCP access enabled

    the Firewall is disabled.

  • 12-31-2008, 8:27 AM In reply to

    Re: Add .NET Users fails: No Process was on the other end of the pipe.

    There's nothing you can do in IIS to fix this.  Try a SQL and/or ASP.NET forum.

    Jeff

    Look for Wrox's new book Professional IIS 7 in your local bookstore, or order now at Amazon.com
  • 12-31-2008, 12:28 PM In reply to

    • colela
    • Not Ranked
    • Joined on 12-16-2008, 8:05 PM
    • Posts 4

    Re: Add .NET Users fails: No Process was on the other end of the pipe.

    Sql server by default is setup to use windows authentication.  The password portion of the connection string is for a SQL password.

    Removing the password portion and replaceing it with :

    Integrated Security=True

    Solves the problem.

    So the connection string should be:

    Server=localhost;Database=aspnetdb;User ID=MyUser;Integrated Security=True

    You have to check custom connection string in the dialog box for the connection string and modify it directly.

    P.S.

    Make sure the user you choose has sysadmin permission and is set up to logon as service.

    The documentation for Sql Server provisioning for IIS could be better.

Page 1 of 1 (3 items)
Microsoft Communities