‎2011 Jun 02 11:23 AM
Hi,
One of my ABAP program gives an error and locks the window as Error in Parser-Thread within SE38. This is caused one of ABAP program the other programs not effect as this. What is the problem ?
Regards,
techmaster
‎2011 Jul 05 9:37 AM
Hi,
I have the same problem with a program in SE38. The editor displays the characters ##b in one line. When I want remove this line, the message "Error in Parser-Thread" will be displayed. After that, the SAP GUI isn't responding to any operation...
Regards,
Stefan
‎2011 Aug 31 3:04 PM
Hi,
How have you solved this issue? I am currently experiencing it...
Regards,
Sjoerd
‎2011 Sep 28 4:22 PM
See OSS Note 1619169 'Crash of ABAP Edit Control with Multiple Windows Open'. There's a patch available for SAP GUI at the bottom of this OSS note.
‎2011 Oct 17 8:21 AM
Solved,
That was an ABAP code reading error when SE38 starts. I found the error line and delete completely.
‎2011 Oct 18 10:03 AM
Unfortunately I have still this error since 7.20 installation and it makes me crazy.
The issue matches with note #1619169. I switch between several ABAP editor sessions, I do a lot copy/paste, pretty printer, activate... all this development stuff and suddenly it crashes (several times a day).
And the best thing is, note 1619169 (which is a high priority correction) refers to a solution, to Support Package 9, but it was never available, since August.
I have to use the old ABAP editor and this drives me crazy.
It's a shame.
‎2014 Jan 27 10:20 AM
Hi All,
Code must be having a syntax error. Please correct the syntax error and activate.If you are unable to change the code (system hangs when you open SE38 in change mode), try to open the code in old editer and then make the changes.
Thanks,
VM
‎2014 Jan 27 10:35 AM
Hi Mehgmala,
This thread is 3 years old.
No need to reply.
Thanks
Gourav.
‎2014 Jan 27 11:05 AM
Hi Gaurav,
I faced the same issue today and reached this post while searching for an answer. I could not find a resolution here. Thread was assumed answered with no real resolution. Hence I thought of sharing the resoultion after solving the issue myself,
I know thread is old, but wanted to help those who come here searching for an answer
‎2015 Jun 02 2:51 PM
I'm looking for a solution too, and I agree with Mehgmala and Sue... this is not a resolved issue, so I think you should not care for answers to old questions, because there may be people who are still searching for the solution.
I'm currently using SAPGUI 740 final release and still crashes with error parse.
Best Regards.
‎2014 Apr 24 1:11 AM
I too know thread is old but this is still happening. I experience this error frequently, but intermittently, for more than a year. Does not seem tied to any one program for me, but to some sequence of activities using SE38 (not sure yet of exact pattern).
I'm currently using SAPGUI 730 patch level 8, Windows 7 32-bit. Happened several times today.
‎2015 Jun 02 4:32 PM
Using SAPGUI 740 now and crash after error in Parser still happens. Still not sure what error could be in the code being typed in, maybe I'm hitting a key accidentally that gives non-printable character? I can never replicate so I'm not sure of the trigger.
‎2015 Jul 15 2:50 PM
Yes, we also have this Problem with SAPGUI 7.30 P13 and P14 and versions before... any idea? Seems that Patch 14 makes it worse... System is Windows 7 Pro 32-bit...
‎2015 Sep 29 1:13 PM
Here also SAPGUI 7.40 SP-level 1 (7400.1.1.1098) with this issue.
I can't find SAP Notes about this issue for versions newer than SAPGUI 7.20
Found this issue on:
Windows 7 SP1
Windows Server 2008 R2 Enterprise SP1 with Citrix
‎2016 Jan 12 8:42 AM
In 7.40 with patch 5, it's the same. I'm using win 7 X64 with latest patches from today.
‎2016 Jan 12 3:19 PM
I'm now on 7.40 patch 7 (win7 x64 also) and just got the error. Still can't replicate.
‎2016 Mar 02 8:59 PM
Hi all, I have recently found this information related with this topic.
1770321 - Illegal characters in source code lead to ABAP Editor crash
I hope it would be useful for you.
Best Regards,
Diego L. Gómez
‎2016 May 10 8:32 PM
Thank you Diego,
However the note's report maybe works for a small code.
Unfortunate SAP's solution!
Best Regards.
‎2016 Jun 15 9:17 AM
Hi all,
I have the same Problem with SAP GUI 7.40 (7400.3.8.1123 - Win 7 X64).
The Problem could not be solved by OSS Note 1770321 because I also debug SAP Standard Coding and in this case SAP GUI was terminated. I could not change SAP Standard coding to solve the problem!!!
Is there any solution, OSS-Note, anything else to solve this Problem?
‎2024 Oct 16 11:48 AM
Well for interest, as you will notice, it is now 2024...13 years after this post started and today I am still got this error and searching brought me here 🙂
‎2025 Jul 15 9:04 PM