cancel
Showing results for 
Search instead for 
Did you mean: 

NWDI Broken DCs in Consolidation Compartment

Former Member
0 Kudos

Hi Experts,

We are running CE 7.2 SP04.

We had moved the SCA to some old track (Track2) from current production track (Track1), thru track connections, and then enhanced the code in Track2.

All the custom DCs are Build successfully in NWDS and we Activated and released all Activities successfully, Even the central build during Activation is successful. After importing the Activities into Assembly and while trying to Assemble, we have issues.

The Assembly failed and the log is :

20140128090401 Info   :Starting Step Check-assembly at 2014-01-28 09:04:01.0421 -8:00

20140128090401 Info   :Checks for software component xxx.com,SC1 are performed now:

20140128090401 Info   :list of broken DCs:

20140128090401 Info   :test.com,mdm/cust/gangag/op/ui

20140128090401 Info   :test.com,mdm/cust/menu/ui

20140128090401 Fatal  :Nonempty list of broken DCs, stopping export now

20140128090405 Info   :list of problem DCs:

20140128090405 Info   :test.com,mdm/cust/gangag/op/ui

20140128090405 Info   :test.com,mdm/cust/menu/ui

20140128090405 Fatal  :Nonempty list of problem DCs, stopping export now

20140128090405 Info   :Checks for software component test.com,SC1 finished succesfully

20140128090405 Info   :Step Check-assembly ended with result 'fatal error' ,stopping execution at 2014-01-28 09:04:05.0664 -8:00

When checked the Build log, the Track2_D compartment is fine, but Track2_C compartment is showing the above 2 broken DCs. But they are build successfully in NWDS and Activation build also succeeded.

Is there any way to refresh only the above two broken DCs inTrack2_C compartment so that it copies the latest sources from Track2_D compartment.

Regards,

Ramesh.

Accepted Solutions (1)

Accepted Solutions (1)

shreyas_pandya
Contributor
0 Kudos

Hi Ramesh,

Check whether you see any pending activities under the CBS Web UI, "Pending activities" view of _C buildspace.

What i feel is, during "Import into Consolidation" step the Central build for your Cosolidation buildspace must have failed.

please understand the below steps and let me know if all the steps succeed without any failure.

  1. Check-in (From NWDS)
  2. Activation (From NWDS)
  3. Release (From NWDS)
  4. Import into Consolidation (from CMS Web UI)
  5. Assemble (from CMS Web UI)

To make the assembly successful, all the above steps must go successful.

You can also open and check the _C build-space state under CBS Web UI. Check if all the DC are showing green indicator or not.

Fix broken DCs if any, inside _C build-space. and then proceed further to perform Assembly operation.

Let us know about your results.

Regards,

Shreyas Pandya

Former Member
0 Kudos

Hi Shreyas,

Thanks for your inputs. All the steps you mentioned were successful till import into consolidation and only Assembly is getting failed. As I mentioned earlier, there were 2 broken DCs (Custom developed) in Track2_C and now the issue is what the build log (on Assembly fail) is showing errors (component controller reference etc..) are actually fine in Track2_D (DC build and activation are successful (no errors while build) in NWDS and even CBS is not showing any broken DCs), we can not fix the broken DCs from NWDS (Track2_D) and re-activate.

Another point to note is we have transfered the SC from other track into this current track (Track2) thru track connections and this Track2 is not a new track and it is in old state before we move the SC. When the SC is transported into it, it re-synced/updated the Track2_D but Track2_C is still referring to old source files and not updated (Our understanding was - moving the SC from one track to other will update all the existing sources in Target with new, but it did not happened in case of Tracke2_C).

Now the question is how to update Track2_C with the latest source code (DCs) from Track2_D in CBS ? to do this I believe both of them should be synchronized in DTR first. Is there any way that we can copy the latest DC sources or complete SC from Track2_D/Active to Track2_C/Active ?

Note : For one of the DCs reported broken above, there is no child DC existing in Track2_C in DTR itself, but it is there in Track2_D, how to copy the same to _C.

Regards,

Ramesh.


shreyas_pandya
Contributor
0 Kudos

Hi Ramesh,

When you say the Track 2 is in old state. Could you please explain what does it signify?

Does it mean that, the Track 2 is not updated with all the required build-time dependencies?

When I say build-time dependencies, it means all the build-archives that we define in SLD against the SC.

After defining the build-time dependencies in SLD,

Back in Transport Studio

Update CMS operation is carried out.

And then Development and Consolidation Tabs imported with the latest archives.

Anyway, please check the following in CBS Web UI.

for your new Track  please check the The Number of DCs (count of DC) present in both...

_D and _C

It must be same.

If it is not same, that means there's an obvious mismatch in your "DTR-Development workspace" and "DTR Consolidation workspace".

If you are very sure, that a DC is building successfully under _D but fails in _C then,

You have an option of checkin-out the whole DC of _D.

And then check-in the whole DCs again and then activate, release, import in Consolidation and Assmble.

To do so,

  1. Open your DTR perspective in NWDS.
  2. Navigate to the  "Development --> Inactive workspace"
  3. Under the DC folder expand your DC. Here you will see one folder named _comp.
  4. right click on this folder and chose the option "Edit Subtree"
  5. This will checkout the whole DC into an open activity into your NWDS. And then you can carry out the normal transport procedure till assembly.

Let me know about your findings.

Regards,

Shreyas Pandya

Former Member
0 Kudos

Hi Shreyas,

Perfect. Exactly this is what I am looking for. Following the above steps I can move the entire DC from _Dev to _Cons and it resolved the broken DC issue.

Awarding points.

Regards,

Ramesh.

Answers (1)

Answers (1)

Stefan-EA
Contributor
0 Kudos

Ramesh Kotagiri wrote:

When checked the Build log, the Track2_D compartment is fine, but Track2_C compartment is showing the above 2 broken DCs. But they are build successfully in NWDS and Activation build also succeeded.

Please validate that all the build plugins were imported into CONS of track 2.