un-deploy component in NetWeaver 7.3 ( BI Portal )

[Former Member]

Hi all,

Currently we are facing an error with a deployment of component on NetWeaver 7.3 ( BI Portal ) specifically with u201Csap.com/SAPPCUI_GPu201D

<br><br>

One of the resolution that i searched around is to re-deploy back the component. But for NetWeaver 7.3 theres no SDM, is there is a method to un-deploy component in NetWeaver 7.3?

<br><br>

OS: Windows2003 Server

DB:MS SQL

<br><br>

Error in JSPM<br><br>

Details message(s): Messages for component sap.com/SAPPCUI_GP: Deployment of archive
<hostname>\sapmnt\trans\EPS\in\SAPPCUIGP07P_1-20002356.SCA for component sap.com/SAPPCUI_GP aborted Detailed message: 1. Already deployed component has version:1000.603.0.7.1.20101210090058 2. Item is skipped because of failed deployment of item 'sap.com_pcui_gp_{xssfpm' and because the applied error strategy is OnErrorStop 3. Contains Aborted deployment component: sap.com_srm}superp Deployment of archive
<hostname>\sapmnt\trans\EPS\in\SAPPCUIGP07P_1-20002356.SCA --> srm_{superp.sda for component sap.com/srm}superp aborted Detailed message: 1. ASJ.dpl_ds.006193 Operation [deploy] of [C:\usr\sap\<SID>\J01\j2ee\cluster\server0\.\temp\tc_bldeploy_controller\archives\113\SAPPCUIGP07P_1-20002356_SCA1292830999973\DEPLOYARCHIVES\srm_{superp.sda] failed -> Exception while [validating application sap.com/srm}superp. 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, voice_container, Content Container, dbcontentcontainer, ecm_content_handler, src.zip_handler, scheduler_{container, 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, com.sap.security.login-modules, webservices_container, EJBContainer, dbschemacontainer, MDRContainer, com.sap.security.policy-configurations, SAP-EU-GP, app_libraries_container]. 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/srm}superp to point you to the containers that need to be available and started on the system for successful deployment.]. Deployment of archive
<hostname>\sapmnt\trans\EPS\in\SAPPCUIGP07P_1-20002356.SCA --> pcui_gp_{tracking.sda for component sap.com/pcui_gp}tracking aborted Detailed message: 1. ASJ.dpl_ds.006193 Operation [deploy] of [C:\usr\sap\<SID>\J01\j2ee\cluster\server0\.\temp\tc_bldeploy_controller\archives\113\SAPPCUIGP07P_1-20002356_SCA1292830999973\DEPLOYARCHIVES\pcui_gp_{tracking.sda] failed -> Exception while [validating application sap.com/pcui_gp}tracking. 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, voice_container, Content Container, dbcontentcontainer, ecm_content_handler, src.zip_handler, scheduler_{container, 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, com.sap.security.login-modules, webservices_container, EJBContainer, dbschemacontainer, MDRContainer, com.sap.security.policy-configurations, SAP-EU-GP, app_libraries_container]. 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/pcui_gp}tracking to point you to the containers that need to be available and started on the system for successful deployment.]. Deployment of archive
<hostname>\sapmnt\trans\EPS\in\SAPPCUIGP07P_1-20002356.SCA --> pcui_gp_{xssfpm.sda for component sap.com/pcui_gp}xssfpm aborted Detailed message: 1. ASJ.dpl_ds.006193 Operation [deploy] of [C:\usr\sap\<SID>\J01\j2ee\cluster\server0\.\temp\tc_bldeploy_controller\archives\113\SAPPCUIGP07P_1-20002356_SCA1292830999973\DEPLOYARCHIVES\pcui_gp_{xssfpm.sda] failed -> Exception while [validating application sap.com/pcui_gp}xssfpm. 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, voice_container, Content Container, dbcontentcontainer, ecm_content_handler, src.zip_handler, scheduler_{container, 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, com.sap.security.login-modules, webservices_container, EJBContainer, dbschemacontainer, MDRContainer, com.sap.security.policy-configurations, SAP-EU-GP, app_libraries_container]. 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/pcui_gp}xssfpm to point you to the containers that need to be available and started on the system for successful deployment. CSN component for application is [CA-GTF-TS-XSS].]. Create an OSS message in component: CA-GTF-TS-XSS for support. Deployment of archive
<hostname>\sapmnt\trans\EPS\in\SAPPCUIGP07P_1-20002356.SCA --> pcui_gp_{xsscfg.sda for component sap.com/pcui_gp}xsscfg aborted Detailed message: 1. ASJ.dpl_ds.006193 Operation [deploy] of [C:\usr\sap\<SID>\J01\j2ee\cluster\server0\.\temp\tc_bldeploy_controller\archives\113\SAPPCUIGP07P_1-20002356_SCA1292830999973\DEPLOYARCHIVES\pcui_gp~xsscfg.sda] failed -> Exception during deploy: par files are no longer supported. Please use the migration tools for migrating your file. com.sap.portal.prt.sapj2ee.deployment.PortalDeploymentException: par files are no longer supported. Please use the migration tools for migrating your file. at com.sap.portal.prt.sapj2ee.PortalRuntimeContainer.deploy(PortalRuntimeContainer.java:244) at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.deploy(ContainerWrapper.java:309) at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:575) at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:282) at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:220) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:426) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:478) at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2016) at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:382) at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:328) at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:139) at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:138) at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57) at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:213) at com.sap.engine.services.dc.cm.deploy.impl.DeliverOnlineDeployProcessor.deploy(DeliverOnlineDeployProcessor.java:60) at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:282) at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84) at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:100) at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328) See Deploy Controller log C:\usr\sap\<SID>\J01\j2ee\JSPM\log\log_2010_12_17_11_34_06\deploy_api.0.log for details.

<br><br>

Please do share,

cheers.

[Former Member]

Hi Ramesh,

NWDI is the only way I know of, to undeploy packages in older releases of Netweaver... The other obvious way is to re-deploy/ over-write the packages using JSPM forced mode.

Rgds,

Soujanya

Edited by: Soujanya Holla on Dec 29, 2010 12:44 PM

[Former Member]

Hi Ramesh,

Since there is no option of SDM, undeployment will nto be possible. Forced deployment through JSPM will be the way out. Im well aware undeployment is possible through Developer Studio. You just need a Dev studio client and you can connect to your remote system.

Further on, to analyse the error, can you please paste the latest JSPM logs? Also, please let me know the version of your file you are trying to deploy. Since the logs says "Cannot deply due to wrong version", I just want to ensure if the file is compatible with 730 or not.

Rgds,

soujanya

[Former Member]

Hi,

For using developer studio i think NWDi has to be configured first. Is it?

Regards,

Tajinder

[Former Member]

Hi,

DI Usage type is not required. Just the java stack will do. The steps to undeploy any file using a Dev studio client is given here:

http://help.sap.com/saphelp_nw73/helpdata/en/4a/ef4fe6bb3d635ee10000000a421937/frameset.htm

Rgds,

Soujanya

[Former Member]

Hi Tajinder and Sounjanya,

<br><br>

Thanks for the reply;

<br><br>

Unfortunately, we dont have NWDI selected during the implementation, in another word we will not be able to proceed with the un-deployment using Developer Studio method. or you reckon we can still try to un-deploy using the Developer Studio (i doubt this will work since there's no NWDI?

<br><br>

The below component is pre-requiste before we install ESS and MSS component.

SAPPCUIGP07P_1-20002356.SCA - for SAP PCUI_GP 603 SP07 ( This is latest and most up-to-date since 28.12.2010 )

<br><br>

If we know another method of un-deployment than it will be great..

<br><br>

JSPM_MAIN log

<br><br>

Dec 29, 2010 10:23:40 AM [Info]: Deploying Java components...

Dec 29, 2010 10:23:40 AM [Info]: You can find additional information in log file C:\usr\sap\<SID>\J01\j2ee\JSPM\log\log_2010_12_29_10_14_14\DEPLOYMENT_RESULTS_01.LOG.

Dec 29, 2010 10:23:47 AM [Info]: Deployment of Java components finished.

Dec 29, 2010 10:23:47 AM [Info]: Deployment message for component SAPPCUI_GP : Deployment of archive
<hostname>\sapmnt\trans\EPS\in\SAPPCUIGP07P_1-20002356.SCA for component sap.com/SAPPCUI_GP aborted

Detailed message:

1. Already deployed component has version:1000.603.0.7.1.20101210090058

2. Item is skipped because of failed deployment of item 'sap.com_pcui_gp~tracking' and because the applied error strategy is OnErrorStop

3. Contains Aborted deployment component:

sap.com_srm~superp

Deployment of archive
<hostname>\sapmnt\trans\EPS\in\SAPPCUIGP07P_1-20002356.SCA --> srm_{superp.sda for component sap.com/srm}superp aborted

Detailed message:

1. ASJ.dpl_ds.006193 Operation [deploy] of [C:\usr\sap\<SID>\J01\j2ee\cluster\server0\.\temp\tc_bldeploy_controller\archives\122\SAPPCUIGP07P_1-20002356_SCA1293618221015\DEPLOYARCHIVES\srm~superp.sda] failed

-> Exception while [validating application sap.com/srm~superp.

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, voice_container, Content Container, dbcontentcontainer, ecm_content_handler, src.zip_handler, scheduler~container, 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, com.sap.security.login-modules, webservices_container, dbschemacontainer, EJBContainer, MDRContainer, com.sap.security.policy-configurations, 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/srm~superp to point you to

the containers that need to be available and started on the system for successful deployment.].

Deployment of archive
<hostname>\sapmnt\trans\EPS\in\SAPPCUIGP07P_1-20002356.SCA --> pcui_gp_{tracking.sda for component sap.com/pcui_gp}tracking aborted

Detailed message:

1. ASJ.dpl_ds.006193 Operation [deploy] of [C:\usr\sap\<SID>\J01\j2ee\cluster\server0\.\temp\tc_bldeploy_controller\archives\122\SAPPCUIGP07P_1-20002356_SCA1293618221015\DEPLOYARCHIVES\pcui_gp~tracking.sda] failed

-> Exception while [validating application sap.com/pcui_gp~tracking.

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, voice_container, Content Container, dbcontentcontainer, ecm_content_handler, src.zip_handler, scheduler~container, 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, com.sap.security.login-modules, webservices_container, dbschemacontainer, EJBContainer, MDRContainer, com.sap.security.policy-configurations, 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/pcui_gp~tracking to point you to

the containers that need to be available and started on the system for successful deployment.].

Deployment of archive
<hostname>\sapmnt\trans\EPS\in\SAPPCUIGP07P_1-20002356.SCA --> pcui_gp_{xssfpm.sda for component sap.com/pcui_gp}xssfpm aborted

Detailed message:

1. ASJ.dpl_ds.006193 Operation [deploy] of [C:\usr\sap\<SID>\J01\j2ee\cluster\server0\.\temp\tc_bldeploy_controller\archives\122\SAPPCUIGP07P_1-20002356_SCA1293618221015\DEPLOYARCHIVES\pcui_gp~xssfpm.sda] failed

-> Exception while [validating application sap.com/pcui_gp~xssfpm.

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, voice_container, Content Container, dbcontentcontainer, ecm_content_handler, src.zip_handler, scheduler~container, 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, com.sap.security.login-modules, webservices_container, dbschemacontainer, EJBContainer, MDRContainer, com.sap.security.policy-configurations, 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/pcui_gp~xssfpm to point you to

the containers that need to be available and started on the system for successful deployment.

CSN component for application is [CA-GTF-TS-XSS].].

Create an OSS message in component: CA-GTF-TS-XSS for support.

Deployment of archive
<hostname>\sapmnt\trans\EPS\in\SAPPCUIGP07P_1-20002356.SCA --> pcui_gp_{xsscfg.sda for component sap.com/pcui_gp}xsscfg aborted

Detailed message:

1. ASJ.dpl_ds.006193 Operation [deploy] of [C:\usr\sap\<SID>\J01\j2ee\cluster\server0\.\temp\tc_bldeploy_controller\archives\122\SAPPCUIGP07P_1-20002356_SCA1293618221015\DEPLOYARCHIVES\pcui_gp~xsscfg.sda] failed

-> Exception during deploy: par files are no longer supported. Please use the migration tools for migrating your file.

com.sap.portal.prt.sapj2ee.deployment.PortalDeploymentException: par files are no longer supported. Please use the migration tools for migrating your file.

at com.sap.portal.prt.sapj2ee.PortalRuntimeContainer.deploy(PortalRuntimeContainer.java:244)

at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.deploy(ContainerWrapper.java:309)

at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:575)

at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:282)

at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:220)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:426)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:478)

at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2016)

at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:382)

at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:328)

at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:139)

at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:138)

at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)

at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:213)

at com.sap.engine.services.dc.cm.deploy.impl.DeliverOnlineDeployProcessor.deploy(DeliverOnlineDeployProcessor.java:60)

at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:282)

at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)

at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:100)

at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)

at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

See Deploy Controller log C:\usr\sap\<SID>\J01\j2ee\JSPM\log\log_2010_12_29_10_14_14\deploy_api.0.log for details.

Dec 29, 2010 10:23:47 AM [Info]: Detecting components installed on the system...

Dec 29, 2010 10:23:47 AM [Info]: You can find additional information in log file C:\usr\sap\<SID>\J01\j2ee\JSPM\log\log_2010_12_29_10_14_14\DETECT_SYSTEM_COMPONENTS_02.LOG.

Dec 29, 2010 10:23:52 AM [Info]: Loaded usage type data from data source jdbc/pool/<SID>.

Dec 29, 2010 10:23:52 AM [Info]: Detected system products and usage types.

Dec 29, 2010 10:23:53 AM [Info]: Detected components installed on the system.

Dec 29, 2010 10:23:53 AM [Info]: Overal deployment message : Deployment error. See log C:\usr\sap\<SID>\J01\j2ee\JSPM\log\log_2010_12_29_10_14_14\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_srm~superp] failed

com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 Operation [deploy] of [sap.com_srm~superp] failed

com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] Operation [deploy] of [sap.com_srm~superp] failed

com.sap.engine.services.deploy.server.utils.DSRemoteException: ASJ.dpl_ds.006193 Operation [deploy] of [C:\usr\sap\<SID>\J01\j2ee\cluster\server0\.\temp\tc_bldeploy_controller\archives\122\SAPPCUIGP07P_1-20002356_SCA1293618221015\DEPLOYARCHIVES\srm~superp.sda] failed

com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception while [validating application sap.com/srm~superp.

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, voice_container, Content Container, dbcontentcontainer, ecm_content_handler, src.zip_handler, scheduler~container, 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, com.sap.security.login-modules, webservices_container, dbschemacontainer, EJBContainer, MDRContainer, com.sap.security.policy-configurations, 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/srm~superp to point you to

the containers that need to be available and started on the system for successful deployment.].

[Former Member]

Hi,

Netweaver 730 was released as a standalone product. No business Suite applications such as ERP, SCM,SRM etc etc are supported for NW 730. This is the reason why the error says "file no longer supported".

The latest file that you have taken from SMP is supported for NW 702 release. Maybe sometime during Feb or March, the Business Suite applications compatible with NW 730 will be released to the market. You can check this from some1 internally in SAP.

Rgds,

Soujanya

[Former Member]

Hi Soujanya,

Ok, thats could be real issue, due to Application such a ESS/MSS is not supported yet for NW7.3. We might need to wait till the newer version of component is being release next year. Im still interested how do you undeploy a component in NW7.3 since theres no SDM? only way is via NWDI > Developer Studio (is this something we need to note and you must install NWDI > Developer Studio in order to undeploy for NW7.3?

cheers,

[Former Member]

Hi,

The logs read :

SAPPCUIGP07P_1-20002356_SCA1292830999973\DEPLOYARCHIVES\pcui_gp~xsscfg.sda] failed -> Exception during deploy: par files are no longer supported. ..

AFAIK, NW 730 is supported on Windows 2008/SQL 2008 and above.

Win2003 with SQL 2000/2005 version is not supported for NW 730. Please check the 730 IMPL guide once.

Rgds,

Soujanya

[Former Member]

Hi Soujanya,

typo error, its actually running on MS SQL 2008 R2 / Windows Server 2008 Standard Edition.

Do you know how to un-deploy component on NetWeaver 7.3?

cheers,