When looking at issues that participants of customer workshops or participants of the openSAP RAP course had when it comes to enable the ABAP trial account one solution, that is worth a try,is to delete and recreate your trial account.
- Delete your trial account
- Create a new trial account
- Run the booster “Prepare an Account for ABAP Trial”
Delete and recreate your trial account
- Open the SAP Cloud Platform cockpit of your trial account and click Enter your Trial Account https://cockpit.eu10.hana.ondemand.com/trial/#/home/trial
- Click on Delete Trial Account
- Click on Delete
- Now it is time to grab a coffee …
- Click on Go to Trial Home since you want to create a new fresh trial account.
- Choose your favorite region and click on Create Account
- Continue sipping coffee while your new personal trial is being created
Click on Continue
Start the booster
- Enter your trial account again
- Click on Boosters
- Click on Prepare an Account for ABAP Trial
- Wait again …
- Success – Download the service key
Troubleshooting
When the Booster fails you can check in the Service Marketplace of your Dev-Space dev whether the ABAP tile is visible.
It has been observed that (the reason is not clear yet) not all services and especially the ABAP service was not available.
So in case of problems you should check the Service Marketplace whether all services and especially the ABAP service is available.
If yes click on the tile and create the ABAP trial instance manually.
Cool tool, we always wanted smth like that. Thanks for your effort
Been there, done that! 🙂
Also make sure that the clock of your PC have the rigth time.
Great option to move faster.
I still have this issue. Never received a code and not sending any new code. I just got stuck there and created a new account to be able to access trial service. Anyone has any idea ?
Sorry I can’t help with this. My blog refers to the situation where the trial account works as such and the user is already registered, so no need to register the phone number.
After reading your helpful post I just thought that people interested in this post might have encountered an error like mine. So it looks like it’s somehow related to me 🙂 but if you think this question is not belong to this blog post, I can remove it. It wasn’t a direct question to you. Thanks for the post itself again!
Hi Huseyin,
I am having the same trouble. Please share any solution if you found.
Thanks!
Is there a way to reset password for my user CB0000000703?
when I try to log on to Eclipse, it keeps asking me to enter password for this user ID for TRL_EN
Hi Andrew,
followed the steps and got below error. .
Logon to system TRL failed (The message content is not acceptable. Accepted content types: application/vnd.sap.adt.core.http.session.v2+xml)
Thanks,
subba
Have you installed the latest Eclipse and latest ADT version as described here?
https://tools.hana.ondemand.com/#abap
If yes, what is your Eclipse version and what version does your ADT plugin have?
Thanks Andre!! you’re awesome
Below combination worked with Java 15..I guess from Feb 2021 we may have to align with one version for ADT/Eclipse/Cloud Connector( still needs Java 8)..Your thoughts
ADT client version: ABAP Development Tools 3.12
Thanks,
Subba
You can copy the java files (folder jre) within your Eclipse folder, so that the installation would be self contained.
https://blogs.sap.com/2019/10/25/running-abap-in-eclipse-from-a-usb-stick-powered-by-sapmachine/
OK Cool!! That’s really helpful
Hello Kumar,
have you solved the problem yet ?, i faced the same issue during use ADT connect to service instance .
I’m getting exactly the same problem: and this after deleting and recreating the trial account as described above.
After update install software ( Help > Install New Software ) then i issue is fixed.
ref : https://tools.hana.ondemand.com/#abap
Thanks for the tip!
Just enlarging on this comment a little: it’s not intuitively obvious to SAP ABAP developers (at least to this one) that changing the PC software will have any effect on connecting to SCP accounts. However, updating the JRE and ADT on Eclipse to the latest versions (https://tools.hana.ondemand.com/#abap) finally solved this issue for me after much head-scratching.