Important Notice: On February 29th, this community will be put into read-only mode. All existing posts will remain but customers will be unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Machine with PDQ installed can't scan itself

I get the following "Scanner failed with error code -2146233082 when the machine where the PDQ software tries to scan itself.  Other references to this message suggest an issue with the .NET software.  I removed and reinstalled .NET 4 and get the same result.  Remote Repair reports that everything is fine.  

0

Comments

6 comments
Date Votes
  • Hi Brad,

    If you are running Windows 7 or later(Server 2008 or later) upgrade .Net to the 4.5 version. Once .Net has been upgraded, the issue you are seeing should be resolved. Let me know if you continue having issues after the upgrade to .Net 4.5.

    -Brandon

    0
  • It's actually still running on an XP machine at the moment.  

    0
  • Brad,

    This is actually an issue we are currently working on for XP and Server 2003 machines. Usually, a complete uninstall and reinstall of .Net 4 resolves the issue for XP and Server 2003 machines; however, we do have a few cases where the .Net issue persist even after the reinstall.

    For now, Inventory version 3.0.6 is recommended until we have a fix for the .Net 4 issues in XP and Server 2003.

    -Brandon

    0
  • FYI...I am having the same issue and have uninstalled and reinstalled Net 4 at least twice.

    And *yes* I do have Server 2003....I'll upgrade as soon as I can scrape together the funds for a shoestring for our budget ;-)

    Seriously though, I do understand that this is an ongoing issue. Thank you very much for looking into this.

    I have the latest PDQ Inventory version and at least so far it works great except for 

    1) inability to scan itself

    2) oddly it refuses to start when I am logged in as the administrator, but if I use runas to use the alternate admin credentials it starts right up.

     

    Thanks!

    0
  • At the moment, on windows 2003 editions, the best way is to stick with the 3.0.6 version of PDQ Inventory like Brandon wrote.

    The behavior of the new version on these old systems is unpredictable.

    0
  • Yeah, I probably should revert back to 3.0.6....but that smacks of effort and I'm just too lazy to do it right now ;-)

    No worries about the local scan issue. I like the improved speed of the new version and the inability to scan the machine itself and the need to runas are minor inconveniences. If problems get worse I will revert.

     

    Thanks!

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post