Jump to content

If your dongle is not working, please read this


delaney

Recommended Posts

  • 3 months later...
  • Replies 304
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

My Codemeter stick has quit working with an error that reads:

Codemeter 100146:11051 Codemeter API error occurred (Error 52)

Do I need to work this out through eSim or Codemeter?

CMDust results

Copyright © 2005-2008 by WIBU-SYSTEMS AG. All rights reserved.

CmDust Version 4.00 Build 120 of 2008-12-17

================================================================================

Listing some system information

Current Systemtime: 2009-09-18 21:45:44

CmDust was started from: D:\Program Files\CodeMeter\Tools\CmDust

Operating System: Microsoft Windows XP Home Edition Service Pack 3 (Build 2600)

Language Information: Machine: English; Current User: English

.NET Framework 1.0 is not installed.

.NET Framework 1.1 service pack 1 is installed.

.NET Framework 2.0 service pack 2 is installed.

.NET Framework 3.0 is installed with no service packs.

.NET Framework 3.5 service pack 1 is installed.

Overview of available drives:

C:\ = Fix Drive (476937 MB)

D:\ = Fix Drive (476936 MB)

E:\ = CDROM

F:\ = Fix Drive (142655 MB)

G:\ = Fix Drive (9969 MB)

H:\ = CDROM

I:\ = Removable Drive

J:\ = Removable Drive

K:\ = Removable Drive

L:\ = Removable Drive

M:\ = Removable Drive (2 MB), contains codemtr.io

N:\ = Fix Drive (476929 MB)

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

================================================================================

Current User has administrator rights

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

================================================================================

Listing all relevant registry entries

[HKEY_LOCAL_MACHINE\SOFTWARE\WIBU-SYSTEMS\CodeMeter]

"RuntimeVersion" = "4.00.120.501"

[HKEY_LOCAL_MACHINE\SOFTWARE\WIBU-SYSTEMS\CodeMeter\Server]

[HKEY_LOCAL_MACHINE\SOFTWARE\WIBU-SYSTEMS\CodeMeter\Server\CurrentVersion]

"ActionTimeIntervall" = "10"

"ApiCommunicationMode" = "1"

"BindAddress" = "0.0.0.0"

"CertifiedTimeAutomaticUpdate" = "1"

"CertifiedTimeMaxDifference" = "604800"

"CleanUpTimeOut" = "120"

"ExePath" = "D:\Program Files\CodeMeter\Runtime\bin"

"HelpFile" = "D:\Program Files\CodeMeter\Runtime\help"

"IsNetworkServer" = "0"

"IsUpdateInstall" = "1"

"LastLogCleanup" = "306554608" Thu Sep 17 22:03:28 2009

"LogCleanupTimeout" = "336"

"LogPath" = "D:\Program Files\CodeMeter\Logs"

"Logging" = "0"

"NetworkAccessFsb" = "0"

"NetworkPort" = "22350"

"NetworkTimeout" = "100"

"ProxyPasswordSecure" = "/eYHVCGsSuQ="

"ProxyPort" = "8080"

"ProxyServer" = ""

"ProxyUser" = ""

"StartAlways" = "1"

"StartDaemon" = "0"

"TimeServerTimeout" = "20"

"TimeServerURL1" = "cmtime.codemeter.com"

"TimeServerURL2" = "cmtime.codemeter.fr"

"TimeServerURL3" = "cmtime.codemeter.de"

"UDPWaitingTime" = "1000"

"UpdateInstallURL" = "www.wibu.com"

"UseUmsDA" = "1"

[HKEY_LOCAL_MACHINE\SOFTWARE\WIBU-SYSTEMS\CodeMeter\Server\CurrentVersion\Backup]

"1-1058579" = "306639350" Fri Sep 18 21:35:50 2009

"Interval" = "24"

"Path" = "D:\Program Files\CodeMeter\Backup"

"UpdateCertifiedTime" = "0"

[HKEY_LOCAL_MACHINE\SOFTWARE\WIBU-SYSTEMS\CodeMeter\Server\CurrentVersion\BorrowServer]

[HKEY_LOCAL_MACHINE\SOFTWARE\WIBU-SYSTEMS\CodeMeter\Server\CurrentVersion\HTTP]

"HtmlArchive" = "D:\Program Files\CodeMeter\Runtime\bin\CodeMeterUs.wbb"

"PasswordSecure" = "RgjkBaUb9nxa5A=="

"RemoteCommand" = "0"

"RemoteRead" = "1"

"RemoteWrite" = "0"

"User" = ""

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CodeMeter.exe]

"DisplayName" = "CodeMeter Runtime Server"

"ErrorControl" = "0"

"ImagePath" = ""D:\Program Files\CodeMeter\Runtime\bin\CodeMeter.exe""

"ObjectName" = "LocalSystem"

"Start" = "2"

"Type" = "272"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CodeMeter.exe\Enum]

"0" = "Root\LEGACY_CODEMETER.EXE\0000"

"Count" = "1"

"NextInstance" = "1"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CodeMeter.exe\Security]

"Security" = "01 00 14 80 90 00 00 00 9c 00 00 00 14 00 00 00 30 00 00 00 02 00 1c 00 01 00 00 00 02 80 14 00 ff 01 0f 00 01 01 00 00 00 00 00 01 00 00 00 00 02 00 60 00 04 00 00 00 00 00 14 00 fd 01 02 00 01 01 00 00 00 00 00 05 12 00 00 00 00 00 18 00 ff 01 0f 00 01 02 00 00 00 00 00 05 20 00 00 00 20 02 00 00 00 00 14 00 8d 01 02 00 01 01 00 00 00 00 00 05 0b 00 00 00 00 00 18 00 fd 01 02 00 01 02 00 00 00 00 00 05 20 00 00 00 23 02 00 00 01 01 00 00 00 00 00 05 12 00 00 00 01 01 00 00 00 00 00 05 12 00 00 00"

Could not find or read in registry: HKEY_LOCAL_MACHINE\SOFTWARE\WIBU-SYSTEMS\AxProtector

Could not find or read in registry: HKEY_LOCAL_MACHINE\SOFTWARE\WIBU-SYSTEMS\CM Password Manager

Could not find or read in registry: HKEY_CURRENT_USER\SOFTWARE\WIBU-SYSTEMS\CM Password Manager

Could not find or read in registry: HKEY_LOCAL_MACHINE\SOFTWARE\Griffin Technologies\SecuriKey

Could not find or read in registry: HKEY_CURRENT_USER\SOFTWARE\Steganos

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\USBSTOR]

"Start"="3"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\usbhub]

"Start"="3"

[HKEY_CLASSES_ROOT\Interface\{00040000-0000-1010-8005-0000C06B5161}]

"(Default)"="ITrigger"

[HKEY_CLASSES_ROOT\WibuCmTrigger.Trigger\CLSID]

"(Default)"="{00040000-0000-1011-8005-0000C06B5161}"

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

================================================================================

Listing all relevant files with version information

File: D:\Program Files\CodeMeter\Runtime\bin\CodeMeter.exe; Version: 4.00 (Build 120, Count 501)

File: WibuCm32.dll; Version: 4.00 (Build 120, Count 501)

found in location: D:\WINDOWS\system32\WibuCm32.dll

File: D:\Program Files\CodeMeter\Runtime\bin\CodeMeterCC.exe; Version: 4.00 (Build 120, Count 500)

File: D:\Program Files\CodeMeter\Runtime\bin\CmRmtAct32.dll; Version: 4.00 (Build 120, Count 501)

File: WibucmJNI.dll; Version: 4.00 (Build 120, Count 501)

found in location: D:\WINDOWS\system32\WibucmJNI.dll

File: D:\WINDOWS\system32\WibuCmWeb32.dll; Version: 4.00 (Build 120, Count 500)

File: D:\Program Files\CodeMeter\Runtime\bin\WibuCmTrigger32.dll; Version: 4.00 (Build 69, Count 500)

File: D:\WINDOWS\system32\WibuXpm4J32.dll; Version: 6.30 (Build 91, Count 501)

File: D:\Program Files\CodeMeter\Runtime\bin\WibuCmId32.dll; Version: 4.00 (Build 23, Count 500)

File: D:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorlib.dll; Version: 1.01 (Build 4322, Count 2407)

File: D:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\mscorlib.dll; Version: 2.00 (Build 50727, Count 3082)

File: D:\Program Files\CodeMeter\Tools\CmConfigDisk\CmConfigDisk.exe; Version: 4.00 (Build 32, Count 500)

File: D:\WINDOWS\system32\DRIVERS\usbstor.sys; Version: 5.01 (Build 2600, Count 5512)

File: D:\WINDOWS\system32\DRIVERS\usbhub.sys; Version: 5.01 (Build 2600, Count 5512)

File: D:\WINDOWS\system32\DRIVERS\Usbd.sys; Version: 5.01 (Build 2600, Count 0)

File: D:\WINDOWS\system32\usbui.dll; Version: 5.01 (Build 2600, Count 5512)

File: D:\WINDOWS\system32\DRIVERS\Usbport.sys; Version: 5.01 (Build 2600, Count 5512)

File: D:\WINDOWS\system32\DRIVERS\usbuhci.sys; Version: 5.01 (Build 2600, Count 5512)

File: D:\WINDOWS\system32\DRIVERS\usbehci.sys; Version: 5.01 (Build 2600, Count 5512)

File: D:\Program Files\CodeMeter\Runtime\bin\CodeMeterUs.wbb; Version: File is in use, could not be opened

File: D:\Program Files\CodeMeter\Runtime\bin\CodeMeterDe.wbb; Version: Version 4.00 vom 11. Nov. 2008

File: D:\Program Files\CodeMeter\Runtime\bin\CodeMeterFr.wbb; Version: Version 4.00 du 11. Nov. 2008

File: D:\Program Files\CodeMeter\Runtime\bin\CodeMeterIt.wbb; Version: Version 4.00 of Nov/11/2008

File: D:\Program Files\CodeMeter\Runtime\bin\CodeMeterCn.wbb; Version: Version 4.00 of Nov/11/2008

File: D:\Program Files\CodeMeter\Runtime\bin\CodeMeterJp.wbb; Version: Version 4.00a of Dec/15/2008

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

==========================Get Additional Information============================

Currently running CodeMeter (ID 1584) started from D:\Program Files\CodeMeter\Runtime\bin\CodeMeter.exe

Loaded Modules:

SecuriKey is not active.

Internet Explorer Version: 7.0.5730.13.

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

================================================================================

Get information about CodeMeter and CmSticks via API

Getting information about the system

Local system (dad-newxp with IP 192.168.0.19) is Microsoft Windows XP.

The version of CodeMeter is 4.0 (Build 120, Count 501) of 2008-12-17.

The version of the loaded security library (user site) is 4.0 (Build 120, Count 500) of 2008-12-17.

The version of CodeMeterAct is 4.0 (Build 18, Count 500) of 2008-12-08.

The library version used by this application is 4.0 (Build 120, Count 501) of 2008-12-17.

There are found 1 CmSticks

Get CmStick specific data

ERROR: Error 200 in CmAccess().

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

================================================================================

Listing some interesting details about CmSticks

CmStick 1-1058579:

No entry for CM Password Manager found (0:100000)

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

=================================Dump of CmSticks==============================

************************** Dump of CmStick 1-1058579 **************************

ERROR: Error 200 in CmAccess().

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

=================================Dump of Files==================================

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

Link to comment
Share on other sites

  • Members

I think it's best to contact CodeMeter support directly. I wouldn't know what "Error 52" means, anyway.

They will want to have this log file however, so copy it and paste it into your email. You can CC me in that email if you want me to monitor the troubleshooting process.

Link to comment
Share on other sites

  • 2 months later...

Hi,

I am trying to register my CMStick and I have registered an account for myself at my.codemeter.com. However when I enter my account and select "Register CMStick" it shows a small box (where I should write my CMStick number), but I can not write in that box. Is it possible that I'm doing something wrong? When I click "My CMSticks" it shows no stick registered.

...

!!!FIXED!!! - this might be important

The registration page is NOT displayed correctly(doesn't work) in my preferred browser (Google Chrome). It worked in Microsoft Internet Explorer.

Link to comment
Share on other sites

I had the same problem at the CM website as well, only with IE8. Then I realized it was the pop-up blocker. Clicked the yellow bar up top & I was good to go.

I run SB on an HP Blackbird. Intel 2.6GHz quad core, 4G ram, Vista 64 bit. Was running two 9800GTs, but after I fried both of those (while playing SB?) I upgraded to a BFG GTX 260. Had no problems, CM or otherwise until I got the 260. Now I experience a "flash" or freezeframe when panning quickly. (?) Have tinkered w/ Nvidia settings to no avail. Doesn't seem to happen when the frame rate drops. (Usually around 60fps w/all sliders maxed, but I've seen it drop to 20s.)

Drivers are current. Temps are well within normal. Any ideas? Is SB really that demanding? Don't get me wrong, I love the graphics (except maybe the infantry :biggrin: )

Link to comment
Share on other sites

I mailed in a sick dongle, I got back a healthy one. I was happy. Steel Beasts was happy.

I upgraded Steel Beasts with the 2009 Expansion Pack CD.

I was happy, my dongle was happy, Steel Beasts was happy.

Two weeks later, dongle died, Bradley cried.

---

All jokes aside, I'm at a loss for what's happened. The dongle doesn't light up at all and isn't seen by Vista. I've re-installed the latest CodeMeter software and it still doesn't see a dongle. The dongle has only ever been in A) my keyboard USB port or B) in it's sheath on my desk. I've tried the other USB ports and no dice.

What now? Mail it back in? Sacrifice a squirrel? Ask a padre for a young priest and an old priest for an exorcism? Borrow a defibrillator and try to shock a heart-beat back into the thing?

Link to comment
Share on other sites

  • Members

While CM sticks may occasionally fail, failing twice on the same persion shouldn't happen more than maybe once in the entire SB community. Of course we will replace it if necessary, but you should still go through the whole troubleshooting procedure first - run the CmDUST, activate logging in the CM Control Center, copy that log as well, and send both to Support@CodeMeter.com (feel free to CC me). They may make suggestions what to try, or ask for further info, and once that they say that it needs to be replaced, mail it in like last time.

I should mention however that we already had one guy frying three sticks in a row. Turned out that his wall socket wasn't grounded (yikes! :eek2:) so that static electricity built up which then killed the CM hardware on insertion. A "freak" incident of sorts, but it just goes to show that one can't rule out anything, not even a fault with the wiring of one's home.

Link to comment
Share on other sites

  • 3 months later...

Well, my codemeter failed for the first time, the red light remains on permanently and SBP reports a codemeter error at launch. Tried it in different ports and in another computer and it doesn't change.

E-mailing separately my registration number and the CmDust log. :(

Cheers,

Panta

Link to comment
Share on other sites

Well, the Codemeter people says that my problem might be:

"thanks for the information. It seems that your CmStick is in the

Firm Update Mode.

This occurs when a firmware update didn’t work as expected.

Please try to update the firmware again in the CodeMeter Control

Center.

If this won’t work the CmStick must be unlocked and has to be

returned to the software vendor."

Where is the CM control center? In my Codemeter directory? (coudn't find it) And how do you update the firmware? :eek2:

Link to comment
Share on other sites

You all guessed well, it was a case of codemeter blockage, I re-installed the software and ran an upgrade at the CM Center and ...voilà!

After that I had to re-install SBP, because in that particular machine it didn't work.

Some interesting remarks:

1-I hadn't tried to upgrade the CM's firmware and somehow the program was absent (NOD anti-virus?)

2-After that the icon showed up again in the tray down at right, but after I rebooted the PC it disappeared again, though the program runs normally.

3-Uninstalling SBP was a little trickier. At first the program didn't unistall it at all and I had to do it manually. I guess that this is due to the fact that my (bloody) OS is in Spanish and SBP gets installed by default in a directory called "\Archivos de Programa\". The same thing had happened longtime ago when I installed Decisive Action, so it didn't catch me by surprise.

The whole unistalling-reinstalling process took a good two hours, but now SBP is running again smoothly.

Tx for the assistance! :)

Link to comment
Share on other sites

  • 3 weeks later...

Hi I'm experiencing the same problem as Panta had, it lights red, tried updating firmware but it is up to date (reported by the software) and when I hover over the icon in the tray it says "1 CmStick (disabled) connected" I haven't had any time to play for a good while so in my case the stick has been unused for serveral months. Should I resend the stick to eSim? Or what should I do? The stick has a solid red light that never goes away (unless you unplug it ;)) just like Panta.

Best regads,

Alexander Källberg

Link to comment
Share on other sites

Hi I'm experiencing the same problem as Panta had, it lights red, tried updating firmware but it is up to date (reported by the software) and when I hover over the icon in the tray it says "1 CmStick (disabled) connected" I haven't had any time to play for a good while so in my case the stick has been unused for serveral months. Should I resend the stick to eSim? Or what should I do? The stick has a solid red light that never goes away (unless you unplug it ;)) just like Panta.

Best regads,

Alexander Källberg

In my case the only way to upgrade the cm's firmware was to reinstall the game completely, that reinstalled the CM software, which was, IMO, which was failing.

Cheers,

Panta

Link to comment
Share on other sites

In my case the only way to upgrade the cm's firmware was to reinstall the game completely, that reinstalled the CM software, which was, IMO, which was failing.

Cheers,

Panta

Thank you, I will give that a try! :)

EDIT: It didn't help :(

Link to comment
Share on other sites

  • 2 weeks later...

I was in contact with CodeMeter and they told me that the stick was broken. So Ssnake contaced me with information, I was offered to send it back to Germany rather then USA which I gladly accepted as it is as Ssnake concluded, closer ;)

$5 USD later and about two or three days (took the precaustion to get a sturdy bubble rapped envalope) it arrived at Ssnakes office (today, friday) and he sent a new one back right away on the same day.

That's what I call service! Thank you very much Ssnake and eSim! I'm now happy to get back into the wonderfull world of the Leopard 2! :)

The hardest bit with this was to actually write the address on the package, I am suffering from dyslexia, so I have a tendency to get things wrong, but it seems to have worked :D

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...