Custom Membership

Discussion in 'Microsoft Development' started by nightday, May 9, 2009.

  1. nightday

    nightday Guppy

    Hey everyone,

    I've developed a custom membership provider and it works great locally. When I move it to the jodo servers, I get this error.

    A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

    My connection string is definately ok as I confirmed everything in there. My web.config membership tag looks like this

    <membership defaultProvider="SpiritMovedMembershipProvider" userIsOnlineTimeWindow="15">
    <add name="SpiritMovedMembershipProvider"
    writeExceptionsToEventLog="false" />

    Everything looks ok to me so I have no idea, any ideas?
  2. Stephen

    Stephen US Operations Staff Member

    is it using for SQL?
  3. nightday

    nightday Guppy

    No the sql is setup to go to with the proper userid/pwd
  4. SubSpace

    SubSpace Bass

    I'm not sure named pipes are supported. Try using TCP/IP instead?
  5. nightday

    nightday Guppy

    I'm not using Named pipes though, unless I am missing something
  6. SubSpace

    SubSpace Bass

    The error message led me to believe you were:
    You might want to check your connection string, just to be sure.
  7. kawaldeep

    kawaldeep Perch

    This is correct in most cases this is the reason. If still needing aid then send us ticket with complete DB details in ticket.

Share This Page

JodoHost - 26,000 hosting end-users in 100 countries
Plesk Web Hosting
VPS Hosting
H-Sphere Web Hosting
Other Services