Doc ID |
|
SOLN360283 |
Version: |
|
1.0 |
Status: |
|
Published |
Published date: |
|
01 Mar 2021 |
Details
15.1 Security and 3rd Party Update Kit 16
Problem Clarification
cannot configure LDAPS
Cause
As per verint analysis:
Caused by: weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception
at weblogic.jdbc.rmi.internal.StatementImpl_weblogic_jdbc_wrapper_Statement_com_microsoft_sqlserver_jdbc_SQLServerStatement_12214_WLStub.executeUpdate(Unknown Source)
at weblogic.jdbc.rmi.internal.StatementStub_weblogic_jdbc_rmi_internal_StatementImpl_weblogic_jdbc_wrapper_Statement_com_microsoft_sqlserver_jdbc_SQLServerStatement_12214_WLStub.executeUpdate(Unknown Source)
at weblogic.jdbc.rmi.SerialStatement_weblogic_jdbc_rmi_internal_StatementStub_weblogic_jdbc_rmi_internal_StatementImpl_weblogic_jdbc_wrapper_Statement_com_microsoft_sqlserver_jdbc_SQLServerStatement_12214_WLStub.executeUpdate(Unknown Source)
at com.verint.tools.security.wlconfiguration.logic.steps.DBUpdate.doLogic(DBUpdate.java:95)
... 2 more
Caused by: java.rmi.UnmarshalException: Problem deserializing error response; nested exception is:
java.io.InvalidClassException: com.microsoft.sqlserver.jdbc.SQLServerException; local class incompatible: stream classdesc serialVersionUID = -2195310557661496761, local class serialVersionUID = -5240672651897777543
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:237)
It seems to be "sql class files between the WLConfig tool and weblogic are not compatible".
Solution
- Reverted the config of weblogic to WFO DB Authentication
- Make sure WFO and Weblogic Console is accessible,
- Post that validated the AD values whichever customer added to configure through ADValidation Tool.
- Post that Re-ran the New WL Config Tool version which released in FEB 2021
- Post that WFO is accessible and users are able to login as well.