A check says it couldn't run
A check that couldn't run shows as a warning, with "Check couldn't run" and a reason in Issues to resolve, and "couldn't run" on its area tile. It means Ledger Doctor has no result for that check, not that it found a problem.
The reasons
- Incompatible: this GP's tables are laid out differently
- The check needs a GP table or column this database doesn't have. Rather than guess, Ledger Doctor skips it. It can happen with older GP versions or third-party products that change GP's tables. If you think the check should apply, email us the check ID and your GP version; a later check library may handle your layout.
- Blocked: blocked by a safety rule
- Every check has to be a plain read-only query. Ledger Doctor refuses to run one that isn't, and records why. You shouldn't see this; if you do, please tell us.
- Error: it hit an error
- SQL Server returned an error while the check ran, such as a timeout or a database that's offline or in single-user mode. It usually clears on the next scan. If it doesn't, choose Recheck on the issue to see it again, and email us if it keeps happening.
Not the same as "Not installed"
"Not installed" means the company doesn't use that GP module, so its checks don't apply. That's normal and isn't counted as a problem.