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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DNN 6.0 503 ErrorsDNN 6.0 503 Errors
Previous
 
Next
New Post
7/29/2011 9:30 AM
 
When adding a simple module to a pane, the application crashes and spits out a 503 error. I can't understand why this is happening since this is a server error and an application error.

At first I figured, ok, maybe something corrupted the database. I did a restore from a recent bak successfully and no change. I can't understand how adding a simple module to a page could cause something like this to happen.

This happened twice. The first time I cleared out the website and reinstall DNN over again. The site came back up but then it happened again.

Ideas?
 
New Post
7/29/2011 6:48 PM
 
a 503 happens when a site cannot process requests - generally when it is performing too much work. I'd recommend running a http proxy such as fiddler to see if the request is going into an infinite page loop - also consider running sql profiler to see if there are a mass of database updates (db loop)

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
7/31/2011 6:04 PM
 

I'm get this error whenever I'm updating page information at admin > pages. Specifically actions on SEO and Design.

First I'll get get a connection timed out error and when I try to get back into my site I'll get the 503 error. Each time, I've restarted the server and recycled my app. On one instance I got the stack trace.

Server Error in '/' Application.
There is insufficient system memory in resource pool 'internal' to run this query.
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: There is insufficient system memory in resource pool 'internal' to run this query.
 
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): There is insufficient system memory in resource pool 'internal' to run this query.]
   System.Data.SqlClient.SqlConnection. (SqlException exception, Boolean breakConnection) +404
   System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning() +412
   System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +1363
   System.Data.SqlClient.SqlDataReader.ConsumeMetaData() +58
   System.Data.SqlClient.SqlDataReader.get_MetaData() +118
   System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) +6369073
   System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) +6370642
   System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) +538
   System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) +28
   System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) +256
   System.Data.SqlClient.SqlCommand.ExecuteReader() +291
   System.Data.SqlClient.SqlCommand.DeriveParameters() +2884699
   System.Data.SqlClient.SqlCommandBuilder.DeriveParameters(SqlCommand command) +241
   Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.DiscoverSpParameterSet(SqlConnection connection, String spName, Boolean includeReturnValueParameter, Object[] parameterValues) +122
   Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSetInternal(SqlConnection connection, String spName, Boolean includeReturnValueParameter) +237
   Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSet(String connectionString, String spName, Boolean includeReturnValueParameter) +103
   Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues) +100
   DotNetNuke.Data.SqlDataProvider.GetEventMessages(String eventName) +133
   DotNetNuke.Common.Initialize.InitializeApp(HttpApplication app) +559
   DotNetNuke.Common.Initialize.Init(HttpApplication app) +167
   DotNetNuke.HttpModules.RequestFilter.RequestFilterModule.FilterRequest(Object sender, EventArgs e) +232
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +80
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +270
 
 
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.225

DNN 6.0
SQL 08 R2 64
Win 7
IIS 7
IE9, FF5

I'm still testing and trying to track down the issue, but if anyone cares to share any knowledge on this, I'm all ears.

 
New Post
7/31/2011 8:18 PM
 
FWIW the memory footprint of dnn600 seems to require a worker pool of up to150meg.  

On a clean install after login and opening of Host and Admin settings and a HTML Content Editor - our worker pool is sitting at 125 meg.

If you are on a hosting that limits the worker pool memory to 100meg - which used to be common then it could be contributing to the problems you are seeing.

Westa
 
New Post
7/31/2011 9:37 PM
 

Thanks Wes,

This is a local install with a seperate app pool and no restrictions. But I think I found the issue.

Working with a custom skin, I found out I had to register the DDRMenu namespace. Which is weird because it seemed like the CP and other admin pages were functioning just fine except for those small issues.

So, to everyone else, make sure to add this into your skins

<%@ Register TagPrefix="dnn" Namespace="DotNetNuke.Web.DDRMenu.TemplateEngine" Assembly="DotNetNuke.Web.DDRMenu" %>

So far no more issues, so I'm pretty sure this was it.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DNN 6.0 503 ErrorsDNN 6.0 503 Errors


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