Problems while trying to look at the code from Eclipse

[daniel_herreramarmolejo]

Hello

I'm having problems trying to look at ABAP code within Eclipse, every time I try to open a program i get this error:

The editor cannot be shown because the content cannot be synchronized with the back end: Synchronize Content Result for /ABAPsystem/.adt/programs/programs/zprogram/zprogram.approg; System failure: "Exception condition "NOT_POSSIBLE" raised." (For detailed information, check the generated short dump in transaction ST22 of system ABAP).

The system configuration:

SAP_BASIS:    731    0004

SAP Kernel :  721_EXT_REL

We just upgraded from kernel 720_EXT_REL to 721_EXT_REL to enable debug within Eclipse, however I can't see any code now. Basis has no idea what it could be, they told me they haven't changed anything in the configuration.

Any help would be appreciated.

Thanks!

Daniel H.

[dilorenzo]

Hi Daniel,

is there anything interesting in the shortdump (transaction ST22)?

Regards,

Dominik

[schneidermic0]

Hi Daniel,

Some time ago, something similar happened, when ADT was installed in HANA Studio. See note http://service.sap.com/sap/support/notes/1834948. This note does also describe a workaround. Maybe this helps.

If not, does transaction ST22 show a short dump that might be related to this operation?

Michael

[Kiran_Valluru]

Hi Daniel,

Check and follow the instructions in SAP Note 1834948

Hope this helps u,

Regards,

Kiran

[daniel_herreramarmolejo]

Nevermind, it's happening again.

Here is the text of ST22 if anyone wants to look at it:

Open a editor dump - Pastebin.com

SAP Note 1834948 wasn't helpful

Daniel

[schneidermic0]

Hi Daniel,

Would it be possible for you to raise a customer ticket and assign it to component BC-DWB-AIE-SRC. I guess we have to access your system remotely to understand the reason for this dump.

Thanks,

Michael

[Former Member]

Hi Daniel,

we get the same Error, could you solve the problem?

best regards

Daniel

[schneidermic0]

Hi Daniel,

The following note might solve this issue:

http://service.sap.com/sap/support/notes/2045882

Michael