Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Scheduler exception and event failure errors - Do these matterScheduler exception and event failure errors - Do these matter
Previous
 
Next
New Post
1/7/2007 9:25 PM
 
ROB AX

Joined: 9/3/2004
Posts: 2185

I'm now checking the log quite often in order to determine what actions cause exceptions and failures and here's one I've just dicovered:

Simply visiting the Admin, Authentication page causes this pair of exceptions every time:

InnerException: The specified domain either does not exist or could not be contacted.
Message: System.Runtime.InteropServices.COMException (0x8007054B): The specified domain either does not exist or could not be contacted. at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail) at System.DirectoryServices.DirectoryEntry.Bind() at System.DirectoryServices.DirectoryEntry.get_AdsObject() at System.DirectoryServices.PropertyValueCollection.PopulateList() at System.DirectoryServices.PropertyValueCollection..ctor(DirectoryEntry entry, String propertyName) at System.DirectoryServices.PropertyCollection.get_Item(String propertyName) at DotNetNuke.Security.Authentication.ADSI.Utilities.GetRootForestPath(Path ADSIPath)

InnerException: The specified domain either does not exist or could not be contacted.
Message: System.Runtime.InteropServices.COMException (0x8007054B): The specified domain either does not exist or could not be contacted. at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail) at System.DirectoryServices.DirectoryEntry.Exists(String path) at DotNetNuke.Security.Authentication.ADSI.Configuration..ctor()

It's unrelated to the ones in the thread so far and is probably irrelevant, but I've posted it here just for interest to the thread and so that others can see if theirs does it as well. I've never been in that page previously in this instance and have not configured anything in it.

Rob
 
New Post
1/8/2007 8:21 AM
 
ROB AX

Joined: 9/3/2004
Posts: 2185

So after 24 hours, my logs are not exception-free, but they are looking better since truncating that table.

One of the portals had this: Unhandled Error Adding Module to L
Followed by this: Unhandled Error Adding Module to L
The two modules in that pane are Core Links and Orizonti Nukefeeds, both of which are normally pretty reliable and I've not seen them fail myself.

Then, there is the typical set of four scheduler exceptions, mostly stating something about the search engine scheduler and labeled "Thread was being aborted" followed by one search engine scheduler event  failure . This is the pattern that seems to happen quite often, though it only happened once in 24 hours now.

Then there is a set of 4 page load errors for another portal on the instance, all saying "The state information is invalid for this page and might be corrupted". Not sure what did that and the site seems fine.

Apart from that it's looking pretty good I think. I'll clear it out and let it go another 24 hours.

Rob

 
 
New Post
1/8/2007 8:54 AM
 

Joined: 1/1/0001
Posts: 0

Rob,

You can clear the search tables by running this:

delete SearchItemWordPosition where SearchItemWordId in (select SearchItemWordId from SearchItemWord where SearchItemID in (select SearchItemId from SearchItem)) 
delete SearchWord where SearchWordsId in (select SearchWordsId from SearchItemWord where SearchItemID in (select SearchItemId from SearchItem)) 
delete SearchItemWord where SearchItemId in (select SearchItemId from SearchItem) delete SearchItem 

after you have done that you can force to fill the tables from Host -> Search Admin

The state information error probably comes from a bot that searches your site. I have them also. Check what User Agent string is in that error message. It could also be Opera doing that.
 
New Post
1/9/2007 12:12 AM
 
ROB AX

Joined: 9/3/2004
Posts: 2185

Ok, I'm carrying this out now.

I've backed everything up.. then I looked closely at the statement and copied and pasted it to notepad, and then after another close look, pasted it into the Host, SQL form. Then I ticked "run as script" and zappo! It returned the success message.

Now I've also restarted the application and so go and re-index the content... hang on, quick look in the log viewer first.... everything looks clean in there so I'll re-index.

This is exactly the sort of information I needed to know as it restores a measure of confidence in my DNN instance. The logs already looked much better since the first truncate and this will no doubt help further. The best bit is that I can now make better judgement of exceptions and errors - something that I could not do so long as I did not know what was legit and what was just garbage or buggy. Thanks for providing the information!

I will report again after 24 hours and see how this goes.

Thanks heaps!
Rob
 
New Post
1/10/2007 1:02 AM
 
ROB AX

Joined: 9/3/2004
Posts: 2185

Well happy day! My logs are now nearly clear of errors!

Since yesterday there is only one set of errors that looks like an issue. The good news is that this is the only set, where I used to have dozens of these daily. It's the sequence with 4 sheduler exceptions follows by a scheduler failure. This is the failure message:

THREAD ID: 1
TYPE: DotNetNuke.Entities.Users.PurgeUsersOnline
EXCEPTION: Thread was being aborted.
RESCHEDULED FOR: 1/1/0001 12:05:00 AM
SOURCE: STARTED_FROM_BEGIN_REQUEST
ACTIVE THREADS: -1
FREE THREADS: 2
READER TIMEOUTS: 0
WRITER TIMEOUTS: 0
IN PROGRESS: 0
IN QUEUE: 5

And these are the 4 exceptions that lead up to it:

InnerException: Thread was being aborted.
Message: System.Threading.ThreadAbortException: Thread was being aborted. at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.WorkStarted(SchedulerClient& objSchedulerClient) at DotNetNuke.Services.Scheduling.SchedulerClient.Started() at DotNetNuke.Services.Scheduling.DNNScheduling.ProcessGroup.Run(ScheduleHistoryItem objScheduleHistoryItem)

InnerException: Thread was being aborted.
Message: System.Threading.ThreadAbortException: Thread was being aborted. at DotNetNuke.Services.Scheduling.DNNScheduling.ProcessGroup.AddQueueUserWorkItem(ScheduleItem s) at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.FireEvents(Boolean Asynchronous) at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.Start()

InnerException: Thread was being aborted.
Message: System.Threading.ThreadAbortException: Thread was being aborted. at System.Threading.Thread.SleepInternal(Int32 millisecondsTimeout) at DotNetNuke.Services.Scheduling.DNNScheduling.ProcessGroup.AddQueueUserWorkItem(ScheduleItem s)

InnerException: Thread was being aborted.
Message: System.Threading.ThreadAbortException: Thread was being aborted. at System.Threading.ReaderWriterLock.AcquireWriterLockInternal(Int32 millisecondsTimeout) at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.RemoveFromScheduleQueue(ScheduleItem objScheduleItem) at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.WorkStarted(SchedulerClient& objSchedulerClient)

So, the question is... does this matter and if so, what can be done about it?

I should add that I have changed nothing from the default scheduler settings. I have been leaving many parts of DNN untouched unless I have solid knowledge and good reason to make a change. I don't go tweaking around just for kicks at this stage in the game for me.

Thanks for your assistance Mariette and thanks also for any further advice on this matter.

Regards,
Rob
 
 Page 3 of 4
Previous1234Next 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Scheduler exception and event failure errors - Do these matterScheduler exception and event failure errors - Do these matter


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out