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.
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.
The standard CMD line method is as follows:
- In Windows Services (services.msc), stop the Capture Services service if it is running.
- If this is a new implementation of PSIcapture, skip to step 6; if batches or Capture Profiles already exist in this environment, continue with step 3.
- In Windows File Explorer, navigate to C:\ProgramData\PSIGEN\Capture.Services\configuration.
- Rename configuration.mdf and .ldf.
- Repeat steps 3 and 4 for BatchManager.mdf and .ldf found at C:\ProgramData\PSIGEN\Capture.Services\Batch Manager.
- Still in File Explorer, navigate to C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft.
Note: Since config and systemprofile are protected directories, it may be necessary to start at the System32 directory and then double-click each additional directory; if prompted, click to allow access to the directory.
- Rename the Microsoft SQL Server Local DB directory.
- Download and extract PSTools link: DOWNLOAD
- Open a command prompt and type the following:
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.
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"
- Restart Capture Servicess in Windows Services. After several moments, new configuration and BatchManager files should be created in the directories noted in steps 2 and 4.
- If this is a new implementation, skip to step 17. If not, continue with step 12.
- In Windows Services, stop the Capture Services.
- In File Explorer, under C:\ProgramData\PSIGEN\Capture.Services\configuration, delete the newly-created configuration.mdf and .ldf files.
- Rename the original configuration.mdf and .ldf files to their former names.
Example: configuration_OLD.mdf to configuration.mdf
- Repeat steps 14 and 15 for the BatchManager files under C:\ProgramData\PSIGEN\Capture.Services\Batch Manager.
- Start the Capture Services.
- Try to open PSIcapture again, and it should now launch successfully.
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.
Article is closed for comments.