| Author |
Messages |
|
cyborama
DNN Creative Magazine Subscriber
Nuke Master
Posts:122
 |
| 18 Feb 2008 9:56 AM |
|
Hello guys,
I am constantly getting the following erros in my dotnetnuke event viewer
| 2/18/2008 7:24:54 AM
Scheduler Event Failure
THREAD ID: 11; TYPE: DotNetNuke.Services.Search.SearchEn ...
|
THREAD ID: 11
TYPE: DotNetNuke.Services.Search.SearchEngineScheduler
EXCEPTION: Thread was being aborted.
RESCHEDULED FOR: 1/1/0001 1:00:00 AM
SOURCE: STARTED_FROM_BEGIN_REQUEST
ACTIVE THREADS: -5
FREE THREADS: 6
READER TIMEOUTS: 0
WRITER TIMEOUTS: 0
IN PROGRESS: 0
IN QUEUE: 10
Server Name: WEB131 | |
| 2/18/2008 7:24:46 AM
Scheduler Event Failure
THREAD ID: 8; TYPE: DotNetNuke.Services.Scheduling.Purge ...
|
THREAD ID: 8
TYPE: DotNetNuke.Services.Scheduling.PurgeScheduleHistory
EXCEPTION:
The query has been canceled because the estimated cost of this query
(9269) exceeds the configured threshold of 1500. Contact the system
administrator.
RESCHEDULED FOR: 2/20/2008 7:24:46 AM
SOURCE: STARTED_FROM_BEGIN_REQUEST
ACTIVE THREADS: 0
FREE THREADS: 1
READER TIMEOUTS: 0
WRITER TIMEOUTS: 0
IN PROGRESS: 1
IN QUEUE: 10
Server Name: WEB131 | |
| 2/18/2008 7:35:17
AM
Scheduler Event
Failure THREAD ID:
17; TYPE: DotNetNuke.Services.Log.SiteLog.Pur ...
|
THREAD ID:
17
TYPE:
DotNetNuke.Services.Log.SiteLog.PurgeSiteLog
EXCEPTION: Thread was
being aborted.
RESCHEDULED FOR: 1/1/0001 2:00:00 AM
SOURCE:
STARTED_FROM_BEGIN_REQUEST
ACTIVE THREADS: -5
FREE THREADS:
6
READER TIMEOUTS: 0
WRITER TIMEOUTS: 2
IN
PROGRESS: 0
IN QUEUE: 10
Server Name: WEB131
| |
| 2/18/2008 7:24:53
AM
Scheduler Event
Failure THREAD ID:
11; TYPE: DotNetNuke.Services.Search.SearchEn ...
|
THREAD ID:
11
TYPE:
DotNetNuke.Services.Search.SearchEngineScheduler
EXCEPTION: Thread was
being aborted.
RESCHEDULED FOR: 1/1/0001 1:00:00 AM
SOURCE:
STARTED_FROM_BEGIN_REQUEST
ACTIVE THREADS: -4
FREE THREADS:
5
READER TIMEOUTS: 0
WRITER TIMEOUTS: 0
IN
PROGRESS: 0
IN QUEUE: 10
Server Name: WEB131
| |
Most frequently the failed schedules seem to be:
Search Engine Schedular
Purge Schedule History
Once in a while PurgeSiteLog errors out and it has done so more than once but I don't get as many schedule errors on this as I do on the two above. So my question is first what could be causing these scheduled tasks not to be able to fulfill what they were set out to do correctly.
Secondly could the constant flood of these dumped scheduled failers cause for a memory consumption of a dotnetnuke installation to go out of control.
While I'm on the event log erros I will give you a couple other errors I am constantly getting via my dotnetnuke portal and see if you could give me some direction in these as well.
| 2/18/2008 6:16:00
AM
Host Alert EventQueue.ProcessMessage:
Message Processing Failed; Proces ... |
EventQueue.ProcessMessage:
Message Processing Failed
ProcessorType:
DotNetNuke.Entities.Modules.EventMessageProcessor, DotNetNuke
Body:
Sender:
BusinessControllerClass:
DotNetNuke.Modules.Media.MediaController,
DotNetNuke.Modules.Media
DesktopModuleId:
79
UpgradeVersionsList: 03.02.00,03.02.03
ExceptionMessage:
Object reference not set to an instance of an object.
Server Name:
WEB131
| |
| 2/18/2008 6:16:00
AM
Host Alert EventQueue.ProcessMessage:
Message Processing Failed; Proces ... |
EventQueue.ProcessMessage:
Message Processing Failed
ProcessorType:
DotNetNuke.Entities.Modules.EventMessageProcessor, DotNetNuke
Body:
Sender:
BusinessControllerClass:
DotNetNuke.Modules.Events.EventController,
DotNetNuke.Modules.Events
DesktopModuleId:
68
UpgradeVersionsList: 03.03.07
ExceptionMessage: Method
not found: 'DotNetNuke.Entities.Modules.ModuleControlInfo
DotNetNuke.Entities.Modules.ModuleControlController.GetModuleControlByKeyAndSrc(Int32,
System.String, System.String)'.
Server Name: WEB131
| |
| 2/18/2008 6:16:00
AM
Host Alert EventQueue.ProcessMessage:
Message Processing Failed; Proces ... |
EventQueue.ProcessMessage:
Message Processing Failed
ProcessorType:
DotNetNuke.Entities.Modules.EventMessageProcessor, DotNetNuke
Body:
Sender:
BusinessControllerClass:
DotNetNuke.Modules.Events.EventController,
DotNetNuke.Modules.Events
DesktopModuleId:
68
UpgradeVersionsList:
03.01.00,03.02.00,03.03.00,03.03.02,03.03.03,03.03.05,03.03.07
ExceptionMessage:
Method not found: 'DotNetNuke.Entities.Modules.ModuleControlInfo
DotNetNuke.Entities.Modules.ModuleControlController.GetModuleControlByKeyAndSrc(Int32,
System.String, System.String)'.
Server Name: WEB131
| |
Other alerts I have been receiving as of late are these general exceptions like the following:
| 2/18/2008 7:33:38 AM
General Exception
AssemblyVersion:
04.08.00; PortalID: -1; PortalN ... |
AssemblyVersion:
04.08.00
PortalID: -1
PortalName:
UserID:
-1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL: /Default.aspx
AbsoluteURL:
/Default.aspx
AbsoluteURLReferrer:
UserAgent: Mozilla/4.0
(compatible; MSIE 7.0; Windows NT 6.0; SLCC1; .NET CLR 2.0.50727; .NET CLR
3.0.04506)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider,
DotNetNuke.SqlDataProvider
ExceptionGUID:
c049ca9f-2485-4202-bb61-708893a9ef4d
InnerException: Thread was being
aborted.
FileName:
FileLineNumber:
0
FileColumnNumber: 0
Method:
System.Collections.Generic.Dictionary`2.Insert
StackTrace:
Message: System.Threading.ThreadAbortException: Thread was being
aborted. at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue
value, Boolean add) at
DotNetNuke.Entities.Tabs.TabController.FillTabInfo(IDataReader dr, Boolean
CheckForOpenDataReader, Boolean CheckForLegacyFields) at
DotNetNuke.Entities.Tabs.TabController.FillTabInfoCollection(IDataReader dr,
Boolean CheckForLegacyFields)
Source:
Server Name:
WEB131
| |
| 2/18/2008 7:35:36
AM
Scheduler
Exception AssemblyVersion:
-1; PortalID: -1; PortalName< span> ...
|
AssemblyVersion:
-1
PortalID: -1
PortalName:
UserID:
-1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider:
ExceptionGUID:
InnerException: Thread was being aborted.
FileName:
FileLineNumber: -1
FileColumnNumber: -1
Method:
StackTrace:
Message:
System.Threading.ThreadAbortException: Thread was being aborted. at
DotNetNuke.Services.Search.SearchEngineScheduler.DoWork() at
DotNetNuke.Services.Scheduling.DNNScheduling.ProcessGroup.Run(ScheduleHistoryItem
objScheduleHistoryItem)
Source:
Server Name:
WEB131
| |
| 2/18/2008 7:35:36
AM
General
Exception AssemblyVersion:
-1; PortalID: -1; PortalName< span> ...
|
AssemblyVersion:
-1
PortalID: -1
PortalName:
UserID:
-1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider:
ExceptionGUID:
InnerException: Thread was being aborted.
FileName:
FileLineNumber: -1
FileColumnNumber: -1
Method:
StackTrace:
Message:
System.Threading.ThreadAbortException: Thread was being aborted. at
SNINativeMethodWrapper.SNIPacketGetConnection(IntPtr packet) at
System.Data.SqlClient.TdsParserStateObject.ProcessSniPacket(IntPtr packet,
UInt32 error) at
System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult,
TdsParserStateObject stateObj) at
System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected) at
System.Data.SqlClient.TdsParserStateObject.ReadBuffer() at
System.Data.SqlClient.TdsParserStateObject.ReadByte() 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, CommandType commandType, String commandText) at
Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String
connectionString, String spName, Object[] parameterValues) at
DotNetNuke.Services.Log.EventLog.DBLoggingProvider.Data.SqlDataProvider.GetEventLogPendingNotifConfig()
at
DotNetNuke.Services.Log.EventLog.DBLoggingProvider.DBLoggingProvider.SendLogNotifications()
at
DotNetNuke.Services.Log.EventLog.SendLogNotifications.DoWork()
Source:
Server Name: WEB131
| |
These are just some of the different kinds of errors I am still receiving and am wondering if you have any idea of the kinds of things that could be causing all these errors to be thrown.
Would you suggest that I start by turning off the automatically scheduled events of those things that are continually failing or is their some way of easily getting to the bottom of continually failing scheduled tasks.
Lastly would turning off tasks that keep failing save on memory and perhaps allow the web app not to consume so much memory thanks
Bo
|
|
|
|
|
mgordon
DNN Creative Magazine Subscriber
Nuke Master
Posts:173
|
| 27 Feb 2008 10:02 AM |
|
Was there an answer on this?
My DNN just went belly up because of the Scheduler. I'm getting the exact same kinds of errors as Bo is getting. I had to turn Scheduler off in order for my site to respond as it should.
Help would be MOST appreciated.
Thanks,
Mark |
|
Mark Gordon
Webmonkey |
|
|
mgordon
DNN Creative Magazine Subscriber
Nuke Master
Posts:173
|
| 27 Feb 2008 1:24 PM |
|
Actually, this is the error I keep getting over and over, like every 10th of a second:
2/27/2008 11:42:52 AM 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: Add failed. Duplicate key value supplied.
FileName:
FileLineNumber: -1
FileColumnNumber: -1
Method:
StackTrace:
Message: System.ArgumentException: Add failed. Duplicate key value supplied.at Microsoft.VisualBasic.Collection.Add(Object Item, String Key, Object Before, Object After)at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.AddToScheduleInProgress(ScheduleHistoryItem objScheduleHistoryItem)at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.WorkStarted(SchedulerClient& objSchedulerClient)
Source:
Server Name: PWCPAWEB
When I put my scheduler on Request Method or Timer, the site slows to a stop and takes, literally, forever to get a page up and running.
Thanks,
Mark |
|
Mark Gordon
Webmonkey |
|
|
Joseph Craig
DNN Creative Staff
Nuke Master VI
Posts:6139
|
| 28 Feb 2008 8:30 AM |
|
Did this just start happening, or has this always happened?
Check your database, truncate the event file, etc. |
|
Joe Craig
DNN Creative Support
Subscribe to the website |
|
|
Lee Sykes
DNN Creative Staff
Nuke Master VI
Posts:6011
|
|
mgordon
DNN Creative Magazine Subscriber
Nuke Master
Posts:173
|
| 06 Mar 2008 11:20 AM |
|
Hi All,
I figured out what the problem was (well thanks to outside help! I ain't that smart!)
The culprit is the timing of the Search Engine Indexer in the scheduler. The thing is, you have to
change the values. When DNN was initially setup, it came with a preset of Indexing every 30 minutes.
The problem is that when you have more and more content, it takes longer to perform the indexing,
so it gets to the 30 minute timeframe and then starts to reindex, even though the other index never
finished, so it throws error after error.
I had to stop the indexing, change the values, restart the Application and then startup the scheduler.
I changed the index to a 6 hour timeframe. My content won't show up so quickly on internal searches,
but at least it won't go into spasms anymore. This answer was actually provided by Mitch Sellers who
I contacted. I'm in the process of signing a contract to have him on retainer to help in the future. Well
worth the oney in my opinion to have someone who really knows what's going on.
Cheers all!
p.s. Joe, do you have anything for me yet? :-) |
|
Mark Gordon
Webmonkey |
|
|
|