Overview
The error messages referencing the "Failed to connect to a server" issue are usually caused by insufficient permissions of the current Windows login on specific folders/files, and that could be fixed as described in this knowledge base article.
If permissions are corrected, however, the error persists, then the next step would be to check the status of the LocalDB server. This is explained in the second knowledge base article.
If there are still issues, then re-installation of the Microsoft SQL Server LocalDB is very likely required.
This article provides guidance on how to manage LocalDB, including installation and some basic operations.
Checking if LocalDB is already Installed if it is, then its Presence and Status
These commands below will list all LocalDB instances and installed versions.
Potentially more than one instance of the LocalDB (MGFFT now use the 2019 LocalDB)
Using Command Prompt
sqllocaldb info
sqllocaldb versions
Using PowerShell
# Check LocalDB instances
& sqllocaldb info
# Check specific instance
& sqllocaldb info "GBSQL2019"
# Check the registry for installed versions
Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Microsoft SQL Server Local DB\Installed Versions\*"
After we confirm from the above steps that GBSQL2019 exists but somehow managed to misbehave, there are two ways to fix this.
The First option:
Manually uninstalling (LocalDB)GBSQL2019
- Open the Control Panel.
- Go to Add or Remove Programs.
- Look for Microsoft SQL Server or LocalDB in the list of installed programs.
- Select the Uninstall option and follow the prompts to complete the uninstallation process.
Re-installing LocalDB:
- Download the latest version of LocalDB from Microsoft SQL Server Downloads
- Choose the correct architecture (x86 or x64) and SQL Server version.
- Run the downloaded installer file and select the "LocalDB" installation option when prompted for the installation type.
- You can choose the desired installation location and other options as you need.
- The description of how to set the correct(expected by MGFFT) LocalDB name, start/stop the instance, etc., is in this knowledge base article.
The Second option:
Uninstalling the Micromine Geobank for Field Teams
Re-installing Micromine Geobank for Field Teams
This option is preferable as all the uninstalling and re-installing of the "LocalDB" happens in the background, with the correct name and state assigned as required.
Want to learn more?
Online Help Manuals - Click here for the latest version
Learning Management System - Click here to login or here to request access
Comments
0 comments
Please sign in to leave a comment.