PDQ Inventory 1.1 (Release 3) Pro Mode all computers have either aborted or pending state.

Follow
J de Vroede

PDQ Inventory doesn't seem to be able to scan the systems anymore. I have checked that the service runs and that it uses the correct credentials. Scan status just gives a Scan Error Aborted, nothing else.

 

Regards,

 

Jeroen

0

Comments

9 comments

Date Votes
  • Adam Ruth
    The aborted status is what you will see when the service is restarted while a scan is pending. What happens if you start a new scan?
    0
    Comment actions Permalink
  • J de Vroede

    Nothing happens. I’ve aborted all scans that remained Pending, but nothing seems to happen. When I select a Scan with Profile than nothing seems to happen. The Scan status remains Aborted (for a machine that had that status)

    Nothing happens. I’ve aborted all scans that remained Pending, but nothing seems to happen. When I select a Scan with Profile than nothing seems to happen. The Scan status remains Aborted (for a machine that had that status)

    0
    Comment actions Permalink
  • Adam Ruth

    Here are a couple of things you can try.  

    Check you application event log for errors from PDQ Inventory. 

    Open a computer window and go to the scans page.  When you start a new scan, do you see it appear in the list?

    0
    Comment actions Permalink
  • J de Vroede

    Indeed there are errors in the application log, see attached screenshot.

    The scan options are disabled and all scans are either aborted or pending, see attached screenshot.

    0
    Comment actions Permalink
  • Adam Ruth

    Thank you for sending in your database, as mentioned on the support ticket the cause was corruption in the database file that we were able to fix.

    0
    Comment actions Permalink
  • Shane Corellian

    Just an update for others who view this post. When all targets show a status of Pending or Queued this usually means that the PDQInventory service (AKA Background service via Preferences) is either stopped or is not functioning on the console computer. Restarting the service is usually the fix. In this case, as Adam noted, the problem was corruption in the DB. This is a rare occurence, however.

    0
    Comment actions Permalink
  • Terrence

    I am now having the same issue for forever queued scans. My Windows 7 PDQ Inventory client has not been working for the past week or two but he XP client was until today. I have deleted stopped/restarted/aborted several times but still cannot resolve this issue. I do have some PDQ log errors. I will post in a few minutes. As I only have a few clients, I am deleting my db on my Windows 7 client. If that does not work, I will reinstall PDQ on both XP and Windows 7.

    0
    Comment actions Permalink
  • Terrence

    The error is on a secured network so I am typing the info:

    Event ID 1000 Task Category 100

    Faulting application name: PDQDeployConsole-----never mind this a PDQ Deploy issue vice an Inventory one.

    0
    Comment actions Permalink
  • Terrence

    Deleting the db appears to have reconciled my issue.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post