6 Replies Latest reply on Apr 18, 2008 12:27 PM by seamus151

    LDIScn32: bind failed Event ID 17


      I have about 10 PC's in my network that keep bluescreening in the middle of the night. After checking the event viewer the last thing that kicked off was the Inventory Scanner. There was an error in the event viewer that read


      Event ID 17



      LDIScn32: bind failed.



      Then there was no further activity in the log until the user rebooted the PC's when coming in during the morning. When I check the ldiscn log on the local PC it reads:



      Sun, 09 Mar 2008 17:50:08 Checking if firewall is enabled : ({77DE0087-6962-49F9-89C8-7307C0B2BF4A})

      Sun, 09 Mar 2008 17:50:32 Failed to init : (800706D9)

      Sun, 09 Mar 2008 17:50:33 UninstallString: msiexec.exe /i{50e125d1-88e5-48ce-80ae-98ec9698e639}

      Sun, 09 Mar 2008 17:50:33 Installed

      Sun, 09 Mar 2008 17:50:57 open key Software\Utimaco\SGEasy with flags 0x20019 returns handle 0, status 2



      I am pretty sure it's the Inventory scanner that's blue screening these PC's. Why it's bluescreening, I don't know. These particular PC's are each connected to a Schick dental Xray machine (http://www.schicktech.com/) via a USB sensor.



      What's weird, is during the day I can run a manual Inventory scan on a PC with no problem. The only thing I can think is at night the PC power features kick in and maybe this is causing the problem in combination of the Schick Xray and USB sensor. The power features are setup as Home/Office Desk and turn off monitor after 20 minutes. These are Dell Optiplex 745.



      What I've done now is changed the power features to always on and never turn off monitor. Then I created a new agent that has the following settings



      a. Inventory Scan only happens when user is logged in and inbewteen the hours of 0800 and 1400 and Monday through Friday. This will ensure that inventory scans happen only during working hours and when someone is logged. The scans seem to complete fine during the day, it seems they only fail when running in the middle of the night.



      So apart from any suggestions as to why the BSoD might be happening...is there a way I can check the local agent on the PC to ensure that the inventory scans are going to happen at the times I set in the newly created agent? I know I am being paranoid but these BSoD are causing my department much grief.