Visual Pursuits ICM Install LocalDB

If you are installing the Image Competition Manager (ICM) program on a new computer, you must first install the Microsoft SQL Server Express LocalDB program. This program is a database that manages the competition data on your computer.

Sometimes the LocalDB program does not install properly or cannot start. Be sure to follow the instructions on installing the LocalDB program. You find these using your website menu "Help", "Install the Image Competition Manager".

If you still have trouble, start a "command prompt" and enter "sqllocaldb create MSSQLLocalDB". This should help resolve the issue.

A different issue can occur when placing the ICM data folder on a drive with a sector size larger than 4096 bytes.   There is a known issue where Windows 11 mis-reports the sector size on some SSD drives.   The issue only really shows up when upgrading from Win10 to Win11. You could search for a command that shows the correct sector size to see if this is your problem.

The safest place to store your ICM data without encountering problems is to use C:\ICMData. Other drives might have incompatibilities. 

To reset where your ICM database and folder are located you need to delete the ICM configuration file. Delete C:\Users\Public\Software Pursuits\Image Competition Manager3.ICM3.config. When you start the ICM program again it will prompt you for your data folder location.

More troubleshooting from an API search:

1. Check the LocalDB Instance:
   • Open a command prompt and run sqllocaldb info MSSQLLocalDB to verify the instance exists and is in a stopped state.
   • If it doesn't exist, try recreating it using sqllocaldb create MSSQLLocalDB.
   • If the instance is stopped, attempt to start it using sqllocaldb start MSSQLLocalDB.
2. Recreate the LocalDB Instance:
   • Delete the existing instance by running sqllocaldb delete MSSQLLocalDB.
   • Create a new instance using sqllocaldb create MSSQLLocalDB.
3. Verify LocalDB Installation:
   • Check if LocalDB is installed correctly on your system.
   • Run sqllocaldb v to see installed instances.
4. Check LocalDB Log Files:
   • Look for errors or warnings in the LocalDB log files, typically located in C:\Users\<YourUsername>\AppData\Local\Temp\.
5. Adjust Registry Settings (Windows 11 with SSD):
   • If you're on Windows 11 with an SSD, particularly a Samsung one, and suspect sector size compatibility issues, follow the registry modification steps outlined in the provided Reddit thread to force a 4KB sector size.
6. Use SQL Server Configuration Manager:
   • Open SQL Server Configuration Manager and review the configuration settings for the LocalDB instance.
7. Check System File Permissions:
   • Ensure that system file permissions haven't been tampered with, potentially affecting registry access.
8. Run System File Checker (SFC):
   • Use the sfc /scannow command in an elevated command prompt to scan and repair corrupted system files.
9. Update Windows:
   • Make sure your Windows system is up-to-date, as pending updates might include fixes for LocalDB compatibility issues.
10. Check for Conflicting Software:
    • If the error occurs after installing a new program, consider uninstalling it to see if it resolves the issue. 

• Registry changes: Modifying the registry can be risky. Always back up your registry before making changes.
• Specificity of the error: The exact file or key that RegOpenKeyExW cannot find might not be explicitly stated in the error message. You may need to investigate further to pinpoint the missing element.
• If you're unsure: Consult with a qualified IT professional or the Microsoft support resources for further assistance.