Hi Jeremy - I made some changes to our server including all but the last steps you mentioned in the KB article. As of right this moment, the software is still working. Along with these changes though, I used the set devmgr_show_nonpresent_devices=1 command and opened the device manager. Then I changed the view to show hidden devices.
When I did this I ended up seeing “ghost” images from when the machine was a physical box, or at least that looks like what they were. I removed those and rebooted and the server and we haven’t had the problem since.
Granted, it’s only been about 2 hours since that was done and the intervals where it works are not predictable. If everything is ok by Monday and I don’t have any errors, or problems I will consider it resolved. Then I’ll have to put my patches back on and see if that breaks it again.
Good afternoon Jeremy - Over the weekend unfortunately my issue still lives on. The server in question was definitely “losing” connection to the devices and the application depending on the key was failing. I ended up scheduling a reboot of the server every 60 minutes to fix it so I didn’t have to keep my finger on it.
Of course this was not ideal, but better than babysitting.
I also added in the registry entry for the “PermittedDevice” list this morning, but I’m not sure that will help matters at all.
Any other suggestions would be helpful. I haven’t had any more BSOD’s yet.
The next time the issue happens, please note the following (before rebooting the server), as soon as you can after the issue happens, i.e. when you’re in a “failed state” and share that info with me:
The color and activity of the Port LEDs on the front panel of the AWUSB? If you have an AWUSB/14 model, the Ports LEDs in question would be specific to the Ports that the host PC are connected to.
Is the AWUSB still listed in the AWUSB config util? Click View / Refresh after checking this, to see if anything changes.
Are the license dongles still listed in Windows Device Manager, as if they’re still connected and recognized by Windows?
What about the AWUSB components in the USB section of Device Manager? Are they still present?
Now perform a Scan for Hardware Changes in Device Manager and answer questions #3 and #4 again.
I have been working with a vendor which uses HASP/dongles for their licensing model. They have been in contact with SafeNet regarding this issue. Apparently, SafeNet has no intention of supporting HASPs/dongles on AnywhereUSB. The claim is apparently that on a network as such it is a security risk. That leaves us high and dry unless/until we can get to ESX4.1 or above which provides better USB support and we no longer require the USB network hub at all.
Jeremy - So this morning I got the notification that our software was failling again. So, per your request I went through the troubleshooting steps.
I am running an AWUSB/5 Gen2
Color and Activity of port lights: Ports 1-5 were all solid green, no blinky-blinky. The System Status light was blinking green.
The AWUSB is listed in the Config Util. After a refresh, there were no changes.
The Hard lock Key, USB Key, Realport USB Controller and USB Super Pro/Ultra Pro all show up in Device manager. No yellow disconnect bangs.
The AWUSB components show in the System devices of Device Manager.
When the problem was happening I performed a “scan for hardware changes” and the machine BSOD’d on me instantly.
After a reboot, the same steps did not cause a BSOD, but I noticed after I had added the Reg Entry for “Permitted Devices”, that Only a “Device Failed Enumeration” error showed up in the AWUSB View Utility. In order to get the Dongle’s back I had to remove that entry from the Registry. Maybe I did the reg entry wrong, but don’t believe so.
Hopefully this gives us some more information to go on.
We are currently working with SafeNet regarding the BSOD issue that can happen when these kinds of dongles are attached to AnywhereUSBs. I will be sure to post an update here after that’s resolved.
grinnell.michael@mayo.edu,
Hopefully SafeNet will change their stance soon, considering that we have established a relationship with them during the BSOD troubleshooting. They’ve sent us a dongle to test with and we’ve sent them an AWUSB to test with.
Hopefully, Digi and SafeNet can come to an understanding as to what is supported and how. Below is a note from my vendor contact –
By the way, SafeNet seems to be against supporting AnywhereUSB because “it
makes the USB key available to any machine in the network”, so I do not
think SafeNet will claim they support other “USB over network” devices
either but it is possible that manufactures other than Digi works better
with SafeNet hasp keys.
Having the same BSOD problem here running Windows 2008 x64 R1 on VMWare ESX 4.1 with a SafeNet Dongle on an Anywhere USB2. Server is running for a while and then crashes with bluescreen.
The server is running a production management system. If the server crashes, the whole production is stopped because the production machines do not get further data –> really big problem!
To anyone who using using an AnywhereUSB and a SafeNet dongle (or dongle that uses a SafeNet driver) that’s experiencing bluescreens, I have great news!
Digi has been working with SafeNet regarding this issue, and we believe that it’s been resolved, via a fix in the SafeNet dongle driver.
To get the new driver, we suggest contacting the vendor of the protected software that you are using. That vendor should then contact SafeNet to ask them for the new driver. Please do not contact SafeNet directly about this. I’m told that the fix will be included in SafeNet’s upcoming release.
SafeNet provided a beta release of this driver to the vendor of my software almost two months ago. The vendor tested this patch and it appears to fix the issue. SafeNet, however, seems to be dragging its feet on releasing it to production. There is no ETA to release this to production so far.
We had this problem about a year ago and SafeNet finally provided what, at the time, we tested and showed to be a fixed version of the SafeNet driver. This past Friday evening, June 22, however, our VMWare instances began to BSOD. Some had received monthly Windows patches and some had not. All of the BSOD had the same signature which points at the Digi software. I don’t understand why this bug would suddenly show up again. Beginning later on a Friday evening we would start slowing down load-wise and, as I said, not all of the servers had received any monthly patches yet. Any ideas, however far-fetched, would be appreciated.