We upgraded our system recently from 9.3.1 to 9.10.1 and I am now seeing millions of entries in the event log.
We only have a few non DNN extensions installed:
The errors are:SCHEDULER_EVENT_FAILURE and SCHEDULER_EXCEPTION
THREAD ID 35 TYPE DotNetNuke.Services.Social.Messaging.Scheduler.CoreMessagingScheduler, DotNetNuke EXCEPTION Object reference not set to an instance of an object. RESCHEDULED FOR 1/1/0001 12:00:30 AM SOURCE STARTED_FROM_TIMER ACTIVE THREADS -3916641 FREE THREADS 3916642 READER TIMEOUTS 0 WRITER TIMEOUTS 0 IN PROGRESS 0 IN QUEUE 10
Ideas on what the issue could be?
Many thanks!
Ron
Hello Ron:
You'll want to also review the event log files at the following location. You might find more events logged that could help troubleshoot this issue for you. I haven't personally seen that message logged on our upgraded sites yet.
<code>/Portals/_default/Logs/</code>
In the meantime, if you're not using the messaging feature right now, you could just disable that task.
Video: https://www.youtube.com/w...-0y8o5EBYVcCY2yzhTZk
Hello Will, thanks for the assist!
I am not sure what the Messaging service is used for (I did disable it) and the errors continue.
I see this in the current schedule:
Evotiva UserFiles Scheduler
11/15/2021 11:09:02 - Starting Operations. Clearing Temp folders. UserFiles Scheduler Failed: System.Data.SqlClient.SqlException (0x80131904): Invalid object name 'dbo.Evotiva_Folders_Log'. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry) 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 TruuTJc1mC2v_fSsAHIvWC65my8dGMjp9bRJ$MB85fxZS4sGnWmdUjTLQy9Q5wjrQQ.Zmy$l2S_qzwO6uWjKBy7nbE2nOLDSF4n1iux5Ml0HrKW() at Evotiva.DNN.Modules.UserFiles.UserFilesSchedule.DoScheduledWork() at Evotiva.DNN.Modules.UserFiles.UserFilesSchedule.DoWork() ClientConnectionId:4a94a79c-6d98-4ed1-9438-b2f5a8ee23de Error Number:208,State:1,Class:16
I did look at each task and that is the only one that references:
Messaging Dispatch
DotNetNuke.Services.Social.Messaging.Scheduler.CoreMessagingScheduler,
Just confirming that you are NOT an Evoq customer correct? We have seen this issue with Evoq only installations, to the point that they are recommending that with Evoq that you stop the scheduler before you upgrade the site.
We are using DNN
Sorry I'm just now getting back to this. I get hundreds of e-mails from the community site every week.
It sounds like you have or had Evotiva's User Files extension installed. Either it didn't fully uninstall or there's an update to be made. If you can, I'd suggest upgrading the extension as soon as you can. If the extension is no longer in use, I'd suggest contacting support at Evotiva so they can help you with getting rid of any remnants.
These Forums are for the discussion of the open source CMS DNN platform and ecosystem.
For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:
Awesome! Simply post in the forums using the link below and we'll get you started.