Error in qw log file - DbC PreconditionViolation

MarkS451

What could cause the error below: (I deleted my log file, restarted quicken, and see this line only in the log file)
"Process id : 2836 Thread id : 9964 : Time 12:01:41 : DbC PreconditionViolation 'pDB != 0 && itemType < GetNumItemTypes() && pItemSpec != 0' in QDBNumItems (qdb.c @ line # 1935.)"

Windows 10
Quicken 2020 R25.21, Build 27.1.25.21 (says latest update when I check)

I have also copied the data file, am using the new file, and did a file validation.

Also seeing a long clock when I try to update accounts before I get the password prompt.

Thanks

Chris_QPW

The thing to understand about that log file is it is for the developers.  If they want to get more information on what is happening in given spot they can log this information.  What they log may or may not indicate any kind of problem.  Really only the developers can tell if a given log entry show a problem or is just information.  In a lot of log systems they tag entries with Information, Warning, Error, but that isn't universal, and isn't true in this case.

Chris_QPW

P.S. the long wait for the password prompt.  Ironically this problem does seem to stem from the problem @GeoffG is pointing to in that link, but in an "indirect way".

It seems Quicken Inc wants to inform everyone of this problem.  So when One Step Update starts they are somehow checking/requesting how to put up a dialog with that same message about the stimulus checks.  For  whatever reason this is taking a long time (and maybe even times out/fails in some cases).  But once that dialog is displayed and you select not to see it again, the delay seems to be gone.

GeoffG

This appears to be a normal condition, I have this throughout my file dating back to Jan. If you are concerned about issues with OSU, there are multiple connection issues that will self correct.

https://community.quicken.com/discussion/7874067/ongoing-4-16-20-you-may-experience-errors-updating-some-of-your-accounts#latest

Chris_QPW

The thing to understand about that log file is it is for the developers.  If they want to get more information on what is happening in given spot they can log this information.  What they log may or may not indicate any kind of problem.  Really only the developers can tell if a given log entry show a problem or is just information.  In a lot of log systems they tag entries with Information, Warning, Error, but that isn't universal, and isn't true in this case.

Chris_QPW

P.S. the long wait for the password prompt.  Ironically this problem does seem to stem from the problem @GeoffG is pointing to in that link, but in an "indirect way".

It seems Quicken Inc wants to inform everyone of this problem.  So when One Step Update starts they are somehow checking/requesting how to put up a dialog with that same message about the stimulus checks.  For  whatever reason this is taking a long time (and maybe even times out/fails in some cases).  But once that dialog is displayed and you select not to see it again, the delay seems to be gone.