‎2015 Feb 17 10:10 AM
Hey guys,
I currently try to execute a guide. My problem is that I always get a dump "dynpro_send_in_background" if i try to access the gateway system via my eclipse.
It happens if I wanna share my project in eclipse.
I've got SAP_ALL acces and usertype: dialog... so this should work well.
I'm using eclipse luna
It's none of my systems, so I'm not allowed to change the output.
Do you know a solution for this problem?
‎2015 Feb 17 1:48 PM
I got a dump exactly at this place yesterday, while configuring EQ Manager.
What's happening is that:
1) An error condition is reached
2) The backend system wants to tell you about that error condition.
3) If this was happening in SAPGui, you'd be able to figure out the issue. But you're not. You're in Eclipse. So step 2) gets a dump.
I resolved the issue by setting a breakpoint at the position in code where the dump happened. I looked at the program stack, and identified what was going on at step 1). That gave me enough information to search service.sap.com for further clues.
In summary: the dump isn't your problem. That's caused by the systems attempt to tell you about the error that's the real cause. However, the fact that the error is reported back to you (instead you get a dump) is also a bug. Which may have a resolution in service.sap.com
‎2015 Feb 17 10:15 AM
‎2015 Feb 17 10:19 AM
‎2015 Feb 17 11:30 AM
Hi,
Which program are you trying to execute?...
Check SM21 logs along with ST22 .
Thanks
KH
‎2015 Feb 17 11:53 AM
Hello, Nils!
How do you share your project? What is your target object? Could you give us more info about this? It looks like you're trying to change SAP's object.
‎2015 Feb 17 12:12 PM
I try to create a new BSP application in eclipse.
Therefore I created a package and a transport request in the gateway system.
Afterwards I try to create the new BSP:
After this I select my transport request and press Finish.
And that´s the point when the dump occurs.
‎2015 Feb 17 12:21 PM
Your BSP application's name should begin with "Z" or "Y", not "X". Try to create BSP named X* manually, you'll get a popup screen. This popup is the reason of the dump.
‎2015 Feb 17 12:30 PM
"Customer object WAPA Y_TEST cannot be assigned to package X_PACKAGE"
Doesn´t work
‎2015 Feb 17 12:35 PM
‎2015 Feb 17 12:37 PM
Hi,
Assign the object to a customer package whose name begins with Y or Z.If you want to create the object as a test object, you can also assign it to a local package (1st character = $) or a test package (1st character = T).
Thanks
KH
‎2015 Feb 17 12:44 PM
Y or Z is not allowed. And if I create a Test package I have no transport request - which I need to fullfill the guide.
If I try to use the test Package with x name I get the error: "Test objects cannot be created in foreign namespaces"
If I change the name to y I get the "remote creation in customer namespace not possible" error.
‎2015 Feb 17 12:49 PM
Ok, then try to manually create your X* BSP application on the side of SAP development system, providing all nessecary input. After your X*-named BSP will be successfully created, repeat the sharing.
‎2015 Feb 17 1:14 PM
I created the BSP manually now. And it worked.
But now it isn´t shown in my eclipse.
I´m able to open it in the gateway system but it isn´t shown in eclipse.
I restarted eclipse but still nothing.
‎2015 Feb 17 1:22 PM
Have you successfully shared your SAPUI5 project with BSP that you've just created? Or you have only created new BSP in SAP?
‎2015 Feb 17 1:30 PM
‎2015 Feb 17 1:48 PM
I got a dump exactly at this place yesterday, while configuring EQ Manager.
What's happening is that:
1) An error condition is reached
2) The backend system wants to tell you about that error condition.
3) If this was happening in SAPGui, you'd be able to figure out the issue. But you're not. You're in Eclipse. So step 2) gets a dump.
I resolved the issue by setting a breakpoint at the position in code where the dump happened. I looked at the program stack, and identified what was going on at step 1). That gave me enough information to search service.sap.com for further clues.
In summary: the dump isn't your problem. That's caused by the systems attempt to tell you about the error that's the real cause. However, the fact that the error is reported back to you (instead you get a dump) is also a bug. Which may have a resolution in service.sap.com
‎2015 Feb 17 2:46 PM
Thank you for this helpful information
So.. is there any possibility to solve this problem without changig system configuration - which I´m not allowed to do?
‎2015 Feb 17 4:34 PM
Yes - but you'll need to find out what is causing the error that makes the system try to popup a dialog. First step is to examine the call stack at the dump point. What actually is the system trying to advise you of.
For me, it was that it wanted to make a change but couldn't. For you it might be something else.
‎2015 Feb 18 7:56 AM
I think I found the problem.
If I manually create a BSP application I always get a warn message, that it could only be saved in a SAP Package. If I accept the popup I'm able to create the BSP app.
But my manually created BSP apps aren´t shown in eclipse as exisiting ones.