It's all about the answers!

Ask a question

Running scmtools on a build machine


Ryan Kersh (736) | asked Sep 11 '12, 5:48 p.m.
 Ideally, there would be a standalone command line client installer (as asked for in Enhancement 174453), but that doesn't exist yet.  What I've done is zipped up the files from under
C:\Program Files\IBM\Rational Team Concert Client for Microsoft Visual Studio IDE\3rd Party
on my workstation (a WinXP machine where Visual Studio is installed) and copied them over to a build server (a Win2k3 x86-64 machine where Visual Studio is not installed) under
C:\bin\RTC
I've also updated the scm.ini file to point to the included JRE.

With this setup, I'm able to login and create a workspace.  So far, so good.  However, when I attempt to load a workspace I'm running into the following exception (copied from .metadata\.log file):

!SESSION 2012-09-11 11:57:59.874 -----------------------------------------------
eclipse.buildId=unknown
java.fullversion=J2RE 1.5.0 IBM J9 2.3 Windows Server 2003 x86-32 j9vmwi3223ifx-20100511 (JIT enabled)
J9VM - 20100509_57823_lHdSMr
JIT  - 20091016_1845ifx7_r8
GC   - 20091026_AA
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments:  load -r pilot IPFAWorkspace IA
Command-line arguments:  -os win32 -ws win32 -arch x86 -data @noDefault load -r pilot IPFAWorkspace IA
!ENTRY org.eclipse.osgi 2 1 2012-09-11 11:58:00.780
!MESSAGE NLS missing message: PendingChangesUtil_36 in: com.ibm.team.filesystem.cli.client.internal.messages
!ENTRY org.eclipse.osgi 4 0 2012-09-11 11:58:06.077
!MESSAGE Application error
!STACK 1
java.lang.IllegalArgumentException
at com.ibm.team.filesystem.cli.core.util.RepoUtil$SelectorException.<init>(RepoUtil.java:1599)
at com.ibm.team.filesystem.cli.core.util.RepoUtil$UnmatchedSelectorException.<init>(RepoUtil.java:1665)
at com.ibm.team.filesystem.cli.core.util.RepoUtil.findNamedComponent(RepoUtil.java:1829)
at com.ibm.team.filesystem.cli.client.internal.subcommands.LoadCmd.configureLoadOp(LoadCmd.java:409)
at com.ibm.team.filesystem.cli.client.internal.subcommands.LoadCmd.run(LoadCmd.java:206)
at com.ibm.team.filesystem.cli.client.internal.subcommands.LoadCmdLauncher.run(LoadCmdLauncher.java:193)
at com.ibm.team.filesystem.cli.core.internal.SubcommandLauncher.run(SubcommandLauncher.java:651)
at com.ibm.team.filesystem.cli.core.internal.SubcommandLauncher.doStart(SubcommandLauncher.java:398)
at com.ibm.team.filesystem.cli.core.internal.SubcommandLauncher.run(SubcommandLauncher.java:175)
at com.ibm.team.filesystem.cli.core.internal.Application.start(Application.java:39)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
!ENTRY org.eclipse.osgi 2 0 2012-09-11 11:58:06.108
!MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-09-11 11:58:06.108
!MESSAGE Bundle org.eclipse.core.filesystem.aix.ppc64_1.0.1.R35x_v201000319-0930 [167] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-09-11 11:58:06.108
!MESSAGE Bundle org.eclipse.core.filesystem.aix.ppc_1.0.1.R35x_v201000319-0930 [168] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-09-11 11:58:06.108
!MESSAGE Bundle org.eclipse.core.filesystem.win32.ia64_1.1.201.v20100520-0800 [171] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-09-11 11:58:06.108
!MESSAGE Bundle org.eclipse.core.filesystem.win32.x86_64_1.1.100.R35x_v20100928-0452 [175] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-09-11 11:58:06.108
!MESSAGE Bundle org.eclipse.core.filesystem.zos.s390x_3.0.1.v20110623_0150 [176] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-09-11 11:58:06.108
!MESSAGE Bundle org.eclipse.core.filesystem.zos.s390_3.0.1.v20110623_0150 [177] was not resolved.
I've tried with both scm.exe and lscm.bat.  Any suggestions?  Shouldn't this work?  Am I stuck with having to install the full RTC client with GUI (which requires having Visual Studio installed)?

Thanks in advance!

Accepted answer


permanent link
Spencer Murata (2.3k115870) | answered Sep 12 '12, 11:33 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
 The command is formatted correctly, its just not able to find the component IA that you specified.  It could be permissions with the connecting user.  Also make sure that the the connection is connecting the repository you think it should be connecting to.

~Spencer
Ryan Kersh selected this answer as the correct answer

Comments
Ryan Kersh commented Sep 12 '12, 11:53 a.m.

If it's true that the reason this is failing is because the "IA" component can't be found, then this would be a bug, wouldn't it? The error message is horrible to say the least.... How would I go about diagnosing the permissions issue?


Ryan Kersh commented Sep 12 '12, 5:13 p.m.

This did indeed turn out to be a permissions issue. Thanks!

Is it worth following through with a bug report? It seems like the command line client should report a nice error message that says something like: "You don't have permissions to access this component."


Ryan Kersh commented Sep 13 '12, 12:33 p.m.

I went ahead and filed a defect for this. It looks like this has been fixed in 4.0 and there are no plans to back port the fix to 3.x. See RTC defect 231344 (http://goo.gl/tm41W).

2 other answers



permanent link
Shashikant Padur (3.9k27) | answered Sep 12 '12, 12:11 a.m.
JAZZ DEVELOPER
I believe you are using 3.x. Starting 4.0 we have a separate download for scm cli.
What is the error you are seeing on the command line? Is it the same exception as in the log? The exception indicates that the comoponent 'IA' could not be found  ( load -r pilot IPFAWorkspace IA)

Comments
Ryan Kersh commented Sep 12 '12, 11:24 a.m.

See my response (posted as a separate "answer" below). It didn't seem to fit in this space.


permanent link
Ryan Kersh (736) | answered Sep 12 '12, 11:24 a.m.
edited Sep 12 '12, 11:25 a.m.
That's correct, I'm using the 3.0.1.3 Visual Studio client.  Here's the error from the command line (it appears to be the same as the log):
C:\projects\IATrunk>c:\bin\RTC\scmtools\eclipse\scm.exe load -r pilot IPFAWorkspace IA
Unexpected exception
java.lang.IllegalArgumentException
        at com.ibm.team.filesystem.cli.core.util.RepoUtil$SelectorException.<init>(RepoUtil.java:1599)
        at com.ibm.team.filesystem.cli.core.util.RepoUtil$UnmatchedSelectorException.<init>(RepoUtil.java:1665)
        at com.ibm.team.filesystem.cli.core.util.RepoUtil.findNamedComponent(RepoUtil.java:1829)
        at com.ibm.team.filesystem.cli.client.internal.subcommands.LoadCmd.configureLoadOp(LoadCmd.java:409)
        at com.ibm.team.filesystem.cli.client.internal.subcommands.LoadCmd.run(LoadCmd.java:206)
        at com.ibm.team.filesystem.cli.client.internal.subcommands.LoadCmdLauncher.run(LoadCmdLauncher.java:193)
        at com.ibm.team.filesystem.cli.core.internal.SubcommandLauncher.run(SubcommandLauncher.java:651)
        at com.ibm.team.filesystem.cli.core.internal.SubcommandLauncher.doStart(SubcommandLauncher.java:398)
        at com.ibm.team.filesystem.cli.core.internal.SubcommandLauncher.run(SubcommandLauncher.java:175)
        at com.ibm.team.filesystem.cli.core.internal.Application.start(Application.java:39)
        at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:618)
        at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
        at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
        at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
Scm:
An error has occurred. See the log file
C:\projects\IATrunk\.metadata\.log.
This command worked on my workstation using a different user.  Is the method I used for deploying scmtools acceptable in general?  Could this be a permissions issue?

Thanks!

Your answer


Register or to post your answer.