Showing results for 
Search instead for 
Did you mean: 

Journaltask frequently stops

Level 4
 Hi folks,

one of our customers has the problem that the journaltask stops 5-6 times a week.
The eventlog shows the following error (sorry, it's in german):

Ereignistyp: Fehler
Ereignisquelle: Application Error
Ereigniskategorie: (100)
Ereigniskennung: 1000
Datum: 05.05.2009
Zeit: 10:13:21
Benutzer: Nicht zutreffend
Computer: BADVAULT1
Fehlgeschlagene Anwendung JournalTask.EXE, Version, fehlgeschlagenes Modul ntdll.dll, Version 5.2.3790.3959, Fehleradresse 0x0004afb2.

Weitere Informationen über die Hilfe- und Supportdienste erhalten Sie unter
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 4a 6f 75 ure Jou
0018: 72 6e 61 6c 54 61 73 6b rnalTask
0020: 2e 45 58 45 20 38 2e 30 .EXE 8.0
0028: 2e 30 2e 31 34 30 35 20 .0.1405
0030: 69 6e 20 6e 74 64 6c 6c in ntdll
0038: 2e 64 6c 6c 20 35 2e 32 .dll 5.2
0040: 2e 33 37 39 30 2e 33 39 .3790.39
0048: 35 39 20 61 74 20 6f 66 59 at of
0050: 66 73 65 74 20 30 30 30 fset 000
0058: 34 61 66 62 32 4afb2

this causes another problem, becaus there are thousands of pending items in the journal-mailbox.
Is there an easy way to cancel this pending-state (not manually by connecting the journalmailbox)?

Thanks in advance


Level 6
There is a way to cancel the pending items.

Go into the Journal Policy, Advanced Tab.

"Pending Shortcut Timeout" (Change the current entry to 0)

Run the Journal Task in report mode.  This should clear all the pending items, however this does not fix the issue of the Journal Task stopping during the week.


Level 6
Partner Accredited Certified
You should upgrade to EV8 SP1. It contains many fixes, and your problem might be solved there.


cloudficient - EV Migration, creators of EVComplete.

Level 6
Employee Accredited Certified
It looks like it may be some sort of resource issue if this only happens 5-6 times per week.

Is there any pattern to the error? i.e Does it occur around the same time each day etc
How much RAM do you have installed?
Where is your pagefile situated?
Is this a Virtual Machine?
How much C drive free space do you have?
Have you tried deleting and recreating the journal Task?
Have you run deployment scanner and ensured that all best practise settings are implemented?
If all best practise is in place and you still have the issue then take a dump of the proces when you receive the error and either open a support case with us or MS for analysis of the dump file.

Also obviously Michael's suggestion to upgrade to the latest and greatest is solid advice.

Level 2
Hello all, I have exactly the same issue at one of my clients with an EV 8.0 SP2 setup. But the service stops more frequently now...

It worked for a couple of weeks no issues but since a week now, it started to crash on a daily bases and since a couple of days, it crashes a couple of times in an hour so we had to disable journaling all together for now...

Any help is appreciated!