r7 - 2013-05-14 - 10:14:11 - StevenBeardYou are here: TWiki >  Deployment Web > DeploymentTroubleshooting > UpgradeTroubleshooting > CLMUpgradeTroubleshooting > CLMUpgradeScripts > OldJTSVersion

new.png JTS Upgrade Script fails with "Old JTS version could not be determined" error

Authors: Upgrade Troubleshooting Team
Build basis: CLM 3.x and later

One of the most common problems incurred when running the jts_upgrade script is the following error message "CRJAZ2124E: The old JTS version could not be determined." This page will discuss how to move past this error to complete a successful upgrade.

Running jts_upgrade script

The jts_upgrade script upgrades Jazz Team Server version 3.0.1.x or 4.0.0.x to 4.0.1 or later. Here is an example on running jts_upgrade script on Windows and UNIX:

Example

Windows:

cd C:\Program Files\IBM\JazzTeamServer\Server\
upgrade\jts\jts_upgrade.bat -oldJTSHome old_JTS_install_dir\server\conf

UNIX:

cd opt/IBM/JazzTeamServer/Server/
./upgrade/jts/jts_upgrade.sh -oldJTSHome old_JTS_install_dir/server/conf

Full error message

CRJAZ1363I Loading the configuration from "bundleresource://149.fwk505421344/teamserver.properties".

Validating JTS configuration files...
Checking the old JTS version...

CRJAZ2124E The old JTS version could not be determined.  Verify that the oldJTSH ome is pointed at the
correct installation and specify the version using the old JTSVersion parameter.

The jts upgrade failed at step 0.  Correct the problem and run the script again starting at step 0.

Cause

The error message "CRJAZ2124E: The old JTS version could not be determined" is flagged by oldJTSHome parameter when a remote host or none-local location is used for its value. The oldJTSVersion parameter explicitly invokes the previous version that is being upgraded. By default, this is determined by running repotools -version against the old Jazz Team Server. The old Jazz Team Server directory must be present on the same upgrade server and it cannot be a map drive or symbolic link.

Resolution

The jts_upgrade script only supports side by side upgrade. The script only runs on the same server upgrade based on an existing JTS installation. It expects an old JTS server that has been properly installed and configured. Also, you cannot use a map drive or symbolic link for oldJTSVersion parameter value when running the jts_upgrade script.

If you plan to move the JTS server to a new system, you should first upgrade JTS server to version 4.0.1 or later. Then you can follow server rename to complete your server move by requesting a server key from IBM Rational Client Success Team.

Related topics: DeploymentTroubleshooting

External links:

  • None

Additional contributors: WilliamChen, BrettBohnn

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r7 < r6 < r5 < r4 < r3 | More topic actions
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.
Ideas, requests, problems regarding the Deployment wiki? Create a new task in the RTC Deployment wiki project