Error while upgrading JSPM from 7.0014.0 to 7.01.2.2

[Former Member]

Hi Gurus,

While upgrading JSPM from 7.0014.0 to 7.01.2.2 on Solution Manager, I get following error:

Deployment of archive /usr/sap/trans/EPS/in/jspm02_2-20002796.SCA has been rejected because it depends on missing components. Exception occured during extractSingleFile: Unexpected end of ZLIB input stream Error during validation.

Thanks,

[Former Member]

We resolved issue by updating JSPM from 7.0014.0 to 7.0019.0 and then 7.01.2.3.

Thank you everyone for looking at this and giving suggestions.

Regards,

[Former Member]

SDM log is saying failed to load sca file. file has all permission. I have found following error in defaulttrace0 under despatcher\log. We have AIX with Oracle. Checked all j2ee processes are running.

-

---

Thread[SAPEngine_System_Thread[impl:6]_17]

Task: com.sap.engine.core.thread.impl6.ActionObject - Processing Task [classname: com.sap.engine.services.log_configur

ator.archive.ArchivingThread | toString: com.sap.engine.services.log_configurator.archive.ArchivingThread@2ee72ee7] wi

th classloader [com.sap.engine.core.service630.container.ComponentClassLoader@7b127b12@service:log_configurator]#

#1.#00096B6B99D4000000000016007EA03E00046E989F9AD138#1247501698650#System.err##System.err#######Thread[Thread-1,5,mai

n]##0#0#Error##Plain###com.sap.engine.frame.core.configuration.ConfigurationLockedException: Cannot lock Configuration

; it is already locked.

at com.sap.engine.core.configuration.impl.ServerEnvironment.addLock(ServerEnvironment.java:316)

at com.sap.engine.core.configuration.impl.ServerEnvironment.addLock(ServerEnvironment.java:340)

at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.openConfiguration(ConfigurationCache.java:7

56)

at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.

java:734)

at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.

java:693)

at com.sap.engine.core.cache.impl.spi.storage.DBStorage.<init>(DBStorage.java:64)

at com.sap.engine.core.cache.impl.CacheManagerImpl.init(CacheManagerImpl.java:223)

at com.sap.engine.core.Framework.loadSingleManager(Framework.java:577)

at com.sap.engine.core.Framework.loadManagers(Framework.java:255)

at com.sap.engine.core.Framework.start(Framework.java:189)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)

at java.lang.reflect.Method.invoke(Method.java:391)

at com.sap.engine.boot.FrameThread.run(FrameThread.java:61)

at java.lang.Thread.run(Thread.java:770)

Caused by: com.sap.engine.frame.core.locking.LockException: Cannot lock [2009071311145862500000vq2ua268...............

....202415500, !J2EE_CONFIGURATION_MANAGER, 94d735ee/@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@, X]; it is in use by another owner. The l

ock collision occurred with user <internal>.

at com.sap.engine.core.locking.impl3.LockingManagerImpl.lockInternal(LockingManagerImpl.java:257)

at com.sap.engine.core.locking.AbstractLockingManagerImpl.lock(AbstractLockingManagerImpl.java:423)

at com.sap.engine.core.locking.AbstractLockingManagerImpl.lock(AbstractLockingManagerImpl.java:443)

at com.sap.engine.core.locking.ServerInternalLockingImpl.lock(ServerInternalLockingImpl.java:42)

at com.sap.engine.core.configuration.impl.ServerEnvironment.addLock(ServerEnvironment.java:312)

... 16 more

[Former Member]

Hi,

Select whole SP and than try to apply the JSPM.

Regards,

Kannan

[sunny_pahuja2]

Hi,

Could you please paste SDM logs here ?

Thanks

Sunny

[Former Member]

Check this,

Note 1359507 - System update fails because of wrong permissions under JSPM

Also if the above 1 dosent suite for ur problem, paste the SDM log here

You could check the most recent logs under the SDM log directory:

<drive>:\usr\sap\<sid>\JC00\SDM\program\log esp ones like sdm_*.err.

Regards,

Ravi