Journal Task faults and restarts periodically

book

Article ID: 100024827

calendar_today

Updated On:

Description

Error Message

Event Type:     Error
Event Source:  .NET Runtime 2.0 Error Reporting
Event Category:          None
Event ID:        1000
Date:               5/19/2011
Time:               9:34:24 PM
User:                N/A
Computer:       EVSERVER
Description: Faulting application journaltask.exe, version 9.0.1.1073, stamp 4cec5b4e, faulting module ole32.dll, version 5.2.3790.4750, stamp 4c4d5cee, debug? 0, fault address 0x00079fdd.

 
 

Event Type:     Information
Event Source: Enterprise Vault
Event Category:          Journal Task
Event ID:        45330
Date:               5/19/2011
Time:               9:34:24 PM
User:                N/A
Computer:       EVSERVER
Description:External Filter 'Some.Accelerator.PlugIn.Name.Filter' stopped.

V-437-45330

Cause

It is normal behavior for the Journal Task to restart itself after every 50,000 MAPI operations, and this auto-recycle does not produce an Event. When Custom Filtering is implemented, sometimes the recycling will occur while the custom filter is processing a message. Because the Journal Task is told to cease all operation while the custom filter is still processing the item, it can cause the Journal Task to exit ungracefully, and the system logs the ASP.NET fault.

Shortly thereafter, the Task Controller service will automatically restart the Journal Task, and it will continue processing items.
 

Resolution

None. This error is an artifact of the timing of the auto-recycling of the Journal Task, and it can be safely ignored.

 

 

Issue/Introduction

An error with Event 1000 citing the faulting application "journaltask.exe" is periodically logged in the Application Event Log. It is preceded by informational Event 45330, which is logged in the Veritas Enterprise Vault Event Log. There will be instances of Event 45330 preceding each Event 1000, but there will not necessarily be an Event 1000 following each Event 45330.