Symptom
The SAP Application Server JAVA administrator tries to deploy an archive and this activity fails due to the below error recorded in the deployment traces:
****************************************************************************************************************************
[deploy] of <application name>failed [EXCEPTION] Caused by: com.sap.engine.services.dc.gd.DeliveryException: Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Error while reading the application descriptor of EAR [/usr/sap/<SID>/J<nr>/j2ee/cluster/server0/temp/..] Caused by: com.sap.engine.services.deploy.ear.exceptions.BaseIOException: Could not parse deployment descriptor [META-INF/application-j2ee-engine.xml] of component Hint: Check if it is formatted properly according to its DTD or XML Schema.
****************************************************************************************************************************
Read more...
Environment
- Release Independent
- SAP NetWeaver
Product
Keywords
JSPM, 1868308, KM deployment fails, KMCBC, deployment error, SUM stuck, SUM hangs, Deploying offline components, exit code 67, com.sap.sql.connect.pool.Pool.start, SAP JAVA versions, SAPJVM versions, Check if server is started, access point for the protocol is available, 1925352, SRM down, security, application issue, deployment failed , KBA , BC-JAS-DPL , Deployment , BC-CTS-DI , Development Infrastructure (NetWeaver Java) , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.