That was driving me crazy! Thanks for the great, simple, mental health saving solution.
Tom

GREAT !!!! It was bothering me for months !! Thanks so much.

Déclic Vidéo FX

Hello Mitchel,

I am very happy, but it would be fantastic if the "second error" is also removed. For me, an error is still there (it was appearing at the same time that the other one - probably also linked to the scheduler ??)

AssemblyVersion: -1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider:
ExceptionGUID:
InnerException: Unhandled Error:
FileName:
FileLineNumber: -1
FileColumnNumber: -1
Method:
StackTrace:
Message: System.Exception: Unhandled Error: ---> System.Web.HttpException: Request timed out.--- End of inner exception stack trace ---
Source:

I have a feeling that the error is also linked to the scheduler, however, it is a timeout issue and those are not necessarily easy to track down.

Ok, I have submitted it to the DNN team....
http://www.dotnetnuke.com/Community/Forums/tabid/795/mid/2108/threadid/154132/scope/posts/Default.aspx

DV

Great fix Mitchell! Worked perfectly!!

Thanks Mitchel... your solution worked well for me.

Hey guys, I really don't want to sound like an idiot but I need to know. How exactly does one go about doing this fix? Like, if someone would? Step by step for people like me..

Thanks,

David

You can run the script from the Host -> SQL menu when logged in as host.

Mitchel,

This is just to let you know that this has been fixed for dnn 4.6.0. See this Gemini issue: http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=5970

Thanks for this find

Erik,

Thanks for the notification!!

Hi Mitchel,

I appreciate this fix...

Thank you!

Bill

found numerous other annoyances to get rid of this one... finally it's "fixed". Thanks for posting it!

Thanks Mitchel. Saved me a bunch of headaches.

I ran the query from Host > SQL .. now what concerns me is that I haven't had any log entries since ... it's been over an hour .. even login entries are not shown. Please advise.

THis script ONLY will affect entries for the scheduler errors, it will NOT have any affect on other logging items.

David made the following comment:
Hey guys, I really don't want to sound like an idiot but I need to know. How exactly does one go about doing this fix? Like, if someone would? Step by step for people like me..

Can I hope for more of the same. I curt and pasted the above script into host SQL and recieved "There is an error in your script"
I note the Mitchel comments that 'you will need to append any object qualifers" I have DNN_ as an object qualifier. how do I appen this?
Do I run this as script or simple execute?

Thanks,

Paul

Paul,

If you have DNN_ as your object qualifier, use the following when running the script from the SQL Page.

UPDATE DNN_DesktopModules
SET SupportedFeatures = 0
WHERE SupportedFeatures = -1

thanks Mitchel.
Sometimes the obvious takes longer to see.
The log file has reduced dramtically.
Paul

Can you help me now
Event Log : Error

DotNetNuke.Services.Exceptions.ModuleLoadException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> 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.Log.EventLog.DBLoggingProvider.Data.SqlDataProvider.PurgeLog() at DotNetNuke.Services.Log.EventLog.DBLoggingProvider.DBLoggingProvider.PurgeLogBuffer() at DotNetNuke.Services.Log.EventLog.LogController.PurgeLogBuffer() at DotNetNuke.Modules.Admin.Log.LogViewer.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace ---

Chinh - VietNam

This appears to be a timeout issue with the event log.

You could try clearing the table manually using "TRUNCATE TABLE eventLog" (Without the quotes)

Worked perfectly for me...keep coming back to this one, so I need to write it down in my notes.

Any idea whether all this has worked itself out in 4.7? ...thinking of making the switch, but usually like to wait until the x.x.2 version. :)

Terp,

This was actually fixed in I believe 4.6.0. They added code in the SqlDataProvider file to fix the current errors, and then with their overhaul to the module installation process fixed the underlying error.

I would have to dig through the data providers to find the exact version but I am quite sure it was 4.6.0

Thank you very much for the help.

We´ve been trying to resolve this issue for a long time.

This was driving me nuts. Thanks for posting the fix.

Thanks a MILLION! This was really haunting me for few weeks!

Thanks! I've been having this issue in too many versions of DNN that I can remember. This stopped the error. BTW, we had already upgraded to 4.6.2 and still had the problem. So it wasn't fixed.

After we ran the SQL, we didn't get the error, but we didn't get any results either. On several DNN installations.

Come to find out that the Search Results module had a cache setting of 1200. After each search, you had to wait 20 minutes b4 the results would change. Set it to 0 and all is well with the world!!!

Will any object qualifier with a -1 value give the same error? Because I have User ID, ModuleDefId, ModuleId,
AssemblyVersion, PortalID, all returning a -1 value in the Event Viewer error messages at different times. Runinng 4.5.5

Itmes in the event log with a -1 indicate that they were not done via a specific portal. That is not an issue.