Ajesh
8th January 2018, 07:22
Hello All
We are facing this error while cancelling a Sales Order Line on Live Production Server.
Now i have searched Infor Incidents where they have suggested that Error 111 usually occurs in case of corruption of a table and usually reorganization of Table needs to be done.
Now i am going to follow up on that.
But my question is when 111 Error occurs, No record found means what? If record is not found the program should not go into the loop and therefore why is the need for a Fatal Error. What am i missing here?
Regards
Ajesh
bhushanchanda
8th January 2018, 09:44
Hi Ajesh,
There might be a bad character(something like a High-Ascii character) in the data which can cause the issue. I have experienced it in the past, when I was opening up a Sales Order session, when scrolled, it kicked me out.
Then I found out that, one of the sales order had a note or something with a High-Ascii character which caused the bshell error.
So, the basic select will fail with the bshell error.
Ajesh
8th January 2018, 12:10
Hi Bhushan
Appreciate your answer. But there is no description field in the Linked Order Line Data.
Regards
Ajesh
mark_h
9th January 2018, 15:28
It does not necessarily have to be a description field - it could be and character based variable. We have run into something like this a few times over the years - something about the control character or what ever is in the data that just causes the fatal error.
Ajesh
10th January 2018, 07:25
Ok..So what did you guys do about it then?
mark_h
10th January 2018, 15:06
I know in one case we re-org'ed the tables. In another case I believe we knew which record was causing the problem and just used table maintenance to clean it up(but I can't remember if we just deleted the record or re-entered the data). Been a long time since we ran into this issue - I think we finally along the way convinced users to stop cutting and pasting from word which caused several interesting text and print issues.
bhushanchanda
10th January 2018, 18:06
In our case, we had multiple records(thousands of them) which had this data issue. I extracted all the data to Excel by exchange. I created a macro to replace all the extended ascii characters by space and then re-uploaded the data using the exchange.
Here's a link. (https://stackoverflow.com/questions/37024107/excel-vba-remove-unicode-characters-in-a-string)
Ajesh
12th January 2018, 07:17
Thanks for your responses. I really appreciate. I have forwared the response to Client and told my advice and also asked them to log an incident with Infor. Shall inform what worked..