Borland® StarTeam® 13.0 Update 1 Release Notes

Last updated: January 30, 2013

Welcome to Borland StarTeam 13.0 Update 1! These release notes contain important information that might not appear in the documentation and cover the StarTeam Server, Cross-Platform Client, StarTeamMPX, Web Client, Web Server, and Command Lines.

The StarTeam Installation Guide for each release is available online at

Note: These release notes represent the known issues at the time of this release. For late-breaking information that may become available after the release, check the Micro Focus Web site for the most recent version of the Release Notes at

What's New in 13.0 Update 1 What's New in 13.0
StarTeam Server StarTeam Cross-Platform Client
StarTeamMPX StarTeam Web Client
StarTeam Web Server Command Lines
StarTeam Documentation Getting Help

What's New in 13.0 Update 1

This section provides an overview of the new features found in StarTeam 13.0 Update 1.

View Compare/Merge Optimization

A new View Compare/Merge (VCM) optimization feature has been added. The optimization is a workaround for very large VCM commits (that is, tens of thousands of VCM operations), which cannot realistically succeed when run in a server and database transaction.

To use this workaround, the VCM session MUST be committed by a user who has the Modify system configuration Server Access Rights granted and is preferably using the 64-bit SDK/CPC. The VCM session should also be run when there is little to no other activity on the StarTeam Server, because of the extensive resource allocation to be provided for this commit session.

For administrators who intend to run VCM with transactions disabled, follow the steps below:

  1. Turn ON the setting AtomicBehavior in the starteam-server-configs.xml file. There is no need to stop and restart the server just to change this setting.
    The default value of this setting is 0, meaning that Atomic Transactions are enabled by default.
        <option name="AtomicBehavior" value="0"/>
  2. Set the AtomicBehavior setting value to 1 (as shown below).
        <option name="AtomicBehavior" value="1"/>
  3. Wait for a minute, then run the large VCM commit from a 64-bit version of the SDK/CPC using the Administrative Context with privileges to modify server settings.
    Note: Running the session from a 32-bit SDK/CPC runs the risk of the CPC running out of memory before the session is committed.

When the VCM session starts up and discovers that AtomicBehavior is disabled, it will immediately re-enable it and then run the VCM session without transactions. This means that a subsequent VCM session will automatically run with transactions enabled.

If the VCM session is run using non-administrative privileges, then the attempt to re-enable transactions in the server will fail, and the setting will be ignored. In this case, the session will run with multi-command transactions enabled, as if the settings were unchanged.

Internal testing has indicated that a VCM session with 65,000 files being reverse-shared run in 2 hours on a single machine and 5 hours across a network with this new workaround. Without the workaround (that is, with transactions enabled), the same commit takes over 24 hours and does not complete.


Translated versions of the StarTeam SDK, Server, Cross-Platform Client, and Web Server in Japanese, French, German, Portuguese, and simplified Chinese are now supported. Only the applications and user interfaces are translated. The documentation for this release is only available in English. Translated documentation is provided for 2009 and 2009 Release 2 at

The Release Notes for 13.0 will be translated into the supported languages. Check the Micro Focus Web site for the most recent version of the translated Release Notes at

Cross-Platform Client

This section provides an overview of the new features found in the StarTeam Cross-Platform Client 13.0 Update 1.

View Usage Property

A new property is available on the View Properties dialog for distinguishing how a View is used. The available values to set on this property are Main, Release, Sandbox, and Unknown. StarTeam Agile will limit the visible Views for selection and planning to only the Release Views.

Show/Hide Change Packages in the Change Details Pane

An option has been added to the Change Details pane to toggle the visibility of Change Packages.  When the option is turned off, all changes from the relevant Change Packages are rolled up into a sortable list in the pane.  When the option is turned on, the Change Packages are displayed and can be opened to see each of their change objects.

What's New in 13.0

This section provides an overview of the new features found in StarTeam 13.0.

StarTeam Server

This section provides an overview of the new features found in the StarTeam 13.0 Server.

StarTeam Agile 1.0 Support

Support has been added for StarTeam Agile 1.0.

Red Hat Enterprise Linux Support

StarTeam Server 13.0 is now available on Red Hat Enterprise Linux 5.5 (32-bit).

StarTeam Agile Component Types

The new component types Sprint and Story have been added to support the new 1.0 StarTeam Agile Web application. Sprints and Stories can be created in StarTeam Agile and viewed in the Cross-Platform Client. See the StarTeam Agile 1.0 documentation for a complete list of supported features.

starteam-server-configs.xml File

Two new session options have been added to the starteam-server-configs.xml file.

Command Lines

This section provides an overview of the new features found in StarTeam Command-lines 13.0.

VCMUtility New Feature

CustomDifferenceTypes (CDT) has been added as a supported option of VCMUtility.  Using Custom Difference Types provides an alternative mechanism to specifying either Match States or Session Option Properties such as Lock Source for Difference, Ignore Merge Points, and so on. Specifically, the values of the difference type actions and session properties from Custom Difference Types override anything equivalent specified through the vcmutility command-line utility.   Besides supporting tracking all configuration options through the Server Administration Tool, this also has the added advantage of simplifying and minimizing the vcmutility parameter set. See the Command-line Tools Help documentation for VCMUtility example commands.

Cross-Platform Client

This section provides an overview of the new features found in the StarTeam Cross-Platform Client 13.0.

Open StarTeam Agile

You now have a quick and easy way to launch StarTeam Agile from within the Cross-Platform Client. Your server administrator must first specify the StarTeamAgileWebAddress option information in the starteam-server-confs.xml file. Once defined you can then choose Project > Open StarTeam Agile from the main menu to launch StarTeam Agile in your default browser.

Show Advanced Menus Option

A new Show Advanced Menus option allows you to control whether standard or advanced menu items display in the Main Menu for the component selected. Choose Tools > Show Advanced Menus from the Main Menu to turn the feature on or off. This feature is turned on by default and a check box displays when the option is turned on. When enabled, you will see advanced menu items displayed in the menu of the component selected. The component Main Menu options include: View, Folder Tree, File, Folder, Change Request, Requirement, Task, and Topic.

StarTeam Agile Component Types

The new component types Sprint and Story have been added to support StarTeam Agile. Sprints and Stories can be created in StarTeam Agile and viewed in the Cross-Platform Client. Personal options tabs have been added where you can define system tray notifications to indicate how often the application should search for new sprints and stories and define URL options for displaying templates.

Deleted File and Folder Status Values

The following status values are now available in the CPC. You can only view these statuses in the File Items pane and they are not value options in a query if you choose Status as a Field condition. However, when you generate a report these statuses do display on the report.

Working Folder New Features

StarTeam Server

Known Issues and Notes about StarTeam Server
Server System Requirements/Prerequisites

Server System Requirements for Windows and Linux

System Area Requirement

Microsoft Windows Server 2003 R2 SP2 (32-bit)

Microsoft Windows Server 2008 (32- and 64-bit)

Microsoft Windows Server 2008 R2 (64-bit)

Red Hat Enterprise Linux 5.5 Server (32-bit)

Databases and ODBC versions

Microsoft SQL Server 2005 Express SP3 (Windows Server only)

Microsoft SQL Server 2008 Express (Windows Server only)

Microsoft SQL Server 2008 Express R2 (Windows Server only)

Microsoft SQL Server 2005 SP3 (Windows Server only)

Microsoft SQL Server 2008 (Windows Server only)

Microsoft SQL Server 2008 R2 (Windows Server only)

Oracle Client 10g R2 version (32- and 64-bit)

Oracle Client 11g version (32- and 64-bit)

Oracle Client 11g R2 (32- and 64-bit)

Note: You can install Microsoft SSE as part of the StarTeam Server installation. You must purchase the other database products from the appropriate vendor. Refer to the StarTeam Installation Guide (ST_Install_en.pdf) for more information about recommended system configurations for running StarTeam and SSE on the same computer and for running StarTeam Server and its associated database on separate computers.

Important: Never modify database contents or vault files other than through a Client or Server Administration tool. Direct database manipulation is unsupported.

Web browser

Microsoft Internet Explorer 8 or later

Firefox 4 or later


Adobe Acrobat Reader for viewing the StarTeam documentation in PDF format.

Virus Scanning Utilities

Every StarTeam Server computer should be equipped with a virus protection utility that has up-to-date virus definition files. All StarTeam Servers should also be equipped with up-to-date virus protection and the settings should be set to alert only the administrator. The StarTeam administrator should halt the StarTeam Server immediately upon virus detection, perform a full StarTeam backup, and then follow the instructions provided by the virus protection vendor for cleaning the virus from the infected file. If the infected file cannot be cleaned or if problems exist, contact before restarting the Server. Some viruses can be immediately destructive to the repository and in rare cases data loss will be inevitable. Micro Focus strongly recommends that regular backups be performed.

A virus that might be a nuisance to a file system can be far more destructive when checked into the repository. For example, many virus protection utilities are set by default or can be set to delete infected files. If an archive file is deleted by the virus protection utility, data may be lost.

Another example is that a virus may not be detected in the archive and may sit dormant waiting to infect the computers of all project users. Your network will rapidly spread the virus and a data loss could occur.

Note: If any process or program such as anti-virus software alters files under StarTeam control the system could behave erratically. It is highly recommended that these processes not be allowed to modify system or data files under StarTeam control.

Note: The StarTeam 13.0 Cross-Platform Client can only access the following StarTeam Servers: 13.0, 12.5, 12.0, 2009 R2, and 2009. All Servers prior to 2009 will not support the 13.0 Client.

Important: If you are upgrading from a previous version of StarTeam Server, you MUST review the upgrade instructions in the StarTeam 13.0 Installation Guide (ST_Install_en.pdf). There are some steps that you must complete in order for the upgrade to complete successfully. Failure to complete these steps can cause the upgrade to fail.

Known Issues and Notes about StarTeam Server

Known issue about ODBC/DSN Decommission Process and the workaround

During the database upgrade process for existing pre-13.0 configurations, the ODBC DSN information in the configuration file is replaced with entries for direct database connectivity.  During this time, we are able to detect the database server and instance name and update the configuration accordingly.

Connecting to a database (SQL Server or Oracle) running on a non-default port is now supported directly—during the creation of a new configuration, there is an option to select the port, if desired.  However for SQL Server configurations upgraded to 12.0 from previous versions of StarTeam, the default port will always be assumed.  This is because the workaround to connect to a SQL Server on a non-default port using ODBC does not return the port information when queried.

If attempting to upgrade an existing configuration to 13.0, where the SQL Server ODBC DSN used by the existing configuration references a non-default port, it may be necessary to edit the starteam server configuration file to enter the correct port.

Installation Issues

Server Issues

Native-II Vault

StarTeam Sample Server Configuration

If you plan to use the sample Server configuration, StarDraw, and want to run it as a service, you may have to start it once as an application, shut it down, and then set it as a service.

Opening Ports on Windows XP

If you are using a firewall, you have to open the port number on Windows XP SP2. This is 49201 by default. If you don't open this port in the Windows firewall, you cannot connect to the Server.

Windows Server 2008 also requires an Exception to the Windows Firewall Settings. However, it may be a better practice to grant all access to the StarTeam Server as follows:

  1. Start the Control Panel and select Windows Firewall.

  2. Select Change Settings in the Windows Firewall dialog box.

  3. Select the Exceptions tab.

  4. Select Add program…

  5. In the Add a Program dialog box, select Browse…

  6. Browse to \Borland\StarTeam Server 13.0\ and select the StarTeam Server Application.

  7. Click OK.

  8. Note: This will grant access to any port to the StarTeam Server. The above procedure could be followed to grant an Exception for MPX, Cache Agent and Web Server.

You will run into a similar problem for an MPX-enabled StarTeam Server. You will need to open the ports that are used by MPX. For example, the default port for Message Broker is 5101. If you are using this port you need to open it. To open a port:

1. Start the Control Panel and select Windows Firewall.

2. Select the Exceptions tab.

3. Select Add Port and enter in any name and the appropriate port number.

4. Click OK.


If you run StarTeam Server on a Windows XP Professional computer, the person who creates and/or starts the first Server configuration becomes the only person who can create and/or start Server configurations. We provide the GrantAdmin utility that allows other administrators to create and start Server configurations.

Note: Windows XP is not officially supported for StarTeam 13.0 Server.

The utility is installed in the Server installation folder. It must be run by the user who installed/started the Server. It does not require any arguments. The GrantAdmin utility grants access rights to the key container to the other administrators. Otherwise, only the administrator who created the key container (that is started the Server for the first time) has the rights needed to create and start Server configurations.


If you run StarTeam Server and the StarTeam Cross-Platform Client on Windows XP SP2 with all updates, running the StarTeam Server or the StarTeam Toolbar for the first time can result in a "Server Blocked" or "Toolbar Blocked" error message from the Windows Firewall. This is not a problem. Click Unblock.


StarTeam Server needs MDAC 2.8, and Windows XP SP2 comes with that version of MDAC. During the installation of StarTeam Server, you may see a message about MDAC 2.8 being incompatible with this version of Windows. This is not a problem. Click Cancel.

Running the Server as a Service

If you are running StarTeam Server as a service, you may see the Windows error 2186 indicating that the service is not responding to the Start Control function. Windows 2003 displays this message when a service takes longer to start than expected. Depending on the size of your database, StarTeam Server may take longer to complete the startup process than Windows expects. Usually StarTeam Server starts without a problem (despite this error message). However, to be sure, run the Event Viewer (Start\Programs\Administration Tools (Common)\Event Viewer. Check the most recent events for StarTeam Server. You will probably see: StarTeam Server Service started. If not, you will find the reason why it did not start or start properly and take appropriate action.

If an MPX-enabled StarTeam Server runs as a service, the Message Broker must start before the StarTeam Server service. Usually it does. If StarTeam Server fails to enable MPX and the Message Brokers on the same computer, you may want to make the StarTeam Server service dependent on the Message Broker service. Check with your system administrator before using the following technique.

Warning: Create a backup of the registry before making any registry changes. If you have disastrous results, the only way to recover is to restore from a registry backup or to reinstall the entire operating system.

To set up a service dependency for Windows 32-bit or 64-bit:

1. Click Start > Run from the Start menu.

2. Type Regedit32 or Regedit64, depending on your operating system.

3. Click OK.

4. Select HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\StarTeamServer-configName

5. Select Edit > New > Multi-String Value.

6. Set the Value Name to DependOnService.

7. Double-click the DependOnService Value to open the Data window.

8. Enter your StarTeam Message Broker internal service name into the Data window. (Example: StarTeam Message Broker 6.8).

Time Issues

StarTeam Server stores time stamps in UTC (also known as Universal Coordinated Time, Greenwich Time, or Zulu Time) format and adjusts the time stamp for the time zone that the computer specifies. For example, if a file is saved and checked in at 5 P.M. in California, its time stamp in California is 5 P.M. However, its time stamp on a computer in New York would be 8 P.M., the time it was in New York when the file was checked in. When a file is modified, the time stamp reflects that of the operating system. This means that if a file is checked in by a user in one time zone and modified by a user in another, the file's time stamp may appear to be earlier than the most recently checked-in revision. This does not affect file statuses within StarTeam because the UTC times are used to calculate statuses.

If you are in an area that observes Daylight Savings Time (DST), the StarTeam status bar may display the incorrect time when rolling back a view (View\Select Configuration\Configuration As Of). For example, if you are currently in DST and rollback the view to a point in time prior to DST, the time display in the status bar (lower left corner of the StarTeam window) will be ahead by one hour. If you are not currently in DST and rollback the view to a point in time during DST, the time in the status bar will be behind one hour.

Microsoft Project Tasks

MSP tasks imported into a StarTeam Server should not have work records that occur before the start date. If they do, the work hours will not be subtracted from the remaining work.

Disk-imaging Software

Using Disk-imaging Software in StarTeam: Disk-imaging software, such as Norton Ghost, does not work well with StarTeam. StarTeam needs to be installed on each workstation. StarTeam creates a unique connectionmanager.ini file for each workstation. The connectionmanager.ini is used to identify one workstation from another. If you use disk-imaging software, this .ini file is copied, and when the image is installed to another computer, there are now two or more workstations with the same .ini file. This can lead to unusual status problems.

Logging in Using Previously Logged on User

When working in the Server Administration tool and logging in using a previously logged on user, an error displays indicating that "A user has already been logged on for this session." As a workaround, close and reopen the Server Administration tool and log on again. Click OK to terminate the program.

To avoid this situation, be sure to stop the Server application before shutting down Windows or run the Server as a service.

StarTeam Cross-Platform Client

Known Issues and Notes about Cross-Platform Client Cross-Platform Client Limitations
System Requirements/Prerequisites for the Cross-Platform Client

System Requirements/Prerequisites for the Cross-Platform Client

The StarTeam Cross-Platform Client is implemented in Java and can be installed on Microsoft Windows systems and any system that supports the Java Runtime Environment (JRE) 1.6.0_29 . However, only the following Java-enabled platforms have been tested for compatibility with this product:

Known Issues and Notes about Cross-Platform Client

The following are known issues found in the Cross-Platform Client (CPC).

Cross-Platform Client Issues

Cross-Platform Client Limitations

On non-Windows systems, jsafe.jar automatically installs with the Cross-Platform and Universal Edition (stcmd) Clients and is used for encryption. The jsafe.jar file is required if you are running standalone scripts on non-Windows platforms, and you need to establish an encrypted connection to a StarTeam Server. Without jsafe.jar installed, you will receive a meaningful "encryption algorithm not supported" message. If you receive this error, you should re-install the Cross-Platform Client as a workaround.


System Requirements/Prerequisites  
Known Issues  

Important: Prior to installing, please read the StarTeamMPX Administrator's Guide (ST_MPX_Help.pdf) and the StarTeam Installation Guide  (ST_Install_en.pdf) on the Product Documentation page of the Micro Focus web site at Proper planning is required in order to achieve best results from StarTeamMPX.

System Requirements/Prerequisites for StarTeamMPX

StarTeamMPX transmitters have the same system requirements as the StarTeam Server because they are part of that system. The Message Broker is required. The Message Broker is a publish/subscribe messaging engine that broadcasts messages to subscriber components on a topic basis. It is a stand-alone process that can run on a separate computer to offload network processing overhead in high-volume environments. For details, see the StarTeam Server for Windows Server System Requirements in this file.You can also set up Cache Agents in tiers at a variety of locations so that file contents and objects, transmitted by the file transmitter, can be network near any StarTeam user. Cache Agents work with the StarTeam Client to check out files and fetch objects faster.

Message Brokers & Cache Agent

Note: For Cache Agent, these requirements should be sufficient for teams that have 50 to 100 members.

Known Issues and Notes about StarTeamMPX

StarTeam Web Client

System Requirements/Prerequisites for the Web Client

Known Issues with the Web Client

StarTeam Web Client has the following limitations and known issues:

StarTeam Web Server

System and Installation Requirements for the Web Server

Known Issues with the Web Server

Command Lines

Known Issues with the Command Lines

Known Issues with Command Lines

When specifying a quoted argument that contains a space, the beginning quote must be preceeded by a space.  The following are examples of both incorrect and correct syntax for arguments with spaces:

Incorrect: stcmd set project=”StarFlow Extensions”
Correct: stcmd set project = “StarFlow Extensions”

Incorrect: stcmd select name from File where query=”Flagged Items”
Correct: stcmd select name from File where query = “Flagged Items”


Known Issues and Notes about the Documentation

StarTeam Installation Guide

In the Installation Guide, the Additional Customizations table in the Installing the Cross-Platform Client chapter contained incorrect values. The following information should replace the content in the guide:

Original File Name Description Installation File Name
starteam-servers.xml StarTeam Servers at a site server
starteam-client-options.xml StarTeam personal options starteam-client-default-options.xml

Eclipse Infocenter

When you open the first instance of a StarTeam application, such as the Cross-Platform Client, and click on the Help Topics menu, the Eclipse Infocenter opens and displays the correct help contents for that application. However, when you close the application, and/or open another StarTeam Application, such as the Server Administrator Tool, when you click on the Help menu, the Eclipse Infocenter displays the help from the previous application, in this case, the Cross-Platform Client.

The workaround for this is to go into the installation directory of the first application in which you clicked Help (Cross-Platform Client in this example), and in the \borland-help subfolder, double-click shutdown.bat. This releases the previous applications Help contents from memory so the correct help will display when you open it in the second application.

Getting Help

To obtain help for StarTeam, see Micro Focus SupportLine.

Copyright© 2013 Micro Focus. All Rights Reserved. Portions Copyright © 2004-2009 Borland Software Corporation (a Micro Focus company).