What causes the Solaris StarTeam Client error: "../sfw/bin/zsh: File name too long /opt/StarTeamCP_2008R2/bin/StarTeamCP: cannot shift"

0 Likes

Problem:

What causes the Solaris StarTeam Client error: "../sfw/bin/zsh: File name too long /opt/StarTeamCP_2008R2/bin/StarTeamCP: cannot shift"

Resolution:


  • Product Name: StarTeam
  • Product Version: 2008R2
  • Product Component: Client
  • Platform/OS Version: Solaris

This error occurs when the StarTeamCP.lax file has been edited incorrectly to reflect a new java install location. The StarTeamCP.lax file is located in the StarTeam binary directory "/opt/StarTeamCP_2008R2/bin/"

An example of the full error is shown below

27248 Nov 13 2006 zcat -rwxr-xr-x 1 root other
69216 Dec 15 2004 zenity -r-xr-xr-x 1 root bin
77376 Jan 23 2005 zip -r-xr-xr-x 1 root bin
27016 Jan 23 2005 zipcloak -r-xr-xr-x 2 root bin
177328 Oct 26 2006 zipinfo -r-xr-xr-x 1 root bin
30972 Jan 23 2005 zipnote -r-xr-xr-x 1 root bin
33460 Jan 23 2005 zipsplit lrwxrwxrwx 1 root root
19 Nov 27 2007 zonename -> ../../sbin/zonename lrwxrwxrwx 1 root root
14 Nov 27 2007 zsh -> ../sfw/bin/zsh: File name too long /opt/StarTeamCP_2008R2/bin/StarTeamCP: cannot shift

The error is caused by an incomplete path to the java executable, for example, the following value is incorrect:

lax.nl.current.vm=/opt/Borland/java/jre1.6.0_02/bin/

The full path to the java executable must be specified, similar to the example below:

lax.nl.current.vm=/opt/Borland/java/jre1.6.0_02/bin/java

Correct the "lax.nl.current.vm" entry to refer to the java executable as above, save the file and attempt to start StarTeam. The client should now load.

If you continue to experience issues please log a support case.


Old KB# 30331
Comment List
Related
Recommended