SAP CAL issue Activating HANA instance on AWS

My CAL instance of openSAP Course: Introduction to Software Development on SAP HANA 2013.01 is stuck in Activating status. I had previously deactivated my AWS account, and have now reactivated it. I got an error when trying to active the instance that my AWS account did not have the services required for the instance, and now I seem to be stuck in between creating the instance and the instance actually getting created. My AWS account is active, and I entered the security keys on the CAL side, but it is not working. Any help would be appreciated.

Hello Eric,
The instance entered in a state that does not allow to disappear from the list after the termination. We (the SAP CAL Team) just fixed the instance manually and it should disappear from your list. I also would suggest you to double check that there is no created instance in AWS console also.
Now you can create a new instance.
Best Regards,
Kremena

Similar Messages

Managing CAL ABAP on HANA instance and removing the secondary windows instance?

When you setup the ABAP on HANA CAL instance with AWS you get two AWS instances. One which is the ABAP on HANA server and one which is a Windows system holding copies of the development tools, etc.
I never use this second instance as I log on from my own pc/laptop; so its just wasting money. Can I simply delete it from the AWS console. The CAL does not allow me to delete it on its own. If I do delete that instance can I still manage it with CAL or am I on my own with AWS from that point?
Regards,
--Jason.

Hi Jason,
SAP CAL keeps track of what happens to the instances in your AWS account, the status is polled every other minute or so. Simply suspending or terminating it could have a severe effect on the operations in CAL.
Have you thought about starting the Windows instance on a smaller (probably too small) instance type which costs just a couple of cents? CAL cannot track if the SAP system in the instance is functional or not, CAL just checks the status of the container. So you could start the Windows instance on a 512MB machine ....
I know that this is not what you was aiming for, but it will probably solve the costs issue in the first place quickly.
Regards,
Hannes

Terminate CAL instance error - AWS credentials

Hi there,
I'm on a slightly misleading 'free' Fiori course via openSAP.
Once I realised 'free' meant that I may be charged hundreds of dollars by AWS I canceled/closed my AWS account.
Unfortunately I can't seem to now delete my CAL instance because it's trying to verify my credentials with my non-existent AWS account
Not quite sure how to get me out of this? Is there anyone that can help?
Thanks in advance,
Rob

Hi Rob,
The “undefined” instance stayed in SAP CAL although no VMs left in AWS after the terminate operation. The SAP CAL Team is working on a solution to clean-up such instances.
Apologies for the inconvenience,
Stanimir

SAP CAL Activation with AWS - Failure

Following Instruction for Getting Started. Followed SCN documentation
Created user, Assigned two groups with with all four policy's @ IAM
SAP CAL still fails to validate.
Also wonder if there is more than one user, How does Cloud Application library authenticate the correct user in AWS.
Kindly help

Hi Kaustubh,
This particular solution has two VMs and you were able to create only one of them because of the following error:
Operation Start failed on step Start Virtual Appliances with message: Start failed for VM SAP ERP 607 on SAP HANA SPS07 due to Amazon Web Services issue : AMAZON : Your account is currently being verified. Verification normally takes less than 2 hours. Until your account is verified, you may not be able to launch additional instances or create additional volumes. If you are still receiving this message after more than 2 hours, please let us know by writing to [email protected] We appreciate your patience. (Service: AmazonEC2; Status Code: 400; Error Code: PendingVerification; Request ID: cec64f67-b058-46ad-a813-be175b78b7fc)
This put the solution instance in status INCONSISTENT and the following Suspend and Resume operations will change the status of the existing VM but will not bring the missing VM up. To do so you may terminate this instance and create a new one. A couple of days should be enough for the AWS verification. If not, I would recommend to contact [email protected] as the error message advises.
Best regards,
Stanimir

CAL - Connect to an instance of SAP ERP Foundation Extension powered by SAP HANA

Hello,
I created and activated an instance in CAL today, the ERP on HANA trial.
Once this instance is activated ("green button"), the "connect" option appears but I'm not able to connect to it using http or SAP Gui.
I have no firewall, the error is:
This webpage is not available
Could you help me?
Thank you!

hi Pierre,
There could be multiple reasons for not being able to connect to the instance:
1. After click create instance, you need to wait for 45 minutes. Also the green botton comes,in the backend it is still working to complete the creation.
2. Once you have IP address, please try to connect to SAP GUI by manually add the server, instance number, etc into SAP GUI. See if it works. In addition, try to connect to BI launchpad via http:<IP address>:8080/BOE/BI.
3. Some user reported connection problem, we found out that certain AWS account may have problem with VPC layout used for this solution. check out the support AWS account:
• Click on EC2 Dashboard in left side navigation of the AWS Management Console • In upper right section of screen under Account Attributes section the Supported Platforms are listed http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-supported-platforms.html
regards, Xiaohua

SAP HANA ERP on AWS License Issue

Hi,
what licenses are available for the ERP version of SAP HANA for deployment on AWS? What is a MINISAP license? We tried to set up the ERP Trial from the SAP Cloud Appliance Library but can't access it via SAPGUI. Our expert says, the MINISAP license is valid for hosting on 64GB or less. Since we have chosen the smallest memory model available, it looks like we can't run it on AWS, which cannot be true. The system comes up, AWS charges money, but we can't access it. What did we do wrong? Seems like a few people here in this community use it already. I'd appreciate someone telling us how to fix this issue. We do not have problems with our BW instance which works well.
Best regards,
Chris

Hello Christian,
Trial systems in CAL come with a 30 day temporary license, already included. There is no need to install any other license into the system.
So your problem is, that you started an instance of the ERP Foundation Extension Trial System in CAL using your AWS account and you used the default settings in CAL (no changes to firewall or instance types. After 30 minutes or so the traffic light in the CAL UI under "INSTANCES" shows a green light - but you are still not able to connect with SAPGUI.
Is this correct? If so, there are two possible root causes:
1) your client machine is not in the same network as the ERP system. Could it be the case that your client machine is in a corporate network (behind a firewall) and the ERP system has been started on the internet?
2) the ERP on HANA system did not start automatically (which is very strange as everyone is using the same appliance). It could be the case that the AWS account has limits which prevent the instances to start up - but then CAL should give you an error message and it should NOT show green traffic lights in CAL.
Can you please check if you are affected by root cause 1).
If you can rule out 1) we need to investigate why 2) is happening. Can you please ssh into the HANA instance and fetch the dev_disp file from /usr/sap/<SID>/DVEBMGS00/work.
Regards,
Hannes

SAP CAL HANA - Connectivity issues

I deployed SAP HANA on AWS through SAP CAL.
I can connect to the HTTP interface and the HDB through the command line.
hdbsql=> \c -i 00 -u system
Password:
Connected to HDB@vhcalhdbdb:30015
hdbsql HDB=>
But if I try to connect to port 30015 remotely I just timeout. I have the 30015 open to the world in the AWS security group.
Is there a daemon that runs on the server that accepts remote connections or do I have a AWS network issue I need to investigate?

Hi Joseph,
Most probably you are behind a corporate firewall that does not allow you to connect to port 30015. Could you try to connect from another network?
Best regards,
Stanimir

SAP CAL HANA errors

SAP HANA, developer edition 1.0 SPS 09 created from SAP CAL running on AWS.
I am receiving the following errors when executing a query in HANA via jdbc.
The first execution runs for 6 minutes then produces this error:
Caused by: com.sap.db.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: [2]: general error: Allocation failed $REASON$
Caused by: com.sap.db.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: [2048]: column store error: [9] Memory allocation failed
I re execute the query it runs for 25 minutes then produces the same error.
Then the instance is unresponsive.
If I look in HANA studio general overview there is plenty of memory and cpu available to the HANA instance.
There is also a crush dump listed in the log files.
I see the following errors in the indexserver_alert_vhcalhdbdb.trc on the HANA server:
[3742]{-1}[-1/-1] 2015-03-18 18:41:42.430797 e Licensing
LicenseMeasurementPersistence.cpp(00161) : Error storing license measurement for application id '000670', value 26 at ' 2015-03-18 18:41:39.3910000', internal error
[3742]{-1}[-1/-1] 2015-03-18 18:41:42.430999 e Licensing
LicensePluginRegistry.cpp(00394) : Error storing license measurement: internal error
[3732]{300601}[27/-1] 2015-03-18 18:30:16.406867 e Executor
PlanExecutor.cpp(00825) : pop1245 (rc 9, Memory allocation failed)
pop = RowPlanOperator() # pop1245
pop.setDetails('')
[3732]{300601}[27/-1] 2015-03-18 18:30:16.406890 e Executor
PlanExecutor.cpp(00825) : pop1243 (rc 9, Memory allocation failed)
[4437]{300601}[27/-1] 2015-03-18 18:28:13.921145 e Memory
ReportMemoryProblems.cpp(00799) : 8: 0x00007f0b1ba7a8c5 in ptime::TrexPlanOp::executePtimeOp(ltt_adp::vector<Executor::PlanData*, ltt::integral_constant<bool, true> > const&, ltt_adp::vector<Executor::PlanData*, ltt::integral_constant<bool, true> > const&, TRexCommonObjects::TRexApiError&, Executor::ExecutionInfo const&)+0x41 at trex_plan.cc:340 (libhdbcswrapper.so)
The memory errors are repeated many times.
What is the recommendation to investigate this issue?
Thank you.

The file indexserver_alert_vhcalhdbdb.trc contains the following errors:
[4175]{300560}[23/-1] 2015-03-19 10:57:26.017346 e Executor
X2.cpp(02961) : 1: 0x00007f049f94df0a in _ZN5ptime3pcc16MonitorAllocBase14throwExceptionEv.isra.53+0x22 at pcc_MonitorAlloc.h:61 (libhdbrskernel.so)
[4175]{300560}[23/-1] 2015-03-19 10:57:26.017346 e Executor
X2.cpp(02961) : 2: 0x00007f049f9403f5 in ptime::Transaction::Transaction(ptime::Connection*, bool, bool, bool, bool)+0x18f1 at pcc_MonitorAlloc.h:114 (libhdbrskernel.so)
[4175]{300560}[23/-1] 2015-03-19 10:57:26.017346 e Executor
X2.cpp(02961) : 3: 0x00007f049ca15949 in ptime::TrexTempIndex::clearIndex() const+0x25 at trex_itab.cc:3020 (libhdbcswrapper.so)
[4175]{300560}[23/-1] 2015-03-19 10:57:26.017346 e Executor
X2.cpp(02961) : 4: 0x00007f049eb7bd74 in ptime::TrexObjectFactory::destroyTrexTempIndexObject(char const*, char const*, char const*)+0x40 at trex_object_factory.cc:1386 (libhdbrskernel.so)
[4175]{300560}[23/-1] 2015-03-19 10:57:26.017346 e Executor
X2.cpp(02961) : 5: 0x00007f049ca4e706 in ptime::TrexPlanData::~TrexPlanData()+0x1d2 at trex_plan_data.cc:49 (libhdbcswrapper.so)
6: 0x00007f049ca4e849 in ptime::TrexPlanData::~TrexPlanData()+0x5 at trex_plan_data.cc:53 (libhdbcswrapper.so)
7: 0x00007f04c44739ed in Executor::X2ConnectorValue::deleteItsValue()+0x29 at X2.cpp:323 (libhdbexecutor.so)
8: 0x00007f04c4488101 in Executor::X2::failPop(int)+0xb0 at X2.h:176 (libhdbexecutor.so)
9: 0x00007f04c44879b4 in Executor::X2::finishValue(Executor::X2ConnectorValue&, int&, bool)+0x110 at X2.cpp:920 (libhdbexecutor.so)
10: 0x00007f04c4488163 in Executor::X2::failPop(int)+0x110 at X2.cpp:3571 (libhdbexecutor.so)
11: 0x00007f04c44879b4 in Executor::X2::finishValue(Executor::X2ConnectorValue&, int&, bool)+0x110 at X2.cpp:920 (libhdbexecutor.so)
12: 0x00007f04c4488163 in Executor::X2::failPop(int)+0x110 at X2.cpp:3571 (libhdbexecutor.so)
13: 0x00007f04c44938d0 in Executor::X2::runPopTask(Executor::X2::PopTaskInfo&, int&, ltt::allocator&, ltt::allocator&)+0x1290 at X2.cpp:3548 (libhdbexecutor.so)
14: 0x00007f04c4494e32 in Executor::X2::runPopJob(Executor::X2Job*)+0x80 at X2.cpp:2956 (libhdbexecutor.so)
15: 0x00007f04c44956b8 in Executor::X2Job::run(Execution::JobObject&)+0x224 at X2.cpp:5294 (libhdbexecutor.so)
16: 0x00007f04ab3ec1fe in Execution::JobObjectImpl::run(Execution::JobWorker*)+0x72a at JobExecutorImpl.cpp:822 (libhdbbasis.so)
17: 0x00007f04ab3fadd2 in Execution::JobWorker::runJob(ltt::smartptr_handle<Execution::JobObjectForHandle>&)+0x2e0 at JobExecutorThreads.cpp:205 (libhdbbasis.so)
18: 0x00007f04ab3fbd24 in Execution::JobWorker::run(void*&)+0x1a0 at JobExecutorThreads.cpp:370 (libhdbbasis.so)
19: 0x00007f04ab433759 in Execution::Thread::staticMainImp(void**)+0x875 at Thread.cpp:492 (libhdbbasis.so)
[4175]{300560}[23/-1] 2015-03-19 10:57:26.017346 e Executor
X2.cpp(02961) : 20: 0x00007f04ab4343bd in Execution::Thread::staticMain(void*)+0x39 at ThreadMain.cpp:26 (libhdbbasis.so)
[4190]{300560}[23/-1] 2015-03-19 10:57:26.576080 e Memory
ReportMemoryProblems.cpp(00799) : OUT OF MEMORY occurred.
Host: sid-hdb
Executable: hdbindexserver
PID: 3599
Failed to allocate 131088 byte.
Current callstack:
1: 0x00007f04ab5a07fd in MemoryManager::PoolAllocator::allocateNoThrowImpl(unsigned long, void const*)+0x2a9 at PoolAllocator.cpp:1139 (libhdbbasis.so)
2: 0x00007f049dcfca79 in ptime::pcc::SingletonAlloc<ptime::pcc::MonitorAlloc<ptime::pcc::HeapAlloc>, ptime::pcc::GlobalScope>::allocate(unsigned long)+0x15 at pcc_MonitorAlloc.h:97 (libhdbrskernel.so)
3: 0x00007f049e095b50 in ptime::fastvector<void*, 16ul>::__allocate(unsigned long)+0x50 at fastvector.h:325 (libhdbrskernel.so)

Cant activate SAP ERP on HANA - Instance Status "Undefined"

Dear all,
following: http://sapappcenter.com/medias/SAP-ERP-powered-by-SAP-HANA-Getting-Started-Guide?context=bWFzdGVyfHJvb3R8MTE0MzE4MnxhcHB…
I tryed to run an ERP on HANA demo instance. So I have created an AWS account, activated EC2 and tryed to activate an appropriate 30 days image afterwards. All I can see is actually:
If I tryed to activate the instance through clicking the button "Activate" I was told to wait something about 40min, since the proccess need some time. I have waited for longer and also tryed more then one time, but sadly without any success: the instance is still in status "Undefined". Am I doing something wrong? Thanks,
cheers

Hi Stanimir,
SAP CAL should create a default VPC if you left the default network option. Could you check the network name in the instance details in SAP CAL?
I have checked this and found a default VPC, looks ok for me:
subnets:
route tables:
Not sure what you meant by network name, does this help?
Regarding rules, you just need to go back to the screen in the AWS console that you attached and click on view rules. Port 22 should be open for inbound calls.from anywhere, i.e. from 0.0.0.0/0.
Not sure I got you right, I took a look to Network ACL's and found the in resp outbound rules as following (here and further related to vpc-838446ea (10.0.0.0/16) | SAP CAL Default Network) :
I also found 3 appropriate security groups with in resp outbound rules:
None of these settings were done by me, they came obviously out of the box. Should I adapt something? Im a bit irritated since I have 3 security groups, no idea why. Thank you very much, I appreciate your help.
cheers

Error trying to activate HANA through SAP CAL

Hello,
I am encountering the following error when I try to activate AWS HANA through SAP CAL
"We are sorry, we cannot provide you with the solution due to the results of an export control check"
There seems to be a solution floating around but I can't seem to find the details.
Thank you in advance.
Jeff

Hi Stanimir, I am facing the same issue when trying to activate
1. openSAP - BI Clients and Applications on SAP HANA
2. SAP Business Warehouse 7.4 SP5 incl. SAP Business Objects BI 4.1 SP2 on SAP HANA 1.0 SP7 BYOL
error message
"We are sorry, we cannot provide you with the solution due to the results of an export control check."
Can you please help me ?
Sharan
[email protected]

HANA One on AWS default username and password for hdbsql having issues

Hello, I am going through the SAP HANA Academy online for the HANA Recommends project, and just getting my HANA instance setup and running through AWS.
In this video: http://youtu.be/P0U-XSnSd1Y
There is a point where the author is showing how to change the password for hdbsql. In order to do this, I need to log into hdbsql first using the default password, and then change it. Unfortunately, I keep getting an error saying that the username or password is incorrect (*10: invalid username or password: SQLSTATE: 28000).
Here are the commands I'm entering into PUTTY:
hdbsql => \c -i 00 -n localhost:30015 -u SYSTEM -p manager
Is the default password different?

Hi Ahmed,
I got the same problem.
To solve it, you can change the password in SAP HANA One Management Console.
Open your browser and put in the public DNS of your HANA box.
Enter your AWS Access Key Id and Secret Access Key
You should have the options to change the password.
For more information, go to
Configuring SAP HANA One | SAP HANA

Cannot create AWS Hana instance - RelayState

Hi all,
when I try to create an AWS Hana instance, I get the error message
HTTP Status 400 - Service Provider endpoint saml2/sp/acs could not redirect to original application URL because it could not get the RelayState value from the request.
The request has a RelayState, though:
RelayState:"oucrspobrksorqmpspnfqxuxw"
-- Micha

Hi Micha,
Out of curiosity (and self-interest), was a solution for this problem ever discovered?
I have been encountering the exact same issue at the exact same step. Every attempt I make to create a AWS HANA instance is generating the error message you lis above. This is true regardless of browser. I even attempted to create a new account using an alternative e-mail address, to no effect.
Were you able to make any headway?
Regards,
Matt

SAP hana one on AWS

Hi Experts,
I have launched SAP Hana One on AWS with CC2.8x Large suse linux environment. And configured Hana studio with database user SYSTEM.
My question is that is SAP Hana on on AWS comes with SAP solution (like ECC EHP6 or EHP7) or do we need to install SAP solution seperately?
I can login to OS level thru putty with HDBADM user and i can see /usr/sap/HDB/instance.
Please let me know if SAP Hana one on AWS comes with sap solution then let me know how to launch it with SAP gui
If sap solution not comes with Hana one let me know how to implement sap solution on HAna one AWS.
Thanks,
Krish

Hi Krish,
I'm afraid you have posted your questions in the wrong forum. Please try http://www.saphana.com/community/implement/support-communities/sap-hana-one-support for support on SAP HANA One related questions.
Thanks and Regards,
Bernd

Cannot start BW or HANA instances in SAP Management console

Hi,
I created instance of "SAP Business Warehouse 7.4 SP5 incl. SAP Business Objects BI 4.1 SP2 on SAP HANA 1.0 SP7". When I'm trying to start SAP BW or SAP HANA instances in "SAP Management console" via remote desktop connection I receive an error message :
"WebService error: 21 The operation timed out" / "The RPC server in unavailable".
Any ideas how to fix this?

Hi,
See note: 535532
Mid way through the note it says:
You can then register the SAP J2EE Engine as a windows-service by using the SAP J2EE Engine Config Tool. Open a command prompt and change to the directory <J2EE Engine installation directory>configtool and run configtool.bat or start this tool via your Start-Menu "Tools->Config Tool" of the J2EE Server entry. Select at the left navigation area of this tool the entry "cluster/ server" the checkbox "Enabled" at the tabstrip "NT Service". Apply these settings by clicking on "File->Apply" at the menu. Do the same with the entry "cluster / dispatcher".
After you have finished these steps you can register now the J2EE Engine as a windows service.
Start service.exe, which is also located in the directory
<J2EE Engine installation directory>configtool. It works with three
parameters:
Service.exe u2013install u2013 the service(s) is (are) registered as NT/2000 Service(s). For each specified cluster node, a separate service is generated. All services have startup mode automatic. To start the service(s), open the Control Panel ¨Services folder. Find the service in the list of available services (for example: SAP J2EE Server 1, SAP J2EE Dispatcher 1, SAP J2EE Server 2, and so on). Select it, and choose u201CStartu201D on the right-hand side. No u201CStartup Parametersu201D are needed for the service to run. The system starts the particular J2EE Engine 6.20 node in background mode. It can be used and administered as usual. The only difference is that the server does not run in a console window.
There may be other notes along these lines.
You should also check any notes on the setup of SAP in MSCS cluster, as it will contain instructions for registering the services.
Hope this gives you a pointer in the right direction.

Unable to activate or suspend HANA instance

After activating my HANA instance the status was “not defined”. So I tried to suspend but this also did not work, saying: Operation Suspend failed on step Suspend with message: Action Suspend did not complete in 600 seconds.
How to continue?

Hi Michael,
Your instance stayed in status STOPPING for several hours starting at 7 am PST. This is not an expected behavior so I looked at the AWS Status History and found the following log for Nov 21, EC2 (us-east)
[RESOLVED] Increased API Error Rates
6:25 AM PST We are investigating increased API error rates in the US-EAST-1 Region.
7:11 AM PST We are experiencing increased error rates for RunInstances and VPC related APIs. Error rates for new launches are also elevated. Existing running instances are unaffected.
8:31 AM PST 8:30 AM PST We are seeing recovery in API error rates and new launches are succeeding. Some API requests are being throttled with a RequestLimitExceeded error while recovery proceeds. Existing running instances were unaffected.
8:55 AM PST Between 5:40 AM and 8:35 AM PST we experienced increased error rates for RunInstances and VPC related APIs. Error rates for new instance launches were also elevated. Existing instances were not impacted. The service is currently operating normally.
This explains the issues you experienced on November 21st.
Best regards,
Stanimir

SAP CAL issue Activating HANA instance on AWS

Similar Messages

Maybe you are looking for