Icon

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 TeamCity 2018.1 documentation or refer to the listing to choose the documentation corresponding to your TeamCity version.

 

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Configuring server memory settings
Reporting server slowness issues

Back to top

Anchor
failsInTeamCityButNotLocally
failsInTeamCityButNotLocally
 
Anchor
Build fails or behaves differently in TeamCity but not locally
Build fails or behaves differently in TeamCity but not locally

...

If the build succeeds from the console but still fails in TeamCity, please use a command line runner in TeamCity to launch the same command as in the console. If it still behaves differently in TeamCity, most probably this is an environment or a tool issue.
If the command line runner works but the dedicated runner does not while the options are all the same, please create a new issue in our tracker detailing the case. Please attach all the build step settings, the build log, all agent logs covering the build, the command you used in the console to run the build and the full console output of the build.

Wiki Markup
{hidden-data}
A bit related: way to disconnect from the Windows remote desktop but leave the screen "attached": [http://support.smartbear.com/viewarticle/30747/]
{hidden-data}

Back to top

Build is slow under TeamCity

If you experience slow builds, the first thing to do is to check the build log to see if there are some long operations or the time is just spread over the entire process.
You can compare build logs of slower and faster builds to figure out what the difference is.
You can also run the build from the console on the same machine as detailed above to see if there is any difference between the build run from the console and the build in TeamCity.

...

If you cannot find the cause of the delayed agent upgrade in the logs, contact us and provide the full agent and server logs. Please also check/include the state of the agent processes (java ones) on the agent machine.
Back to top

Artifacts of a build are not cleaned

...

  • the cleanup rules of the build configuration in question, artifacts cleanup section
  • presence of the icon "This build is used by other builds" in the build history line (prior to Pin action/icon on Build History)
  • build's Dependencies tab, "Delivered Artifacts" section. For every build configuration, check whether "Prevent dependency artifacts clean-up" is turned ON (this is default value). If it is, then the build's artifacts are not cleaned because of the setting.
    Read more on cleanup settings.

Back to top

Database-related issues

"out of memory" error with internal (HSQLDB) database

...

  1. Create a new database with the appropriate character set and collation. We recommend using a unicode case-sensitive collation: see instructions for PostgreSQL and MySQL.  For MySQL, utf8_bin or utf8mb4_bin is preferred. 

    Note

    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.

Back to top

MySQL exception: Specified key was too long; max key length is 767 bytes 

...


The parameters above have the following default values:

 MySQL 5.5.59MySQL 5.6.39MySQL 5.7.21MariaDB 5.5.58 MariaDB 10.0.33 MariaDB 10.1.30 MariaDB 10.2.12
innodb_large_prefix 0010001
innodb_file_formatAntelope Antelope BarracudaAntelope Antelope Antelope Barracuda
innodb_file_per_table0111111

...

For MySQL 5.7+ and MariaDB 10.2+ use the defaults, no changes are required.

Back to top

'This driver is not configured for integrated authentication' error with MS SQL database

...

    • either set the TEAMCITY_JRE environment variable
    • or remove the JRE bundled with TeamCity from <TeamCity home>\jre and set JAVA_HOME.

      Note

      Note that on upgrade, TeamCity will overwrite the existing JRE with the default 32-bit version, so you'll have to update to the 64-bit JRE again after upgrade.

      See also this related external posting.

Back to top

Protocol violation error (Oracle only)

...

It makes sense to check if the server-side settings.xml files contain correct information about remote repositories, proxies, mirrors, profiles, credentials etc.

Back to top

Anchor
Critical error in configuration file
Critical error in configuration file

...

VCS root with id "XXX" does not exist
The build configuration or template reference a VCS root which is not defined in the system.
Remedy actions: Restore the VCS root or create a new VCS root with the id noted or edit the file noted in the message to remove the reference to the VCS root.

Back to top

TeamCity installation problems

If the TeamCity Web UI cannot be accessed after installation, you might be running TeamCity on a port that is already in use by another program. Check and configure your TeamCity installation.

Back to top

Problems with TeamCity NuGet Feed

...

For earlier versions, refer to this section.

Back to top 

Problems with .Net-related TeamCity Tools

...

    1. Add the following setting described in the Microsoft documentation to the machine.config file on all agents:

      Code Block
      <configuration>
      	<runtime>
      		<generatePublisherEvidence enabled="false"/>
      	</runtime>
      </configuration>

      You can modify the machine.config file as described in this external blog post and pass this config file to all agents, e.g. using a custom script.

    2.  Alternatively, upgrade .Net Framework on the TeamCity agents to version 4.0 and above. Details are available in the Microsoft documentation

Back to top