Quantcast
Channel: SCN : Unanswered Discussions - SAP NetWeaver Development Infrastructure (NWDI)
Viewing all articles
Browse latest Browse all 562

SAP_ESS 633 import fails

$
0
0

Hi all.

 

I'm trying to create a TRACK into NWDI to add SAP_ESS SC and the Development import fails. We are on Portal 7.30 and SAP_ESS 633.

 

I've created the TRACK using the wizard (through NWA) and manually, both attempts failed. I've added SAP_ESS 633 to TRACK and imported the SCA for the SC dependencies defined in SLD and still fails. Then I've added the remaining dependencies from SAP note # 1457908, imported the SCAs and still fails.

 

When the import fails it restart the server, puts the build space on PRIVILEGED input mode and add INIT_COMPARTMENT request to CBS.

 

Reading the log for the failed activation request it shows errors:

"... does not exist [public-part: def] AS Build Plugin Dependency

[validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated"

for missing dependencies:

'sap.com/tc/bi/bp/webDynpro', 'sap.com/com.sap.aii.proxy.framework', 'sap.com/com.sap.mw.jco' and others.

It seems to me that SAP_ESS 633 its still using old version dependencies.

 

Seeing the build space information through CBS Web GUI shows 321 total DCs and 10 broken DCs.

 

More information:

Portal: 7.30 SP09

SC added to TRACK: SAP_ESS 633 SP0

Dependencies:

ECM-CORE         7.30 SP09

ENGFACADE      7.30 SP09

ENGINEAPI        7.30 SP09

EP_BUILDT         7.30 SP09

ESCONF_BUILDT             7.30 SP09

FRAMEWORK    7.30 SP09

J2EE-FRMW       7.30 SP09

MOIN_BUILDT  7.30 SP09

SAPPCUI_GP     7.30 SP09

SAP_BUILDT      7.30 SP09

SERVERCORE     7.30 SP09

WD-RUNTIME   7.30 SP09

WD-RUNTIME-EXT         7.30 SP09

 

Am I missing some SC dependency?

Have somebody an idea what could be happening?

 

Regards,

Gregory.


Viewing all articles
Browse latest Browse all 562

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>