Q: I'm running SAP HANA or MSSQL and Boyum Server Components on different machines and get this message in my event logs.
B1UP Server Component version of the error:
SQL Server not installed locally (Service SQL Server (MSSQLSERVER) was not found on computer '.'.). Waiting for 220 seconds before starting the service (to avoid timeouts connecting to the SQL server)
Why is that?
A: This was part of a check we make in cases you are running MSSQL and Server Component and database are not the same machines. We added this warning by mistake to your Log file
(iPayment Server Component has never had the same issue). B1UP 2019.08 and higher will stop showing this wrong message and in all prior, the message can simply be ignored and there is no 220-second delay as the message states
Q: What happens if I have a non-running SQL server on the same machine as the Server Component that actually uses a SQL Server on another machine or HANA?
A: If there is a non-running SQL server on the machine there will be a 3-min delay in the Server Component starting up + this message is added to the log "SQL Server is not running, waiting for it to get online". So it will delay but not causes it to not work.
In a HANA case, there is no delay as the check simply checks if there is a Windows Service on the machine called "SQL Server (MSSQLSERVER)" and in such a case there is not.
Q: Why are you doing these checks in the first place?
A: This is done in that Server Component and SQL Server on same machine case, where the server is being restarted. Since the server components of Boyum are dependant of SQL Server, we need to be sure that that service is running prior to us starting. So the system checks that MSSQL Service is up and running and in case it is not it sleep for 3 minutes before starting its work (so SQL server have time to finish its startup)