It's all about the answers!

Ask a question

How do I resolve JBE Issue with loading components - Unable to create Symbolic link error?


Chris Fagyal (462109) | asked Oct 03 '12, 4:54 p.m.
When I try to use the jazz build engine to load a bunch of components before sending it off to do a hudson build I get the following issue:

2012-10-03 15:43:13 [Jazz build engine] running on host: NCK-102500L
2012-10-03 15:43:13 [Jazz build engine] Should build occur?
2012-10-03 15:43:13 [Jazz build engine] Yes: Always build a user initiated request.
2012-10-03 15:43:13 [Jazz build engine] Invoking pre-build participant "com.ibm.team.build.jazzscm"
2012-10-03 15:43:14 [Jazz build engine] Accepting changes into workspace "GPSG_1000 Build Workspace" ...
2012-10-03 15:43:14 [Jazz build engine] Deleting fetch destination "/space/Builds" before fetching ...
2012-10-03 15:43:14 [Jazz build engine] Fetching files to fetch destination "/space/Builds" ...
com.ibm.team.build.internal.scm.SourceControlUtility$3: Status WARNING: com.ibm.team.filesystem.client code=0 There have been 2 problems running this operation null children=[Status WARNING: com.ibm.team.filesystem.client code=0 There were 4 errors.  After correcting the problems, it is recommended that components be reloaded.  The reload will be incremental, loading only the missing items.  You can further reduce the reload time by reloading just the projects out of sync. null children=[Status WARNING: com.ibm.team.filesystem.client code=0 Unable to create symbolic link /Common_UI/qt.conf to qt.conf.x86 because the underlying platform does not support symbolic links null Status WARNING: com.ibm.team.filesystem.client code=0 Unable to create symbolic link /Common_UI/Test/EventMessageTest/tcp.conf to /space/cp/target/X86/Startup/tcp.conf because the underlying platform does not support symbolic links null Status WARNING: com.ibm.team.filesystem.client code=0 Unable to create symbolic link /Common_UI/Test/EventMessageTest/dds.ini to /space/cp/target/X86/Startup/dds.ini because the underlying platform does not support symbolic links null Status WARNING: com.ibm.team.filesystem.client code=0 Unable to create symbolic link /Common_UI/Test/EventMessageTest/repo.ior to /space/cp/target/X86/Startup/repo.ior because the underlying platform does not support symbolic links null] Status WARNING: com.ibm.team.filesystem.client code=0 There were 6 errors.  After correcting the problems, it is recommended that components be reloaded.  The reload will be incremental, loading only the missing items.  You can further reduce the reload time by reloading just the projects out of sync. null children=[Status WARNING: com.ibm.team.filesystem.client code=0 Unable to create symbolic link /GPSG_Engine/libFlash_DB_Name.so to /space/cp/target/X86/engines/lib/libFlash_DB_Name.so because the underlying platform does not support symbolic links null Status WARNING: com.ibm.team.filesystem.client code=0 Unable to create symbolic link /GPSG_Engine/libRam_DB_Name.so to /space/cp/target/X86/engines/lib/libRam_DB_Name.so because the underlying platform does not support symbolic links null Status WARNING: com.ibm.team.filesystem.client code=0 Unable to create symbolic link /GPSG_Engine/src/Test/gtest-1.6.0/lib/libgtest.so to libgtest.so.0.0.0 because the underlying platform does not support symbolic links null Status WARNING: com.ibm.team.filesystem.client code=0 Unable to create symbolic link /GPSG_Engine/src/Test/gtest-1.6.0/lib/libgtest_main.so to libgtest_main.so.0.0.0 because the underlying platform does not support symbolic links null Status WARNING: com.ibm.team.filesystem.client code=0 Unable to create symbolic link /GPSG_Engine/src/Test/gtest-1.6.0/lib/libgtest.so.0 to libgtest.so.0.0.0 because the underlying platform does not support symbolic links null Status WARNING: com.ibm.team.filesystem.client code=0 Unable to create symbolic link /GPSG_Engine/src/Test/gtest-1.6.0/lib/libgtest_main.so.0 to libgtest_main.so.0.0.0 because the underlying platform does not support symbolic links null]]
    at com.ibm.team.build.internal.scm.SourceControlUtility.updateFileCopyArea(SourceControlUtility.java:685)
    at com.ibm.team.build.internal.engine.JazzScmPreBuildParticipant.preBuild(JazzScmPreBuildParticipant.java:238)
    at com.ibm.team.build.internal.engine.BuildLoop.invokePreBuildParticipants(BuildLoop.java:889)
    at com.ibm.team.build.internal.engine.BuildLoop$2.run(BuildLoop.java:693)
    at java.lang.Thread.run(Thread.java:662)
Contains : 0 There were 4 errors.  After correcting the problems, it is recommended that components be reloaded.  The reload will be incremental, loading only the missing items.  You can further reduce the reload time by reloading just the projects out of sync.
Contains : 0.0 Unable to create symbolic link /Common_UI/qt.conf to qt.conf.x86 because the underlying platform does not support symbolic links
Contains : 0.1 Unable to create symbolic link /Common_UI/Test/EventMessageTest/tcp.conf to /space/cp/target/X86/Startup/tcp.conf because the underlying platform does not support symbolic links
Contains : 0.2 Unable to create symbolic link /Common_UI/Test/EventMessageTest/dds.ini to /space/cp/target/X86/Startup/dds.ini because the underlying platform does not support symbolic links
Contains : 0.3 Unable to create symbolic link /Common_UI/Test/EventMessageTest/repo.ior to /space/cp/target/X86/Startup/repo.ior because the underlying platform does not support symbolic links
Contains : 1 There were 6 errors.  After correcting the problems, it is recommended that components be reloaded.  The reload will be incremental, loading only the missing items.  You can further reduce the reload time by reloading just the projects out of sync.
Contains : 1.0 Unable to create symbolic link /GPSG_Engine/libFlash_DB_Name.so to /space/cp/target/X86/engines/lib/libFlash_DB_Name.so because the underlying platform does not support symbolic links
Contains : 1.1 Unable to create symbolic link /GPSG_Engine/libRam_DB_Name.so to /space/cp/target/X86/engines/lib/libRam_DB_Name.so because the underlying platform does not support symbolic links
Contains : 1.2 Unable to create symbolic link /GPSG_Engine/src/Test/gtest-1.6.0/lib/libgtest.so to libgtest.so.0.0.0 because the underlying platform does not support symbolic links
Contains : 1.3 Unable to create symbolic link /GPSG_Engine/src/Test/gtest-1.6.0/lib/libgtest_main.so to libgtest_main.so.0.0.0 because the underlying platform does not support symbolic links
Contains : 1.4 Unable to create symbolic link /GPSG_Engine/src/Test/gtest-1.6.0/lib/libgtest.so.0 to libgtest.so.0.0.0 because the underlying platform does not support symbolic links
Contains : 1.5 Unable to create symbolic link /GPSG_Engine/src/Test/gtest-1.6.0/lib/libgtest_main.so.0 to libgtest_main.so.0.0.0 because the underlying platform does not support symbolic links


This is running on OpenSuse 11.4 64-bit using RTC 4.0 and the Jazz Build Toolkit version 4.0

2 answers



permanent link
Sudhakar Frederick (80113431) | answered Oct 03 '12, 11:01 p.m.
JAZZ DEVELOPER
Perhaps https://jazz.net/library/article/892 applies?

permanent link
Ahmed El-Madhoun (1) | answered Sep 05 '13, 10:15 p.m.
 Hi,

I am facing this on an Ubuntu 64-bit 12.0.4 LTS server edition. The workaround mentions installing the 32-bit client, do you mean the scm client? 

This does not resolve the issue. Can you please elaborate a bit more on the workaround?

Your answer


Register or to post your answer.