Problem with 2k8 x64 drivers

USB Edgeport
21

Thanks.

Now I’d like for you to get a different kind of .log file for us.

Use any of the PCs or VMs that you’ve seen the reboot issue on, that’s running the new v2.60 driver.

Let me know which PC or VM you ended up using for the host.

  1. Disconnect all USB devices from the AnywhereUSB then power cycle the AnywhereUSB and reboot the host.

  2. Click the Configure button in the AnywhereUSB Configuration Utility and fill in the “Debug Log Address” field at the bottom with that hosts IP address. Click the Update button and confirm to reboot the AnywhereUSB.

  3. Open a command prompt (start, Run, “cmd”), then go to the root c:\ folder ("cd c:") and enter the following command:

awusblog

That should start logging to disk.

  1. Connect the HASP key to the AnywhereUSB. After the AnywhereUSB reboots, press Esc to stop awusblog from logging. It should create a file called “awusb00001.log” (or similar) in the root c:\ folder. Upload that file here.
22

I’ll use Win2K3x64 on Virtual Maschine (Hyper-V)
There is log-file.
I connect HASP to first port on AnywhereUSB and wait for BSOD.

you may see all reconnection attempts and maybe last attempt (if it was saved before BSOD appear)…

I’ll attach awusb*.log and Configuration utility log.

23

Thanks.

I will escalate this to our engineering group and forward them all the info I’ve collected here.

I will keep you updated.

24

Thank you!

p.s. by the way… I install “Win2k3 x32” to Virtual PC and all latest drivers…(HASP driver and AnywhereUSB 260). All work fine on 32bit system…

Message was edited by: maximilian@mail333.com

25

  1. What is the 50xxxxxx part number (and revision, which is a single letter) of your AnywhereUSB?

  2. What kind of Ethernet switch is the AnywhereUSB connected to? Are the PCs in question connected to the same switch?

  3. What Service Pack versions are running on these systems?

Server 2003 x64 Virtual Machine - SP?
Server 2003 x64 Physical PC - SP?
Server 2008 x64 Virtual Machine - SP?

  1. What “Editions” are the above systems running? i.e. Enterprise, Standard.
26

  1. 50000818-01 C

  2. I too think about this, but I try different configuration - frim simple microswitch (such as 3com) to Cisco 3560. PC was connected to same switch and in another (via router). I’ll also connect to my device via Internet directly (Public to Public) and via NAT (USB-Public to PC-on-LAN-behind-NAT). That does not change any symptomps… In any case with 32 bit systems all ok, with 64-bit - crash…

  3. All latest servicepacks. Fully updated.
    2k3_R2_x64-SP2 (Physical and Virtual)
    2k8x64-SP1

  4. All Enterprise editions.

27

I shared your information with our engineering group. Based on the awusblog log file, they can see that the dongle is crashing the AWUSB firmware repeatedly every minute or so, but unfortunately the error message in the log file isn’t very helpful in pointing to the exact problem. They would need to have the dongle in house in order to make progress on solving this aspect of the problem.

Can you send us the dongle in question? If not, could you contact Aladdin and try to get them to send us one (an evaluation/loaner)?

28

I’ll also contact the Alladin. They escalate problem to Israel office. Maybe it connect with you about this qestion.
As I also say, sending from Ukraine to You will spent much more time than we have… Aprox ~1 month. In addition, the cost for this sending will be much more than cost of new device from other vendor or software desigion… So if able try to correct problem without dongle…
A again purpose to connect to device remotely. I may perform all needed manipulation from my side for you testing.

29

Good day, Jeremy!
Do you have any information about our problem?

30

Good day!

I was under the impression that you were contacting Aladdin. Would you prefer for us to try to contact them? Ultimately, the only way we can potentially resolve this is by re-creating the issue, which means we need a dongle/key from Aladdin.

31

I wanted to let you know that other customers have reported the same issue. We don’t yet have a resolution but we are looking into this.

32

Thank you, we will wait for good result… :slight_smile:

33

This has been resolved with the v2.70 AnywhereUSB driver. This driver mainly fixes an issue related to USB dongles causing the AnywhereUSB to reboot constantly. It also fixes some blue screens and adds support for upcoming 2nd generation AnywhereUSB hardware.

It’s been WHQL’d (digitally signed) by Microsoft. Here are download links:

32-bit version:
ftp://austin:!15st3n!@ftp1.digi.com/support/AnywhereUSB/2.70 (WHQL)/32-bit/AnywhereUSB v2.70 driver 32-bit.zip

64-bit version:
ftp://austin:!15st3n!@ftp1.digi.com/support/AnywhereUSB/2.70 (WHQL)/64-bit/AnywhereUSB v2.70 driver 64-bit.zip

(Copy and paste the link, since the spaces broke the links.)

You should first uninstall the existing AnywhereUSB driver by clicking “View / Driver Information / Uninstall” and reboot the PC when prompted.

This is the same version that will end up on our website.

Please provide feedback – either good or bad – by replying to this e-mail.