Borland® StarTeam® 2008 Release 2 Release Notes

Last updated: August 18, 2008

Welcome to Borland® StarTeam 2008 Release 2! This file contains important information that might not appear in the documentation and covers the StarTeam Server for Windows, Cross-Platform Client, StarTeam Workflow Extensions, StarTeamMPX, and StarTeam Layout Designer. Read this file in its entirety.

For an overview of the new features in the current release, see the What's New topic in StarTeam Help or Administering and Using StarTeam (AdministeringAndUsingStarTeam.pdf).

Note: The information in this readme represents the known issues at the time of this release. For late-breaking information that may become available after the release, check the Borland web site for the most recent version of this readme: http://techpubs.borland.com/starteam/ .

Contents
StarTeam Server for Windows StarTeam Layout Designer
StarTeam Cross-Platform Client StarTeam Integrations
StarTeamMPX Getting Help
StarTeam Extensions Complete Installation Instructions 

StarTeam Server for Windows

Contents
Important Announcement Known Issues
System Requirements/Prerequisites Limitations
Getting Help

Important Announcement

System Requirements/Prerequisites

In addition to the following system requirements, StarTeam Server uses Sun Microsystems Java Virtual Machine 1.6.0_02, which is automatically installed.

System Area Requirement
Platforms

Microsoft Windows 2003 Server SP2 (32-bit version)

Microsoft Windows 2003 Server R2 SP2 (32-bit version)

Note: You can run StarTeam 2005 Release 2 and subsequent releases on VMware ESX Servers.

Databases and ODBC versions

Microsoft SQL Server 2005 Express SP2 (SSE) on x86 32-bit CPU - ODBC version v2005.90.3024.0

Microsoft SQL Server 2005 SP2 on x86 32-bit CPU - ODBC version v2005.90.3024.0

Oracle Database 10g Release 2 version 10.2.0.3.0 on 32-bit CPU - ODBC version 10.2.0.3.0

Oracle Database 11g version 11.1.0.6.0 on 32-bit CPU - ODBC version 11.01.00.06

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 2008 R2 Installation Guide  (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.

Hard disk space

200 MB to install the application

Note: The amount will vary depending on your use of the product.

Web browser (for viewing online help)

Microsoft IE6 SP1+

Opera 8.5.2+

Netscape 7.2+

Firefox 0.9+

Other

Adobe Acrobat Reader 4.0 or higher for viewing the StarTeam Installation Guide (Install_en.pdf)

Display

SVGA, high color mode, 1024x768 or greater

Recommended resolution: 1280x1024 or more

Virus Scanning Utilities

Every StarTeam client 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 http://support.borland.com before restarting the server. Some viruses can be immediately destructive to the repository and in rare cases data loss will be inevitable. Borland 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. Since StarTeam only acts as a conduit between users and the storage mechanism, it is highly improbable that any contamination/bad behavior will be propagated.

Note: You can access the StarTeam Cross-Platform Client with this release of StarTeam Server and StarTeam Server 2006. This makes it easier to roll out your upgrades of the client after installing the server.

Important: If you are upgrading from a previous version of StarTeam Server, you MUST review the upgrade instructions in the StarTeam Installation Guide (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.

 

Top

Known Issues

Installation Issues

Database Issues

Microsoft SQL Server/SSE

Oracle

Server Issues

Native-II Vault

Purge Issues

Before purging data, Borland recommends running either starteam_oracle_compute_stats.sql (for Oracle) or starteam_sqlserver_update_statistics.sql (for Microsoft SQL Server). By default, these scripts install in the C:\Program Files\Borland\StarTeam Server 2008 R2\DBScripts\Oracle_Scripts or C:\Program Files\Borland\StarTeam Server 2008 R2\DBScripts\Sqlserver_Scripts folders.

Evaluations

Borland allows you to extend the evaluation period for StarTeam Server by contacting http://www.borland.com/us/company/how-to-buy.html and obtaining an evaluation extender key.

Server Configuration File Option

The option ItemCacheMemoryLoadMaxPct is obsolete and does not have any effect in StarTeam 2008 and 2008 R2. A new server configuration file option ItemCacheMemoryLimit defines the maximum amount of memory that can be used for caching item data, in MB. The default value is -1, which means no limit is set, and the server will use up to the maximum amount of memory available to the server process for caching the data. For example, adding <option name="ItemCacheMemoryLimit" value="100"/> to the configuration file will set the cache limit to 100 MB.

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.

You may receive an error message when entering data in APEs.

4GT RAM Tuning

If your StarTeam Server runs on Windows Server 2003, either Enterprise Edition or Datacenter Edition, you can use Microsoft's 4GT RAM Tuning to give the StarTeam Server process the use of 3 GBs of memory. To enable this feature the /3GB switch needs to be added to the Boot.ini file.

Please see: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/memory/base/4gt_ram_tuning.asp for more information on setting this switch.

For example: "multi(0)disk(0)rdisk(0)partition(2)\WINNT="Microsoft Windows 2000 Advanced Server" /3GB /fastdetect

For more details, see http://technet.microsoft.com/en-us/library/cc758478.aspx.

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.

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, and the default port for Multicast Service is 5104. If you are using these ports you need to open them.

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. Press OK closing all of the dialogs.

Security

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.

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.

Blocking

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. This is not a problem. Click Unblock.

MDAC

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 or Multicast Services must start before the StarTeam Server service. Usually it does. If StarTeam Server fails to enable MPX and the Message Broker or Multicast Service are on the same computer, you may want to make the StarTeam Server service dependent on the Message Broker or Multicast Service 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 2003:

1. Click Start>Run from the Start menu.

2. Type Regedt32.

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 or StarTeam Multicast Service service name into the Data window. (Example: StarTeam Message Broker 6.7).

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.

Miscellaneous Issues