can not create new tracks CBS-make error

[Former Member]

getting an error com.sap.tc.cbs.client.error.CommunicationException Have not set up a new track since august09

patched JDI from 701P4 to 701P5 in september

Applied support packs to ess system and need to build new tracks

when tring to set up new track for ess

checked in all sca files

sap.com_SAP-JEE 700P20,sap.com_SAP_JTECHS 700P20,sap.com_SAP_BUILDT 700p20,sap.com_SAP_BUILDT 700P20,sap.com_SAPPCUI_GP 603P5,sap.com_SAP_ESS 603p5,but when i go to import the sca files it runs for 3 hours and fails

in the cbs_make import failed,just trying 1 sca SAP_JEE,

from the log after 3 hours of waiting:

20091125181042 Info :Starting Step CBS-make at 2009-11-25 18:10:42.0801 -6:00

20091125181045 Info :wait until CBS queue of buildspace JDI_ZESS7P20_D is completely processed, before starting the import

20091125181045 Info :CBS queue of buildspace JDI_ZESS7P20_D is completely processed. Starting the import now.

20091125181131 Info :deploy archive /usr/sap/trans/JTrans/CMS/extract/200911260010360533_sap.com_SAP-JEESAP AG~20091021135454/DEPLOYARCHIVES/add_ejb.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'

20091125181131 Info :deploy archive /usr/sap/trans/JTrans/CMS/extract/200911260010360533_sap.com_SAP-JEESAP AG~20091021135454/DEPLOYARCHIVES/com.sap.security.core.ume.service.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'

20091125181131 Info :deploy archive /usr/sap/trans/JTrans/CMS/extract/200911260010360533_sap.com_SAP-JEESAP AG~20091021135454/DEPLOYARCHIVES/dsr.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'

20091125181131 Info :deploy archive /usr/sap/trans/JTrans/CMS/extract/200911260010360533_sap.com_SAP-JEESAP AG~20091021135454/DEPLOYARCHIVES/dsr_ejbcontext_api.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'

20091125181131 Info :deploy archive /usr/sap/trans/JTrans/CMS/extract/200911260010360533_sap.com_SAP-JEESAP AG~20091021135454/DEPLOYARCHIVES/httptunneling.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'

20091125181131 Info :deploy archive /usr/sap/trans/JTrans/CMS/extract/200911260010360533_sap.com_SAP-JEESAP AG~20091021135454/DEPLOYARCHIVES/javamail.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'

20091125181131 Info :deploy archive /usr/sap/trans/JTrans/CMS/extract/200911260010360533_sap.com_SAP-JEESAP AG~20091021135454/DEPLOYARCHIVES/jms_provider.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'

20091125181131 Info :deploy archive /usr/sap/trans/JTrans/CMS/extract/200911260010360533_sap.com_SAP-JEESAP AG~20091021135454/DEPLOYARCHIVES/ormapping_api.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'

20091125181131 Info :deploy archive /usr/sap/trans/JTrans/CMS/extract/200911260010360533_sap.com_SAP-JEESAP AG~20091021135454/DEPLOYARCHIVES/rfcengine.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'

20091125181131 Info :deploy archive /usr/sap/trans/JTrans/CMS/extract/200911260010360533_sap.com_SAP-JEESAP AG~20091021135454/DEPLOYARCHIVES/runtimeinfo.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'

20091125181131 Info :deploy archive /usr/sap/trans/JTrans/CMS/extract/200911260010360533_sap.com_SAP-JEESAP AG~20091021135454/DEPLOYARCHIVES/sapj2eenginedeploy.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'

20091125181131 Info :deploy archive /usr/sap/trans/JTrans/CMS/extract/200911260010360533_sap.com_SAP-JEESAP AG~20091021135454/DEPLOYARCHIVES/tc_sec_destinations_interfaces.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'

20091125181131 Info :deploy archive /usr/sap/trans/JTrans/CMS/extract/200911260010360533_sap.com_SAP-JEESAP AG~20091021135454/DEPLOYARCHIVES/tc_sec_destinations_service.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'

20091125181131 Info :deploy archive /usr/sap/trans/JTrans/CMS/extract/200911260010360533_sap.com_SAP-JEESAP AG~20091021135454/DEPLOYARCHIVES/tc_sec_saml_service.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'

20091125181131 Info :deploy archive /usr/sap/trans/JTrans/CMS/extract/200911260010360533_sap.com_SAP-JEESAP AG~20091021135454/DEPLOYARCHIVES/tc_sec_securestorage_service.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'

20091125181131 Info :deploy archive /usr/sap/trans/JTrans/CMS/extract/200911260010360533_sap.com_SAP-JEESAP AG~20091021135454/DEPLOYARCHIVES/tc_sec_vsi_interface.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'

20091125181131 Info :deploy archive /usr/sap/trans/JTrans/CMS/extract/200911260010360533_sap.com_SAP-JEESAP AG~20091021135454/DEPLOYARCHIVES/tc_sec_vsi_service.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'

20091125181131 Info :deploy archive /usr/sap/trans/JTrans/CMS/extract/200911260010360533_sap.com_SAP-JEESAP AG~20091021135454/DEPLOYARCHIVES/tc_sec_wssec_api.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'

20091125181131 Info :deploy archive /usr/sap/trans/JTrans/CMS/extract/200911260010360533_sap.com_SAP-JEESAP AG~20091021135454/DEPLOYARCHIVES/tc_sec_wssec_service.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'

20091125181131 Info :deploy archive /usr/sap/trans/JTrans/CMS/extract/200911260010360533_sap.com_SAP-JEESAP AG~20091021135454/DEPLOYARCHIVES/webservices.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'

20091125181131 Info :deploy archive /usr/sap/trans/JTrans/CMS/extract/200911260010360533_sap.com_SAP-JEESAP AG~20091021135454/DEPLOYARCHIVES/webservices_lib.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'

20091125181131 Info :=================================================================

20091125181131 Info :buildspace = JDI_ZESS7P20_D build request id = 1938

20091125181131 Info :wait until CBS queue of buildspace JDI_ZESS7P20_D is completely processed, before asking for build results

20091125181132 Info :waiting for CBS queue activity

20091125181202 Info :build process already running: waiting for another period of 30000 ms

20091125181232 Info :build process already running: waiting for another period of 30000 ms

20091125181302 Info :build process already running: waiting for another period of 30000 ms

20091125181332 Info :build process already running: waiting for another period of 30000 ms

20091125181402 Info :build process already running: waiting for another period of 30000 ms

......and on and on

20091125221204 Info :build process already running: waiting for another period of 30000 ms

20091125221234 Info :build process already running: waiting for another period of 30000 ms

20091125221304 Info :no changes on the CBS request queue (JDI_ZESS7P20_D) after a waiting time of 14430000 ms

20091125221304 Fatal :The request queue is not processed by the CBS during the given time intervall => the import failed because not every request including follow-up requests were processed

20091125221304 Fatal :Please look after the operational status of the CBS.

20091125221304 Info :Step CBS-make ended with result 'fatal error' ,stopping execution at 2009-11-25 22:13:04.0619 -6:00

Any ideas

Edited by: ken bearth on Dec 1, 2009 1:12 PM

Edited by: ken bearth on Dec 1, 2009 1:13 PM

Edited by: ken bearth on Dec 1, 2009 1:18 PM

Edited by: ken bearth on Dec 1, 2009 1:19 PM

Edited by: ken bearth on Dec 1, 2009 1:20 PM

Edited by: ken bearth on Dec 1, 2009 1:20 PM

Edited by: ken bearth on Dec 1, 2009 1:21 PM

Edited by: ken bearth on Dec 1, 2009 1:21 PM

Edited by: ken bearth on Dec 1, 2009 1:22 PM

Edited by: ken bearth on Dec 1, 2009 1:22 PM

[former_member389591 · Accepted solution]

I am having a similar problem (i.e. Info :build process already running: waiting for another period) repeated until timeout eventually fails when trying to import in to a new buildspace. What did you do to resolve your problem?

[former_member214355 · Accepted solution]

Hi

Is the CBS running?

1. In the CBS service properties, can you please check whether the

idlestart is set to false. CBS does not start processing requests until

idlestart is set to false.

2. Can you please log on to the CBS Web UI (Component Build service link

on top of the CMS UI page) and do a search for requests (requests tab

in the CBS UI) for the last week in the buildspace. Do check and let

me know whether there are any requests that are queued or failed. As

you see in the log attached the TCS cannot import the request because

queue is not empty and can be caused for any problem in previous

request.

Thanks

Kenny

[Former Member · Accepted solution]

Hi,

It looks the .SCA files does not contain the Soucrce Archives.

Regards

Kaushik Banerjee

[p330068]

Hi

Check the track domain data is correct or not.

Ans also check the SDM password stored in the Domain.

Thanks

Arun Jaiswal

[Former Member]

Hi,

Check the CBS Settings in Visual Admin.

Can you please write me the settings in

Visual Admin -> Server Instance -> Services -> Component Build Service ?

Regards

Kaushik Banerjee

[Former Member]

i was on patch ess 603 2-12 and was tring to go to ess 603 5-2 when having the problem

i ended up patching the J2ee to all the 701 sp5 one off patches and then first building the track to ess 603 4-12 and then rebuilding to ess 603 5-2

and then it worked

Edited by: ken bearth on Feb 15, 2010 5:33 AM