Databases
StackOverflow2013
Postsdbo
POMVC3 Deployed to Hosting - Worked for 16 days now SQL Error
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMVC3 Deployed to Hosting - Worked for 16 days now SQL Error
    text
    copied!<p>I've built an MVC3 application and deployed it to 3rd party hosting. After some serious fiddling with connection strings and the like I finally managed to get it connecting to the SQL DB on the hosting and the application ran fine, allowing all the bells and whistles of MVC to work (Adding, Updating, Deleting ect).</p> <p>I left the website to run for two or so weeks (making <strong>no changes</strong> whatsoever), now when I browse to it I get the following error (when custom errors turned off).</p> <pre><code>&gt; Server Error in '/' Application. &gt; &gt; A network-related or instance-specific error occurred while &gt; establishing a connection to SQL Server. The server was not found or &gt; was not accessible. Verify that the instance name is correct and that &gt; SQL Server is configured to allow remote connections. (provider: SQL &gt; Network Interfaces, error: 26 - Error Locating Server/Instance &gt; Specified) &gt; &gt; Description: An unhandled exception occurred during the execution of &gt; the current web request. Please review the stack trace for more &gt; information about the error and where it originated in the code. &gt; &gt; Exception Details: System.Data.SqlClient.SqlException: A &gt; network-related or instance-specific error occurred while establishing &gt; a connection to SQL Server. The server was not found or was not &gt; accessible. Verify that the instance name is correct and that SQL &gt; Server is configured to allow remote connections. (provider: SQL &gt; Network Interfaces, error: 26 - Error Locating Server/Instance &gt; Specified) &gt; &gt; Source Error: &gt; &gt; An unhandled exception was generated during the execution of the &gt; current web request. Information regarding the origin and location of &gt; the exception can be identified using the exception stack trace below. </code></pre> <p>I know its a problem connecting to the SQL database, but what I want to know is <strong>WHY</strong> after two weeks of running it's happened? <strong>AND</strong> if I fix it will it then happen again after another two weeks?</p> <p>Cheers.</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload