IT Console Purchase GoMyid Remote Desktop

DeskGate troubleshooting and administration

SQL Database Test Failed

Check the fixed instance, credentials and saved connection before retrying server setup.

Maintained by DeskGate · Updated October 6, 2026

  1. 1. Identify the stage

    Separate SQL installation from the database connection test.

  2. 2. Check the connection

    Verify the instance and credentials privately.

  3. 3. Confirm the result

    Require the database test to pass before continuing.

Recognize the symptom

This guide applies to the customer GoMyid Server by DeskGate Release setup. The SQL step either cannot continue, reports a SQL installation failure, or fails the database/Sql.udl connection test. Record the exact message first: these are different stages and need different checks.

Check the SQL screen

Release SQL setup with fixed GOMYID instance and password confirmation
Actual installer in non-installing preview mode; example values and success messages are illustrative. Open the image for its original size.
  1. Next is disabled: enter both password fields. They must be nonempty and match exactly, including case.
  2. An existing instance is present: the Release installer reuses local GOMYID. Enter its current sa password; setup does not reset it.
  3. SQL must be installed: the separately supplied SQLEXPR_x64_ENU-2022.exe must be beside GoMyidSetup.exe. Follow the error dialog’s exit code and setup-summary details when installation fails.
  4. The database test fails: confirm that the GOMYID SQL service is running and that the supplied credentials are correct. Check the exact saved-connection error before changing a provider or configuration file.

Distinguish the database from the web interface

Setup prepares Sql.udl and reuses an already attached GoMyid database. A missing or inaccessible connection file can prevent the application from connecting even when an administrator can open SQL in another tool. Check the selected installation folder and the permissions used by the application.

If installation reaches the web checks, a login-page response alone is not enough. The registration/database check must also succeed. Do not treat a page that loads as proof that the database is healthy.

Verify the fix

Repeat the failed step after correcting the identified cause. Continue only when the wizard reports DATABASE: TEST COMPLETE, then let the remaining installation checks finish. The example status in a screenshot is not a test result from your server.

Do not delete an existing database, reset a password or run unrelated scripts merely to bypass an error. If unresolved, send support the release, failed stage, timestamp and sanitized error. Never include an unredacted Sql.udl or installation report: it can contain the actual password.

Continue setup

Full SQL setup walkthrough