SQL Local DB 2017 - Capture Services Fails to Start/Crashes - PSIcapture 7.8+



This article is a troubleshooting guide for PSIGEN support staff or authorized PSIGEN partners and IT associates representing customers. It covers the installation of SQL Local Database (DB) as a critically necessary component of PSIcapture. Explore the guide below to determine the best method for ensuring that SQL Local DB is properly installed on your system.


Important Note:

Multiple instances of SQL Local DB may or may not be supported at this time. Install the relevant SQL Local DB Instance for your version of PSIcapture and OS. If you encounter problems while multiple SQL Local DB instances are present, see the note "Encountering Errors" below.


PSIcapture 7.4+ requires the specific SQL Local DB Version listed below on the corresponding operating systems:

Windows 10 - SQL Local DB 2017
Server 2016 - SQL Local DB 2017
Server 2019 - SQL Local DB 2017


Please use the method below to troubleshoot this issue.


CMD Method

The standard CMD line method is as follows:

  1. Download and extract PSTools link: DOWNLOAD
  2. Open a command prompt and type the following:
  3.      cd [extracted PSTools path]

         psexec -i -s cmd.exe

         (on the subsequent CMD window, elevated to NT AUTHORITY)
    sqllocaldb info "MSSQLLocalDB"

         (If this shows "Instance not created" continue with:)
         sqllocaldb create "MSSQLLocalDB"

    (If this shows "Instance is corrupted" continue with:)
    sqllocaldb delete "MSSQLLocalDB"
    sqllocaldb create "MSSQLLocalDB"
  4. Restart capture services under services.msc. and ensure they stay on and generate the configuration.mdf, batchmanager.mdf, etc.
  5. NOTE: The syntax for the SQL Local DB 2014 and 2017 are identical, using "MSSQLLocalDB" as the instance name. This can cause some problems in some environments, as stated below.

Encountering Errors:

If encountering errors during the CMD prompt entries like so:


There may be another instance of SQL Local DB present that is throwing these errors. Check your Windows Event Viewer logs for entries from SQL Local DB instances that do not align with your version.


Was this article helpful?
3 out of 3 found this helpful



Article is closed for comments.