on 04-26-2016 2:44 AM
We recently applied the SPS17 patching to SAP PI 7.3 (Java only system). The patching was executed using the Java Administrator account. After the support pack update, none of the users are able to login to system. All users including Administrator account receives "User authentication failed" for their valid password logons.
This was the steps followed for patching the system -
1) From solution manager --> LMDB --> Product System --> Maintenance optimizer transaction --> Created the stack XML
2) Used SUM tool 1.0 SP12 to apply the patching
3) Took backup of exe, global and profile directories (OS is AIX 64-bit).
4) First patched the jvm to 6.01.87.0 successfully ( from 6.01.76.0).
5) Then started the java components and kernel patching. Kernel updated to kernel release 722, patch# 101.
6) During the middle of offline deployment of java components, the SUM tool showed error -
[Error ]: The following problem has occurred during step execution: com.sap.sdt.jspm.service.JspmServiceException: Could not update components.
Deployment of queue Queue_2016.04.21 at 15:04:55 completed with error Deployment error. See log deploy_api.0.log for details.
java.lang.RuntimeException: com.sap.engine.services.dc.api.AuthenticationException: [ERROR CODE DPL.DCAPI.1148] Could not establish connection to AS Java on [host:50004]. Authentication did not succeed. Wrong or missing security credentials (password) for principal [Administrator], or the specified principal has no permissions to perform JNDI related operations.
com.sap.engine.services.dc.api.AuthenticationException: [ERROR CODE DPL.DCAPI.1148] Could not establish connection to AS Java on [host:50004]. Authentication did not succeed. Wrong or missing security credentials (password) for principal [Administrator], or the specified principal has no permissions to perform JNDI related operations.
javax.naming.NoPermissionException: Exception during getInitialContext operation. Wrong security principal/credentials. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Authentication did not succeed.]
com.sap.engine.services.security.exceptions.BaseLoginException: Authentication did not succeed.
7) At this time the system was starting up in safe mode and after a while system started up normally, but then users are getting login failure for their valid passwords.
😎 In-order to complete the patching, we enabled the SAP* login to the system and reset password for Administrator account.
9) Restarted the SUM tool from point of failure and patching completed fine with no errors.
10) But after patching, all users get "User authentication failed" error for login with their valid passwords which they used before the patching was applied. (If we reset their password, they can login to system)
Has anyone encountered this issue after SPS17 patching on a SAP PI 7.3 Java only system? If so could you please let us know what was the resolution taken to fix this?
Thank you in advance!
Looking forward of a solution to this problem.
Thank you Manu for response,
I referred to the note (1678363 - JSPM fails during the validation phase in NW 7.3) you mentioned and yes like I already said we had applied JVM patching first and also the core patches are included in the SPS17 patching.
We did not restart full system at that time when SUM showed error, it was just the Java systems restart only by SUM process. After patching was completed, we did a full system restart, but still the login issue remains.
ISSUE RESOLUTION:
The java core patches were applied to system and the user login issue was resolved.
So if anyone planning to do SPS17 patching then include these latest patch level for java core patches -
SERVERCORE17P_17-20007148.SCA
ENGINEAPI17P_11-20007071.SCA
BASETABLES17P_1-10009491.SCA
EPRUNTIME17P_26-20007134.SCA
J2EEFRMW17P_10-20007080.SCA
CORETOOLS17P_3-20007067.SCA
LMNWABASICAPPS17P_3-10009493.SCA
UMEADMIN17P_3-20007085.SCA
thanks,
Noora
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi ,
The first issue you encountered seems to be a JVM issue. Please read the following Note ( and perform as recommended if the issue reappears while patching on subsequent systems )
and deploy the latest JVM available
As for the second issue of users not able to login before reset of password
Did you perform a full restart of the system . ?
Also can you post the default trace and the security trace files
Thanks ,
Manu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.