The current error message for SQL connection failures during for example “updatedb” is very generic and from my perspective misleading. It implies more of a connection issue, but is also used when the database has the wrong permissions on the database.
As an example, this here is the error I received in such a case:
Unhandled exception. System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 40 - Could not open a connection to SQL Server) at Bit.Setup.Program.MigrateDatabase(Int32 attempt) in /home/runner/work/server/server/util/Setup/Program.cs:line 196 at Bit.Setup.Program.Update() in /home/runner/work/server/server/util/Setup/Program.cs:line 143 at Bit.Setup.Program.Main(String args) in /home/runner/work/server/server/util/Setup/Program.cs:line 65 ClientConnectionId:00000000-0000-0000-0000-000000000000
This makes bugfixing harder than it has to be.