Updated PDQ Inventory, now it doesn't start.
braxen+pdq
Updated to 16.6, seems like it didn't do a database migration correctly.
C:\Program Files (x86)\Admin Arsenal\PDQ Inventory\CrashLog-PDQInventoryConsole-2019-02-07T12_53_18.8750152+01_00.txt
UNIQUE constraint failed: Versions.Version
Database = C:\ProgramData\Admin Arsenal\PDQ Inventory\log.db
Error Code = SQLITE_CONSTRAINT
SQL = create unique index if not exists UX_Versions_Version on Versions (Version)
Column Names = Versions.Version
Sqlite Connection Elapsed = 00:02:05.9485602
UNIQUE constraint failed: Versions.Version
Database = C:\ProgramData\Admin Arsenal\PDQ Inventory\log.db
Error Code = SQLITE_CONSTRAINT
SQL = create unique index if not exists UX_Versions_Version on Versions (Version)
Column Names = Versions.Version
Sqlite Connection Elapsed = 00:02:05.9485602
It doesn't start at all, just throws an application error in the event viewer. What do i do from here? Repair in installer doesn't help.
0
Comments
I deleted the log database and now it works. Great job.
Yeah, sorry about that. This is a bug we're investigating. You found our recommended workaround of deleting/renaming the log.db file.
Isn't the bug because you already have an unique id named IX_Versions_Version? Or some collision like that.
Just thought I'd chime in as well. I was running version 16.5 and trying to run the installer to 16.6. The installer would simply crash after I consented to the UAC prompt. I saw the above comments and renamed the log.db file and everything ran smoothly thereafter.
FYI, the information from the Windows event log:
Event #1/3:
Event #2/3:
Event #3/3:
what was the ultimate solution to this? I have been back and forth with support, including a db repair and upload. Issue persists. I also tried to do a db restore from a recent BU, no dice. Also tried deleting the log file, same result. The tech I have been working with is great I just wanted to see if there was something else I can try while the issue is being looked at on PDQs side. Thanks
It looks like you were actually running into a different problem. Your database had a null entry in the AutoReports table that the console didn't know how to handle. Hopefully the fixed database Solutions sent you solves the problem 😃