After 2 Years DNN DotNetNuke Site Dies

I have had our DotNetNuke site up for 2 years now with no problems.

http://www.acocares.org/aco/

No changes have been made to the files on the site (other the jpg's and pdf's). No changes were made to the webpages for 3 days before the error. This is a very simple site with a very simple DNN DB that has not changed in years. As of Friday August 16th, the site has been down with the following error:

ERROR: Could not connect to database.

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: 0 - Insufficient system resources exist to complete the requested service.)

---

This is the part that gets me "Insufficient system resources exist to complete the requested service". What can I do.. I have backups, but all the data is IDENTICAL! I think it's a Webserver or SQL Server issue. What can I do??? I need to get this back up and running but am at a loss as to what has happened when nothing was changed and the data on the server is the same as the data in my backups.

Here is the website: http://www.acocares.org/aco/

Thanks for any help you can give this non-profit organization that helps people in need.

Jean-Marie Vaneskahian
[email protected]

 

Are you upgrading DotNetNuke?

DotNetNuke Upgrade Error - The Assembly Version ( [ASSEMBLYVERSION] ) does not match the Database Version ( [DATABASEVERSION] )

If so, there may bea configuration file that is lacking the proper information...aside from that maybe a DNN user can shed some light.

You might also try resetting the password in the Control Panel SQL 2005 Login Manager, just to make sure it matches your config/connection string.

 

Nope, there is no upgrade at all. I have never upgraded this site in its entire history. All of the files on the site are exactly as they were when the site was created 2 years ago. The only files that have been added are some jpg?s and pdf?s (and those were done over the history of the site, the last one being uploaded over a month ago).


From reading the DotNetNuke forums the Upgrading message is a canned response with the lack of database connectivity.


I have verified that my SQL connect strings are still correct (the web.config was last changed 2 years ago). And I also even tried connecting to the SQL DB via SQL Management Studio. I can FTP to the Website and I can also connect SQL Management Studio to the SQL DB using the proper connect string credentials and server. The problem I think is that the Website cannot connect to the SQL DB. Part of the error message that I think explains the problem is: "Insufficient system resources exist to complete the requested service". I have stopped and restarted the IIS service via the DiscountAsp.net web based control panel to no avail. I think perhaps the process is out of resources. Again, nothing has changed.


Any ideas?


Thanks for the help.


Jean-Marie Vaneskahian
[email protected]

 

Here are some postings I have found on this error:


http://209.85.215.104/search?q=cache:tmnBwgAMX3YJ:blogs.msdn.com/sql_protocols/archive/2005/09/28/474698.aspx+%22provider:+HTTP+Provider%22+DNN&hl=en&ct=clnk&cd=2&gl=us


----


"An error has occurred while establishing 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: HTTP Provider, error: 0 - )"


This occurs randomly, but always under heavy _client_ load. I suppose client first tries some other "provider", but fails, and HTTP provider isn't configured.


-----


Hi


I encounterd a rare error,that was 'provider: HTTP Provider, error: 0 - ' with managed SqlClient.


Of course,I did not make a HTTP end point.


This error occured when SQL Server was doing heavy batch process.


SqlClient might have tried to connect the (local)instance with shared memory protocol,but failed.


In past,Koterpillar posted about this HTTP provider error,and I entirely agree with him.


----

 

The web server is now up and running.

Here was the fix:
www.fasthostinghelp.com/error-assembly-version-assemblyversion-t81.html?s=baa9a3b38c595dcfbc00f837d7e5d687&s=fecd12ee7902be831c6bf9ebcf5971ca&p=160

Even though the site had never been upgraded or the config (or any) files modified since it was setup 2 years ago, the 'web.config' file still needed to be updated to make the site work now.

Here is the entry that needed to be made in the web.config:

<appSettings>
<add key='UseDnnConfig' value='false' />
</appSettings>

I hope this information will help others, though I am still very baffled by what made this setting necessary after all this time.

Jean-Marie Vaneskahian
[email protected]

 

I still would like to know, if anyone has the answer, why did the site require this change after it has been up and running for so long?