cancel
Showing results for 
Search instead for 
Did you mean: 

No Resulting DCs for Deployment

Former Member
0 Kudos

Dear SDN,

I am developing a web dynpro DC which has a reference to the Public DC (Jar DC). An activity for this public DC has been created, build. It is then checked in, activated and released. The activation log didnt show any error

When the activity is under consolidation, following info comes up

20091224141450 Info   :Starting Step SDM-deployment-notification at 2009-12-24 14:14:50.0591 +5:00
20091224141450 Info   :Deployment is performed asynchronously.
20091224141450 Info   :Following DCs are marked for deployment (buildspace = EPD_AXCMS_C): 
20091224141450 Info   :
20091224141450 Info   :RequestId: 585
20091224141450 Info   :==> no resulting DCs for deployment
20091224141450 Info   :Follow-up requests: 
20091224141450 Info   :
20091224141450 Info   :
20091224141450 Info   :Step SDM-deployment-notification ended with result 'success' at 2009-12-24 14:14:50.0591 +5:00

Please advise...

Regards,

Ganesh N

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Ganesh,

Option 1: Clear the CBS cache and try conslidating the both external dc and webdynpro dc.

Option 2 : Create a new external dc and refer the external dc to the webdynpro dc and conslidate it.

Kindly try the above options.

regards

Priya

Answers (1)

Answers (1)

siarhei_pisarenka3
Active Contributor
0 Kudos

Hi Ganesh N

Check which types of Development Component are included in the activity. Not all DC types produce archives for deployment (EAR, SDA). For example, Web Module DC or EJB Module DC do not. It might be that the activity includes only such DC.

Check that CBS rebuilt all EAR or WebDynpro components dependent on the "Jar DC".

Check that the consolidation request consists some EAR or WebDynpro components. Only the components can be deployed.

BR, Siarhei