Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Complete/working installtion randomally claims "DotNetNuke Upgrade Error"Complete/working installtion randomally claims "DotNetNuke Upgrade Error"
Previous
 
Next
New Post
5/4/2007 8:19 PM
 

I am using DNN 4.3.5 and developing custom modules with it.  I am also using AJAX.NET 1.0 and the ControlToolkit in my module.  Everything works with IIS 6.0 running on windows server 2003.  Randomly when trying to browse to my site via http://localhost/[My Install] / it will give me the following error, even though my site was working perfectly fine before (no code changes).

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

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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server).

Here are some things I have found out:

  • The MS SQL Server 2005 is still up and running.
  • A sql server trace reveals no open connections or connection attempts.
  • I am using IIS 6.0 and my site is in its own application pool using .NET 2.0.
  • Other sites on this computer are still up and running; even running off the same SQL Server.
  • The SQL connection string in my web.config still successfully works using other applications. 


The windows event log gives me the following error:

Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 5/4/2007 7:49:22 PM
Event time (UTC): 5/4/2007 11:49:22 PM
Event ID: 12477364ea3545eea282ca2a64fa9780
Event sequence: 5
Event occurrence: 2
Event detail code: 0


Thread information:
    Thread ID: 1
    Thread account name: NT AUTHORITY\NETWORK SERVICE
    Is impersonating: False
    Stack trace:    at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.SqlClient.SqlConnection.Open()
   at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters)
   at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText)
   at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues)
   at DotNetNuke.Data.SqlDataProvider.GetPortals()
   at DotNetNuke.Entities.Portals.PortalController.GetPortals()
   at DotNetNuke.Common.Global.CacheMappedDirectory() in d:\inetpub\wwwroot\mysite\App_Code\Global.asax.vb:line 145
   at DotNetNuke.Common.Global.Application_Start(Object Sender, EventArgs E) in d:\inetpub\wwwroot\mysite\App_Code\Global.asax.vb:line 255


Thread information:
    Thread ID: 5
    Thread account name: NT AUTHORITY\NETWORK SERVICE
    Is impersonating: False
    Stack trace:    at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.SqlClient.SqlConnection.Open()
   at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters)
   at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText)
   at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, String spName, Object[] parameterValues)
   at DotNetNuke.Services.Log.EventLog.DBLoggingProvider.Data.SqlDataProvider.PurgeLog()
   at DotNetNuke.Services.Log.EventLog.DBLoggingProvider.DBLoggingProvider.PurgeLogBuffer()
   at DotNetNuke.Common.Global.LogEnd() in d:\inetpub\wwwroot\mysite\App_Code\Global.asax.vb:line 124
   at DotNetNuke.Common.Global.Application_End(Object Sender, EventArgs E) in d:\inetpub\wwwroot\mysite\App_Code\Global.asax.vb:line 285


The weird thing is, this will last for about 10 or so minutes and then my site will just up and start running again.  It’s a hassle when it happens several times a day. 

So far I have tried the following:

  • restarted the IIS service
  • stopped/restarted the webpage
  • removed my site from the application group and re-added
  • restarted the SQL service on the DB server
  • recompiled my project
  • verified connection string and DB

…. and nothing brings the site back online.  Anyone have any ideas? I’m stuck!  Thanks

 
New Post
5/5/2007 9:40 PM
 

Applications shutting down is often associated with the workthread consuming too much memory and being forced to close by the IIS process.

Also if you are doing work with AJAX - you should really consider moving to 4.5.1

- there are a lot of performance enhancements in the builds between 4.3.5 and 4.5.1 that may possibly resolve the issues youare seeing.

Westa

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Complete/working installtion randomally claims "DotNetNuke Upgrade Error"Complete/working installtion randomally claims "DotNetNuke Upgrade Error"


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out