This page is part of the larger series of blogs relating to SAP Omnichannel POS -
Admin & Operational Topics.
This page discusses about the various Startup issues related to the 25 odd GK Applications. This provide hints, leads, suggestions towards solving the start up issues.
GK Cluster Applications - Startup Issue
Applications : CIS, SDC, MWB, UCON, POS-Server, POS-Service, GK-Portal, GKR-Launchpad
Prerequisite:
You have already learnt about the
Restart Tips of GK Applications, you might know the locations of the logs, which contain valuable information about the status of the application.
- Check the Debug log file of the respective application, where there is a start up issue
- Find the relevant error message, which triggered the shutdown of the application. (This could happen to an already running application or during the startup of the application)
- Follow the below provided most commom error messages section to troublshoot the issue according to the error message encountered in Your debug log file.
- Ensure to follow always the cardinal rule: If the CIS is affected, then stop all GK Cluster applications and then restart CIS. Once CIS is fine (check in logs), then startup all GK Cluster applications.
Issue: Failed to connect to [tcp://hostname1:7000, tcp://hostname2:7000]
- Above error message indicates that the embedded ActiveMQ on CIS is unreachable
- Check whether the CIS is running and heathy by confirming their logs.
- Check if the hostnames are reachable
- Check if the port is not blocked (Firewall, etc)
- If CIS is running fine, then start the failiing GK Application again and check the logs for confirmation
Issue:SAP DBTech JDBC: [362]: invalid schema name: WKO_MASTER: line 1 col 12
There is an error message similar to:
META-INF/com.gk-software.core.server/mod-tenant/tenant-registry/tenant-schema-registry.xml]: Invocation of init method failed; nested exception is org.springframework.transaction.CannotCreateTransactionException: Could not open JDBC Connection for transaction; nested exception is com.sap.sql.exception.OpenSQLException: SAP DBTech JDBC: [362]: invalid schema name: WKO_MASTER: line 1 col 12 (at pos 11)OpenSQLExceptionCategories: [NON_TRANSIENT, DB_OBJECT_UNKNOWN]
- The above error message is clearly pointing to the Configuration at the Storemanager.
- Check the node for this application in the Storemanager, especially the DB conneciton under parameter section: ds-embedded.properties or similar.
Issue: could not resolve placeholder 'datasource.driver'
This error might not appear in the usual logs, but it would appear in the NW Java Default trace / application logs.
[META-INF/com.gk-software.svs/app-svs/component-container-beans.xml]: Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: Invalid bean definition with name 'originalDataSource' defined in class path resource [META-INF/com.gk-software.core.server/mod-datasource-dbcp/datasource/data-source.xml]: Could not resolve placeholder 'datasource.driver']
- This error also denotes that the application configuration in SM related to Database connection is not correct
- However, just check if the Datasource defined in the Netweaver Java is proper (use ping test in the Netweaver Admin) - To rule out any issue with the Datasource.
- Check the node for this application in the Storemanager, especially the DB conneciton under parameter section: ds-embedded.properties or similar
Issue: gk.ee_common.encryption.EncryptorException: Problem during decrypting (please check if provided text isn't in plain form or wasn't malformed)
The error message might be similar to:
ERROR {Thread-61115} [N/A] [N/A ] [AuthenticationConfig] Failed to decrypt password.
gk.ee_common.encryption.EncryptorException: Problem during decrypting (please check if provided text isn't in plain form or wasn't malformed)
- This error denotes that the password that is being expected for the Application in question for any usage (DB, export URL [PI]) is wrong.
- Either the password itself is wrong or the password in the files are in 'unencrypted form'.
- Please check and correct the error as per the information available in note: 2729737
This page will be continuously updated with more known & common errors.
