Why dose the Confluenc service doesn't connect to my MS SQL Database?

[it]

Hi,

I recently migrated my H2 Database to a MS SQL Database. Because of the Server configuration I had to use an Domain-User. I followed this issue and combined it with this Articel to get a connection.

After that the installation and dataimport finished without problems. Then I installed the Confluence-Service. When I tried to start Confluence through the service I got an error message:

The startup_bundled_jre.bat starts Confluence as intended. I suspect the login data is not used correctly from the service, until now I wasn't able to solve the problem.

Can someone help me please?

Thanks!

[repi · Accepted solution]

Have you checked the 3 points of the error message?
The DB user used by Confluence must have rights in the Confluence DB as Admin

How did the H2 to MS SQL migration take place?

[it]

Hi,

thank you for your answer.

I created an XML backup file and copied the attachment folder. Douring reinstallation of Confluence an Import backup option appeared that I used.

The Database is running. The DB user used by Confluence has rights as Admin and like I said when I use the startup_bundled_jre.bat Confluence is functioning as intended. Confluence receives a connection and all imported Data is available.

Only if I try to start Confluenc as a Service I get this problem. Is it correct that the Service uses the same connection information as the startup_bundled_jre.bat?

[repi]

You seem to have set up the service incorrectly. The start parameters are either incorrect or incomplete.

Are you sure you followed these instructions?

https://confluence.atlassian.com/doc/start-confluence-automatically-on-windows-as-a-service-172071.html

https://confluence.atlassian.com/doc/setting-the-java_home-variable-in-windows-8895.html

[it]

Hi,

thank you for your replay.

I figured out a solution for my problem. My mistake was the login information for the Confluence service. If you look at the “Log On”-Tab of the service properties, you can change the executing account. By default, the Local System account is selected. I had to change the account to the domain user with database rights. Additional I extend the account rights to a degree that the user could log on as a service.