Skip to Content
avatar image
Former Member

Broken Dependency (UMEADMIN) exists in standard UCES 6.35 Software Component

Hi Experts,

We have created a track for UCES 6.35 software component for doing the customizations.

When we add UCES 6.35 SC to the track and save the track, one of the dependency (UMEADMIN 7.00) is resulting into broken state because of

which the entire SC is sitting in broken state.

We even tried to create another track for UCES 6.35 and this time, we replaced the dependeny (UMEADMIN 7.00) release version with

(UMEADMIN 7.30) but still this dependency is resulting into broken state but the entire SC is not getting broken in this case.

Please suggest as why this dependency (UMEADMIN) is getting broken as soon as we add / attach the SC (UCES 6.35) to the track.

Landscape Details:

UCES - 6.35 deployed on Portal server 7.4 SP06

NWDI - 7.40 SP06

Any pointers will be highly appeciated.

BR,

Anurag

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    avatar image
    Former Member
    Dec 25, 2014 at 01:25 PM

    Hi Anurag,

    Can you please paste the log please.

    Thanks,

    Hamendra

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Hamendra,

      Thanks for the reply!!!

      The issue has been resolved now.

      There were inconsistencies in the Dependency Definitions for the Software Component (SC) which were resolved after synchronizing the Software Component Dependencies.

      BR,

      Anurag