Error deploying MII in NetWeaver Java 7.4

[former_member221487]

Could not update components. Deployment of queue Queue_2015.08.25 at 20:58:08 completed with error Deployment error. See log E:\SUM\SUM\sdt\log\SUM\deploy_api.0.log for details. com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException. Reason: ASJ.dpl_dc.001085 Operation [deploy] of [sap.com_xapps~mpm~mii] failed com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 Operation [deploy] of [sap.com_xapps~mpm~mii] failed com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] Operation [deploy] of [sap.com_xapps~mpm~mii] failed com.sap.engine.services.deploy.server.utils.DSRemoteException: ASJ.dpl_ds.006193 Operation [deploy] of [D:\usr\sap\MAD\J00\j2ee\cluster\server0\.\temp\tc~bl~deploy_controller\archives\45\OEEMII00_0_SCA1440532835605\DEPLOYARCHIVES\xapps~mpm~mii.sda] failed com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception while [validating application sap.com/xapps~mpm~mii. The Deploy Service called the following containers: [developmentserver] to process it but none of them returned information about deployed components. The registered containers at this moment were [KMContentHandler, BRMS_Content_Archive, z_com.sap.security.policy-configurations, utl_handler, developmentserver, Monitoring Configurator, component.info_handler, ConfigFwkContainer, servlet_jsp, connector, classification_handler, CTCContainer, PortalRuntimeContainer, JDBCConnector, Content Container, ecm_content_handler, dbcontentcontainer, scheduler~container, src.zip_handler, PCD Content Deployment Handler, ConfigFwkContentHandler, ConfigurationsContainer, orpersistence, appclient, JMSConnector, Cluster File System, Cache Configuration Upload, com.sap.security.ume, SCA Composites Container, metamodelrepository, ESRContentHandler, textcontainer, eden_handler, Galaxy_Content_Archive, uddi_handler, MigrationContainer, webservices_container, com.sap.security.login-modules, dbschemacontainer, com.sap.security.policy-configurations, EJBContainer, MDRContainer, SEAHandler, app_libraries_container, SAP-EU-GP]. Possible reason: An AS Java service, which is providing a container and is required for deployment, is stopped or not deployed. Hint: Contact the owners of application sap.com/xapps~mpm~mii to point you to the containers that need to be available and started on the system for successful deployment. CSN component for application is [MFG-MII-CON].]. sap.com/OEE_MII: Deployment of archive E:\SUM\51048210\DATA_UNITS\MII\OEEMII00_0.SCA for component sap.com/OEE_MII aborted Detailed message: 1. Item is skipped because of failed deployment of item 'sap.com_xapps~mpm~mii' and because the applied error strategy is OnErrorStop 2. Contains Aborted deployment component: sap.com_xapps~mpm~mii Deployment of archive E:\SUM\51048210\DATA_UNITS\MII\OEEMII00_0.SCA --> xapps~mpm~mii.sda for component sap.com/xapps~mpm~mii aborted Detailed message: 1. ASJ.dpl_ds.006193 Operation [deploy] of [D:\usr\sap\MAD\J00\j2ee\cluster\server0\.\temp\tc~bl~deploy_controller\archives\45\OEEMII00_0_SCA1440532835605\DEPLOYARCHIVES\xapps~mpm~mii.sda] failed -> Exception while [validating application sap.com/xapps~mpm~mii. The Deploy Service called the following containers: [developmentserver] to process it but none of them returned information about deployed components. The registered containers at this moment were [KMContentHandler, BRMS_Content_Archive, z_com.sap.security.policy-configurations, utl_handler, developmentserver, Monitoring Configurator, component.info_handler, ConfigFwkContainer, servlet_jsp, connector, classification_handler, CTCContainer, PortalRuntimeContainer, JDBCConnector, Content Container, ecm_content_handler, dbcontentcontainer, scheduler~container, src.zip_handler, PCD Content Deployment Handler, ConfigFwkContentHandler, ConfigurationsContainer, orpersistence, appclient, JMSConnector, Cluster File System, Cache Configuration Upload, com.sap.security.ume, SCA Composites Container, metamodelrepository, ESRContentHandler, textcontainer, eden_handler, Galaxy_Content_Archive, uddi_handler, MigrationContainer, webservices_container, com.sap.security.login-modules, dbschemacontainer, com.sap.security.policy-configurations, EJBContainer, MDRContainer, SEAHandler, app_libraries_container, SAP-EU-GP]. Possible reason: An AS Java service, which is providing a container and is required for deployment, is stopped or not deployed. Hint: Contact the owners of application sap.com/xapps~mpm~mii to point you to the containers that need to be available and started on the system for successful deployment. CSN component for application is [MFG-MII-CON].]. Create an OSS message in component: MFG-MII-CON for support. See Deploy Controller log E:\SUM\SUM\sdt\log\SUM\deploy_api.0.log for details.

[abhijeet_singh2 · Accepted solution]

Step by Step procedure for you.

1. If its an Addon, then check for the dependency of the addon from Mopz only. ie Mopz select singly component.Also check in PAM from the "exact component name". Use SUM SPS13. its stable

2.  its a stack package. then generate XML and follow procedure and get an ADDON of MI. Very. it tells whether the ADDON will be possible or not.

Thanks

ABhijeet