FAILURE - Could not start application in context path [/ ccos]

[danivalle]

Hello,

I have followed step by step the installation of SAP Customer Checkout manager, but when I try to start the CCOS, from tomcat, it fails: "FAILURE - Could not start application in context path [/ ccos]"

I have tried many times the installation, clean everything, but I get the same error everytime.

Could you please help me with this?

Thank you.

[sa0016187518]

I looks like you have a TLS version mismatch, whereby the SQL Server is using the old TLS1.0 protocol (and Tomcat the newer). If this is a internet facing SQL Server, I would advise against the use of TLS 1.0/1.1 (they are not considered secure anymore and prone to exploits), you should rather set it up with v1.2, which is also supported by (fully patched) older versions of SQL Server (from 2008 onwards, I think).

Best Regards

[danivalle]

We have removed everything. and started the configuration from scratch.

Now, the service "ccos" is running on apache, but while finishing the configuration of CCOS, we get the following error:

"The driver was unable to establish a secure connection to SQL Server with Secure Sockets Layer (SSL) encryption. Error: "The server selected protocol version TLS10 is not accepted by client preferences [TLS13, TLS12]". ClientConnectionId: 320cc175-8e78-41f3-a44f-f22ce61682f7"

How can we fix this?

Thank you.

Regards,

Daniel Valle.

[sa0016187518]

Hello Daniel,

it seems you have on the same device a mix of multiple java instances: JRE v8, HotSpot instance (I'm not sure this is supported from CCOM?!), and SAP Java 11. This leads to convoluted ENV Var configs (assuming you're on windows). On what Java instance is Tomcat exactly running on? Take a look a this blog post for reference: https://blogs.sap.com/2019/05/29/sap-customer-checkout-supports-sap-jvm/

The MSSQL DB also seems to be unreachable to the setup, which might be either a cause or a consequence of the errors above.

The IP you posted seems to be public one (btw I would refrain from posting it online), you should make sure that the network connectivity both ways is in place (although, it is indeed a public IP, you shouldn't have you SQL Server directly exposed, but rather keep it within VPNs or at least make sure the DB access is encapsulated with encrypted protocols).

Best Regards

[danivalle]

Hello,

Apache Tomcat 9
java version "1.8.0_291"
Java(TM) SE Runtime Environment (build 1.8.0_291-b10)
Java HotSpot(TM) 64-Bit Server VM (build 25.291-b10, mixed mode)
SAP Machine 11
SP10 for SAP CUSTOMER CHECKOUT MANAGER 2.0 PL 11

LOG:

2021-06-04 13:45:47,545 [http-nio-8080-exec-10] ERROR com.sap.scco.cs.init.ContextListener - ERROR

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'shiroFilter' defined in class path resource [applicationContext.xml]: Cannot resolve reference to bean 'securityManager' while setting bean property 'securityManager'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'securityManager' defined in class path resource [applicationContext.xml]: Cannot resolve reference to bean 'myRealm' while setting bean property 'realm'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'myRealm': Unsatisfied dependency expressed through field 'adminUserDAO'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'adminUserDAO': Unsatisfied dependency expressed through field 'sequenceNumberService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'sequenceNumberServiceImpl': Unsatisfied dependency expressed through field 'configurationService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'configurationService': Unsatisfied dependency expressed through field 'executorService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'serverExecutorServiceImpl': Unsatisfied dependency expressed through field 'adminUserService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'adminUserService': Unsatisfied dependency expressed through field 'authService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'authService': Unsatisfied dependency expressed through field 'userService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'userService': Unsatisfied dependency expressed through field 'securityService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'securityServiceImpl': Unsatisfied dependency expressed through field 'passwordPolicyManager'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'passwordPolicyManager' defined in class path resource [applicationContext.xml]: Cannot resolve reference to bean 'cdbSession' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'cdbSession' defined in class path resource [applicationContext.xml]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.sap.scco.ap.pos.dao.CDBSession]: Factory method 'createDBSession' threw exception; nested exception is javax.persistence.PersistenceException: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.7.7.v20200504-69f2c2b80d): org.eclipse.persistence.exceptions.DatabaseException

Internal Exception: java.sql.SQLException: Connections could not be acquired from the underlying database!

Error Code: 0

Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: No se pudo realizar la conexión TCP/IP al host IP, puerto 1433. Error: "connect timed out: IP:1433. Verifique las propiedades de conexión, compruebe que hay una instancia de SQL Server ejecutándose en el host y aceptando las conexiones TCP/IP en el puerto y compruebe que no hay ningún firewall bloqueando las conexiones TCP en el puerto.".

at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(SQLServerException.java:234) ~[mssql-jdbc-7.4.1.jre8.jar:?]

at com.microsoft.sqlserver.jdbc.SQLServerException.ConvertConnectExceptionToSQLServerException(SQLServerException.java:285) ~[mssql-jdbc-7.4.1.jre8.jar:?]

[anderson_schmitt]

Hello Daniel,

Is there any information in the CCO manager log files? See KBA #2543967

What is the version (FP and PL) of the CCO manager?
What is the version of the JAVA?
What is the version of the Apache Tomcat?

Regards,

Anderson