Sueetie Forum
»
Sueetie Forum Discussions
»
Using Sueetie
»
Setup and Configuration
»
Network-related error: server was not found or was not accessible
Topic Tags:
no tags for this item
Rank: Guru
Joined: 1/13/2013(UTC) Posts: 84   Thanks: 10 times
|
The following is the error message and stack trace that appears when I install Sueetie on a windows 2008 R2 server. My test environment and production environment are identical accept for the difference in Operating system; my test environment is running Windows 8. All credentials, database names, and other permissions are the same:
Server Error in '/forum' Application.
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) Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: 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)
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[SqlException (0x80131904): 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)] System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +706 System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +89 System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +6415550 System.Data.SqlClient.SqlConnection.Open() +300 YAF.install.SueetieInstall.ExecuteSqlInStream(Stream stream) +978 YAF.install.SueetieInstall.ExecuteSqlInFile(String pathToSqlFile) +93 YAF.install.SueetieInstall.btnInstall_OnClick(Object sender, EventArgs e) +173 System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +154 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3707
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.272 Any information on this would be great; this is like the forth time this has happened, and the forth content management system that has had this problem. I can connect just find to the database created for the web site using the credentials I gave in the web connections.config. I would rather not reinstall SQL server Express 2012 if I can avoid it; I already reinstalled it about a month and a half ago, but it can't be a corrupt installation since things worked before. Thanks for anything you can provide. |
Administrator of the AccessCop Network, founded in 2008. |
|
|
|
|
|
Rank: Guru
Joined: 1/13/2013(UTC) Posts: 84   Thanks: 10 times
|
and I should probably say that my Windows 8 workstation where I was testing this on has the Developer Edition of SQL server 2012 and not the express edition. |
Administrator of the AccessCop Network, founded in 2008. |
|
|
|
|
|
Rank: Guru
Joined: 10/11/2009(UTC) Posts: 261  Thanks: 4 times Was thanked: 19 time(s) in 18 post(s)
|
The bad news: This one is not Sueetie-specific, so there aren't answers to this one that you would *only* find in this community.
The good news: You really don't need the stack to work this one. The error summary says it all, clearer than anyone in this community could state it. A network-related or instance-specific error occurred while establishing a connection to SQL Server. Either a typ-o in your connections.config, or there is an issue with the configuration of your SQL server.
|
|
|
|
|
|
Rank: Guru
Joined: 1/13/2013(UTC) Posts: 84   Thanks: 10 times
|
I figured it out today actually. It looks as if the (local) a.k.a. Named Pipes syntax, is not supported in the Express Version of SQL server 2012 which I was unaware of. It works fine using .\SQLExpress instead. |
Administrator of the AccessCop Network, founded in 2008. |
|
|
|
|
|
| Users browsing this topic |
|
Guest
|
Sueetie Forum
»
Sueetie Forum Discussions
»
Using Sueetie
»
Setup and Configuration
»
Network-related error: server was not found or was not accessible
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.