Unable to complete setup: looping on "configure how Bamboo will connect to your database"

[Bob Rzadzki]

I've installed Bamboo 9.2.7 and am running into this issue while working through the setup wizard. "Enter license" and "configure instance" are completed with no issues. The "configure database" page is giving me problems.

I'm attemping to "Connect using JDBC," and have left the driver class name at the default provided. For the Database URL, I've entered our database server and the name of the empty database "Bamboo":

jdbc:sqlserver://xxx.yyy.zzz:1433;databaseName=Bamboo

For the user name and password, I'm using known-good credentials. The database is accessible over the network, because Bitbucket is running on this same machine and accessing it without problems.

When I click Continue, I'm taken to the page that reads "Please wait while Bamboo sets up your database..." This persists for 5-10 seconds and then bounces back to the "Configure how Bamboo will connect to your database" page. No error or additional information is displayed.

I have Java Run-time Environment 8u421 x64 installed, with JRE_HOME set to its base path, and the bin/ folder inside added to my system's PATH.

What am I missing?

[Shashank Kumar · Accepted solution]

Hello Bob,

Welcome to Atlassian community.

Looking at similar problems from past can you follow the steps from Errors in the database setup screen during the Bamboo Wizard's setup  to see if it helps resolved your problem.

If not can you provide check the logs at <bamboo-home>atlassian-bamboo.log file and see if you are able to spot any error post Bamboo is restarted.

Regards,

Shashank Kumar

[Bob Rzadzki]

Hi Shashank, thanks for reaching out.

I followed the steps in that post previously to no effect. Following your lead, I've resolved the database issue. Posting here for anyone encountering this issue in the future.

After the loop from the spinning wheel of configuration, back to the database details input page, the tail of atlassian-bamboo.log looks like this:

2024-09-16 18:19:37,235 INFO [mail-queue-processor] [EmailService$MailQueueProcessor] Successfully initialised mail queue processor
2024-09-16 18:19:38,808 INFO [performSetupDatabaseConnectionBackgroundThread] [RemoteAgentManagerImpl] Heartbeat timeout for remote agents: 600 seconds.
2024-09-16 18:19:38,991 INFO [performSetupDatabaseConnectionBackgroundThread] [TransportConnector] Connector vm://bamboo started
2024-09-16 18:19:41,151 WARN [performSetupDatabaseConnectionBackgroundThread] [ResourceResolver] Unable to find resource bamboo-capabilities.properties
2024-09-16 18:19:41,173 INFO [performSetupDatabaseConnectionBackgroundThread] [DefaultAgentCapabilityManagerImpl] Failed to load bamboo-capabilities.properties
2024-09-16 18:19:42,587 INFO [performSetupDatabaseConnectionBackgroundThread] [QuartzScheduler] Scheduler scheduler_$_NON_CLUSTERED started.
2024-09-16 18:19:42,598 INFO [performSetupDatabaseConnectionBackgroundThread] [DefaultHibernateConfigurator] Spring context refreshed after 38.54 s
2024-09-16 18:19:42,599 INFO [performSetupDatabaseConnectionBackgroundThread] [DefaultHibernateConfigurator] Creating Bamboo schema...
2024-09-16 18:19:43,413 INFO [performSetupDatabaseConnectionBackgroundThread] [DefaultHibernateConfigurator] Bamboo schema created.
2024-09-16 18:19:43,470 ERROR [performSetupDatabaseConnectionBackgroundThread] [SetupUtilityBean] Database configuration failed. Schema creation complete, but database tables don't seem to exist.
com.atlassian.config.bootstrap.BootstrapException: Schema creation complete, but database tables don't seem to exist.
 at com.atlassian.config.bootstrap.DefaultAtlassianBootstrapManager.bootstrapDatabase(DefaultAtlassianBootstrapManager.java:232) ~[atlassian-config-1.1.3.jar:?]
 at com.atlassian.bamboo.ww2.actions.setup.SetupUtilityBean.setupStandardDatabase(SetupUtilityBean.java:170) ~[atlassian-bamboo-web-9.2.7.jar:?]
 at com.atlassian.bamboo.ww2.actions.setup.SetupDatabaseConnectionAction.lambda$execute$0(SetupDatabaseConnectionAction.java:92) ~[atlassian-bamboo-web-9.2.7.jar:?]
 at com.atlassian.bamboo.setup.DefaultSetupPersister.executeSetupStep(DefaultSetupPersister.java:80) ~[atlassian-bamboo-web-9.2.7.jar:?]
 at com.atlassian.bamboo.ww2.actions.setup.SetupDatabaseConnectionAction.execute(SetupDatabaseConnectionAction.java:90) ~[atlassian-bamboo-web-9.2.7.jar:?]
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_202]
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_202]
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_202]
 at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_202]
 at ognl.OgnlRuntime.invokeMethodInsideSandbox(OgnlRuntime.java:1266) ~[ognl-3.1.29.jar:?]
 at ognl.OgnlRuntime.invokeMethod(OgnlRuntime.java:1251) ~[ognl-3.1.29.jar:?]
 at ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:1969) ~[ognl-3.1.29.jar:?]
 at ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:68) ~[ognl-3.1.29.jar:?]
 at com.opensymphony.xwork2.ognl.accessor.XWorkMethodAccessor.callMethodWithDebugInfo(XWorkMethodAccessor.java:98) ~[struts2-core-2.5.31-atlassian-1.jar:2.5.31-atlassian-1]
 at com.opensymphony.xwork2.ognl.accessor.XWorkMethodAccessor.callMethod(XWorkMethodAccessor.java:90) ~[struts2-core-2.5.31-atlassian-1.jar:2.5.31-atlassian-1]
 at ognl.OgnlRuntime.callMethod(OgnlRuntime.java:2045) ~[ognl-3.1.29.jar:?]
 at ognl.ASTMethod.getValueBody(ASTMethod.java:97) ~[ognl-3.1.29.jar:?]
 at ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:212) ~[ognl-3.1.29.jar:?]
 at ognl.SimpleNode.getValue(SimpleNode.java:258) ~[ognl-3.1.29.jar:?]
 at ognl.Ognl.getValue(Ognl.java:537) ~[ognl-3.1.29.jar:?]
 at ognl.Ognl.getValue(Ognl.java:501) ~[ognl-3.1.29.jar:?]
 at com.opensymphony.xwork2.ognl.OgnlUtil$3.execute(OgnlUtil.java:531) ~[struts2-core-2.5.31-atlassian-1.jar:2.5.31-atlassian-1]
 at com.opensymphony.xwork2.ognl.OgnlUtil.compileAndExecuteMethod(OgnlUtil.java:583) ~[struts2-core-2.5.31-atlassian-1.jar:2.5.31-atlassian-1]
 at com.opensymphony.xwork2.ognl.OgnlUtil.callMethod(OgnlUtil.java:529) ~[struts2-core-2.5.31-atlassian-1.jar:2.5.31-atlassian-1]
 at com.opensymphony.xwork2.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:438) ~[struts2-core-2.5.31-atlassian-1.jar:2.5.31-atlassian-1]
 at com.opensymphony.xwork2.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.java:293) ~[struts2-core-2.5.31-atlassian-1.jar:2.5.31-atlassian-1]
 at org.apache.struts2.interceptor.BackgroundProcess$1.run(BackgroundProcess.java:55) ~[struts2-core-2.5.31-atlassian-1.jar:2.5.31-atlassian-1]
 at java.lang.Thread.run(Thread.java:748) ~[?:1.8.0_202]
2024-09-16 18:19:43,702 INFO [http-nio-8085-exec-14] [SpringObjectFactoryProxy] Switching to Struts-Spring object factory
2024-09-16 18:19:43,703 INFO [http-nio-8085-exec-14] [SpringObjectFactory] Setting autowire strategy to name
2024-09-16 18:19:43,703 INFO [http-nio-8085-exec-14] [StrutsSpringObjectFactory] Struts-Spring integration initialised successfully

 Previously, I had been following migration guides, and so I skipped a step setting up the new database. This is the guide I followed which finally solved the database setup problem:

https://confluence.atlassian.com/bamboo/connect-bamboo-to-a-microsoft-sql-server-database-289276827.html

I strongly suggest to Atlassian to surface errors in the setup wizard in the interface itself. "Silent failure" is frustrating in the extreme. This error was my own fault, but the journey to find out why it was failing was way too long. Please, just put errors in the UI.

[Bob Rzadzki]

Per another answer on the forums here, I ran the following:

ALTER DATABASE Bamboo SET READ_COMMITTED_SNAPSHOT ON WITH ROLLBACK IMMEDIATE;

This no longer throws the wizard back to the previous page, but it has been on "Please wait while Bamboo configures your database" for a solid five minutes without creating any tables. Still stuck.