Re: Journal error messages 8.2 v16-12-08
Lee D Papworth
2-4-17
Hi,

New migration from 6.2 to version 8.2 16-12-18

Customer uses Journaling.

When restarting the service it hung for quite a bit of time but did eventually start. Errors were written to the hansa.log file and the log grew about 40mb

017-02-04 21:11:12 --------------------------------------------------
2017-02-04 21:11:12 failed to read ORVc record from journal
2017-02-04 21:11:12 dumping stack due to failed to read record from journal
2017-02-04 21:11:12 --------------------------------------------------
2017-02-04 21:11:12 0 0x00000001403C46F8 - 0x0000000000000000
2017-02-04 21:11:12 1 0x00000001401C7FA1 - 0x0000000000000000
2017-02-04 21:11:12 2 0x00000001401CA644 - 0x0000000000000000
2017-02-04 21:11:12 3 0x00000001401CA6BA - 0x0000000000000000
2017-02-04 21:11:12 4 0x00000001401C54DB - 0x0000000000000000
2017-02-04 21:11:12 5 0x00000001401C5FDC - 0x0000000000000000
2017-02-04 21:11:12 6 0x00000001401C6CB0 - 0x0000000000000000
2017-02-04 21:11:12 7 0x0000000140084714 - 0x0000000000000000
2017-02-04 21:11:12 8 0x000000014009B22B - 0x0000000000000000
2017-02-04 21:11:12 9 0x00000001400DDDDC - 0x0000000000000000
2017-02-04 21:11:12 10 0x00000001403C78D5 - 0x0000000000000000
2017-02-04 21:11:12 11 0x00000001403C86F3 - 0x0000000000000000
2017-02-04 21:11:12 12 0x00007FFFD20E5ADA SubscribeServiceChangeNotifications - 0x00007FFFD20E5810
2017-02-04 21:11:12 13 0x00007FFFD04A13D2 BaseThreadInitThunk - 0x00007FFFD04A13B0
2017-02-04 21:11:12 14 0x00007FFFD2C754E4 RtlUserThreadStart - 0x00007FFFD2C754B0
2017-02-04 21:11:12 --------------------------------------------------

2017-02-04 21:11:12 failed to read ORVc record from journal
2017-02-04 21:11:12 dumping stack due to failed to read record from journal

2017-02-04 21:11:12 --------------------------------------------------
2017-02-04 21:11:12 0 0x00000001403C46F8 - 0x0000000000000000
2017-02-04 21:11:12 1 0x00000001401C7FA1 - 0x0000000000000000
2017-02-04 21:11:12 2 0x00000001401CA627 - 0x0000000000000000
2017-02-04 21:11:12 3 0x00000001401CA6BA - 0x0000000000000000
2017-02-04 21:11:12 4 0x00000001401C54DB - 0x0000000000000000
2017-02-04 21:11:12 5 0x00000001401C5FDC - 0x0000000000000000
2017-02-04 21:11:12 6 0x00000001401C6CB0 - 0x0000000000000000
2017-02-04 21:11:12 7 0x0000000140084714 - 0x0000000000000000
2017-02-04 21:11:12 8 0x000000014009B22B - 0x0000000000000000
2017-02-04 21:11:12 9 0x00000001400DDDDC - 0x0000000000000000
2017-02-04 21:11:12 10 0x00000001403C78D5 - 0x0000000000000000
2017-02-04 21:11:12 11 0x00000001403C86F3 - 0x0000000000000000
2017-02-04 21:11:12 12 0x00007FFFD20E5ADA SubscribeServiceChangeNotifications - 0x00007FFFD20E5810
2017-02-04 21:11:12 13 0x00007FFFD04A13D2 BaseThreadInitThunk - 0x00007FFFD04A13B0
2017-02-04 21:11:12 14 0x00007FFFD2C754E4 RtlUserThreadStart - 0x00007FFFD2C754B0

2017-02-04 21:11:12 --------------------------------------------------

This is just a couple of the messages.

We have database accelerator with this customer and import a lot of orders in batches.

Is anyone able to throw some light on these messages please?

Thanks

// Lee Papworth [ 2017-02-04 - 22:19 GMT ]
-----------------------------------------------------------
Leave Comment
You can subscribe to notifications for this post by selecting the 'star' icon on the top right corner of the post.
Latest Posts
Bror-Erik Kotiranta
Clients have their own cache, and then the server has the shared cache, if you want it kind of black and white. Presense should be there as far as i know...
10:55 7 July 2025
Yavuz Yigiterhan
Hello Paul, That is something only HansaWorld can do. But that would help to understand is that causing the problem and - if so - we fix the issue. Additional information is appreciated. Yavuz...
10:45 7 July 2025