Call stack entry during 8.4 import
Björn Schwab
10-10-17
Get lots of these during import to 8.4 190407

2017-10-10 10:03:19 Trying to reference array out-of-bounds (returning blank)
2017-10-10 10:03:19 dump of call stack
2017-10-10 10:03:19 call stack entry: hal/Tools/VarietyToolsCommon.hal: SPLITVARS
2017-10-10 10:03:19 call stack entry: hal/Tools/VarietyToolsCommon.hal: FILLMASKVAR
2017-10-10 10:03:19 call stack entry: hal/Tools/VarietyToolsCommon.hal: CORRECTITEMVAR
2017-10-10 10:03:19 call stack entry: hal/Tools/VarietyToolsCommon.hal: READFIRSTITEMINCLCLOSED
2017-10-10 10:03:19 call stack entry: hal/Tools/StockTools.hal: SHOULDITEMUPDATESTOCK
2017-10-10 10:03:19 call stack entry: hal/Tools/StockToolsSerialNr.hal: PURUPDATESERIALNR

2017-10-10 10:03:19 call stack entry: hal/RActions/PUVcRecAction.hal: PUVCRECORDIMPORTAFTER
2017-10-10 10:03:19 Trying to reference array out-of-bounds (returning blank)
2017-10-10 10:03:19 dump of call stack

Reply
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
qupdating collisions
Paul Timms
I've found an issue which I'm trying to find the best way to resolve. An integrated proof of delivery system sends two pieces of data to the SERP API, in two separate calls - let's c...
17:59 20 Feb 2026
Optional Features > Idle Client Timeout
Andis Blicāns, Grasko
There are some topics in this Q&A related to this question, but none of them is about Idle users - Concurrent or Named. If timeout minutes are specified in Optional Features, then all idle users are...
15:53 18 Feb 2026