SQL database does not exist error

Microsoft SQL Kingdom projects in Auto SQL Server Express (SSE) mode need to be attached before you can link the projects in Insight (see Downloading and Installing SQL Server). Kingdom does this automatically, thus a project can be left open in Kingdom and then connected to Insight, or manually attached (see Manually Attaching Kingdom SQL Database).

This error is coming from the SQL server used to access data from your Kingdom project. The error says the server is unable to access the Kingdom database because the path to the database file (.mdf) on the specified drive is no longer valid. There are two possible reasons for this:

  • If this network drive is no longer available, or if the location of the kingdom project has changed, you would get this error message. You may need to check with your IT support for help with this.
  • If you did not manually attach the Kingdom database, the project must be open in Kingdom when you connect to the database from Insight. This error will appear if you try to connect to the database without Kingdom running. To connect without Kingdom running, the project has to be manually attached (see Manually Attaching Kingdom SQL Database).

Note: If you no longer need to access data from the kingdom database you can disconnect the link and the error will no longer appear.

Genuine offer of assistance

If the problem persists, or if you have any questions, please contact our support team at [email protected].

You may be asked to send data of your session from the Logs window for a clearer picture of what happened when the error occurred (see Viewing and Sending Diagnostic Logs).