[SOLVED] D*** eLicenser

[dsharman]

My USB eLicenser has stopped working on my MacBook Pro. It works on my iMac -- which has version 6.3.2 of the eLicenser software (so in theory out of date). Tried several eLicenser versions on my MacBook, it just spins then eventually says it caused an error '???'. My USB licenser never shows up in the list.

Have tried several versions of the eLicenser software, no difference.

Help! How do I get this to work.

[Paul]

Welcome dsharman [:)], 

Did you try a restart or connecting the key to a different USB port on your computer? It´s often a power-problem of the USB Port. 

Best,

Paul

[dsharman]

Thanks for the response. I had tried both USB ports, no luck. As I said, the dongle works fine on my iMac. When I plug it in (on my macbook) the elicenser software recognizes that it's been plugged in ( says 'reading elicensers' and starts spinning) but never shows the device on the left panel. The light on the dongle is on. Eventually the elicenser software says:

eLicenser Control - Error

Application 'LCC2' has caused the following error:

???

I thought I would try a powered USB hub to see if that helps.

Here's what the dongle looks like in System Information before running the elicenser software:

ProtectExecuter:

  Product ID: 0x0101

  Vendor ID: 0x0819

  Version: 1.01

  Speed: Up to 12 Mb/sec

  Manufacturer: Syncrosoft

  Location ID: 0xfa133000 / 7

  Current Available (mA): 500

  Current Required (mA): Unknown (Device has not been configured)

After running the elicenser software it looks like this (so presumably is getting the power it needs...):

ProtectExecuter:

  Product ID: 0x0101

  Vendor ID: 0x0819

  Version: 1.01

  Speed: Up to 12 Mb/sec

  Manufacturer: Syncrosoft

  Location ID: 0xfa133000 / 9

  Current Available (mA): 500

  Current Required (mA): 8

[dsharman]

Also... thought I'd run System Info on my iMac to see what that shows - same, 8 mA current draw after eLicenser software has run.

BTW, yes, also have tried restarting etc.

[dsharman]

Found a solution. On a whim I thought I would try resetting my MBP's PRAM (on a Mac you get so accustomed to things working you take it for granted) -- that worked (!)

Here's the instructions for resetting PRAM if anybody else is having this problem: 

http://support.apple.com/kb/HT1379?viewlocale=en_US&locale=en_US

[Paul]

Hi dsharman, 

Thanks for the update, glad to see you got it working. 

I also forget that resetting PRAM is a last resort.... now it´s on the emergency list again!

Best,

Paul