on 09-23-2010 4:28 PM
Dear All,
I am facing a build error when setting up the application in NWDS.
The error:--
DC Model check:
All used DCs are available locally
ERROR: Check for used DCs failed: Used component not found: sap.com/crm/tc/core. DC not found in DC syncdb
Build failed with errors.
Basically the application is not able to find the standard component "sap.com/crm/tc/core" during build.
I am not able to locate the Software component in which this DC "sap.com/crm/tc/core" is present.
Contents of Repository info log file:--
Software Component SAP-SHRWEB
Version MAIN_CRM50VAL_C.20061207074907
Label 5.0 Level 7 Update CRM50VAL.12070749
System CRM-Development
Step Repository-import
Log G:\usr\sap\trans\EPS\in\CMShwun130DCR\CMS\log\CRM_D\DCR\CRM_D\DCR201007271513430991Repository-import.log
Info:Starting Step Repository-import at 2010-07-27 17:14:42.0225 +2:00
Info:Component:sap.com/TEALEAF
Info:Version :NIGHTLYBUILD-dev.20050614115400
Info:13. PR is of type TCSSoftwareComponent
Info:==> sources will not be imported for this SC
Info:Component:sap.com/STRUTS
Info:Version :NIGHTLYBUILD-dev.20060120135700
Info:12. PR is of type TCSSoftwareComponent
Info:==> sources will not be imported for this SC
Info:Component:sap.com/SAP_JTECHS
Info:Version :SAP AG.20070201154800
Info:11. PR is of type TCSSoftwareComponent
Info:==> sources will not be imported for this SC
Info:Component:sap.com/SAP_BUILDT
Info:Version :SAP AG.20070131224800
Info:10. PR is of type TCSSoftwareComponent
Info:==> sources will not be imported for this SC
Info:Component:sap.com/SAP-SHRWEB
Info:Version :MAIN_CRM50VAL_C.20061207074907
Info:9. PR is of type TCSSoftwareComponent
Info:propagatable is known in repository, it is not necessary to write the workspacecontent to the DTR
Info:OK : integrating of changelist 054dc33785c711dba0700030057116fe succeeded without conflicts.
Info:Component:sap.com/SAP-SHRJAV
Info:Version :MAIN_CRM50VAL_C.20061207073034
Info:8. PR is of type TCSSoftwareComponent
Warning:import not processed because the archive contains no sources
Info:Component:sap.com/SAP-SHRAPP
Info:Version :MAIN_CRM50VAL_C.20061207072706
Info:7. PR is of type TCSSoftwareComponent
Info:propagatable is known in repository, it is not necessary to write the workspacecontent to the DTR
Info:OK : integrating of changelist d2c104315f3211db9def0030057116fe succeeded without conflicts.
Info:Component:sap.com/SAP-JEE
Info:Version :SAP AG.20070201154700
Info:6. PR is of type TCSSoftwareComponent
Info:==> sources will not be imported for this SC
Info:Component:sap.com/SAP-IPCMSA
Info:Version :MAIN_CRM50VAL_C.20061109083347
Info:5. PR is of type TCSSoftwareComponent
Info:==> sources will not be imported for this SC
Info:Component:sap.com/SAP-CRMWEB
Info:Version :MAIN_CRM50PAT_C.20070302132802
Info:4. PR is of type TCSSoftwareComponent
Info:propagatable is known in repository, it is not necessary to write the workspacecontent to the DTR
Info:OK : integrating of changelist d504a983a7a011dbaeb20030057116fe succeeded without conflicts.
Info:Component:sap.com/SAP-CRMJAV
Info:Version :MAIN_CRM50VAL_C.20061207072126
Info:3. PR is of type TCSSoftwareComponent
Info:==> sources will not be imported for this SC
Info:Component:sap.com/SAP-CRMDIC
Info:Version :MAIN_CRM50VAL_C.20061109083343
Info:2. PR is of type TCSSoftwareComponent
Info:propagatable is known in repository, it is not necessary to write the workspacecontent to the DTR
Info:OK : integrating of changelist ef25f5325f3111db9d900030057116fe succeeded without conflicts.
Info:Component:sap.com/SAP-CRMAPP
Info:Version :MAIN_CRM50VAL_C.20061207071924
Info:1. PR is of type TCSSoftwareComponent
Info:propagatable is known in repository, it is not necessary to write the workspacecontent to the DTR
Info:OK : integrating of changelist 40c857da85c311dbab450030057116fe succeeded without conflicts.
Info:Step Repository-import ended with result 'success' at 2010-07-27 17:14:42.0569 +2:00
-
Contents of CBS-make log file:--
Info:Starting Step CBS-make at 2010-07-27 17:14:42.0584 +2:00
Info:wait until CBS queue of buildspace DCR_CRM_D is completely processed, before starting the import
Info:deploy archive G:\usr\sap\trans\EPS\in\CMShwun130DCR/CMS/extract/201007271514350897_sap.comSAP_JTECHSSAP AG~20070201154800/DEPLOYARCHIVES/AdobeSAPServerChallenge.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
Info:deploy archive G:\usr\sap\trans\EPS\in\CMShwun130DCR/CMS/extract/201007271514350897_sap.comSAP_JTECHSSAP AG~20070201154800/DEPLOYARCHIVES/ArchivingConnector.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
Info:deploy archive G:\usr\sap\trans\EPS\in\CMShwun130DCR/CMS/extract/201007271514350897_sap.comSAP_JTECHSSAP AG~20070201154800/DEPLOYARCHIVES/ArchivingConnectorInit.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
Info:deploy archive G:\usr\sap\trans\EPS\in\CMShwun130DCR/CMS/extract/201007271514350897_sap.comSAP_JTECHSSAP AG~20070201154800/DEPLOYARCHIVES/ArchivingConnectorSchema.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
Info:deploy archive G:\usr\sap\trans\EPS\in\CMShwun130DCR/CMS/extract/201007271514350897_sap.comSAP_JTECHSSAP AG~20070201154800/DEPLOYARCHIVES/CMSclient.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
Info:deploy archive G:\usr\sap\trans\EPS\in\CMShwun130DCR/CMS/extract/201007271514350897_sap.comSAP_JTECHSSAP AG~20070201154800/DEPLOYARCHIVES/CMSutil.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
Info:deploy archive G:\usr\sap\trans\EPS\in\CMShwun130DCR/CMS/extract/201007271514350897_sap.comSAP_JTECHSSAP AG~20070201154800/DEPLOYARCHIVES/J2EEDocs.ear is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
Info:deploy archive G:\usr\sap\trans\EPS\in\CMShwun130DCR/CMS/extract/201007271514350897_sap.comSAP_JTECHSSAP AG~20070201154800/DEPLOYARCHIVES/MISync.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
Info:deploy archive G:\usr\sap\trans\EPS\in\CMShwun130DCR/CMS/extract/201007271514350897_sap.comSAP_JTECHSSAP AG~20070201154800/DEPLOYARCHIVES/Modeler.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
Info:deploy archive G:\usr\sap\trans\EPS\in\CMShwun130DCR/CMS/extract/201007271514350897_sap.comSAP_JTECHSSAP AG~20070201154800/DEPLOYARCHIVES/SAPJ2eeCcmsCustomizing.ear is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
Info:deploy archive G:\usr\sap\trans\EPS\in\CMShwun130DCR/CMS/extract/201007271514350897_sap.comSAP_JTECHSSAP AG~20070201154800/DEPLOYARCHIVES/SDMClient.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
Info:deploy archive G:\usr\sap\trans\EPS\in\CMShwun130DCR/CMS/extract/201007271514350897_sap.comSAP_JTECHSSAP AG~20070201154800/DEPLOYARCHIVES/SDMutil.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
Info:deploy archive G:\usr\sap\trans\EPS\in\CMShwun130DCR/CMS/extract/201007271514350897_sap.comSAP_JTECHSSAP AG~20070201154800/DEPLOYARCHIVES/SQLTrace.ear is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
Info:deploy archive G:\usr\sap\trans\EPS\in\CMShwun130DCR/CMS/extract/201007271514350897_sap.comSAP_JTECHSSAP AG~20070201154800/DEPLOYARCHIVES/SystemInfo.ear is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
Info:deploy archive G:\usr\sap\trans\EPS\in\CMShwun130DCR/CMS/extract/201007271514350897_sap.comSAP_JTECHSSAP AG~20070201154800/DEPLOYARCHIVES/TestSuiteUUIE.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
Info:deploy archive G:\usr\sap\trans\EPS\in\CMShwun130DCR/CMS/extract/201007271514350897_sap.comSAP_JTECHSSAP AG~20070201154800/DEPLOYARCHIVES/WebDynproCoreComponents.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
Info:deploy archive G:\usr\sap\trans\EPS\in\CMShwun130DCR/CMS/extract/201007271514350897_sap.comSAP_JTECHSSAP AG~20070201154800/DEPLOYARCHIVES/WebDynproDispWda.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
Info:deploy archive G:\usr\sap\trans\EPS\in\CMShwun130DCR/CMS/extract/201007271514350897_sap.comSAP_JTECHSSAP AG~20070201154800/DEPLOYARCHIVES/WebDynproPdfObject.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
Info:deploy archive G:\usr\sap\trans\EPS\in\CMShwun130DCR/CMS/extract/201007271514350897_sap.comSAP_JTECHSSAP AG~20070201154800/DEPLOYARCHIVES/WebDynproTools.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
Info:deploy archive G:\usr\sap\trans\EPS\in\CMShwun130DCR/CMS/extract/201007271514350897_sap.comSAP_JTECHSSAP AG~20070201154800/DEPLOYARCHIVES/WebDynproWsLib.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
Info:deploy archive G:\usr\sap\trans\EPS\in\CMShwun130DCR/CMS/extract/201007271514350897_sap.comSAP_JTECHSSAP AG~20070201154800/DEPLOYARCHIVES/WebServicesAddOn.ear is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
Info:deploy archive G:\usr\sap\trans\EPS\in\CMShwun130DCR/CMS/extract/201007271514350897_sap.comSAP_JTECHSSAP AG~20070201154800/DEPLOYARCHIVES/XML_DAS.ear is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
Info:deploy archive G:\usr\sap\trans\EPS\in\CMShwun130DCR/CMS/extract/201007271514350897_sap.comSAP_JTECHSSAP AG~20070201154800/DEPLOYARCHIVES/aii_ibtranslationclient.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
Info:deploy archive G:\usr\sap\trans\EPS\in\CMShwun130DCR/CMS/extract/201007271514350897_sap.comSAP_JTECHSSAP AG~20070201154800/DEPLOYARCHIVES/aii_ibtransportclient.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
Info:deploy archive G:\usr\sap\trans\EPS\in\CMShwun130DCR/CMS/extract/201007271514350897_sap.comSAP_JTECHSSAP AG~20070201154800/DEPLOYARCHIVES/aii_proxy_rt.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
Info:deploy archive G:\usr\sap\trans\EPS\in\CMShwun130DCR/CMS/extract/201007271514350897_sap.comSAP_JTECHSSAP AG~20070201154800/DEPLOYARCHIVES/aii_util_misc.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
Info:deploy archive G:\usr\sap\trans\EPS\in\CMShwun130DCR/CMS/extract/201007271514350897_sap.com~SAP_JTECHS
Info:no changes on the CBS request queue (DCR_CRM_D) after a waiting time of 14430000 ms
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
Fatal:Please look after the operational status of the CBS.
Fatal:communication error: The request queue is not processed during the given time intervall. Please look after the operational status of the CBS.
Info:Step CBS-make ended with result 'fatal error' ,stopping execution at 2010-07-27 21:16:37.0095 +2:00
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
G:\usr\sap\trans\EPS\in\CMShwun130DCR/CMS/extract/201007271514350897_sap.com~SAP_JTECHS Info:no changes on the CBS request queue (DCR_CRM_D) after a waiting time of 14430000 ms 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 Fatal:Please look after the operational status of the CBS. Fatal:communication error: The request queue is not processed during the given time intervall. Please look after the operational status of the CBS. Info:Step CBS-make ended with result 'fatal error' ,stopping execution at 2010-07-27 21:16:37.0095 +2:00
Can you please check this first?
http://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29%28CBS%29Q0010
Best Regards,
Ervin
Hi Disha
Please check the runtime system update properly or not in CMS. [Click here|http://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29%28CMS%29Q0001].
Once you import the track in the NWDS, try to click on track and do the sync activtiy. Try to find the used dc in the active tab and then check in the your DC >> used dc area.
Hope it will helps
Regards
Arun Jaiswal
Hi Ervin,
As per the error message Disha's is getting is import failed in CMS. This is might cause if the runtime system not updated properly.
If the Disha's not able to find used DC in software component, then need to verify to check the used dc and software component.
Hope it will helps.
Regards
Arun Jaiswal
Hi Arun,
I would rather say that the DCs are not imported into the buildspace (instead of using the word runtime system...).
This statement of yours has absolutely nothing to do with the situation:
Once you import the track in the NWDS, try to click on track and do the sync activtiy. Try to find the used dc in the active tab and then check in the your DC >> used dc area.
If the CMS import failed (and so the DCs are not available in the corresponding buildspace) then whatever you do on client side in your NWDS, it'll not help...
In Disha's case I'd rather check what is going on with CBS, so I'd suggest the evaluation of the link I sent above as well as the evaluation of the log files:
-...\j2ee\cluster\server<n>\log\services\tc.CBS.Service\cbs.<n>.log
-...\j2ee\cluster\server<n>\log\defaultTrace.<n>.trc
Best Regards,
Ervin
HI ,
Ervin is correct, the successful import of dcs after checkin is a must to do the development. It is very common that import of a dc fails because during import it unzips many files which takes a lot of time and space based on the dc.
During import if your server gets more requests ,it hangs and communication to CBS could not be established (it can be checked in cbs logs that it keeps on waiting.)
To resolve it : check the CBS input mode for corresponding track in cbs webUI, change it to open(if privileged) and restart the server instance. Now retry importing the dc. if import is successful and it shows number of dirty dcs as 0 ,you should reimport the track in nwds and create the project from dc/sync sources. the problem should not come now.
Regards
Deepak
I have checked the decelopment tab in CMS.
The components(eg sap.com_SAP-CRMDIC) are listed there with state as import failed and state import-check as
Not executed.
All the other components are in the same status as above.
What does this import failed here means?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
this is the problem. Until those SCs won't get imported into the buildspace, you'll face the syncing problem in your NWDS.
Now the question is why they are failing. To find this out please click on the line where you can see "import failed" and press the "Details..." button. A popup will come where you'll find 3 log files. Repositiory Import, CBS Make, and SDM Deployment. Depending on where the process failed, some of these will be grayed out, or in best case scenario all of then are active and selectable. Check them all and copy-paste here if you find in any of them errors.
(It is not a problem if the import-check was not executed)
Best Regards,
Ervin
Hi,
I believe you did not import the dependent software into the Development buildspace. You do this right after check-in phase in the CMS's transport studio. On the development tab you need to import the SCA files. Only after this makes sense to import the development configuration into the NWDS. Check in the CBS webui (buildspace view) how many imported DCs do you got. If 0, then it is no wonder there's nothing to be synced ("DC not found in DC syncdb").
Best Regards,
Ervin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
91 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.