The SQL LocalDB instance 'RedGateTemp' does not exist
Published 10 March 2016
The following error text appears when running a DLM Automation PowerShell cmdlet or add-on:
Error message
... The SQL LocalDB instance 'RedGateTemp' does not exist ...
Cause
Your RedGateTemp instance may be corrupt. This is a known issue with LocalDB.
Fix
Delete the corrupt RedGateTemp instance from LocalDB. DLM Automation will recreate this when needed.
If you're using an external tool, such as TeamCity, you'll need to log on to the same account the service uses before deleting the RedGateTemp instance.
Find what account the external tool is using:
- In the Windows Start menu, enter services.msc.
- Find the external tool, and note the entry in the Log On As column. In this example, the TeamCity build agent is running under "Local System":
Use Microsoft's PsExec tools to log on to the account the external tool is using:
- Download and unzip PsTools, which contains PsExec. See Using PsTools.
- Open an elevated command prompt.
- In the Windows Start menu, type cmd
- Right-click on the command prompt program and select Run as administrator.
- Using the command prompt, navigate to the PsExec download location.
- Enter one of the following commands, depending on which account you need to run to configure the build agent:
- For Local System, enter
psexec -i -s cmd.exe - For Local Service, enter
psexec -u "nt authority\Local Service" cmd.exe - For other accounts or for more information about using PsExec, see PsExec.
- For Local System, enter
- A new command prompt is displayed. You should be logged on to the correct account for your external tool. To check this, enter
whoami
You can now delete the RedgateTemp instance:
- At the command prompt, enter
SqlLocalDB.exe info RedGateTempIf an error message is displayed containingLocalDB instance "RedGateTemp" is corrupted!, delete the instance. Enter
SqlLocalDB.exe delete RedGateTempEnter
SqlLocalDB.exe infoto display a list of instances. Check that the RedGateTemp instance no longer exists.
You can now try running the process again. The instance should be created automatically without corruption errors.
If you're still experiencing issues with LocalDB, contact Redgate Support.
