Changing CBS URL in results in Broken DCs?

[prasanstar1986]

Hi All Gurus ,

I tried to import a track from NWDI.

I got the error as

1. com.sap.tc.devconf.SyncException: Could not create mountpoint for SC in compartment sap.com_CUSTCRMPRJ_1: Checking existence failed for /dtr/ws/XXI04D60/sap.com_CUSTXXX/dev/inactive/SCs/sap.com/CUSTXXX/_comp/TopLevelDCs/(Communication error [cause: Unable to open connection to host "vas123:50100". The IP address of the host could not be resolved. Maybe the URL is misspelled or the host does no longer exist..])
Checking the track details the CBS was mentioned as http://vas123:50100 and the dtr as http://vas123.det.xxx.net:50100/dtr

We changed the CBS URL to http://vas123.det.xxx.net:50100 and there are 3 option SAVE , SAVE and RESTORE, SAVE and REIMPORT.

We click SAVE.

After we found that all the DCs inside the track are broken .

Checked the details of the broken DC in CBS  , I am getting

"xxx.com/ecs/dd/dc/ivdelord" (variant "default") is being marked as BROKEN. USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED

And in the Request Log , we could see that 

INVALID DEPENDENCIES: The following dependencies of the DCs in this request are being marked as invalid as they refer to non-existent public parts.

[validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED

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

there are more than 4 SCs and we each Sc has more than 15 Dcs.

All the DCs are broken and the ITs highlighting MetaData and Used DC error in DC error Details.

Could you all guide me on how to solve this . 

I need to restore it at the earliest.

Thanks in Advance ,

Prasanna Kumar.S

[ErvinSzolke]

Hello Prasanna,

"xxx.com/ecs/dd/dc/ivdelord" (variant "default") is being marked as BROKEN. USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED

This simply means that the dependent SCs are not imported (here I mean the SCs you defined as build-time dependencies of ESS).

All you need to do (assuming this ESS track has been properly constructed) is that you check-in the SCs and then import the SCs which are sitting in the import queue of Development with status "Waiting for import". You do this is CMS webui -- Transport Studio -- Development tab (and Check-in tab if you haven't checked in the SCs yet).

Read also about this error on our TSG:

http://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29Home  --> CBS reports a broken DC

(direct link to the Error "USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED" : http://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29%28CBS%29Q0033)

I hope this helps.

Best Regards,

Ervin

[prasanstar1986]

Hi Ervin,

Thanks for your reply .

These are not ESS components ,

They all are custom developed components .

As mentioned when we try to change the CBS URL it promted for three options

SAVE , SAVE and RESTORE, SAVE and REIMPORT.

We click SAVE.

Its after that the All the DCs got broken .

If we change it to the original value as http://vas123:50100 and SAVE will the Broken DCs get restored ?

[ErvinSzolke]

Hi,

yes, sorry I have overseen, you are right, the vendor is xxx.com and not sap.com and the dc I have mixed is ecs and not ess. I wasn't precise enough when reading the description.

Anyway, it doesn't change on the fact what I wrote it still applies to the broken dc problem.

Can you please simply reimport all the software into the Development? After SAVE the track configuration will change, and so it will differ from the data stored in the buildspaces (this is why you face the error).

To mention another example we often face at customers that they change the nwdi communication user's pass, and then forget to reimport into the buildspaces (which also stores the logon credentials of the communication user), and so this user sooner or later gets locked since at import an authentication is made and after 3 attempts cbs locks the user.

This is why if you change the URL back then it suddenly matches again to the data stored in the buildspaces.

What I recommend is to simply reimport all the SCs into the Development as well as Consolidation buildspaces. Let me know if after a succesful import you face any broken DCs.

Thank you and Best Regards,

Ervin

[prasanstar1986]

Hi Ervin,

What you say is what ever compenents which are listed in Check-in tab of Transport Studio has to be imported to Development tab for that track will sort out this ?

Adding another question what would happen to the Open Activities of the DCs which we are working on. ?

I still not clear what I have done to the CBS for that track .

To carify myself , After changing it to the new CBS URL and cliking SAVE , have I created new Buildspace for the track and with no DC imported from the Old CBS URL? Is that correct?

Should I have click SAVE and REIMPORT option?

Regards,

Prasanna

[ErvinSzolke]

Hi,

I mean all the SCs that you can see on the Track Configuration. I rather say this way, because the Check-in tab is listing all releases of the given SC. Example: if your track uses 700 SAP_BUILDT but in the cms inbox you also have the 730 version of it, then it is also available on the Check-in table, so rather use the Landscape Config's Track Data tab, and check what SC dependencies are assigned to your custom SC. Or use SLD from where actually all this data origins.

Regarding activities, please do as follows. Close all the activities, and change the URL afterwards and do the reimport only then.

I am also wondering what happens if you enhance the corresponding hosts file, and then try to import again using the URL "vas123:50100".

Regards,

Ervin

[prasanstar1986]

Hello Ervin,

Before I start doing the changes let me summarise what should I do :

1. Import All the SC listed in the Landscape configurator tab for that track and how do I it from the Landscape configurator.
2. Delete all open activities in NWDS.

I am not able to understand the point, " enhance the corresponding hosts file, and then try to import again using the URL "vas123:50100".

Will changing the CBS URL to "vas123:50100" track would work ?.

Please do let me know if anyother things has to be done .

Thanks Ervin for sparing your time to guide me .

[ErvinSzolke]

Hi,

1. you cannot do the import from the landscape configurator, use it only to look up which SCs to use, and check-in only the SCs which have the release and SP you intend to develop for. Of course you do the import in the transport studio of CMS (on tabs development and consolidation).

2. I meant to close the activities, not to delete them. those you don't require can be reverted, those you require can be checked in and activated.

Regarding the hosts file: on windows it is under %windir%\system32\drivers\etc folder, on unix it is under the /etc folder. This ensures IP, FQDN and hostname resolution.

I meant to change back the URL to the one that was working, else activation (that also triggers build) will fail due to the broken DCs.

Best Regards,

Ervin

[prasanstar1986]

Hi Ervin,

The SCs has only SAP-JEE,SAP_BUILDT,SAP_JTECHS with version 7.00.

So if I transport from CMS transport studion Check-in tab to Development and Consolidation tab with the same version , the broken DCs will get resolved?

Also I dont find any option to move from CMS Check-in tab in transport studio.

Kindly let me know on how to move it to development and consilidation.

[ErvinSzolke]

Hi,

from the check-in tab you cannot make the entries disappear. Therefore I would not use the word "move" here. If you select an entry and press "Check-in" then after a succesful check-in, that SC will show up on Development tab. If you do there an "Import" (and this case the SC will disappear from the list) then the SC will show up on Cons and you can also trigger there the import.

Regards,

Ervin