Symptom
After connect a Diagnostics Agents to a SAP Solution Manager 7.20, the SMDAgent logs shows errors with message:
java.io.IOException: javax.crypto.BadPaddingException: Invalid PKCS#5 padding length: <xxxxxx> |
The complete error message may refer to distinct SMDAgent resources, for example:
# | Error Message |
1 | Error P4 configuration error [EXCEPTION] java.io.IOException: javax.crypto.BadPaddingException: Invalid PKCS#5 padding length: 41 at com.sap.smd.core.runtime.broker.application.core.application.ApplicationConfigStore.refreshProperties(ApplicationConfigStore.java:437) |
2 | Error LogService_7b7c67c4: Error during initialization [EXCEPTION] java.io.IOException: javax.crypto.BadPaddingException: Invalid PKCS#5 padding length: 66 at com.sap.smd.core.runtime.broker.application.core.application.ApplicationConfigStore.refreshProperties(ApplicationConfigStore.java:437) |
3 |
Error Extracting configuration from secstore file /usr/sap/DAA/SMDA98/SMDAgent/applications.config/com.sap.smd.agent.application.logfilecollector/_Default_Configuration.properties Failed. |
Read more...
Environment
- SAP Solution Manager 7.20
- SAP Solution Manager Diagnostics
Product
Keywords
KBA , SV-SMG-DIA-SRV-AGT , Agent Framework , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.