Knowledgebase

Search:     Advanced search

TestTrack Project Upgrades Fail

Article ID: 410  |  Last updated: 29 Dec, 2014

Problem

A TestTrack project cannot be upgraded. The following errors are written to the server log:

‘RDBMS data source cannot be upgraded if in use by multiple TestTrack Servers.’
‘The RDBMS data source is in use by another TestTrack Server.’

The following error may be returned in the TestTrack Server Admin Utility:

‘A project could not be upgraded because the data source appears to be in use by more than one TestTrack Server.’

Cause

One or more of the projects to be upgraded is associated with another TestTrack Server. Projects can only be associated with one TestTrack Server at a time. Each project stores the universally unique identifier (UUID) of the TestTrack Server that hosts the project. When starting an upgrade, the server checks the UUID stored in the project against the UUID stored on the server. If the values do not match, the upgrade fails.

If you are upgrading projects stored in an RDBMS database, you must upgrade all the projects in the database at the same time. If one or more project in the database is associated with a different server, the upgrade fails for all projects. We do not recommend storing projects for multiple TestTrack Servers in one RDBMS database because upgrade issues like this can occur.

TestTrack native projects are stored in individual files and upgraded one at a time.

Solution

In the TestTrack Server Admin Utility, make sure all projects you want to upgrade are only associated with the TestTrack Server you are logged in to.

  • If a project is displayed in the Projects list on the current server, but is associated with another server, click Remove to remove it and then click Add Existing to re-add it and replace the old UUID with the current server’s UUID.
  • If you want to upgrade a project that is not in the Projects list on the current server, remove it from any other servers and then click Add Existing on the current server to add it and replace the UUID.
Article ID: 410  |   Last updated: 29 Dec, 2014
Tags
UUID rdbms upgrade cannot upgrade data source

Prev   Next
PostgreSQL Returns a Nonstandard Use of Backslashes Warning     Locking Table (Microsoft Access) ODBC Error