 |
|
|
 |
Joined: 6/17/2009
Posts: 117
|
|
|
Hello,
A few months ago we upraded to DNN 4.9.5. Today, our site was brought down. After some looking around, we noticed that the sqlservr.exe process is growing on our SQL server until it uses all of the systems resources and our website is brought down.
Any advice???
Thanks!!!
|
| |
|
|
 | |
|
|
|
You want to be sure that you configure SQL Server to only be able to consume a fixed amount of memory so that it cannot overtake the server. My personal recommendation is no more than 50% of the total physical RAM.
|
| |
|
|
| |
|
|
|
Joined: 6/17/2009
Posts: 117
|
|
|
Thank you! I am working on that right now. I am also getting the following events in the event viewer, do you think the 2 things can be related or now of a fix to this scheduling problem I am having?
| Scheduler Exception AssemblyVersion: -1; PortalID: -1; PortalName ... |
AssemblyVersion: -1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider:
ExceptionGUID:
InnerException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
FileName:
FileLineNumber: -1
FileColumnNumber: -1
Method:
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.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.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters) 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.Scheduling.DNNScheduling.SqlDataProvider.PurgeScheduleHistory() at DotNetNuke.Services.Scheduling.DNNScheduling.DNNScheduler.PurgeScheduleHistory() at DotNetNuke.Services.Scheduling.PurgeScheduleHistory.DoWork()
Source:
Server Name: TOB_WEB_PRI
|
| 2/20/2010 9:26:10 AM General Exception AssemblyVersion: -1; PortalID: -1; PortalName ... |
AssemblyVersion: -1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider:
ExceptionGUID:
InnerException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
FileName:
FileLineNumber: -1
FileColumnNumber: -1
Method:
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.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.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters) 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.Scheduling.DNNScheduling.SqlDataProvider.PurgeScheduleHistory() at DotNetNuke.Services.Scheduling.DNNScheduling.DNNScheduler.PurgeScheduleHistory() at DotNetNuke.Services.Scheduling.PurgeScheduleHistory.DoWork()
Source:
Server Name: TOB_WEB_PRI
|
| 2/20/2010 9:26:10 AM Scheduler Event Failure THREAD ID: 42; TYPE: DotNetNuke.Services.Scheduling.Purg ... |
THREAD ID: 42
TYPE: DotNetNuke.Services.Scheduling.PurgeScheduleHistory
EXCEPTION: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
RESCHEDULED FOR: 2/20/2010 10:25:40 AM
SOURCE: STARTED_FROM_BEGIN_REQUEST
ACTIVE THREADS: 0
FREE THREADS: 1
READER TIMEOUTS: 0
WRITER TIMEOUTS: 0
IN PROGRESS: 0
IN QUEUE: 10
Server Name: TOB_WEB_PRI
|
|
|
|
Thanks again!!!
Matt
|
| |
|
|
| |
|
|
|
Joined: 6/17/2009
Posts: 117
|
|
|
we were running our website on a webfarm and one of the 2 servers went down. Some of the scheduled events were set up to run only on the one server that was not running anymore and kept re-trying to run the scheduled event. After changing the event to run on the one remaining server and restarting the application and clearing cache everyhing stabled off.
Thanks!!!!
|
| |
|
|
| |