Troubleshooting Issues with Team Explorer Everywhere

Article
06/27/2011

If you encounter issues when you use Team Explorer Everywhere, this topic provides information about the most common of those issues and how to resolve them.

In this topic

Command-line client is not on the path

To easily use the Cross-platform Command-Line Client for Team Foundation Server, you must add the directory that contains the Cross-platform Command-Line Client for Team Foundation Server application to the execution path for your shell. The instructions below are specific to the operating system upon which you are using the Cross-platform Command-Line Client for Team Foundation Server.

Important

You must install the Cross-platform Command-Line Client for Team Foundation Server before you can add it to your execution path.

To resolve this issue, refer to the instructions for the operating system that is running on the same computer as the Cross-platform Command-Line Client for Team Foundation Server.

Windows

To add the command-line client to a Windows path

On the Start menu, right-click My Computer (or Computer) and click Properties.
Click Advanced system settings.

The System Properties dialog box appears.
Click the Advanced tab and then click Environment Variables.
In the System variables list, click Path and then click Edit.

The Edit System Variable dialog box appears.
In Variable value, append a semicolon to the end of the path, followed by the path of the folder that contains the command-line client, and then click OK three times.

You must open a new Command Prompt window for the updated path to take effect.

Unix (includes Mac OS X)

The configuration procedure for Unix is different for different command shells. Most Unix operating systems default to the sh or bash shell.

Note

If you installed the Cross-platform Command-Line Client for Team Foundation Server inside your home directory and the "~" syntax is not parsed correctly by your shell, you can substitute "$HOME" for "~". For example, you might specify "$HOME/teamexplorer".

To update the path for the bash shell

Open the file ~/.bashrc in a text editor. If the file already contains a line that starts with “PATH=”, add a colon followed by the path of the folder in which you installed the Cross-platform Command-Line Client for Team Foundation Server.

For example, you might update it to match the following:
```
PATH=”/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games:~/teamexplorer”
```
If the file ~/.bashrc does not exist or does not contain a line that starts with “PATH=”, instead add a line such as the following to the end of the file:
```
PATH=”$PATH:~/teamexplorer”
```
By using this syntax, you preserve any existing path that is inherited by your shell.
Save and close the file.

All new bash shells for you now include the Cross-platform Command-Line Client for Team Foundation Server on their path.

To update the path for the csh or tcsh shell

Open the file ~/.cshrc (or ~/.tcshrc for tcsh) in a text editor. If the file already contains a line that starts with "set path =", add a space and the path to the folder that contains the Cross-platform Command-Line Client for Team Foundation Server.

For example, you might update it to match the following:
```
set path = ( /usr/local/bin /usr/bin /bin /usr/bin/X11 /usr/games ~/teamexplorer )
```
If your ~/.cshrc (~/.tcshrc for tcsh) does not exist, or does not contain a line that starts with "set path =", instead add a line such as the following to the end of the file:
```
set path = ( $path ~/teamexplorer )
```
By using this syntax, you preserve any existing path that is inherited by your shell.
Save and close the file.

All new csh or tcsh shells for you now include the Cross-platform Command-Line Client for Team Foundation Server on their path.

zsh

This procedure is similar to the procedure for bash, but you modify the file ~/.zshrc.

sh and ksh

This procedure is similar to the procedure for bash, but you modify the file ~/.profile.

Cannot find the cache or settings files

Team Explorer Everywhere stores cache information and settings in a directory that is specific to the computer account with which you run the Team Foundation Server plug-in for Eclipse or Cross-platform Command-Line Client for Team Foundation Server. The location of the file varies on different operating systems, and it is always in a user's "home" directory.

All cache files and settings are separated by the major version of Team Explorer Everywhere that uses them, and a different subdirectory inside the base settings directory is maintained for each version of these files.

Operating System	Location	Notes
Windows	%USERPROFILE%\Local Settings\Application Data\\Microsoft\Team Explorer	%USERPROFILE% is a Windows environment variable that usually expands to something like C:\Documents and Settings\UserName (or C:\Users\UserName).
Mac OS X	~/Library/Application Support/Microsoft/Team Explorer/10.0	~ is a Unix shell convention that means your home directory.
Unix	~/.microsoft/Team Explorer/10.0	~ is a Unix shell convention that means your home directory.

Running Team Explorer Everywhere as the Root User causes problems

Team Explorer Everywhere is designed to be run as a non-root user on computers that are running Unix.

If you run the Team Foundation Server plug-in for Eclipse or Cross-platform Command-Line Client for Team Foundation Server as the root user, you might encounter issues when you check out or check in files.

To resolve this issue

Run the Team Foundation Server plug-in for Eclipse or Cross-platform Command-Line Client for Team Foundation Server as a non-root user.

User Immutable Flag not set for read-only files on Mac OS X

The Apple HFS and HFS+ file systems support file flags that contain optional metadata, such as the "user immutable" flag. This flag prevents a file from being modified, regardless of Unix permissions. Mac OS X software routinely sets the user immutable flag when it sets a file to read-only. Although the teeplugin and teeclc set files to read-only, by default, those clients do not set the user immutable flag. This is done to support legacy applications that do not understand that flag.