Q&A
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
Erik Munoz
10-19-17
Hi,

Do you have halcust/halpatch?
if you have it seems that there some changes in those specific hals (VarietyToolsCommon.hal, StockTools.hal, etc) between your previous version and version 8.4 190407. I recommend to compare the functions mentioned in the log in both version, there might be a change of arguments.


Best regards

HansaWorld
Reply
Björn Schwab
10-19-17
Created byErik Munoz10:01 19 Oct 2017
Hi, Do you have halcust/halpatch? if you have it seems that there some changes in those specific hals (VarietyToolsCommon.hal, StockTools.hal, etc) between your previous version and version 8.4 190407. I recommend to compare the functions mentioned in
I did the import with only datadef.hal an no other halcust file.
Therefor the above is "incorrect".
Reply
Björn Schwab
10-19-17
Created byBjörn Schwab10:30 19 Oct 2017
I did the import with only datadef.hal an no other halcust file. Therefor the above is "incorrect".
I also found the following in our hansa.log file


2017-09-19 15:52:03 BAH/THREAD(13) dump of call stack
2017-09-19 15:52:03 BAH/THREAD(13) call stack entry: hal/Reports/ProStatTool.hal: ADDPTTOLIST
2017-09-19 15:52:03 BAH/THREAD(13) call stack entry: hal/Reports/ProStatRn.hal: PRINTPROJECTSPECSTATS
2017-09-19 15:52:03 BAH/THREAD(13) call stack entry: hal/Reports/ProStatRn.hal: PROJSTATTRANSACTION
2017-09-19 15:52:03 BAH/THREAD(13) call stack entry: hal/Reports/ProStatRn.hal: PROSTATRN
2017-09-19 15:52:03 BAH/THREAD(13) Trying to reference array out-of-bounds (returning blank)
2017-09-19 15:52:03 BAH/THREAD(13) dump of call stack
2017-09-19 15:52:03 BAH/THREAD(13) call stack entry: hal/Reports/ProStatTool.hal: ADDPTTOLIST
2017-09-19 15:52:03 BAH/THREAD(13) call stack entry: hal/Reports/ProStatTool.hal: ADDNOTDONEACTIVITIES
2017-09-19 15:52:03 BAH/THREAD(13) call stack entry: hal/Reports/ProStatRn.hal: PRINTPROJECTSPECSTATS
2017-09-19 15:52:03 BAH/THREAD(13) call stack entry: hal/Reports/ProStatRn.hal: PROJSTATTRANSACTION
2017-09-19 15:52:03 BAH/THREAD(13) call stack entry: hal/Reports/ProStatRn.hal: PROSTATRN


We do not have these files in our halcust
Reply
Leave Comment
You can subscribe to notifications for this post by selecting the 'star' icon on the top right corner of the post.
Back to the list
Latest Posts
Re: Re: COMMUNICATION PROTOCOL VIOLATION
Reino Botha
Please check your version of android if it is the same as the server you are connecting too. ...
08:24 21 Nov 2024
Re: Folder
Bror-Erik Kotiranta
In NC you hace operations>>ai chats. They are used for these Br, Bror-Erik...
05:12 21 Nov 2024