SQL 2005 Remote Connection Error
-
Dear Web Owner, My apologies for repeating the same thread on another section. As i am confused who are the best people can ans this ASP or SQL... Thanks!! Error Details... An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) I have checked my conn string, Surface config set to local/remote, created alias aslo........WHAT NEXT PLEASE HELP Thanks for your time... Amit Amit
-
Dear Web Owner, My apologies for repeating the same thread on another section. As i am confused who are the best people can ans this ASP or SQL... Thanks!! Error Details... An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) I have checked my conn string, Surface config set to local/remote, created alias aslo........WHAT NEXT PLEASE HELP Thanks for your time... Amit Amit
I have answered it in the ASP.NET Forum. Pls check it out there.
Regards, Satips.:rose:
-
Dear Web Owner, My apologies for repeating the same thread on another section. As i am confused who are the best people can ans this ASP or SQL... Thanks!! Error Details... An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) I have checked my conn string, Surface config set to local/remote, created alias aslo........WHAT NEXT PLEASE HELP Thanks for your time... Amit Amit
Go to Configuration Manager for SQL Server 2005. Check if Shared Memory, Named Pipes & TCp/IP for the instance are enabled or not. Hopefully this should resolve ur error.
Regards SG (sgg245@yahoo.co.in)