Is the platform down for maintenance? Or is something else happening?

[Former Member]

Hello,

I'm trying to access the platform's (Message Management Service Cockpit) display stored messages, and i'm also trying to edit some of the configurations and i'm always receiving 500 Internal Server Error. Also from time to time i'm receiving a Websocket communication problem.

I'm just asking when will this be fixed.

Thank you,

David

[anton_levin · Accepted solution]

Dear Users,

sorry for the late update. Unfortunately, the support of shared HANA DB on Trial has ended [1]. Starting from now, in order to run "iotmms" application, you would need to create the data source (HANA MDC or MaxDB) and respective data source binding manually. "iotmms" will not be able to create a schema (in the shared HANA) and data source binding automatically during deployment like it was before.

We will adapt our documentation as well as "iotmms" deployment procedure accordingly.

Sorry for the inconvenience,

Anton

[1] https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/38686b0610404a5e9c261d189cc...

P.S. "iotmms" might still work for those users who still have their shared HANA schema in place.

[gallada]

I had the same issue and tried all options but not working. IOTMMS is always in status " starting".

Can someone please help me out.

[benoussama]

hello,

I have problem in sap clud platform, I can't start iotmms java application, the statut is still in starting and after a few minutes I get statut of failed.

the error is:

2019 06 06 13:29:11#+00#ERROR#org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/com.sap.iotservices.mms]##anonymous#localhost-startStop-1#na#p2000459019trial#iotmms#web##na#na#na#na#Exception sending context destroyed event to listener instance of class com.sap.iotservices.mms.AppContextListener java.lang.NoClassDefFoundError: com/sap/iotservices/mms/config/Configuration$ConfigurationHolder : cannot initialize class because prior initialization attempt failed at com.sap.iotservices.mms.config.Configuration.getInstance(Configuration.java:238) at com.sap.iotservices.mms.MessageStore.<init>(MessageStore.java:70) at com.sap.iotservices.mms.MessageStore.<clinit>(MessageStore.java:66) at com.sap.iotservices.mms.AppContextListener.destroy(AppContextListener.java:204) at com.sap.iotservices.mms.api.BaseAppContextListener.contextDestroyed(BaseAppContextListener.java:27) at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:5204) at org.apache.catalina.core.StandardContext.stopInternal(StandardContext.java:5877) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:221) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:149) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:1018) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:994) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:652) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1127) at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:2021) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:836) Caused by: java.lang.ExceptionInInitializerError: com.sap.iotservices.mms.exception.InitializationError: Failed to retrieve the database connection from the SAP Cloud Platform SAP HANA / SAP ASE Service. Please check if you specified a valid data source binding for the MMS in the SAP Cloud Platform Cockpit. at com.sap.iotservices.mms.processing.sql.SqlPersistenceService.initSqlProvider(SqlPersistenceService.java:54) at com.sap.iotservices.mms.processing.sql.SqlPersistenceService.<clinit>(SqlPersistenceService.java:16) at com.sap.iotservices.mms.config.ConfigurationDbManager.<init>(ConfigurationDbManager.java:50) at com.sap.iotservices.mms.config.Configuration.<init>(Configuration.java:125) at com.sap.iotservices.mms.config.Configuration.<init>(Configuration.java:47) at com.sap.iotservices.mms.config.Configuration$ConfigurationHolder.<clinit>(Configuration.java:234) at com.sap.iotservices.mms.config.Configuration.getInstance(Configuration.java:238) at com.sap.iotservices.mms.api.BaseAppContextListener.registerConfiguration(BaseAppContextListener.java:73) at com.sap.iotservices.mms.api.BaseAppContextListener.contextInitialized(BaseAppContextListener.java:21) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:5157) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5680) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:1018) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:994) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:652) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1127) at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:2021) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:836) caused by: com.sap.db.jdbc.exceptions.SQLInvalidAuthorizationSpecExceptionSapDB: [10]: authentication failed at com.sap.db.jdbc.exceptions.SQLExceptionSapDB._newInstance(SQLExceptionSapDB.java:165) at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.newInstance(SQLExceptionSapDB.java:42) at com.sap.db.jdbc.packet.HReplyPacket._buildExceptionChain(HReplyPacket.java:976) at com.sap.db.jdbc.packet.HReplyPacket.getSQLExceptionChain(HReplyPacket.java:157) at com.sap.db.jdbc.packet.HPartInfo.getSQLExceptionChain(HPartInfo.java:39) at com.sap.db.jdbc.ConnectionSapDB._receive(ConnectionSapDB.java:3476) at com.sap.db.jdbc.ConnectionSapDB.exchange(ConnectionSapDB.java:1568) at com.sap.db.util.security.AbstractAuthenticationManager.connect(AbstractAuthenticationManager.java:40) at com.sap.db.jdbc.ConnectionSapDB._authenticateAndConnectSession(ConnectionSapDB.java:4087) at com.sap.db.jdbc.ConnectionSapDB._connectAnchor(ConnectionSapDB.java:2081) at com.sap.db.jdbc.DriverSapDB._connect(DriverSapDB.java:1540) at com.sap.db.jdbc.DriverSapDB.connect(DriverSapDB.java:1223) at com.sap.cloud.runtime.kotyo.persistence.client.datasource.DriverDataSource.getConnection(DriverDataSource.java:78) at com.sap.cloud.runtime.kotyo.persistence.client.datasource.DriverDataSource.getConnection(DriverDataSource.java:67) at com.sap.cloud.runtime.kotyo.persistence.client.trace.TraceableDataSource.getConnection(TraceableDataSource.java:78) at com.sap.cloud.runtime.kotyo.persistence.client.datasource.DataSourceConnectionFactory.createConnection(DataSourceConnectionFactory.java:47) at com.sap.cloud.runtime.kotyo.persistence.client.pool.PoolableConnectionFactoryAdapter.makeObject(PoolableConnectionFactoryAdapter.java:53) at org.apache.tomcat.dbcp.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1185) at com.sap.cloud.runtime.kotyo.persistence.client.pool.trace.TraceableGenericObjectPool.borrowObject(TraceableGenericObjectPool.java:37) at org.apache.tomcat.dbcp.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106) at com.sap.iotservices.mms.processing.sql.SqlPersistenceService.initSqlProvider(SqlPersistenceService.java:49) at com.sap.iotservices.mms.processing.sql.SqlPersistenceService.<clinit>(SqlPersistenceService.java:16) at com.sap.iotservices.mms.config.ConfigurationDbManager.<init>(ConfigurationDbManager.java:50) at com.sap.iotservices.mms.config.Configuration.<init>(Configuration.java:125) at com.sap.iotservices.mms.config.Configuration.<init>(Configuration.java:47) at com.sap.iotservices.mms.config.Configuration$ConfigurationHolder.<clinit>(Configuration.java:234) at com.sap.iotservices.mms.config.Configuration.getInstance(Configuration.java:238) at com.sap.iotservices.mms.api.BaseAppContextListener.registerConfiguration(BaseAppContextListener.java:73) at com.sap.iotservices.mms.api.BaseAppContextListener.contextInitialized(BaseAppContextListener.java:21) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:5157) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5680) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:1018) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:994) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:652) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1127) at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:2021) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:836)

at java.lang.Class.setExceptionThrownDuringClinit(Class.java:3685) at com.sap.iotservices.mms.config.Configuration.getInstance(Configuration.java:238) at com.sap.iotservices.mms.api.BaseAppContextListener.registerConfiguration(BaseAppContextListener.java:73) at com.sap.iotservices.mms.api.BaseAppContextListener.contextInitialized(BaseAppContextListener.java:21) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:5157) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5680) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145) ... 10 common frames omitted

Please can some one help me?

regards.

[Daniel_Degenhardt]

Hi,

im facing the same issue on hanatrial. I already tried to add a new binding to the mms Service but this isn't working to.

Regarding to Robs workaround:

4). Delete the existing binding with the shared DB.

there were no existing binging is was empty.

Has someone any idea how to fix this problem ?

best regards,

Daniel

[marcus_schiffer]

Hi,

is the issue fixed now or do i need to use one of the workaraounds ?

[anton_levin]

Unfortunately, an issue with the shared HANA DB on Trial is still valid. So, in order to start iotmms, you would need to bind it either to MaxDB or HANA MDC.

[t_vandijk2]

The second solution described at https://archive.sap.com/discussions/thread/3825912 worked for me:

1. stop MMS
2. remove the binding to MMS from <s-user>trial.iotmms.web schema
3. delete the the <s-user>trial.iotmms.web schema => Connection refused
4. create a new schema => Create a Database, e.g. iotmms2. Assign role IoT-MMS-User to your s-user
5. bind it to MMS app
6. start MMS (After one hour)

Downside: After 12 hours, the trial tenant database is shut down, and if you do not use it for 7 days, it is automatically deleted.

Best regards,

Theo

[vivekkrishnadas]

I have the same issue 😐

I am unable to successfully start the IoT MMS component. Does anyone know how long this downtime would last?

This is the one of the errors:

2017 11 20 13:26:11#+00#ERROR#com.sap.cloud.runtime.kotyo.persistence.client.datasource.DataSourceFactory##anonymous#localhost-startStop-1#na#p442125trial#iotmms#web##na#na#na#na#Failed to open SSL test connection, encrypted communication with server failedcom.sap.db.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: Cannot connect to jdbc:sap://vadbjn1.nwtrial.od.sap.biz:30015/ [Cannot connect to host vadbjn1.nwtrial.od.sap.biz:30015 [Connection refused (Connection refused) (local port 43494 to address 0.0.0.0, remote port 30015 to address 10.117.12.88 (vadbjn1.nwtrial.od.sap.biz))], -813.].

Regards,

Vivek

[anton_levin]

Hello Vivek,

there currently some issues with the shared HANA DB on Trial. IoT MMS is affected, since it cannot be started successfully without underlying data source. Technicians are informed. I will give an update here once it is fixed. As a workaround, you may create a MDC HANA or MaxDB Database/Schema and bind it manually to the IoT MMS

Sorry for the inconvenience,

Anton

[vivekkrishnadas]

Thanks Anton!

I was able to start IoT MMS using your workaround..

Regards,

Vivek

[rob_demandt]

Is there already an ETA on the fix for the shared DB?

[shweta_sahay]

Hi Vivek,

I am facing same difficulty with my trial account. Can you please share steps for workaround.

Thanks

Shweta

[rob_demandt]

Hi Shweta,

Steps for the workaround:

1). Navigate to database & schemas in the cloud platform cockpit

2). Create a new database of the HANA MDC type, start this database

3). Navigate to the data source bindings for the IoT Java application

4). Delete the existing binding with the shared DB.

5). Add a new biding with the newly created DB (user can be SYSTEM with the password you set when creating the database).

6). Start the IoT Java application again.

Hope this helps!

Rob

[former_member296546]

Hi Rob,

I am using an account in hanatrial and there I cannot find an option to navigate to database & schemas. I have only an option to manage Data Source Bindings. Could you please let me know if the path to this is different in the trial accounts?

Thanks,

Borislava

[shweta_sahay]

Thanks Rob, It worked for me .

[former_member373337]

Thanks Rob, It worked for me .

It is worth noting that we need to create Data Source Binding from Java Application >> IoT Application >> Configuration >> Data Source Bindings and not from DataBase and Schema >> db >> Data Source Bindings.

[Former Member]

Hello guys,

Later edit on the start/stop of the MMS service.

While trying to start the platform the logs return:

2017 11 16 12:28:35#+00#ERROR#com.sap.cloud.runtime.kotyo.persistence.client.datasource.DataSourceFactory##anonymous#localhost-startStop-1#na#p1943017867trial#iotmms#web##na#na#na#na#Failed to open SSL test connection, encrypted communication with server failedcom.sap.db.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: Cannot connect to jdbc:sap://vadbjn1.nwtrial.od.sap.biz:30015/ [Cannot connect to host vadbjn1.nwtrial.od.sap.biz:30015 [Connection refused (Connection refused) (local port 49267 to address 0.0.0.0, remote port 30015 to address 10.117.12.88 (vadbjn1.nwtrial.od.sap.biz))], -813.].

Any ideeas?

David

[anton_levin]

Then you have the same issue with the underlying DB like Muhsin has https://answers.sap.com/questions/356386/unable-to-add-a-new-db-or-schema-on-hcp-1.html

[Former Member]

Anton, what can we do in this situation ?

[anton_levin]

An internal ticket is already opened. I will give an update once it is fixed.

[Former Member]

Thank you Anton!

[bmcdonn2]

I submitted a question about this specific issue nearly 3 days ago. Is there any other method to get more expedient support for issues with trial instances? It seems to be the luck of the draw with hoping somebody from SAP notices a topic in the community. In my case it seems I was just unlucky and nobody noticed it.

https://answers.sap.com/questions/355219/trial-region-db-service-error-132.html

[anton_levin]

Sorry for the inconvenience, Brian. There are no SLAs and 24/7 Support provided for the Trial accounts comparing to Enterprise ones [1]. The only way for Trial users to report issues and get support is to report it via Community.

Regards,

Anton

[1] https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/8ed4a705efa0431b910056c0acd... > Table 1 and 2

[bmcdonn2]

I had read through the SLA so that's what I assumed. It's a shame that the options are so limited. I was hoping an OpenSAP course would be in session that makes heavy use of trial DB services as that seemed like my only other hope.

Is there anything I can do to make my questions more visible to SAP representatives in the community? I feel that I supplied exhaustive information and provided regular updates on the issue and yet it was simply ignored.

[anton_levin]

I would have replied that it is a good approach to follow the guidelines [1] on how to ask a question via community or tag your question accordingly [2] but in your thread [3] you did it perfectly already.

[1] https://www.sap.com/community/about/questions-and-answers.html

[2] https://www.sap.com/community/about/using-tags.html

[3] https://answers.sap.com/questions/355219/trial-region-db-service-error-132.html

[Former Member]

Hello Anton, Muhsin,

The IoT MMS was deployed and running, hence i could actually enter the platform, but none of the services was actually working. Not even the display stored messages. I'm attempting now to stop and start the iotmms from the SAP Cloud Platform Cockpit. Hopefully this will make it work.

I'll come back with a later edit when it will start again. Maybe with some printscreens as well.

Thanks for the fast replies.

David

[Former Member]

Can you please post the server log here such that I can get more info on this. HANADB is actually down imu; so if u r using any schema related to it. it can be the reason.

[Former Member]

ljs-trace-dff281f-2017-11-16.txt

Here are the last logs i'm receiving on the platform

[anton_levin]

Hello David,

IoT MMS is a component which is deployed and running in consumer (your) account. I suppose you are using Trial landscape. Please check if the MMS is up and running. Applications in the trial landscape are automatically stopped after a certain period of time. You would need to start it new. See respective IoT FAQ [1]

Regards,

Anton

[1] https://help.sap.com/viewer/7436c3125dd5491f939689f18954b1e9/Cloud/en-US/a012a3788b6e498a8971dd27c97... > MMS