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.
-
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
-
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!
-
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!
Please sign in to leave a comment.
Comments
6 comments