DIM log errors
Should I be concerned about this? Any suggested actions? There's like 50 of these in the log file.
2026-07-23 13:13:27.897 [INFO] :: Installing: 116048-1 : MGAB dForce Strand-Based Fringe Hair for Genesis 9 2026-07-23 13:13:45.990 [WARNING] :: ..\..\..\..\..\src\dzpostgresqlobjectdatabase.cpp(37): db fetch error: Attempt to convert null to long long 2026-07-23 13:13:45.990 [INFO] :: db fetch error: Attempt to convert null to long long 2026-07-23 13:13:45.991 [WARNING] :: ..\..\..\..\..\src\dzpostgresqlobjectdatabase.cpp(37): db fetch error: Attempt to convert null to long long 2026-07-23 13:13:45.991 [INFO] :: db fetch error: Attempt to convert null to long long 2026-07-23 13:13:45.993 [WARNING] :: ..\..\..\..\..\src\dzpostgresqlobjectdatabase.cpp(37): db fetch error: Attempt to convert null to long long 2026-07-23 13:13:45.994 [INFO] :: db fetch error: Attempt to convert null to long long ... 2026-07-23 13:13:46.293 [WARNING] :: ..\..\..\..\..\src\dzpostgresqlobjectdatabase.cpp(37): db fetch error: Attempt to convert null to long long 2026-07-23 13:13:46.293 [INFO] :: db fetch error: Attempt to convert null to long long 2026-07-23 13:13:46.300 [WARNING] :: ..\..\..\..\..\src\dzpostgresqlobjectdatabase.cpp(37): db fetch error: Attempt to convert null to long long 2026-07-23 13:13:46.300 [INFO] :: db fetch error: Attempt to convert null to long long 2026-07-23 13:13:46.310 [WARNING] :: ..\..\..\..\..\src\dzpostgresqlobjectdatabase.cpp(37): db fetch error: Attempt to convert null to long long 2026-07-23 13:13:46.310 [INFO] :: db fetch error: Attempt to convert null to long long 2026-07-23 13:14:10.652 [INFO] :: Install Successful: MGAB dForce Strand-Based Fringe Hair for Genesis 9

Comments
Not something I have seen.
What size does the file have?
Have you tried deleting it and redownload?
Considered if it could be a case of a 0 kB file.
I'm reinstalling my entire library because I lost the DIM manifest folder and CMS to a SSD going kaput.
I can open the zip file in explorer. Those are DB error in the log. I'm assuming something got setup in the CMS incorrectly.