Dirty DC's & Unexpected end of ZLIB input stream

[Former Member]

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.

[AndreyH]

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!

[Former Member]

Looks like a corrupted jar file on the NWDI server.

[Former Member]

Seems like that to me too.

Any way I can delete this and get the dev guys to redeploy?

Thanks again.

[Former Member]

No, it's an NWDI core jar that's corrupt, not something the dev guys created. You will have to replace the broken jar on the NWDI server.

[Former Member]

Hello,

We are facing the same problem with the SAP_BUILDT.sca (SP14).

Any solutions found yet?

Where exactly in the NWDI server can we fix the broken jars?

I would appreciate and kind of input on this one.

Thanks and Regards,

Reena