[Solved] MSSQL DB connection error

Unimus support forum
Post Reply
kra
Posts: 2
Joined: Tue Feb 10, 2026 11:35 am

Thu Feb 26, 2026 9:23 am

Hi

We have updated our DB user password and now the Unimus software does not want to create a connection to the MSSQL DB.
we updated the password via ssms and verified SQL logon capability and then updated the unimus.properties with the new verified password and restarted the MSSQL server .
Windows firewall is disabled and the sql server has allow TCP/IP setting enabled and ports are correct as well


this is the error message:
2026-02-26 08:27:19.309 ERROR 4756 --- [task-1] .s.b.b.s.DatabaseConnectionCheckBootStep : Database 'net.unimus.data.database.config.MSSQLConfig@86881' connection test failed. Reason = 'org.springframework.jdbc.CannotGetJdbcConnectionException: Failed to obtain JDBC Connection; nested exception is com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host 127.0.0.1, port 1433 has failed. Error: "Connection refused: getsockopt. 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.".'

this is the unimus.properties:
# Unimus config file

# License key used by Unimus
license.key =valid license key

# Database type, valid values are HSQL,MARIADB, MSSQL, MYSQL, POSTGRESQL
database.type =MSSQL

# Specify the file system directory path, relevant only for HSQL database
database.path =

# Database host, relevant only for MARIADB, MSSQL, MYSQL, POSTGRESQL databases
database.host =127.0.0.1

# Database port, relevant only for MARIADB, MSSQL, MYSQL, POSTGRESQL databases
database.port =1433

# Database schema name, relevant only for MARIADB, MSSQL, MYSQL, POSTGRESQL databases
database.name =fw_back

# User name to use when connecting to database, relevant only for MARIADB, MSSQL, MYSQL, POSTGRESQL databases
database.user =unimus

# Password to use when connecting to database, relevant only for MARIADB, MSSQL, MYSQL, POSTGRESQL databases
database.password =updated db user passsword

# Key used to encrypt sensitive data
database.encryption.key =encryption password

# Defines each logging file size in MB, valid values are 1 ~ 2047
logging.file.size = 50

# Defines the number of maximum logging files, valid values are 2 ~ 2147483647
logging.file.count = 9

# Core connection server port
core.connection.server.port = 5509
Tommy.c
Posts: 68
Joined: Fri Jan 31, 2025 6:52 pm

Thu Feb 26, 2026 11:20 pm

Looking at the logs, it seems like something is blocking Unimus from even connecting to the MSSQL port. Is 127.0.0.1 allowed as a host for the MSSQL config? (I know this is something for PosgreSQL, I am not 100% on MSSQL)

How are you validating that the Service is accessible? Is it with another application on the same machine connecting to 127.0.0.1?

Here are some shots in the dark:

Have you restarted the Unimus Service?

Also, are there any goofy characters in the password for MSSQL DB? It shouldn't matter, but I know I have seen this pop up in other situations.
kra
Posts: 2
Joined: Tue Feb 10, 2026 11:35 am

Tue Mar 03, 2026 9:18 am

even though i had it up and running in the listed config, changing the localhost ip to its actual present ip address in the properties combined with a reboot of the sql server services and the unimus service fixed the issue.
thanks for the tip :)
Post Reply