What to do if you accidentally delete the starteam-server-configs.xml file

Don’t panic, it is possible to get your configuration working again after deleting the contents of your starteam-server-configs.xml file (which thanks to a combination of Windows Vista and Macromedia Dreamweaver, I managed to do on a test system I was using)

First, you will need to retrieve so information about you StarTeam database itself, so for this you will need to use a database client of some kind. I downloaded SQL Server Management Studio Express from MSDN for this.

This article deals with an example of StarTeam 2006 running on unsupported Windows Vista Enterprise pointing at an MSDE database, but the details for other db configurations are largely identical.

Lookup the login that your starteam server is using to talk to your StarTeam database by going to your Windows ODBC datasources (From Administrative Tools in the Windows control panel, for example) In the System DSN tab, you’ll find a login in for the StarTeam database that the Server uses, you’ll also need to remember the password for this user (or if you ignored the security warnings when creating your server configuration initially, you can test the connection with a blank password) probably, depending on the version of StarTeam that you have installed, the login will be something like the following :

starteam_stardraw90_login (for ST2006)
starteam_stardraw80_login (for ST2005R2)
starteam_stardraw70_login (for ST2005)

(presuming you installed the standard StarDraw configuration and used that configuration, otherwise the database login will be whatever you named it during

the server configuration creation process, although it should still be shown in the Windows System DSNs for ODBC so you can get a big hint by looking there) Once you’ve accessed the database, you’ll need to retrieve the ServerGuid for your server configuration, to do this, simply run the following statement to return the serverGUID for your configuration

select F3 from s0

It is not recommended under any circumstances to change any of the values in the database, as it may have future impacts to your repository.

Now you can start recreating your starteam-server-configs.xml. The best way to do this correctly is to create a new dummy server configuration for the StarTeam server admin console at this point, this creates another valid configuration (particular to your system) in your now blank starteam-server-configs.xml file, which you can then copy and modify with the correct values to restore the old configuration. Additionally, you can use the xml snippet below to help you:

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<StarTeamServerConfigurations version="1.0">

  <Configuration name="StarDraw">
    <option name="ServerGuid" value="be5ff3b0-c719-49c6-a1a1-f493764a03f5"/>
    <option name="CreatedByBuild" value="9.0.225"/>
    <option name="RepositoryPath" value="C:\Program FilesBorlandStarTeam Server 2006SamplesStarDraw Repository"/>
    <option name="LogPath" value="C:\Program FilesBorlandStarTeam Server 2006SamplesStarDraw Repository"/>
    <option name="Initialized" value="1"/>
    <option name="ServiceMode" value="0"/>
    <option name="Sample" value="0"/>
    <option name="DBType" value="2"/>
    <option name="DBCreated" value="1"/>
    <option name="DBServerName" value="StarDrawDB90"/>
    <option name="DatabaseName" value="starteam_stardraw90_db"/>
    <option name="DBUserName" value="starteam_stardraw90_login"/>
    <option name="DBPassword" value=""/>
    <option name="DBMinimumConnections" value="0"/>
    <option name="DBMaximumConnections" value="0"/>
    <option name="ListenIP" value=""/>
    <option name="MinCommandThreads" value="0"/>
    <option name="MaxCommandThreads" value="0"/>
    <option name="NotificationLocale" value=""/>
    <option name="Status" value="Running"/>
    <option name="PID" value="-1"/>
    <option name="Endpoint" value="49201"/>
    <option name="FileAllowCheckoutTrace" value="0"/>
    <option name="FileEnableCheckoutTrace" value="0"/>
  </Configuration>

</StarTeamServerConfigurations>
So, so far you should have the configuration name and the ServerGuid part of this file. The CreatedByBuild tag is simply a reference to the version of the StarTeam server that you are using so it better to use the server’s default value on most occasions, unless you know that your configuration was created on a previous version of StarTeam, then simply enter your version number here. If you’re not sure where your repository path is, this should point to the folder which contains the file Server.en-US.Log and the folders DefaultHiveIndex, HiveIndex, Notifications, Trace folders. For the StarDraw sample repository, this is:

C:\Program FilesBorlandStarTeam Server 2006SamplesStarDraw Repository

The dbservername, databasename and dbuserpassword with be the same as you used to login to the database to retrieve the ServerGUID, dbtype =2 is for MSDE, PID value should be set to -1 initially.

That’s it. Now start your StarTeam server configuration, then I recommend you back everything up properly in case it happens again

——————————————————– 

 Edit 10th April 2008:

 Just as an addition to this post, I recently had problems recreating a ST2006R2 and ST2008 using this method as I needed an encrypted password string in the DBPassword field which I was unable to successfully recreate using online encryptors from the original password (I couldn’t work out the algorithim in other words, despite knowing the original password) so this article may not be valid for 2006R2 and 2008 versions.

I haven’t had time to fully investigate this issue further, but presumably one way to recreate a correctly encrypted password in order to recreate the complete xml file would be to recreate a new server configuration from scratch and during the db creation step, enter your db password for the new config, then the password that is encrypted for the new config, can just be copied and pasted from the server configs xml file for the new config to the one you’re trying to resurrect, no guarantees though as I haven’t tried this to verify it.
 
Interestingly enough, the error message created by the server when I tried to start the server either without the password or with the incorrect pasword was ‘There are not enough pooled connections available’ which wasn’t actually the root cause of this problem, this tip may help if you are trying to start your server and are receiving this error message.

Share This | Email this page to a friend