Scans all hung on 'Queued' since 3.1.1 update

Comments

7 comments

  • Bstacy

    Hello,

    To follow up. I have had a few machines throught the district that have actually scanned but it took a couple of hours for them to complete.  Even after verifying that a lab full of newly re-imaged machines did in fact have .NET4 installed they continue to sit in Queued status. Some have eventually Aborted.

    Barry

    0
    Comment actions Permalink
  • Shane Corellian

    Hi Barry,

    Are you still seeing this issue? Yesterday version 3.1.2 was released. This fixes a couple of issues that are related to what you are seeing. Please let us know if the problems persist after the upgrade.

    0
    Comment actions Permalink
  • Bstacy

    Hello Shane,

    I have updated to 3.1.2 and the issue persists. We currently have 455 machines scanning. Many have been running all weekend long and have not aborted.

    0
    Comment actions Permalink
  • Bstacy

    We found that when scans appear to be hung we needed to stop and restart the 'PDQ Inventory' service.  

    I changed the service from 'Automatic' to 'Automatic (Delayed Start)' and things appear to working well now.  We are though. still having a consistent error when trying to inventory the server that PDQ Inventory is installed on.  We receive the following error as shown in this screenshot.

     

    0
    Comment actions Permalink
  • SelfMan

    Please if not done yet, install the dotNET 4.5.2 framework on that computer and try it out.

    0
    Comment actions Permalink
  • Bstacy

    That did it!  Thank you.

    0
    Comment actions Permalink
  • SelfMan

    With the recent updates Microsft Messed something up with the dotNET 4.0 Framework. The only currently known workarrounds are:

    a) Full uninstall of the dotNET4.0 frameowork, reinstall an patching

    b) upgrading to dotNET 4.5.2 Framework which is essentialy a upgrade.

    0
    Comment actions Permalink

Please sign in to leave a comment.