on 11-28-2007 9:46 AM
We're getting the exception
com.sap.tc.cbs.common.types.InternalErrorException: Failed to instantiate com.sap.tc.cbs.arc.impl.BuildLogWrapper
followed by
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
Caused by: com.sap.tc.cbs.arc.InitializationException: Failed to instantiate com.sap.tc.cbs.arc.impl.BuildLogWrapper
Caused by: java.io.EOFException: Unexpected end of ZLIB input stream
and further list of similiar exceptions while building and activating a DC
We use CMS using the track mechanism and have been able to successfully transport previously created DC's.
We also tried force activation of the said DC and have ended up with two Dirty DC's in the CBS and can't move any more DC's to consolidation and further up to the test machines due to the dirty DC's.
We have trawled through SAP notes but to no avail.
Does anyone have a solution?
Any helpful views will be rewarded with points. Thanks in advance.
The error may be caused by another problem. You might
1. check for (other) CBS-errors in application server logs
2. check also whether there is enough free space in file system where AS is running
best regards!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Looks like a corrupted jar file on the NWDI server.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
95 | |
11 | |
11 | |
10 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.