skip to main content

SAP NetWeaver Newbie

Archive Job Failing on Adapter Engine with 503 Error


If archive job fails with the error "com.sap.aii.af.ra.ms.impl.core.archiving.executor.ArchiveExecutor,
Reason: java.io.IOException: Unable to create collection, returncode is 503 null
" it means that XML_DAS application is not running.

You can track this error While monitoring the Adapter Engine under Component Monitoring section of RWB. Click the details link on "Component messaging-system running?".

You may also have noticed for the error "com.sap.engine.services.deploy.container.ExceptionInfo: Exception during the initialization of container boot classcom.sap.archtech.daservice.ejb.PackMDBean0_0ContainerFP " in defaultTrace file.

To fix the problem start sap.com/tc~TechSrv~XML_DAS application. You can do this using telnet.

telnet <application host> 5<instance number>08
Login using j2ee_admin
lsc
jump <server node >
START_APP sap.com/tc~TechSrv~XML_DAS
list_app | grep XML_DAS
quit


If you see a null pointer exception (java.lang.NullPointerException) as the reason for failure of the archive job, check if there is any message with 0 payload size. use the following SQL command to find those messages:


SELECT MSG_ID, TRAN_HEADER FROM sap<sid>db.XI_AF_MSG WHERE (STATUS='DLVD' OR STATUS='FAIL') AND TRAN_HEADER like '%Content-Length=0%';


Delete those messages manually from the DB table and run the archive job.

1 comment:

Email Subscription

Get every new post into your inbox by subscribing us.

Want a reason to subscribe?
1. This sitemap might convince you to subscribe.
2. We do not misuse email IDs. We respect privacy.

© 2008 - 2017 sapnwnewbie. All rights reserved.