Upgrade error 5.0 to 5.1.2 (Win2008)

I have an existing TeamCity 5.0 Enterprise installation.

I attempted to upgrade to version 5.1.2 by:

1) installing v5.1.2 onto a new server

2) copying the contents of my old TeamCity 5.0 data directory into the new server's data directory

When I started the new server, I received this error message:

Error on step: Starting servlet

jetbrains.buildServer.serverSide.db.DataPartsInconsistentException: Data parts are inconsistent: configurations exist but the version file is absent.

   at jetbrains.buildServer.rootDispatcher.TeamCityDispatcherServlet.processStartupServerInternal(TeamCityDispatcherServlet.java:87)

   at jetbrains.buildServer.rootDispatcher.TeamCityDispatcherServlet.processServerStartup(TeamCityDispatcherServlet.java:60)

   at jetbrains.buildServer.rootDispatcher.TeamCityDispatcherServlet.access$000(TeamCityDispatcherServlet.java:76)

   at jetbrains.buildServer.rootDispatcher.TeamCityDispatcherServlet$1.run(TeamCityDispatcherServlet.java:2)

   at java.lang.Thread.run(Unknown Source)

The new and old servers are running Windows 2008 R2 Web x64.

Any advice would be appreciated.

Best Regards,

David Montgomery

4 comments

David,

Apparently, you did not copy .BuildServer/system directory to the new location.
Please review the upgrade and create a server copy sections in our documentaiton.

0

For clarification, there is no 'version.dat' file in my <data directory>\system path of my working 5.0 installation.

This file seems to be nowhere in my data directory, or on the local drive of my TeamCity 5.0 installation.

and yes, the server is currently running fine.

0

I'm getting the same error. It was all working until I installed Sybase 15 Openclient. Then I get the same error as above. I've been through the posted links above and there seems to be no solution. Anyone managed to solve this yet?

0

Hi

if you've got this exception and you could not fine the 'version.dat' file, you can recover it manually but only if your TeamCity installation works successfully.
So, you can manage it before upgrade TeamCity software.

In order to recover this file, get the 'teamcity-server.log' from the installation that does work correctly, look thru it for the last occurence of the following string

TeamCity configuration version is

and the rest of this string is a number (for example, 321), not zero.

Then, create the 'version.dat' file in the <TEAMCITY_DATA>/system directory with the following line:

version.nr=###

where ### is a number you've found in the log. This line must not contain spaces (even at the end of the line).

Then, restart the server. If the server started successfully — the 'version.dat' file is recovered correctly, and you can follow with upgrade.

Note: don't attempt to do this on the installation that has been unsuccessfully upgraded — because you can encounter unrecoverable data loss or hard-investigable errors.


Best regards,

Leonid

0

Please sign in to leave a comment.