Team City acts like new install after server upgrade
We just upgraded our dev build server from Windows Server 2012R2 to Windows Server 2022. The Team City services and agents are running. However, when visiting the web UI, it acts like it's a fresh install (First Start screen shows). I compared the pre and post upgrade teamcity-startup.properties files, but neither have any configuration information in them. The volumes are all mapped to the same drive letters as before the upgrade. Any assistance with getting it to see the existing instance would be appreciated.
Please sign in to leave a comment.
Is it looking at the same database, with the same database content?
Correct. The database should be identical. I'm not a Team City expert. If you want to point me at the where that configuration is located, I can verify.
This is resolved. There was apparently a TEAMCITY_DATA_PATH that was set to D:\ProgramData\etc before the upgrade, but was reset to C:\ProgramData\etc after the upgrade. Thanfully one of our DevOps folks was familiar with Team City, found it, and was able to get this running again.