topic Re: Error in Parser-Thread - CPARSER in Application Development and Automation Discussions

Error in Parser-Thread - CPARSER

Former Member — Thu, 02 Jun 2011 10:23:13 GMT

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

Re: Error in Parser-Thread - CPARSER

stefankleger — Tue, 05 Jul 2011 08:37:40 GMT

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

Re: Error in Parser-Thread - CPARSER

Former Member — Wed, 31 Aug 2011 14:04:33 GMT

Hi,

How have you solved this issue? I am currently experiencing it...

Regards,

Sjoerd

Re: Error in Parser-Thread - CPARSER

Former Member — Wed, 28 Sep 2011 15:22:17 GMT

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.

Re: Error in Parser-Thread - CPARSER

Former Member — Mon, 17 Oct 2011 07:21:01 GMT

Solved,

That was an ABAP code reading error when SE38 starts. I found the error line and delete completely.

Re: Error in Parser-Thread - CPARSER

former_member442449 — Tue, 18 Oct 2011 09:03:28 GMT

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.

Re: Error in Parser-Thread - CPARSER

Former Member — Mon, 27 Jan 2014 10:20:24 GMT

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,

Re: Error in Parser-Thread - CPARSER

gouravkumar64 — Mon, 27 Jan 2014 10:35:33 GMT

Hi Mehgmala,

This thread is 3 years old.

No need to reply.

Thanks

Gourav.

Re: Error in Parser-Thread - CPARSER

Former Member — Mon, 27 Jan 2014 11:05:44 GMT

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

Re: Error in Parser-Thread - CPARSER

Former Member — Thu, 24 Apr 2014 00:11:19 GMT

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.

Re: Error in Parser-Thread - CPARSER

robson_soares — Tue, 02 Jun 2015 13:51:27 GMT

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.

Re: Error in Parser-Thread - CPARSER

Former Member — Tue, 02 Jun 2015 15:32:53 GMT

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.

Re: Error in Parser-Thread - CPARSER

torsten_blank2 — Wed, 15 Jul 2015 13:50:48 GMT

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...

Re: Error in Parser-Thread - CPARSER

Karel — Tue, 29 Sep 2015 12:13:53 GMT

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

Re: Error in Parser-Thread - CPARSER

wfrede — Tue, 12 Jan 2016 08:42:34 GMT

In 7.40 with patch 5, it's the same. I'm using win 7 X64 with latest patches from today.

Re: Error in Parser-Thread - CPARSER

Former Member — Tue, 12 Jan 2016 15:19:36 GMT

I'm now on 7.40 patch 7 (win7 x64 also) and just got the error. Still can't replicate.

Re: Error in Parser-Thread - CPARSER

Former Member — Wed, 02 Mar 2016 20:59:38 GMT

Hi all, I have recently found this information related with this topic.

1770321 - Illegal characters in source code lead to ABAP Editor crash

https://websmp230.sap-ag.de/sap(bD1lcyZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361…

I hope it would be useful for you.

Best Regards,

Diego L. Gómez

Re: Error in Parser-Thread - CPARSER

robson_soares — Tue, 10 May 2016 19:32:10 GMT

Thank you Diego,

However the note's report maybe works for a small code.

Unfortunate SAP's solution!

Best Regards.

Re: Error in Parser-Thread - CPARSER

former_member382556 — Wed, 15 Jun 2016 08:17:30 GMT

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?

Re: Error in Parser-Thread - CPARSER

Harters — Wed, 16 Oct 2024 10:48:33 GMT

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 🙂