UME properties are getting loaded after during cluster Import.

Question

Hi All,
We are getting an error while starting the JAVA instance of oue SCM system.
We have done a SYSTEM refresh and during our Pre Steps we have exported the Cluster DATA from the config tool.
After the Restore when we have imported the Cluster Data back from Config Tool, we are getting this error
Error occured hile loading UME properties MSG:null.
We are using ABAP database as a userstore, now we are not able to see the UME LDAP DATA tab in the config tool.
nd also we are getting error when we are opening the Propertysheet com.sap.security.core.ume.service.
Kindly help us on that as we are not getting any help on net.
Regards,
Arun Pathak

Answer 1

This the dafault Trace from location /usr/sap/<SID>/DVEBMSG<nn>/j2ee/cluster/server0/log/defaultTrace
#1.#001E0BFD70DA001F00000002000002240004809A3FD2D48C#1267299890942#com.sap.security.core.server.ume.service.UMEServiceFrame##com.sap.security.core.server.ume.
service.UMEServiceFrame.start()#######SAPEngine_System_Thread[impl:5]_72##0#0#Error##Plain###com.sap.security.core.util.config.UMConfigurationException: Readi
ng current UME properties failed.: Invalid PKCS\#5 padding length: 243#
#1.#001E0BFD70DA001F00000003000002240004809A3FD2D521#1267299890942#com.sap.security.core.server.ume.service.UMEServiceFrame##com.sap.security.core.server.ume.
service.UMEServiceFrame.start()#######SAPEngine_System_Thread[impl:5]_72##0#0#Error##Plain###com.sap.security.core.util.config.UMConfigurationException: Readi
ng current UME properties failed.: Invalid PKCS\#5 padding length: 243
        at com.sap.security.core.server.ume.service.SAPJ2EEConfiguration.readPropertiesFromStorage(SAPJ2EEConfiguration.java:242)
        at com.sap.security.core.util.config.UMConfigurationBase.refreshProperties(UMConfigurationBase.java:1043)
        at com.sap.security.core.util.config.UMConfigurationBase.initialize(UMConfigurationBase.java:113)
        at com.sap.security.core.server.ume.service.SAPJ2EEConfiguration.<init>(SAPJ2EEConfiguration.java:143)
        at com.sap.security.core.server.ume.service.SAPJ2EEPlatformTools.<init>(SAPJ2EEPlatformTools.java:79)
        at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:258)
        at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
        at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
        at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
        at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
        at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:81)
        at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:152)
caused by -
com.sap.engine.frame.core.configuration.ConfigurationException: Invalid PKCS\#5 padding length: 243
        at com.sap.engine.core.configuration.impl.security.Crypter.decrypt(Crypter.java:168)
        at com.sap.engine.core.configuration.impl.addons.PropertyEntryImpl.<init>(PropertyEntryImpl.java:97)
        at com.sap.engine.core.configuration.impl.addons.PropertyEntryImpl.readPropertyEntry(PropertyEntryImpl.java:54)
        at com.sap.engine.core.configuration.impl.addons.PropertySheetImpl.<init>(PropertySheetImpl.java:63)
        at com.sap.engine.core.configuration.impl.ConfigurationImpl.getPropertySheetExtensionInterface(ConfigurationImpl.java:198)
        at com.sap.engine.core.configuration.impl.ConfigurationImpl.getPropertySheetInterface(ConfigurationImpl.java:132)
        at com.sap.security.core.server.ume.service.SAPJ2EEConfiguration.readPropertiesFromStorage(SAPJ2EEConfiguration.java:228)
        at com.sap.security.core.util.config.UMConfigurationBase.refreshProperties(UMConfigurationBase.java:1043)
Edited by: Arun Pathak on Feb 28, 2010 10:59 PM