on 09-15-2009 6:36 AM
Hi
I am customizing the ess/us/addr application in ess component, when i sync the sources in the NWDI, it throws the following error with header message as Sync sources and used DCs completed with 1 error(s).
com.sap.tc.devconf.BuildException
at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1911)
at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:6004)
at com.sap.ide.eclipse.component.provider.actions.dc.DcCreateProjectAction.buildDCs(DcCreateProjectAction.java:1027)
at com.sap.ide.eclipse.component.provider.actions.dc.DcCreateProjectAction$1.execute(DcCreateProjectAction.java:299)
at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:71)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:85)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)
Caused by: java.lang.StackOverflowError
Caused by:
java.lang.StackOverflowError
Please give me the solution for this.
Thanks in advance.......
Regards Siva
Hi
I was copied below files in the dir usr\sap\trans\CMS\inbox
EPBUILDT09
ESS09P
PCUIGP009
SAPBUILDT09
SAPJEE09
SAPJTECHS09
but, only the below components are showing in the CMS for SAP_ESS
SAP_JTECHS
SAP_BUILDT
SAP_JEE
SAPPCUI_GP
i am not able to see the EP_BUILDT in the CMS and also in SLD -> Software components
Pls give solution for this
Thanks in advance
Regards
Siva
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Thanks a lot,
I deployed EP_BUILDT_sp7 in SDM, I was restarted the server, but the EP_BUILDT is not showing in SLD and also not in CMS
What is the problem?, I am using EP 7.0 with SP9
please give me the solution.
Thanks & Regards
Siva
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Is it necessary to import EP_BUILDT in CMS ?
I have imported the following dependency files in CMS SAP-JEE, SAP-BUILDT, SAP-JTECHS, PCUIGP007.
if it is necessary to import EP_BUILDT, could you tell me the functions of EP_BUILDT.
Regards
Siva
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Siva,
The broken DCs that you are getting in CBS is because of missing dependent DCs that are there in EP BUILDT compartment. GO to SLD, Select your SC, at the bottom section you will see feature to add prerequiste compartments, there you have to click and search for EPBUILDT and addit over there. You will bydefault see the other 3 compartments.
After adding this compartment you go to CMS, select the track which has this SC and click on UPdate CMS. Then it will be affected in CMS.
Gurmat
Hi
After the SAP_ESS are imported in CMS-development, when I am check in CBS it showing 140 broken dcs out of 165.
The below error is described in build log of sap.com/ess/us/addr dc
-
the following Error in the build log
[wdgen] [Info] Generating packages/com/sap/xss/hr/per/us/address/review/wdp/ResourceVcPerAddressUSReview_en.properties
[wdgen] [Info] Generating configuration/Applications/com.sap.xss.hr.per.us.address.Per_Address_US/Per_Address_US.xml
[wdgen] [Info] Generating portalapp.xml
[wdgen] [Info] Generating wd.xml
[wdgen] [Info] Generating application.xml
[wdgen] [Info] Generating application-j2ee-engine.xml
[wdgen] [Info] Generating PublicPartFileList.properties
[wdgen] [Info] Generating PublicPartFileList.xml
[wdgen] [Info] Generation finished (12 seconds)
[wdgen]
[timer] WebDynpro generator finished in finished in 12.078 seconds
[echo] Starting Java compiler
[javac] Compiling 114 source files to D:\usr\sap\<SYSID>\<INSTANCE>\cluster\server0\temp\CBS\15\.B\641\t\D8D49B3CBE437CC81B5BF89440FC70EA\classes
D:\usr\sap\<SYSID>\<INSTANCE>\j2ee\cluster\server0\temp\CBS\15\.B\641\t\D8D49B3CBE437CC81B5BF89440FC70EA\gwd\packages\com\sap\xss\hr\per\us\address\fc\FcPerAddressUS.java:30: cannot resolve symbol
symbol : class F4TextHelper
location: package helpers
import com.sap.xss.per.helpers.F4TextHelper;
^
D:\usr\sap\<SYSID>\<INSTANCE>\cluster\server0\temp\CBS\15\.B\641\t\D8D49B3CBE437CC81B5BF89440FC70EA\gwd\packages\com\sap\xss\hr\per\us\address\fc\FcPerAddressUS.java:360: cannot resolve symbol
symbol : variable F4TextHelper
location: class com.sap.xss.hr.per.us.address.fc.FcPerAddressUS
F4TextHelper.SetF4Values(wdThis.wdGetAPI(), wdContext.nodeF4_Values() );
^
Note: Some input files use or override a deprecated API.
Note: Recompile with -deprecation for details.
2 errors
Ant runtime 23.25 seconds
Ant build finished with ERRORS
Compile failed; see the compiler error output for details.
Error: Build stopped due to an error: Compile failed; see the compiler error output for details.
Build plugin finished at 2009-09-15 17:20:27 GMT+05:30
Total build plugin runtime: 25.891 seconds
Build finished with ERROR
-
SAP.COM/ESS/US/ADDR - used DCs are 1. ess/per - compiled without errors
2. pcui_gp/xssfpm - complied without errors
3. pcui_gp/xssutils - compiled without errors
but, in the sap.com/ess/us/add compartment-used DCs table, the imported column of the ess/per showing red mark, so it results in not imported.
kindly help me to solve this build errors.
Regards
Siva
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
To make the DCS working fine for the component SAP ESS , we need to ensure that the dependencies are imported to the track successfully and in CBS no broken DCs are shoeing for these dependencies. The required dependencies are as follows:
1.EP_BUILDT,
2.SAP-JEE,
3.SAP-BUILDT,
4.SAP-JTECHS
Please cross check broken DC for all those dependencies in CBS , if broken DC exists then re import the above dependencies one again to track.
Thanks
Susmita
Hi stefan
I am able to find the path of the broken dcs and also the dirty dcs.
kindly help me, how to deploy the SAP_ESS without build errors,
when i am import the SAP_ESS in CMS its result in import finished, After that i refer the CBS, the SAP_ESS is showing 140 broken dcs, how to solve this error
Regards
Siva
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
first we need to know whats wrong in the track. Go to the CBS, click on Buildspaces. Click on the buildspace with the broken DCs. You will see a new list. Select the compartment with the broken DCs. You will see a list below with the development components in this compartment. Select one which doesnt compile, check the used DCs and check their Build Protocol. Copy the build protocol in here (only the section with the error of course, otherwise it might get too long ) If theres no build protocol, copy the request protocol in here.
Thanks Stefan
In CBS ( component build service) it showing total DCs - 165 and Broken DCs - 140, but in CMS ( change management service) -> transport studio - > Development -> History it showing import finished.
please give me the solution, to import the Dcs without build errors (ie) without broken DCs
Regards
Siva
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
my license expired so I cant provide you with the exact navigation path:
Click on the compartment and look for the DC list, broken DCs should be marked with red lights. You can check each one of those. Most likely its the same missing componente for every DC. Check also for used DCs so you can identify the problem at the source. There should be a tab somewhere in the detail view. Hints are usually in the build log for the component.
Also: Can you check the Component Build Service for broken DCs? Maybe there are dependencies missing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Siva,
This seems to be your workspace issue, not the code issue. Please remove your track from studio, cleanup the workspace folder corresponding to this track and try reimporting the track and creating the DC again.
Gurmat
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.