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.0System.Data.SqlClient.SqlConnection.OnError  TimeoutSystem.Data.SqlClient.SqlConnection.OnError Timeout
Previous
 
Next
New Post
7/31/2008 4:48 AM
 

Hi,

First of all I appologize if posting in the wrong forum, but I could not find any category that was more appropriate for the character of my problem.

Recently we have experienced that our dotNetNuke (4.5) platform has become painfully slow even though, to the best of our knowledge, there has been no changes in its configuration (including adding new modules) or in traffic patterns. A possible explanation can be found in the event viewer. Basically hundreds and again hundreds of sql timeout errors are encountered that are not tied to a particular funciton. See bottom of this post.

So far, I have found it hard to find the cause of this or even to constructively fault search the error. Would really appreciate feedback on this as it is really threatning our service.

Kind Regards

Carl

DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: ed1bab9b-6eac-4d7e-847c-7cc54f5c66ed
InnerException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
FileName:
FileLineNumber: 0
FileColumnNumber: 0

Method: System.Data.SqlClient.SqlConnection.OnError
StackTrace:
Message: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlDataReader.ConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(SqlConnection connection, SqlTransaction transaction, CommandType commandType, String commandText, SqlParameter[] commandParameters, SqlConnectionOwnership connectionOwnership) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues) at DotNetNuke.Services.Scheduling.DNNScheduling.SqlDataProvider.GetNextScheduledTask(String Server) in C:\portals.wmu.se\Library\Providers\SchedulingProviders\DNNScheduler\Providers\SqlDataProvider\SqlDataProvider.vb:line 125 at DotNetNuke.Services.Scheduling.DNNScheduling.SchedulingController.GetNextScheduledTask(String Server) in C:\portals.wmu.se\Library\Providers\SchedulingProviders\DNNScheduler\SchedulingController.vb:line 68 at DotNetNuke.Services.Scheduling.DNNScheduling.DNNScheduler.GetNextScheduledTask(String Server) in C:\portals.wmu.se\Library\Providers\SchedulingProviders\DNNScheduler\SchedulingProvider.vb:line 118 at DotNetNuke.Services.Scheduling.SchedulingProvider.set_ScheduleLastPolled(DateTime Value) in C:\portals.wmu.se\Library\Components\Providers\Scheduling\SchedulingProvider.vb:line 112 at DotNetNuke.Common.Global.Application_BeginRequest(Object sender, EventArgs e)

 
New Post
7/31/2008 1:20 PM
 

Carl,

I'm still kind of a newbie in the DNN world so my suggestions could be far off - hopefully not.

I've read an article somewhere that suggested that certain SQL timeouts and problems could be caused if the Cache time for a module was not great enough.  You might try logging in as Host and going to Module Definitions.  Click the edit icon (the pencil) for each of the modules you have in your portal and ensure that the Default Cache Time is set to 0 or -1.

Beyond that - I don't believe you stated the database backend you're using but if it's SQL Server you should probably run a trace in SQL Profiler to see exactly what queries are timing out.  With that information you may have some ammo to attack the problem.  Have you added any custom tables to your database?  If so, you may have an index problem.

Good luck,

BK

 
New Post
7/31/2008 3:34 PM
 

If nothing was done, then it must be the hardware/system software deviation.

Find a better host/server?

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0System.Data.SqlClient.SqlConnection.OnError  TimeoutSystem.Data.SqlClient.SqlConnection.OnError Timeout


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