BCO fails when used with UNC paths

0 Likes

Problem:

BCO fails when used with UNC paths

Resolution:

  • Product Name: Star Team
  • Product Version: 2005 R2
  • Product Component: All
  • Platform/OS Version: All

Question:

Why does BCO fail when used with UNC paths?


Answer:

When running the StarTeam Bulk Checkout tool (BCO) and trying to checkout the files to a UNC network path (share) with the -fp option, the BCO fails. This fails with either "path not found" messages, or places the files in the current working folder.

For instance, the following would fail:

[/pre]

"C:\Program Files\Borland\StarTeam 2005\bco.exe" -p "user:password@server:port/view/folder/path" -fp "\\server\path" -is -fs -o -cfgl label "*"

The BCO command has a problem with the fact that UNC paths start with a double backslash, BCO seems to drop the double backslash and try to use the remainder of the path as a local path relative to the command shell working directory.
This can be prevented by "escaping" the initial backslash with an additional backslash, so the path begins with a triple backslash, \\\.
So our earlier example becomes:

The BCO command has a problem with the fact that UNC paths start with a double backslash, BCO seems to drop the double backslash and try to use the remainder of the path as a local path relative to the command shell working directory.
This can be prevented by "escaping" the initial backslash with an additional backslash, so the path begins with a triple backslash, \\\.
So our earlier example becomes:

"C:\Program Files\Borland\StarTeam 2005\bco.exe" -p "user:password@server:port/view/folder/path" -fp "\\\server\path" -is -fs -o -cfgl label "*"


Old KB# 28020
Comment List
Related
Recommended