Our CEO was in Evo in IN-A looking at a new part.  He used the BOM icon to view the BOM, selected a part on the BOM and was going to look at the receipts, something he always does.
 
This time, when the BOM part showed up in IN-A, there were some errors and then the screen just sat and flickered very quickly before eventually terminating itself.  We tried a second time to see if the process could be replicated and it was.
 
So just to check I had him go back into Evo and just lookup the part from the BOM and that was fine, no issues viewing it or checking receipts.
 
Errors that came up:
 
Warn err -File: WBKLOOKUP.SRC Line: 6065
There is no active record in the file so you cannot delete it.
OK
 
Then
 
Fatal Err1 - File:  WBLOOKUP.SRC Line: 6146
The field you are trying to use is unallocated.  It may belong to a file that hasn't been opened yet, or was an array that was removed frommemory - BKAR.INVT.CODE
OK
 
Then
Error
Terminate Applicaton?
OK   Cancel
 
When he clicked on this last OK that is when Evo when whonky and sat there flickering until it crashed (about a minute).
 
Version of IN-A he was using is 10/08/18.
 
Just for kicks, I tried doing these exact same actions on other parts (same version of IN-A) I knew would have a BOM and I could not replicate the issue, so I am guessing it is an issue with the parent part record or the child part, perhaps? Anyone know if this is the case/seen this before/know how to fix?  Please advise.  Thank you.
 
Kind regards,
 
Val
 

If you were in the Receipts grid when it crashed, the the file you want to look at would be the BKAPHPOL. If you were in the BOM grid when it crashed then the file you need to look at would be the BKBMMSTR file. I would first look over the BOM make sure that part actually exist on the BOM then look over the transactions on that part in IN-E. Then look into those file using maintain database.
 

Val,
 
   Sounds like a BZ (binary zero ) in the bkbmmstr file. I would try running T7BZFIX on that file.  When TAS7 hits a field with a BZ in it it pops the stack and jumps to random lines of code, leading to too many Pops or Stack overflow errors.
 
The latest version for T7BZFIX I overhauled this summer, has 09/26/18 as the banner date.
 
Give that a try and let me know if that solves it.