Getting 4.5.1 running on SQL Server 2005 Express

I'm having no luck getting TeamCity running on SQL Server 2005 Express.  I followed the steps described in Setting up an External Database and the "Switch to Another Database" section of Migrating to an External Database.  This is what my database.properties file looks like:

driverName=net.sourceforge.jtds.jdbc.Driver
connectionUrl=jdbc:jtds:sqlserver://example.com:1433/TeamCity;instance=SQLExpress
connectionProperties.user=teamcity
connectionProperties.password=te@mc1ty

maxConnections=50
poolPreparedStatements=true


The SQL Server 2005 Express database is the default installation, the TeamCity database is using the SQL_Latin1_General_CI_AI collation, and the JDBC driver is jTDS 1.2.2. The user, teamcity, has login permissions to the database and I can log in with this user and run CREATE TABLE statements.

When I start the TeamCity service, it prompts me to accept the EULA and set up an Administrator password.  However, when I log in and switch to the Administration menu the following message appears at the top of the page:

"The server currently uses the internal storage engine. For production purposes it is highly recommended to use a standalone database which provides better stability as the storage engine. Please refer to TeamCity online documentation for migration instructions."

This message appears no matter what combination of port or no port or connectionProperties.instance= or ;instance= provided.

Frustratingly, there is no indication that the software even tried to connect to the SQL Server 2005 Express database.  There are no logging messages that I've found.


JetBrains claims that this configuration is supported, so what am I doing wrong?

Cheers,
Frustrated in Frankfort

2 comments
Comment actions Permalink

Well, I was talking with some other folks here, and they noticed that the database.properties file was actually database.properties.txt.  After fixing that (really annoying default Windows setting), I ran into an Apache error, "The requested resource() is not available."  According to another forum post, this appears to be some kind of Java issue.  In that post, the person having the problem gave up and reinstalled from scratch to solve the issue. I guess I'll go that direction.

0
Comment actions Permalink

Can you attach your server logs? Probably there are some exceptions which can help to locate the cause of the problem.

0

Please sign in to leave a comment.