Hi Mary

We didn't see such issue before, so I cannot say for sure what's the reason.

But as it's fresh installation, and you don't need to preserve data, let's delete it and allow the server to recreate configuration and database from scratch.

1. Stop TeamCity Web Server service.
2. Run <TeamCity Home>\bin\tomcat6w.exe //ES//TeamCity command. You'll need elevated administrative rights to do this. Start cmd.exe using Run as Administrator.
3. This dialog allows to configure the service settings. Go to Java tab, and within Java Options box find the last -Dteamcity.data.path property.
4. This is actual path where the service stores configuration. If you need to change it, you can modify the path here. At the moment our installer suggests a location within user profile by default, but I recommend to change it to C:\TeamCity\.BuildServer (or other folder if you changed installtion path).
5. Find this dolder on the disk and delete it. At next start the server will completely recreate it.
6. Check that the service account (or SYSTEM, as default) has enough permissions to modify files there.
7. Start the service.

Hi Michael,

We tried but didn't work. We still get the same error.

Version 5.1.5 is working without error.

Attached the log file, please check it.

Regards,

Mary

Mary,

Thanks for the log. We'll need some additional information:

1. Output of dir D:\TeamCityServerConfiguration\system command - a list of files there with its size
2. Content of D:\TeamCityServerConfiguration\system\buildserver.script file

Hi Michael,

This is the directory listing:

Directory of D:\TeamCityServerConfiguration\system

02/09/2011  09:57 AM    <DIR>          .
02/09/2011  09:57 AM    <DIR>          ..
02/08/2011  01:36 PM             4,603 buildserver.backup
02/08/2011  01:33 PM         1,048,576 buildserver.data
02/09/2011  09:57 AM                 0 buildserver.lck
02/09/2011  09:57 AM               150 buildserver.log
02/09/2011  09:57 AM               492 buildserver.properties
02/08/2011  01:36 PM            23,111 buildserver.script
               6 File(s)      1,076,932 bytes
               2 Dir(s)  155,785,076,736 bytes free

Hi Mary

Unfortunately, I still cannot reproduce this behavior.
From these logs I can see the database is created successfully, but the server cannot access it later.

Could you change a Data directory to a location on C: drive? Just for test, we'll move it to desired place later.

Also, you said version 5.1 was used before. Was it installed on the same machine? Did you uninstall it or just point 6.0 installer to a new location?

Thanks

Hi Michael,

We also installed TeamCity 2 times in C drive after that we installed it to D drive. So that does not solve the problem.

After 3 or 4 clean installation, we downloaded 5.1.5 version, uninstalled TC6 and installed version 5. We used the same machine but got the same error message about TC6 in 2 different machines.

Thanks

Hi Mary

Sorry to hear you still experience this issue. We'd like to help resolve it, but will need additional input.
Please

1. Stop TeamCity Server service
2. delete data directory (D:\TeamCityServerConfiguration) from disk
3. Start the service
4. Reproduce the issue
5. Ensure the service is stopped
6. Archive content of D:\TeamCityServerConfiguration folder and upload it to our ftp, here are instructions.

and also, all the files from <TeamCity Home>\logs fiolder.

Thanks!

Hi Michael,

Suprisingly it works. An "Upgrade" console window appeared and it worked after that.

Anyway thanks for your help

Hi

Glad to hear it resolved now. Fell free to ask any other any other questions you may have.
As you can see, problems like that could take a time, if they are not reproduced easely. But I'll do my best.

Thanks
Michael

Hi Michael,

I am having this same issue after I have installed a clean copy of TeamCity. I get following exception :

java.lang.IllegalStateException: Could not write version - no version table.
   at jetbrains.buildServer.serverSide.db.DBSchema.writeDatabaseVersion(DBSchema.java:228)
   at jetbrains.buildServer.serverSide.db.DBSchema.populateWithInitialData(DBSchema.java:145)
   at jetbrains.buildServer.serverSide.db.DBSchema.createSchema(DBSchema.java:170)
   at jetbrains.buildServer.serverSide.db.TeamCityDatabaseManager$2.run(TeamCityDatabaseManager.java:468)
   at jetbrains.buildServer.serverSide.db.TeamCityDatabaseManager.withMaintenanceDBF(TeamCityDatabaseManager.java:444)
   at jetbrains.buildServer.serverSide.db.TeamCityDatabaseManager.createNewSchemaWithInitialData(TeamCityDatabaseManager.java:466)
   at jetbrains.buildServer.serverSide.versioning.VersionManager.ensureActualDatabase(VersionManager.java:434)
   at jetbrains.buildServer.rootDispatcher.TeamCityDispatcherServlet.processStartupServerInternal(TeamCityDispatcherServlet.java:145)
   at jetbrains.buildServer.rootDispatcher.TeamCityDispatcherServlet.processStartupServerSafe(TeamCityDispatcherServlet.java:263)
   at jetbrains.buildServer.rootDispatcher.TeamCityDispatcherServlet.access$400(TeamCityDispatcherServlet.java:183)
   at jetbrains.buildServer.rootDispatcher.TeamCityDispatcherServlet$5.run(TeamCityDispatcherServlet.java:2)
   at java.lang.Thread.run(Unknown Source)

I am trying to evaluate TeamCity for our company but no luck so far. What do you suggest?

Regards

please find my andswer in the separate thread