I am going through the setup wizard to connect Bitbucket to MS SQL. However, when I enter the details of the DB server, I keep getting the following:
The configuration entered is not valid. A database connection could not be established. Please check your configuration and try again. com.atlassian.stash.internal.db.DefaultDatabaseManager.validateConfiguration(DefaultDatabaseManager.java:217) com.atlassian.stash.internal.migration.DefaultMigrationService.validateConfiguration(DefaultMigrationService.java:85) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ... Could not get JDBC Connection; nested exception is com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host DELTONEFS, port 1433 has failed. Error: "connect timed out. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall.". org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:80) com.atlassian.stash.internal.db.DefaultDatabaseValidator.validate(DefaultDatabaseValidator.java:44) com.atlassian.stash.internal.db.DefaultDatabaseManager.validateConfiguration(DefaultDatabaseManager.java:214) ... The TCP/IP connection to the host DELTONEFS, port 1433 has failed. Error: "connect timed out. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall.". com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(SQLServerException.java:191) com.microsoft.sqlserver.jdbc.SQLServerException.ConvertConnectExceptionToSQLServerException(SQLServerException.java:242) com.microsoft.sqlserver.jdbc.SocketFinder.findSocket(IOBuffer.java:2369)
I am able to connect to the DB from another machine with the same information so not sure what I am missing.
If the same settings work on another jdbc based connection, then it's your firewalls or network settings.
If your other system is not using identical methods to connect (by which I mean Bitbucket has a connection string, username, password etc, and your other system is using a different format like host, port, username, password, or something else), then can you show us the comparison you've made? What do they both look like?
That's two problems it might have.
Unfortunately, without knowing the setup or doing further testing we can't know what the problem is on the poster's system.
Plus, they're on MS-SQL, so neither point really applies as MS-SQL doesn't use my.cnf and Windows firewalls are not based on iptables.
Ok, I had the wrong idea there, but the first screenshot makes it clear.
You've not entered a host name in the host name field. You've put in a connection via lookup name, which is useless for looking up the name of the database server on the network.
Try changing it to the name of the database server. Or even the ip address if you're not sure.
I am sorry, I was unclear.
What do the MS-SQL Server logs say the problem is? Why is the server choosing to reject the connection?
What you call MS-SQL is a client that doesn't use the plain basic connection settings that the jdbc driver does, so it's not really a good test of the settings you have.
I was finally able to connect to the database with the help of the following article:
My MS SQL is a named instance so after creating the bitbucket.properties file with the info from the link and restarting the service, it connected to the database.
Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs