DUD Scheduler Failure
Last Post 10-04-2011 08:22 PM by Chad Nash. 1 Replies.
AddThis - Bookmarking and Sharing Button
Author Messages
Mark HarleUser is Offline
going with the flow
going with the flow

10-04-2011 04:23 PM
    Hi, we are having some random scheduler failure errors with our DUD implementation.  Specifically, the scheduler will return the error message copied below on random instances. 

    The majority of the time the scheduler runs successfully.  The issue, of course, is the DUD module does not return results following the scheduler failure.

    Our environment is as follows:

    DUD: Ver:
    DNN Ver 5.6.1 Professional running on a PowerDNN server farm. 
    The scheduler runs every 60 minutes on all servers.
    We have approx 36k user accounts.

    Look forward to your suggestions.

    Thank you in advance.

    Mark Harle

    Scheduler Error Message:
    DataSprings.DNN.Modules.DynamicUserDirectory.DUDSchedulerClient, DataSprings.DNN.Modules.DynamicUserDirectory Start creation of tempDUDProfile and tempDUDPivot tables. Failed.Exception: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.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 DataSprings.DNN.Modules.DynamicUserDirectory.Data.SqlDataProvider.DataSprings_RetrieveDNNUserProfileData(Int32 PortalID, String RoleFilter, String LimitResults, Int32 AuthOnly, String strUserFilter, String strOrderBy) at DataSprings.DNN.Modules.DynamicUserDirectory.Business.DynamicUserDirectoryController.DataSprings_RetrieveDNNUserProfileData(Int32 PortalID, String RoleFilter, String LimitResults, Int32 AuthOnly, String strUserFilter, String strOrderBy) at DataSprings.DNN.Modules.DynamicUserDirectory.DUDSchedulerClient.CreateTables() at DataSprings.DNN.Modules.DynamicUserDirectory.DUDSchedulerClient.DoWork()
    Chad NashUser is Offline

    10-04-2011 08:22 PM
    Hi Mark,

    Thanks for your post... At first glance I know I have seen this before and I think this happens randomly because the server has something else going on...The primary problem though here I guess when this happens the directory PIVOT table does not exist anymore and therefore the directory fails until the next time the scheduler runs properly? We might be able to tweak the query down the road so that when this happens it will end up reverting back to the last table that was a success? Might take some work to test and so forth but that might be a good idea. Or maybe set a flag somewhere that another scheduled attempt needs to run soon.

    One option that might be available without any new code is simply changing your web.config connection string to simply have a longer timeout. It could be set to 90 seconds and setting this to something like 120 seconds might end up fixing you up. You might also have it setup to run daily instead of every hour.



  • film izle
  • 720 izle
  • film
  • sinema izle
  • film makinesi
  • T�rk�e dublaj film
  • film izle
  • film izle
  • baglan film izle
  • sinema izle
  • 1080 film izle
  • film mercegi