Custom Membership

[nightday]

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">
<providers>
<clear/>
<add name="SpiritMovedMembershipProvider"
type="SpiritMoved.MembershipProvider.SpiritMovedMembershipProvider"
connectionStringName="SpiritMovedConnectionString"
enablePasswordRetrieval="true"
enablePasswordReset="true"
requiresQuestionAndAnswer="false"
writeExceptionsToEventLog="false" />
</providers>
</membership>

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

 

[Stephen]

is it using 127.0.0.1 for SQL?

 

[nightday]

No the sql is setup to go to mssql8.mydomain.com with the proper userid/pwd

 

[SubSpace]

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

 

[nightday]

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

 

[SubSpace]

The error message led me to believe you were:

(provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

You might want to check your connection string, just to be sure.

 

[kawaldeep]

The error message led me to believe you were:


You might want to check your connection string, just to be sure.

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