Unable to render embedded object: File (TeamCity48.png) not found.

TeamCity 10.x and 2017.x Documentation


You are viewing the documentation of TeamCity 10.x and 2017.x, which is not the most recently released version of TeamCity.
View this page in the latest documentation or refer to the listing to choose the documentation corresponding to your TeamCity version.


Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: related to https://youtrack.jetbrains.com/issue/TW-52707, https://youtrack.jetbrains.com/issue/TW-24224,


TeamCity reports character set/collation mismatch error: database tables/columns have a character set or collation that is not the same as the default character set or collation in your database schema. You may see this message if you are using a non-unicode character set as default for your database as TeamCity enforces unicode charset for some of the varchar fields.

TeamCity displays ???? instead of national symbols


This applies to TeamCity 6.0 and above.

Resolve character set/collation-related problems

Character set/collation-related problems
Character set/collation-related problems

To fix a problem, perform the following steps:

  1. Create a new database with the appropriate character set and collation.

    For the database-specific information, see PostgreSQL, MySQL
    MS SQL. If you are using MySQL or MS SQL, we recommend using the case-sensitive collation to avoid issues with agents on Unix-like OS

    We recommend using a unicode case-sensitive collation: see instructions for PostgreSQL, MySQL and MS SQL. For MySQL, UTF8_bin or UTF8MB4 is preferred. 


    See also PostgreSQLMySQLMS SQL documentation for details on character set.

  2. Copy the current <TeamCity Data Directory>/config/database.properties file, and change the database references in the copy to the newly created database.

  3. Stop the TeamCity server.
  4. Use the maintainDB tool to migrate to the new database:

    Code Block
    maintainDB migrate [-A <path-to-data-dir>] -T <new-database-properties-file>

    Depending on the size of your database, the migration may take from several minutes to several hours. For more information on the maintainDB tool, see this section.

  5. Upon the successful completion of the database migration, the maintainDB tool should update the <TeamCity Data Directory>/config/database.properties file with references to the new database. Ensure that the file has been updated. Edit the file manually if the tool fails to do it automatically.
  6. Start the TeamCity server.