Connection String from Solution Explorer. [modified]
-
Hi, 1) Can anybody tell me how can generate the connection string to my SQL Database from the solution explorer in VisualStudio2008. 2) Also can anybody tell me how i can resolve his error in my SQL;I tried the settings from Surface Area Config: but it didn't help :( Error "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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)" Many Thanks,
modified on Sunday, October 19, 2008 12:32 PM
-
Hi, 1) Can anybody tell me how can generate the connection string to my SQL Database from the solution explorer in VisualStudio2008. 2) Also can anybody tell me how i can resolve his error in my SQL;I tried the settings from Surface Area Config: but it didn't help :( Error "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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)" Many Thanks,
modified on Sunday, October 19, 2008 12:32 PM
new2pgrmg wrote:
Can anybody tell me how can generate the connection string to my SQL Database from the solution explorer in VisualStudio2008.
The solution explorer displays the files in your solution. It can not be used to create a connection string.
new2pgrmg wrote:
Also can anybody tell me how i can resolve his error in my SQL;I tried the settings from Surface Area Config: but it didn't help
What error?
Despite everything, the person most likely to be fooling you next is yourself.
-
new2pgrmg wrote:
Can anybody tell me how can generate the connection string to my SQL Database from the solution explorer in VisualStudio2008.
The solution explorer displays the files in your solution. It can not be used to create a connection string.
new2pgrmg wrote:
Also can anybody tell me how i can resolve his error in my SQL;I tried the settings from Surface Area Config: but it didn't help
What error?
Despite everything, the person most likely to be fooling you next is yourself.
Hi Guffa; Thanks for trying to help. For my first question i found the soln from server explorer. "http://kb.seekdotnet.com/ViewArticle/119data.aspx" For the second question this is my error message "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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)" Thanks for the help
-
Hi Guffa; Thanks for trying to help. For my first question i found the soln from server explorer. "http://kb.seekdotnet.com/ViewArticle/119data.aspx" For the second question this is my error message "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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)" Thanks for the help
The error message simply means that no SQL Server is responding on the server address that you specified in the connection string. Have you checked the address in the connection string? If you have a firewall between the application server and the database server, you need to make sure that the port used by SQL Server is forwarded to the database server.
Despite everything, the person most likely to be fooling you next is yourself.
-
The error message simply means that no SQL Server is responding on the server address that you specified in the connection string. Have you checked the address in the connection string? If you have a firewall between the application server and the database server, you need to make sure that the port used by SQL Server is forwarded to the database server.
Despite everything, the person most likely to be fooling you next is yourself.
Hi Guffa, Thanks for the help. I resolved the issue.There was some issue with the connection string ;after resolving it my connection is working fine.The take away for me from here is if there is any issue with the connection string this error will happen. Thanks Again for your replies..... Keep up the spirit....