Codemeter api error 221 netinfo failed occurred - Исправление ошибок и поиск оптимальных решений проблем

Содержание

Graphisoft Community
Graphisoft Community
Graphisoft Community
Graphisoft Community
Graphisoft Community

Subscribe to RSS Feed
Mark Topic as New
Mark Topic as Read
Pin this post for me
Bookmark
Subscribe to Topic
Mute
Printer Friendly Page

‎2021-07-15 09:14 PM

Yesterday I installed AC 25 INT on a Mac 10.15.7 Catalina and Codemeter stopped working for all versions. After an hour or two of checking with the local dealer, reinstalling Codemeter and License Manager, and restarts, things started working again. Today I installed AC 25 USA and the same story, only that I haven’t yet managed to make it work.

When I insert the Codemeter key, the light blinks intermittently green-orange for a few seconds and then goes off. Google is not helping with interpreting.

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

‎2021-07-16 05:23 AM

I’ve occasionally had this problem with AC24 and Mac OS10.14 Mojave when moving the dongle between computers. Removing the dongle, then reinserting, so the light only blinks once, solves it. I think I saw the dongle show up on the desktop as a drive with the multiple light blinking, so I guessed it was being seen as a storage device.

David Maudlin / Architect

AC26 USA • iMac 27″ 4.0GHz Quad-core i7 | 24 gb ram • MacBook Pro 2.8GHz | 16 gb ram • OSX10.15.7

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

‎2021-07-16 05:33 AM

Thank you very much for your report and I am very sorry to hear about the issue!

Starting with Codemeter 7.20, it no longer accepts Hardware keys configured as KEXT. The keys need to be converted into HID. Yesterday, we just solved this same issue with another client: Hardware keys no longer work after installing Archicad 25. After we converted the key to HID, it can now work properly. Please have a look at the article here and please find the converter here.

I’m not sure whether this is the same issue as what you experienced? If that’s the case, please make sure to convert the key to HID, as Apple will no longer accept the older interface starting from Big Sur.

Looking forward to hearing from you!

Best regards,
Minh

Minh Nguyen
Technical Support Engineer
GRAPHISOFT

Источник

Subscribe to RSS Feed
Mark Topic as New
Mark Topic as Read
Pin this post for me
Bookmark
Subscribe to Topic
Mute
Printer Friendly Page

‎2021-07-15 09:14 PM

When I insert the Codemeter key, the light blinks intermittently green-orange for a few seconds and then goes off. Google is not helping with interpreting.

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

‎2021-07-16 05:23 AM

David Maudlin / Architect

AC26 USA • iMac 27″ 4.0GHz Quad-core i7 | 24 gb ram • MacBook Pro 2.8GHz | 16 gb ram • OSX10.15.7

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

‎2021-07-16 05:33 AM

Thank you very much for your report and I am very sorry to hear about the issue!

Looking forward to hearing from you!

Best regards,
Minh

Minh Nguyen
Technical Support Engineer
GRAPHISOFT

Источник

Subscribe to RSS Feed
Mark Topic as New
Mark Topic as Read
Pin this post for me
Bookmark
Subscribe to Topic
Mute
Printer Friendly Page

‎2021-07-15 09:14 PM

When I insert the Codemeter key, the light blinks intermittently green-orange for a few seconds and then goes off. Google is not helping with interpreting.

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

‎2021-07-16 05:23 AM

David Maudlin / Architect

AC26 USA • iMac 27″ 4.0GHz Quad-core i7 | 24 gb ram • MacBook Pro 2.8GHz | 16 gb ram • OSX10.15.7

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

‎2021-07-16 05:33 AM

Thank you very much for your report and I am very sorry to hear about the issue!

Looking forward to hearing from you!

Best regards,
Minh

Minh Nguyen
Technical Support Engineer
GRAPHISOFT

Источник

Subscribe to RSS Feed
Mark Topic as New
Mark Topic as Read
Pin this post for me
Bookmark
Subscribe to Topic
Mute
Printer Friendly Page

‎2021-07-15 09:14 PM

When I insert the Codemeter key, the light blinks intermittently green-orange for a few seconds and then goes off. Google is not helping with interpreting.

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

‎2021-07-16 05:23 AM

David Maudlin / Architect

AC26 USA • iMac 27″ 4.0GHz Quad-core i7 | 24 gb ram • MacBook Pro 2.8GHz | 16 gb ram • OSX10.15.7

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

‎2021-07-16 05:33 AM

Thank you very much for your report and I am very sorry to hear about the issue!

Looking forward to hearing from you!

Best regards,
Minh

Minh Nguyen
Technical Support Engineer
GRAPHISOFT

Источник

Subscribe to RSS Feed
Mark Topic as New
Mark Topic as Read
Pin this post for me
Bookmark
Subscribe to Topic
Mute
Printer Friendly Page

‎2021-07-15 09:14 PM

When I insert the Codemeter key, the light blinks intermittently green-orange for a few seconds and then goes off. Google is not helping with interpreting.

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

‎2021-07-16 05:23 AM

David Maudlin / Architect

AC26 USA • iMac 27″ 4.0GHz Quad-core i7 | 24 gb ram • MacBook Pro 2.8GHz | 16 gb ram • OSX10.15.7

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

‎2021-07-16 05:33 AM

Thank you very much for your report and I am very sorry to hear about the issue!

Looking forward to hearing from you!

Best regards,
Minh

Minh Nguyen
Technical Support Engineer
GRAPHISOFT

Источник

It is a long story…. I did get an error before that the stick is not present. So now I repeated it with the dongle in another port. Now finally I am receiving the familiar error: I doubleklick on the steelbeasts pro icon, and nothing happens. I can hear the harddisk working for a moment, then nothing. In the task manager I can see sbpro.exe pop up for a second. I am starting sbpro as administrator btw. And before you ask:

C:UsersusernameDocumentseSim GamesSteel Beastslogs

is still empty.

The new CmDUST logfile is in my attachement. Here is also the updated log from my dongle:

2014-07-27 07:05:12: CodeMeter for Windows (B5.10.1224.501.32.150)

2014-07-27 07:05:12: Running on Microsoft Windows 7 Professional Service Pack 1 (build 7601), 64-bit

2014-07-27 07:05:12: Execution path: C:Program Files (x86)CodeMeterRuntimebin

2014-07-27 07:05:12: Found IPv4 address: 127.0.0.1 | 192.168.178.29

2014-07-27 07:05:12: Used Communication Mode: IPv6 IPv4 SharedMemory

2014-07-27 07:05:12: Used IP address: default address

2014-07-27 07:05:12: Used IP port: 22350

2014-07-27 07:05:12: Used CmWAN port: 22351

2014-07-27 07:05:12: Multicast server search: not available

2014-07-27 07:05:12: Run as network server: no

2014-07-27 07:05:12: Run as CmWAN server: no

2014-07-27 07:05:12: Run as system service: yes

2014-07-27 07:05:12: Service startup delay: 1:26 minutes

2014-07-27 07:05:12: Box Access: use direct access mode

2014-07-27 07:05:23: License file «5000173_0001-0.wbb» loaded successfully.

2014-07-27 07:05:23: Detecting CmContainer with Serial Number 2-2640442

2014-07-27 07:05:24: A new CmContainer is available (currently found 1)!

2014-07-27 07:05:24: Detecting CmContainer with Serial Number 32767-4160138177

2014-07-27 07:05:24: A new CmContainer is available (currently found 1)!

2014-07-27 07:05:24: The list of available CmContainers has been updated!

2014-07-27 07:05:24: Found new entries: 3

2014-07-27 07:05:39: Access from local(IPV6) to SubSystem (Handle 16)

2014-07-27 07:05:39: Using security library version (LS) 5.10.1224.501

2014-07-27 07:05:39: Handle 16 released

2014-07-27 07:06:09: Box Event HW410-535 (2640442) occurred.

2014-07-27 07:06:10: Box Event HW410-535 (2640442) occurred.

2014-07-27 07:06:10: Box Event HW70-536 (2640442) occurred.

2014-07-27 07:06:11: API Event WB0070 (BOX ERROR) occurred (returned to caller)

2014-07-27 07:07:35: Box Event HW410-535 (2640442) occurred.

2014-07-27 07:07:36: Box Event HW410-535 (2640442) occurred.

2014-07-27 07:07:36: Box Event HW70-536 (2640442) occurred.

2014-07-27 07:07:36: API Event WB0070 (BOX ERROR) occurred (returned to caller)

2014-07-27 07:09:22: Removable Device has been plugged OUT!

2014-07-27 07:09:23: A CmContainer has been removed (currently found 0)!

2014-07-27 07:09:23: The list of available CmContainers has been updated!

2014-07-27 07:09:48: Removable Device has been plugged IN!

2014-07-27 07:09:49: Detecting CmContainer with Serial Number 2-2640442

2014-07-27 07:09:50: Box Event HW410-535 (2640442) occurred.

2014-07-27 07:09:51: Box Event HW410-535 (2640442) occurred.

2014-07-27 07:09:51: Box Event HW70-536 (2640442) occurred.

2014-07-27 07:09:51: API Event WB0070 occurred.

2014-07-27 07:09:51: API Event WB0021 (FIRM ITEM INVALID) occurred (returned to caller)

2014-07-27 07:09:51: The list of available CmContainers has been updated!

2014-07-27 07:12:06: API Event WB0261 (LICENSE NOT ACTIVATED) occurred (returned to caller)

All handles:

— no handles in use

All handles:

— no handles in use

All connected CmContainers:

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

CmContainer with Serial Number 32767-4160138177 and version 1.18

Certified Time: 2000-01-01 00:00:01 (UTC)

Box Time: 2000-01-01 00:00:01 (UTC)

System Time: 2014-07-27 05:13:30 (UTC)

OEM ID: 0

FSB-FirmCode: 99

CTSB-FirmCode: 98

Box-//UserKey ID: 0/1

Chip Information:

Firmware Bld: 0x00000000

Firmware BldTp: 0x00000000

MdfaLba: 0x00000539

ChipType: 0x00

Silicon Rev.: 0x00

USB Chip Information:

Flash Size: 0 MByte

Variant: 1001

Configuration: fixed,active partition

Implicit Firm Item:

0.) FC=0 (Ref=5632) in CmContainer with Serial Number 32767-4160138177 and version 1.18

FUC=0-10, FAC=65535, Type=0x0000, FPT=2014-07-27 05:05:24 (UTC)

Text: ESIMGAMES

Enable Block Table:

[0|+ ], Opt=0x8000

TimePin, AccessCode Length = 16, Disable Time = (never)

Text (#=7): Default

Enable Lookup Table:

[0], Opt=0x8003, EnableLevel=7, DisableLevel=0

0.1) PC=0 (Ref=16/Dependency=0x07)

Hidden Data (#=14, Type=128/Dependency=0x05): No readable data!

Secret Data (#=32, Type=128/Dependency=0x01): No readable data!

Extended Protected Data (#=3, Type=128/Dependency=0x01):

0x0000: 02 00 00

Extended Protected Data (#=10, Type=129/Dependency=0x05):

0x0000: 00 00 63 00 00 00 62 00 00 00

Extended Protected Data (#=4, Type=130/Dependency=0x05):

0x0000: 03 00 00 00

Extended Protected Data (#=8, Type=131/Dependency=0x00):

0x0000: 01 00 00 00 05 00 00 00

User Data (#=2/Dependency=0x00):

0x0000: 00 00

0.2) PC=1000 (Ref=17/Dependency=0x07)

List of all connected license entries:

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

1.) FC=5000173 (Ref=5952) in CmContainer with Serial Number 32767-4160138177 and version 1.18

FUC=0-10, FAC=65535, Type=0x0001, FPT=2014-07-27 05:05:24 (UTC)

Text: ESIMGAMES

1.1) PC=0 (Ref=18/Dependency=0x07)

2014-07-27 07:21:20: Executing Broadcast for CodeMeter License Servers

2014-07-27 07:21:21: Entry (100146:11091) not found — Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)

2014-07-27 07:21:21: API Error 200 (ENTRY NOT FOUND) occurred!

2014-07-27 07:21:21: Executing Broadcast for CodeMeter License Servers

2014-07-27 07:21:22: Entry (5000173:71091) not found — Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)

2014-07-27 07:21:22: API Error 200 (ENTRY NOT FOUND) occurred!

2014-07-27 07:22:11: Executing Broadcast for CodeMeter License Servers

2014-07-27 07:22:12: Entry (100146:11091) not found — Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)

2014-07-27 07:22:12: API Error 200 (ENTRY NOT FOUND) occurred!

2014-07-27 07:22:12: Executing Broadcast for CodeMeter License Servers

2014-07-27 07:22:13: Entry (5000173:71091) not found — Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)

2014-07-27 07:22:13: API Error 200 (ENTRY NOT FOUND) occurred!

2014-07-27 07:22:18: Executing Broadcast for CodeMeter License Servers

2014-07-27 07:22:19: Entry (100146:11091) not found — Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)

2014-07-27 07:22:19: API Error 200 (ENTRY NOT FOUND) occurred!

2014-07-27 07:22:19: Executing Broadcast for CodeMeter License Servers

2014-07-27 07:22:20: Entry (5000173:71091) not found — Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)

2014-07-27 07:22:20: API Error 200 (ENTRY NOT FOUND) occurred!

2014-07-27 07:22:32: Executing Broadcast for CodeMeter License Servers

2014-07-27 07:22:33: API Event WB0101 (SERVER NOT FOUND) occurred (returned to caller)

2014-07-27 07:36:31: CodeMeter for Windows (B5.10.1224.501.32.150)

2014-07-27 07:36:31: Running on Microsoft Windows 7 Professional Service Pack 1 (build 7601), 64-bit

2014-07-27 07:36:31: Execution path: C:Program Files (x86)CodeMeterRuntimebin

2014-07-27 07:36:31: Application Uptime: 00:31:23 up

2014-07-27 07:36:31: Found IPv4 address: 127.0.0.1 | 192.168.178.29

2014-07-27 07:36:31: Used Communication Mode: IPv6 IPv4 SharedMemory

2014-07-27 07:36:31: Used IP address: default address

2014-07-27 07:36:31: Used IP port: 22350

2014-07-27 07:36:31: Used CmWAN port: 22351

2014-07-27 07:36:31: Multicast server search: not available

2014-07-27 07:36:31: Run as network server: no

2014-07-27 07:36:31: Run as CmWAN server: yes

2014-07-27 07:36:31: Run as system service: yes

2014-07-27 07:36:31: Box Access: use direct access mode

2014-07-27 11:06:46: API Error 221 (NETINFO FAILED) occurred!

2014-07-27 11:07:15: Handle 68 automatically released (no longer valid)

2014-07-27 12:48:47: Removable Device has been plugged OUT!

2014-07-27 12:48:47: The list of available CmContainers has been updated!

2014-07-27 12:49:00: Removable Device has been plugged IN!

2014-07-27 12:49:01: Detecting CmContainer with Serial Number 2-2640442

2014-07-27 12:49:02: A new CmContainer is available (currently found 1)!

2014-07-27 12:49:02: The list of available CmContainers has been updated!

2014-07-27 12:49:02: Found new entries: 2

2014-07-27 12:49:25: Info: A CmWAN-Server cannot do a client-side Access over CmWAN.

2014-07-27 12:49:25: Access from local(IPV4)(PC) to FC:PC=100146:11091 with StationShare Mode (Handle 92)

2014-07-27 12:49:25: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:49:26: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:49:26: Box Event HW70-536 (2640442) occurred.

2014-07-27 12:49:26: API Event WB0070 (BOX ERROR) occurred (returned to caller)

2014-07-27 12:49:43: Handle 92 automatically released (no longer valid)

2014-07-27 12:49:43: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:49:44: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:49:44: Box Event HW70-536 (2640442) occurred.

2014-07-27 12:49:44: API Event WB0070 (BOX ERROR) occurred (returned to caller)

2014-07-27 12:49:44: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:49:45: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:49:45: Box Event HW70-536 (2640442) occurred.

2014-07-27 12:49:45: API Event WB0070 (BOX ERROR) occurred (returned to caller)

2014-07-27 12:49:45: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:49:46: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:49:47: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:49:47: Box Event HW70-536 (2640442) occurred.

2014-07-27 12:49:47: API Event WB0070 (BOX ERROR) occurred (returned to caller)

2014-07-27 12:49:47: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:49:48: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:49:48: Box Event HW70-536 (2640442) occurred.

2014-07-27 12:49:48: API Event WB0070 (BOX ERROR) occurred (returned to caller)

2014-07-27 12:50:07: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:50:08: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:50:08: Box Event HW70-536 (2640442) occurred.

2014-07-27 12:50:08: API Event WB0070 (BOX ERROR) occurred (returned to caller)

2014-07-27 12:50:08: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:50:09: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:50:10: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:50:10: Box Event HW70-536 (2640442) occurred.

2014-07-27 12:50:10: API Event WB0070 (BOX ERROR) occurred (returned to caller)

2014-07-27 12:50:10: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:50:11: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:50:11: Box Event HW70-536 (2640442) occurred.

2014-07-27 12:50:11: API Event WB0070 (BOX ERROR) occurred (returned to caller)

2014-07-27 12:50:11: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:50:12: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:50:12: Box Event HW70-536 (2640442) occurred.

2014-07-27 12:50:12: API Event WB0070 (BOX ERROR) occurred (returned to caller)

2014-07-27 12:50:12: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:50:13: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:50:13: Box Event HW70-536 (2640442) occurred.

2014-07-27 12:50:13: API Event WB0070 (BOX ERROR) occurred (returned to caller)

2014-07-27 12:50:13: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:50:14: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:50:14: Box Event HW70-536 (2640442) occurred.

2014-07-27 12:50:14: API Event WB0070 (BOX ERROR) occurred (returned to caller)

2014-07-27 12:50:14: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:50:15: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:50:15: Box Event HW70-536 (2640442) occurred.

2014-07-27 12:50:15: API Event WB0070 (BOX ERROR) occurred (returned to caller)

2014-07-27 12:50:16: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:50:17: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:50:17: Box Event HW70-536 (2640442) occurred.

2014-07-27 12:50:17: API Event WB0070 (BOX ERROR) occurred (returned to caller)

2014-07-27 12:50:17: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:50:18: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:50:18: Box Event HW70-536 (2640442) occurred.

2014-07-27 12:50:18: API Event WB0070 (BOX ERROR) occurred (returned to caller)

2014-07-27 12:51:16: Handle 102 automatically released (no longer valid)

2014-07-27 12:51:16: Handle 103 automatically released (no longer valid)

2014-07-27 12:52:09: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:52:10: Box Event HW410-535 (2640442) occurred.

2014-07-27 12:52:10: Box Event HW70-536 (2640442) occurred.

2014-07-27 12:52:10: API Event HW0070 (RC) occurred.

CmDust-Result.zip

Источник

I installed Java, and the updater gives me the screenshot at the bottom, which I don’t know whether it means that it can’t find the key or that the key is already HID.

The OS does see the key.

Just in case it means anything related, I am pasting below the contents of the WIBU page Events tab. The Container tab says “Warning There was no CmContainer found” and the License Monitoring page says “ERROR 221 CmError 221: No network license information available, Error 221”.

2021-07-16 09:50:46: proxy: system proxy - host: '', user: ''
2021-07-16 09:50:46: No Kext installed. Using FileIO.
2021-07-16 09:50:46: CodeMeter for macOS/x86_64 (B7.20.4402.501.64.1200)
2021-07-16 09:50:46: Running on Mac OS X  10.15.7 
2021-07-16 09:50:46: Execution path: /Applications
2021-07-16 09:50:46: Found IPv4 address: 127.0.0.1
2021-07-16 09:50:46: Found IPv6 address: ::1 | fe80::1%lo0 | fe80::aede:48ff:fe00:1122%en5
2021-07-16 09:50:46: Used Communication Mode (Client): IPv6 IPv4 
2021-07-16 09:50:46: Used Communication Mode (Server): IPv6 IPv4 
2021-07-16 09:50:46: Used IP address: 127.0.0.1
2021-07-16 09:50:46: Used IP port: 22350
2021-07-16 09:50:46: Used CmWAN port: 22351
2021-07-16 09:50:46: Run as network server: no
2021-07-16 09:50:46: Run as CmWAN server: no
2021-07-16 09:50:46: Run as system service: yes
2021-07-16 09:50:46: TMR-Mode: disabled
2021-07-16 09:50:46: Box Access: use FileIO
2021-07-16 09:51:54: Removable Device has been plugged IN!
2021-07-16 09:51:55: EBL-Trace: 
2021-07-16 09:51:55: EBL-Trace: 
2021-07-16 09:51:55: EBL-Trace: 
2021-07-16 09:51:56: EBL-Trace: 
2021-07-16 09:51:56: EBL-Trace: 
2021-07-16 09:55:10: Removable Device has been plugged IN!
2021-07-16 09:55:14: Removable Device has been plugged IN!
2021-07-16 09:55:14: EBL-Trace: 
2021-07-16 09:55:14: EBL-Trace: 
2021-07-16 09:55:14: EBL-Trace: 
2021-07-16 09:55:14: EBL-Trace: 
2021-07-16 09:55:14: EBL-Trace: 
2021-07-16 10:03:37: Removable Device has been plugged IN!
2021-07-16 10:03:37: EBL-Trace: 
2021-07-16 10:03:37: EBL-Trace: 
2021-07-16 10:03:38: EBL-Trace: 
2021-07-16 10:03:38: EBL-Trace: 
2021-07-16 10:03:38: EBL-Trace: 
2021-07-16 10:28:33: Access from local(IPV4)(Ignacio) to SubSystem (Handle 16) 
2021-07-16 10:28:33: API Event WB201 (BOX NOT FOUND) occurred (returned to caller)
2021-07-16 10:28:33: Handle 16 released
2021-07-16 10:28:33: Access from local(IPV4)(Ignacio) to SubSystem (Handle 17) 
2021-07-16 10:28:33: API Event WB201 (BOX NOT FOUND) occurred (returned to caller)
2021-07-16 10:28:33: Handle 17 released
2021-07-16 10:28:33: Access from local(IPV4)(Ignacio) to SubSystem (Handle 18) 
2021-07-16 10:28:33: License information imported successfully
2021-07-16 10:28:33: Detecting CmContainer with Serial Number 32767-34945 
2021-07-16 10:28:33: Found new entries: 1
2021-07-16 10:28:33: Handle 18 released
2021-07-16 10:28:33: Access from local(IPV4)(Ignacio) to SubSystem (Handle 19) 
2021-07-16 10:28:33: Handle 19 released
2021-07-16 10:28:33: Access from local(IPV4)(Ignacio) to IFI (Handle 20) 
2021-07-16 10:28:33: Handle 20 automatically released (rescan)
2021-07-16 10:28:33: API request failed, Handle 20 is invalid.
2021-07-16 10:28:33: API Event WB106 (INVALID HANDLE) occurred (returned to caller)
2021-07-16 10:28:33: Access from local(IPV4)(Ignacio) to SubSystem (Handle 21) 
2021-07-16 10:28:33: Handle 21 released
2021-07-16 10:28:33: Entry (101074:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:33: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:33: Entry (5000003:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:33: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:33: Entry (6000170:61:4168089601) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:33: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:33: Executing Broadcast for CodeMeter License Servers
2021-07-16 10:28:34: Entry (101074:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (5000003:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (6000170:61:4168089601) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (101074:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (5000003:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (6000170:61:4168089601) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (101074:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (5000003:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (6000170:61:4168089601) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (101074:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (5000003:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (6000170:61:4168089601) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (101074:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (5000003:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (6000170:61:4168089601) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (101074:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (5000003:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (6000170:61:4168089601) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (101074:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (5000003:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (6000170:61:4168089601) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (101074:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (5000003:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (6000170:61:4168089601) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (101074:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (5000003:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (6000170:61:4168089601) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (101074:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (5000003:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (6000170:61:4168089601) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (101074:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (5000003:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:34: Entry (6000170:61:4168089601) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:34: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Entry (101074:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:35: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Entry (5000003:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:35: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Entry (6000170:61:4168089601) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:35: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Entry (101074:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:35: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Entry (5000003:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:35: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Entry (6000170:61:4168089601) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:35: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Entry (101074:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:35: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Entry (5000003:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:35: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Entry (6000170:61:4168089601) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:35: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Entry (101074:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:35: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Entry (5000003:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:35: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Entry (6000170:61:4168089601) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:35: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Entry (101074:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:35: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Entry (5000003:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:35: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Entry (6000170:61:4168089601) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:35: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Entry (101074:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:35: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Entry (5000003:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:35: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Entry (6000170:61:4168089601) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:35: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Entry (101074:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:35: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Entry (5000003:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:35: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Entry (6000170:61:4168089601) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:35: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Entry (101074:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:35: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Entry (5000003:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:35: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Entry (6000170:61:4168089601) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:35: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Entry (101074:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:35: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Entry (5000003:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:35: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Entry (6000170:61:4168089601) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:35: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Entry (101074:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:35: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Entry (5000003:61:137887743) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:35: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Entry (6000170:61:4168089601) not found - Event WB0200 (ENTRY NOT FOUND), Request IP-Address local(IPV4)(Ignacio) (SID 0xce) with StationShare Mode
2021-07-16 10:28:35: API Error 200 (ENTRY NOT FOUND) occurred!
2021-07-16 10:28:35: Access from local(IPV4)(Ignacio) to SubSystem (Handle 88) 
2021-07-16 10:28:35: API Event WB201 (BOX NOT FOUND) occurred (returned to caller)
2021-07-16 10:28:35: Handle 88 released
2021-07-16 10:28:35: Access from local(IPV4)(Ignacio) to SubSystem (Handle 89) 
2021-07-16 10:28:35: API Event WB201 (BOX NOT FOUND) occurred (returned to caller)
2021-07-16 10:28:35: Handle 89 released
2021-07-16 10:28:35: Access from local(IPV4)(Ignacio) to SubSystem (Handle 90) 
2021-07-16 10:28:35: License information imported successfully
2021-07-16 10:28:35: Detecting CmContainer with Serial Number 32767-34945 
2021-07-16 10:28:35: Found new entries: 1
2021-07-16 10:28:35: Handle 90 released
2021-07-16 10:28:35: Access from local(IPV4)(Ignacio) to SubSystem (Handle 91) 
2021-07-16 10:28:35: Handle 91 released
2021-07-16 10:28:35: Access from local(IPV4)(Ignacio) to IFI (Handle 92) 
2021-07-16 10:28:35: Handle 92 automatically released (rescan)
2021-07-16 10:28:35: API request failed, Handle 92 is invalid.
2021-07-16 10:28:35: API Event WB106 (INVALID HANDLE) occurred (returned to caller)
2021-07-16 10:34:35: API Error 221 (NETINFO FAILED) occurred!
2021-07-16 10:34:35: API Error 221 (NETINFO FAILED) occurred!
2021-07-16 10:35:12: Error: No data received in new connection (timeout).
2021-07-16 10:35:40: API Error 221 (NETINFO FAILED) occurred!
2021-07-16 10:35:40: API Error 221 (NETINFO FAILED) occurred!

Источник

Deel op:

Error Messages

The error 106 refers to an «invalid handle» and occurs if a handle was used CodeMeter does not know.

This may, for instance, happen in the following cases:

1. You use a protected software or a software applying CodeMeter Code API/Wupi API and while doing so restart the CodeMeter service. This renders all handles invalid and reusing handles in your software result in error 106.

2. CodeMeter itself automatically release handles, if:

a) the CmDongle was disconnected to which the handles previously referred to,

b) the process which opened the handles no longer exists.

The check for the processes is performed for each new license access, e.g. using ‘CmAccess2()’,

however at latest after 1 minute.

c) the handles were not used longer than the specified CleanUpTimeOut value (default 120 minutes).

Solution options

1. In order to avoid the automatic release of handles as described in 2.c), you should:

a) manually release all handles no longer required after the access using ‘CmRelease()’/’WupiFreeLicense()’.

b) regularily use handles responsible for counting licenses or license management as in AxProtector runtime check

on encryption or on calling ‘CmCrypt()’/’WupiCheckLicense()’ in the code.

Using ‘CmCrypt()’ you may encrypt/decrypt data increasing security.

Morever, at ‘CmCrypt()’/’WupiCheckLicense()’ also the license itself is checked, i.e.

whether the license is still valid and meanwhile the unit counter has not a value of 0 or the expiration time has reached.

2. In addition, you may also set an own CleanUpTime at ‘CmAccess2()’ using the CMCREDENTIAL structure

and the member ‘mulCleanupTime’.

This own time will overwrite the registry default value in HKEY_LOCAL_MACHINESOFTWAREWIBU-SYSTEMSCodeMeter

ServerCurrentVersionCleanUpTimeOut

This may look like:

CmCredential cmCred = new CmCredential();

cmCred.CleanupTime = 240;

CmAccess2 cmAcc = new CmAccess2();

cmAcc.Credential = cmCred;

cmAcc.Ctrl |= CmAccess.Option.UserLimit;

cmAcc.FirmCode = 10;

cmAcc.ProductCode = 13;

HCMSysEntry hcmse = cmApi.CmAccess2(CmAccessOption.Local, cmAcc);
This error message results from a security feature activated on default, i.e. the code integrity check. In AxProtector you are able to activate or deactivate this feature. In the AxProtector GUI you find this option on the navigation page «Security options | Advanced». For the commandline use the parameter -cav.

Please note that the -cav option cannot or should not currently be used when using the Gnu Compiler Collection (GCC) under Windows. At runtime, GCC compiles in such a way that it is not possible to pre-calculate the checksums for later validation.

The code integrity check covers your protected application and DLLs to ensure at runtime, that the files are your original files and no manipulated files are used. In addition, for every second runtime check also the memory integrity of the process space of your application is checked. If then, for example, at runtime, a third party program modifies something in the memory of the process room, for security reasons the check triggers the exit of your application, for example, to prevent a reverse engineering of other manipulations of your application at runtime. Please find a description and more information in the separate CodeMeter Developer Guide documentaion in sections «Automatic Software Protection using AxProtector | AxProtector Tab | Windows Application or DLL | Security Options | Advanced Security Options» and «Automatic Software Protection using AxProtector | Commandline Options for AxProtector | Options for Encrypting and Decrypting».

If the code integrity check falsely strikes, this may also may be triggered by an anti-virus programs. These may also check modifications in memories of running applications. Then it is recommended to exclude your protected application from the anti-virus check and to specify the application as exception.
This error usually occurs when you try to add a new Firm Item for a Firm Code for which a Firm Item already exists.

A Firm Code can only occur once in a CmContainer.

Alternatively, this error can also occur, if you try to create the Context File from a Firm Item that you are not allowed to access.

In this case, the access protection list is controlled, which is configured in CodeMeter WebAdmin at «Settings| Server | License access permissions».

That means, here you have to give your system, from which you create the context file (typically localhost), the permissions to access the Firm Item, or with the setting «Mode | Simple» allow access to all Firm Items.
If the error 229 occurs. the problem does not involve the license update file (*.WibuCmRaU) but the license request file (*.WibuCmRaC) as basis for programming the update.

Exactly from this context file a previous update file must have been already programmed and imported into the CmContainer. On a second import of the update file the error occurs because in the meantime the CmContainer already has a different status due to the first import.

Internal process

Each CmContainer holds an update counter, i.e. the «Firm Update Counter» (FUC), which has a specific counter status. If a context file is created from the CmContainer, the FUC holds the actual count.

The subsequent programming of the update file involves an increment of the FUC by a defined number. The number of counter units depend on the Product Item Options programmed. In addition, for security reasons, the update file also holds the old, i.e. to be expected, counter status to enable a validation of the CmContainer status. On importing the update file it is first checked whether the CmContainer has the expected counter status. If the validation is successful, the FUC in the CmContainer gets a new FUC value. However, if the counter does not match the expected value, the error 229 is issued and the update process is stopped.

To avoid this behavior, please make sure that for each new update programming you must use a current license request context file.
This error occurs because either the CmFirm.wbc file is missing completely or does not contain your Firm Code. You must import this file to your system.

In addition to the Firm Security Box (FSB), programming licenses requires the CmFirm.wbc file with your Firm Code. You received this file from Wibu-Systems when you became a customer. You might find this file on another system, e.g. located in «%ProgramData%CodeMeterDevKit».

You can open the CmFirm.wbc file using a text editor and check for your Firm Code, i.e. not only the Test-Firm Code, e.g. 6000010, is specified.

If the required CmFirm.wbc file is not available, please contact Wibu-Systems Sales.

For importing the correct CmFirm.wbc file, please proceed as follows:

1. Open CodeMeter Control Center

2. Navigate to the menu item «File | Import License» and select the CmFirm.wbc file.

Alternatively drag & drop the file onto CodeMeter Control Center. This however requires that the CmFirm.wbc file has been locally saved before.
Error 231 occurs when trying to assign a license to a CodeMeter License Server whose license access permissions exclude the client.

Please open CodeMeter Control Center on the server and use the WebAdmin button to open the WebAdmin web interface.

Navigate here to «Settings | Server | License Access Permissions».

There are two different modes for the license access permissions:

— Simple: A simple whitelist that defines which clients may occupy a license.

— Advanced: A set of rules with Active Directory integration that allows more complex configurations (Windows only).

In most cases, the simple mode is sufficient.

Now check which clients are already registered and, if necessary, add all clients that should have additional access to the licenses. You must use either the IP or DNS name of the client to do this.

If you want all clients to have access and there should be no special restrictions, use the simple mode and clear the list completely.

After you have made the desired changes, restart the CodeMeter service.

To do this, you can use the menu option «Action | Restart CodeMeter Service» in CodeMeter Control Center.

If the problem persists, create a CmDust.log of client and server and send it to us.
Event 91 occurs, if an attempt is made to re-establish encrypted communication with a CmDongle too often within a certain time period.

For security reasons the CmDongle limits how often an encrypted communication is restablished within a certain time period to make the automatic analysis of the communication with common hacking tools more difficult. If event 91 occurs, this means that the dongle has locked itself to prevent further attempts to establish an encrypted communication. This lock is valid for 5 minutes. During this time, the CmDongle has to stay connected without trying to establish a new communication. So just leave the dongle connected for a while and wait until the lock is released.

The limit is chosen in a way that the lock should not engage during normal use. So, if this event occurs, it means that something has gone wrong. Mostly due to a faulty USB port or controller. It is best to test on another port or PC. If it happens again on another PC, it is possible that the CmDongle could have a technical defect. In this case, you should replace the CmDongle. Please make sure that you do not use 3rd party software which could influence the USB communication and therefore disturb/prevent the encrypted communication.
This behavior occurs, when the number of transactions allowed by your Firm Security Box (FSB) is used up. You cannot use your Firm Code any more to program an empty CmContainer.

In order to provide you with additional transactions, we require a license request (Context) file of your FSB sent to sales(at)wibu.com.

If you are using a Firm Code 1xx.xxx or 5.xxx.xxx (i.e. no Universal Firm Code with 6.xxx.xxx) we need a Context File, which you can send to sales@wibu.com

To create the Context File of your FSB, please proceed as follows:

1. Connect the FSB to the computer.

2. Open CodeMeter Control Center.

3, Select the FSB in the left Licenses tab.

4. Click the «License update»-button.

Licenses are read and the CmFAS Assistant opens.

5. Select the options «Create license request | Extend existing license | Firm Security Box Item (99)» on the subsequent wizard pages.

6. Specify the path and file name to save the context file under any name to your chosen location.
This error occurs, if your CodeMeter Runtime installation still contains some old components.

Please check, if the file ‘C:Program Files (x86)CodeMeterRuntimebinWibuCm32.dll’ is still on your system and delete it if necessary.

Then uninstall CodeMeter completely again.

If you find several entries for the CodeMeter runtime in the Control Panel, please uninstall them all.

Finally restart your system once and reinstall the current CodeMeter Runtime.

Источник

This is an issue I saw crop up in the previous Auth we were using, ever so randomly the API Server pukes and throws a 221 for a valid key (i’ve had it happen to 2 members so far going live).

When this happens, Auth panics, deletes the key, and removes services.

[14/Jan/2016 21:02:07] ERROR [services.managers.eve_api_manager:85] Unhandled APIError occured.
Traceback (most recent call last):
  File "/home/allianceserver/allianceauth/services/managers/eve_api_manager.py", line 80, in check_api_is_type_account
    info = account.key_info()
  File "/usr/local/lib/python2.7/dist-packages/evelink/api.py", line 513, in wrapper
    kw['api_result'] = client.api.get(self.path, params=params)
  File "/usr/local/lib/python2.7/dist-packages/evelink/api.py", line 295, in get
    raise exc
APIError: Illegal page request! Please verify the access granted by the key you are using! (code=221)
[14/Jan/2016 21:02:07] INFO [celerytask.tasks:333] Determined api key 4945473 for user xxx is no longer type account as required.
[14/Jan/2016 21:02:07] INFO [eveonline.managers:183] Deleting user 30 character xxx from api 4945473
[14/Jan/2016 21:02:07] INFO [eveonline.managers:183] Deleting user 30 character xxx from api 4945473
[14/Jan/2016 21:02:07] INFO [eveonline.managers:167] Deleted user 30 api key id 4945473
[14/Jan/2016 21:02:08] INFO [services.managers.phpbb3_manager:184] Disabled phpbb user xxx
[14/Jan/2016 21:02:08] INFO [authentication.managers:52] Updated user xxx forum info in authservicesinfo model.
[14/Jan/2016 21:02:08] INFO [services.managers.teamspeak3_manager:238] Deleted user with id xxx from TS3 server.
[14/Jan/2016 21:02:08] INFO [authentication.managers:101] Updated user xxx teamspeak3 info in authservicesinfo model.
[14/Jan/2016 21:02:09] INFO [services.managers.discord_manager:342] Setting discord groups for user xxxto []
[14/Jan/2016 21:02:09] INFO [services.managers.discord_manager:412] Deleted user with id xxxxfrom discord server id xxx
[14/Jan/2016 21:02:09] INFO [authentication.managers:121] Updated user xxx discord info in authservicesinfo model.
[14/Jan/2016 21:02:09] INFO [celerytask.tasks:50] Disabled expired member xxx
[14/Jan/2016 21:02:09] INFO [celerytask.tasks:442] User xxxhas no valid api keys and has been disabled.

This key was valid, as were the other two when the hiccup happened.

Now, I understand that the deleting key and removing services is expected behavior if a key becomes no longer valid (user fiddles with it, user leaves corp, etc), but the issues I’ve see whether it be the api servers puking or being randomly down between queries, would it be worth it to flag ineligible for a verification pass before removing services?

example: during checks user x comes up as ineligible, mark this and continue checking other keys, after some time (1 minute, 5 minutes, whatever), check marked keys again to be sure, then proceed (all is well carry on, or key is indeed invalid remove services). Something along those lines

Источник

This post has already been read 8831 times!

Starting with VISSIM v8, the CodeMeter dongle stores more licensing data in its flash RAM than earlier VISSIM versions. This may result in an issue called USB pass-through timeout, particularly, when running VISSIM from within a VMWare virtual machine.

In this article, let’s address this issue, and present a documented fix.

In a previous post, we have discussed how to run VISSIM in a VMWare Workstation virtual environment:

https://blog.wupingxin.net/2015/05/21/vmware-usb-passthrough-running-vissim-in-a-virtual-machine/

This should be working fine until recently when PTV released VISSIM 8.0. It is a great upgrade from v7 with a lot of enhancements, especially the mesoscopic traffic simulation, to name just the most note-worthy.

For existing users of VISSIM v7, the upgrade to V8 requires one unusual step, i.e., to update the contents of the CodeMeter key flash. Vissim V8 now apparently has more licensing-related data to enter the dongle than old Vissim versions. As a result, after upgrading to VISSIM v8 with the “re-flushed” CodeMeter key, you might have problem launching VISSIM in a VMWare virtual machine.

The symptom is something like this – first the code meter icon shows up in a yellowish-green color different than the normal color, and then VISSIM complains “CmContainer entry not find Error 200”:

And you might see CodeMeter log output as follows:

The problem is really caused by USB timeouts when reading a large quantity of licenses. This happens when CmStick uses the VMWare USB pass-through communication mode between CodeMeter Run-time Server (that is running inside the virtual machine) and CM-Stick (that is plugged via the host physical computer’s USB port). That is why I believe that PTV has added a lot more license items into the CmStick than earlier versions, since this didn’t happen before. The solution (thanks to the heads up from Mr. John Battista from WiBu USA) is to use the “File I/O” communication mode (UseUmsDA = 0) :

CodeMeter communication mode (on the virtual machine) can be changed as follows:

Then everything is working again. Have fun!

This post has already been read 8831 times!

Источник

Graphisoft Community

Subscribe to RSS Feed
Mark Topic as New
Mark Topic as Read
Pin this post for me
Bookmark
Subscribe to Topic
Mute
Printer Friendly Page

‎2021-07-15 09:14 PM

When I insert the Codemeter key, the light blinks intermittently green-orange for a few seconds and then goes off. Google is not helping with interpreting.

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

‎2021-07-16 05:23 AM

David Maudlin / Architect

AC26 USA • iMac 27″ 4.0GHz Quad-core i7 | 24 gb ram • MacBook Pro 2.8GHz | 16 gb ram • OSX10.15.7

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

‎2021-07-16 05:33 AM

Thank you very much for your report and I am very sorry to hear about the issue!

Looking forward to hearing from you!

Best regards,
Minh

Minh Nguyen
Technical Support Engineer
GRAPHISOFT

Источник

Graphisoft Community

Subscribe to RSS Feed
Mark Topic as New
Mark Topic as Read
Pin this post for me
Bookmark
Subscribe to Topic
Mute
Printer Friendly Page

‎2021-07-15 09:14 PM

When I insert the Codemeter key, the light blinks intermittently green-orange for a few seconds and then goes off. Google is not helping with interpreting.

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

‎2021-07-16 05:23 AM

David Maudlin / Architect

AC26 USA • iMac 27″ 4.0GHz Quad-core i7 | 24 gb ram • MacBook Pro 2.8GHz | 16 gb ram • OSX10.15.7

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

‎2021-07-16 05:33 AM

Thank you very much for your report and I am very sorry to hear about the issue!

Looking forward to hearing from you!

Best regards,
Minh

Minh Nguyen
Technical Support Engineer
GRAPHISOFT

Источник

Graphisoft Community

Subscribe to RSS Feed
Mark Topic as New
Mark Topic as Read
Pin this post for me
Bookmark
Subscribe to Topic
Mute
Printer Friendly Page

‎2021-07-15 09:14 PM

When I insert the Codemeter key, the light blinks intermittently green-orange for a few seconds and then goes off. Google is not helping with interpreting.

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

‎2021-07-16 05:23 AM

David Maudlin / Architect

AC26 USA • iMac 27″ 4.0GHz Quad-core i7 | 24 gb ram • MacBook Pro 2.8GHz | 16 gb ram • OSX10.15.7

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

‎2021-07-16 05:33 AM

Thank you very much for your report and I am very sorry to hear about the issue!

Looking forward to hearing from you!

Best regards,
Minh

Minh Nguyen
Technical Support Engineer
GRAPHISOFT

Источник

Api error 221 netinfo failed occurred базис

Здравствуйте, удалось как-то решить проблему? У меня тоже возникла вчера. До этого все было нормально 🙁

Да вроде бы и перечитал перед тем как написать. Может конечно не максимально внимательно, но показалось, что ничего конкретного там нет. Ну да, объявили намерения перестать поддерживать софт, на старых версиях не поддерживается уже сбор. Но у меня такая же ошибка выскакивала и раньше, потом без обновлений программа самоизлечивалась, вот и интересуюсь если какие-то еще способы реанимации или уже RIP

Нет, я из Украины, плюс парсинг слов идет на английском. 🙂

А при чем тут его ссылка? Там разве данную ошибку решают как-то?

Понял. Спасибо. Парсил без прокси, но как вариант, попробую поставить :)) Мало ли.

Там написано, что решать не будут. Как можно решить на пользовательском уровне, если не вносить правки в шаблоны и код.

Источник

LabVIEW

Ftp error 221

‎07-03-2012 11:16 AM

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report to a Moderator

When trying to FTP a file to another computer in the network using LabVIEW 2011, I had Error 221 in my log file, Error Detail: 221, Error Message: 221 Goodbye. I could not found any useful info online. Could somebody give me some hints how to fix it?

Thanks in advance. Cong.

Re: Ftp error 221

‎07-03-2012 03:26 PM

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report to a Moderator

Are you able to use a program such as FileZilla on the same PC as the LabVIEW program to do the FTP? You might find that you have a problemt here as well. If not then you know it is a LabVIEW problem and not some other issue.

Re: Ftp error 221

‎07-03-2012 04:24 PM

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report to a Moderator

Error 221 is «Service closing control connection». This implies you are not doing something correctly when connecting. How are you doing the ftp? Are you using the Internet toolkit? Some other API, like .NET? Manually using TCP/IP functions?

Re: Ftp error 221

‎01-16-2014 03:32 PM

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report to a Moderator

Resurrecting becaue I have the same «error» actually it is a warning, not an error for me and all data transactions appear to work fine.

The wiki linked in the post prior to this one shows that codes in the «2xx» range are » Positive Completion reply The requested action has been successfully completed. A new request may be initiated.»

I just find it interesting that it shows up on the error cluster even as a «warning» since this seems to be the expected, positive end to an FTP session?

I will just filter out this warning code unless someone can give more details on why this should never be seen?

the session is using the NI FTP vi’s with «active» set to «False».

Источник

Стандартные коды ошибок:

Ошибка	Значение
unspecified	Тип ошибки не указан. Подробности смотрите в сообщении.
invalid_api_key	Указан неправильный ключ доступа к API. Проверьте, совпадает ли значение api_key со значением, указанным в личном кабинете.
access_denied	Доступ запрещён. Проверьте, включён ли доступ к API в личном кабинете и не обращаетесь ли вы к методу, прав доступа к которому у вас нет.
unknown_method	Указано неправильное имя метода.
invalid_arg	Указано неправильное значение одного из аргументов метода.
not_enough_money	Не хватает денег на счету для выполнения метода.
retry_later	Временный сбой. Попробуйте ещё раз позднее.
api_call_limit_exceeded_for_api_key	Сработало ограничение по вызову методов API в единицу времени. На данный момент это 1200 вызовов в минуту. Для метода sendEmail — 60.
api_call_limit_exceeded_for_ip	Сработало ограничение по вызову методов API в единицу времени. На данный момент это 1200 вызовов в минуту. Для метода sendEmail — 60.

Частые ошибки без указания типа:

Ошибка	Значение
«These list ids=»…» has no confirmation letters»	Не создано письмо подтверждение для списка, на который подписывается адресат. Откройте в личном кабинете список контактов на который настроена подписка, внизу слева есть пункт «Инструменты подписки и отписки». Заполните все поля на этой странице и сохраните. Инструкция по созданию письма подтверждения.
“Contacts test@example.org and +77777777 already exist but owned by different subscribers”	Вы добавляете email и телефон контакта, который уже есть в вашем кабинете. Укажите email или телефон, который не принадлежит другому адресату.
«Call to a member function getMessage() on boolean»	Вызов осуществляется с одновременным использованием методов GET и POST. Выполняйте запрос только одним из данных методов.

Кроме этих ошибок, могут быть и другие, указанные в описаниях конкретных методов.

Пример ответа с ошибкой:

{"error":"AK100310-02","code":"invalid_api_key"}

Источник

Table Of Contents

What Is Codemeter.exe?
How to Fix Codemeter.exe errors
- 1st Fix (Removal)
- 2nd Fix (2nd Removal Method)
- 3rd Fix (Uninstall Runtime)
- 4th Fix (Mac Removal)
- 5th Fix (Linux Removal)
- 6th Fix (Malware & Virus Scan)
Forum Feedback
- - Wibu Systems CodeMeter Manifesto Explained: Shaping Software Monetization
Conclusion
- Related Posts:

In this post, we examine the codemeter.exe process. We’ll help you figure out what it is and how to remove it from various operating systems.

Indeed, there are often a few error messages that are related to the executable file known as codemeter.exe.

You’ve probably seen messages like “codemeter.exe is not a valid Win32 application” or “codemeter.exe is not a valid Win32 application”.

Whenever you see this error, some functions may not be able to work properly because codemeter.exe is preventing them from working.

The codemeter.exe errors aren’t very harmful to your computer, so you don’t need to be alarmed.

However, they’re extremely annoying and can prevent certain programs or functions from working properly. Fortunately, there are ways to disable it or even remove it completely.

When that happens, you won’t see those error messages anymore, and the functions that were prevented from working will function properly again.

Before we learn how to fix the errors relating to codemeter, it’s important to know what it exactly is first.

In a nutshell, codemeter is an executable file that comes from the Wibu System’s Runtime Technology Package.

According to the manufacturer’s website, “CodeMeter is the universal technology for software publishers and intelligent device manufacturers, upon which all solutions from Wibu-Systems are built. CodeMeter combines the following applications:” piracy protection, licensing, security.

It’s a software that’s already installed into your system and just stores some data into it. Other than that, it doesn’t have much use actually.

It’s pretty much similar to brstmonw.exe or brccuxsys.exe which are also just executable files inside your system.

Since it doesn’t really serve any purpose like brstmonw.exe, most people would simply disable or take it out instead. Here are a few ways on how to do that:

How to Fix Codemeter.exe errors

1st Fix (Removal)

The fastest fix is to simply remove the executable file from the computer.

It’s actually as simple as deleting it from the Program Files section; however, doing so may incur a few errors.

To prevent that, you should disable Codemeter first.

Here are some steps to do that as instructed by HTG.GG:

First, open Run by pressing Windows key and R at once. Afterward, type services.msc in the search bar.
Look for Codemeter Runtime Server in the Services section.
Right click on that option and click Properties.
On the Startup type section, choose Disable from the dropdown menu then click Stop then Apply.
After that, go to Program Files and look for Codemeter.exe then delete it to remove it permanently from your system.

2nd Fix (2nd Removal Method)

There are times when doing this will just delete the surface version of the Codemeter application.

However, it may still be present in the system. If that’s the case, then you can also try this second method of deleting the application.

This method was provided by the program’s creator Wibu itself:

Go to Software in the control panel of your computer.
Click “Codemeter Runtime Kit” then “Remove”.
If you can’t find the Codemeter Runtime Kit in the Control Panel, you need to uninstall the other software which use Codemeter.

After you do this, you shouldn’t have any more problems with this error.

3rd Fix (Uninstall Runtime)

Another way to do this, as recommended by Process Library, is to uninstall the Runtime Technology Package completely instead of just uninstalling the Codemeter Runtime Kit.

To do so, simply follow these few steps:

Run the program appwiz.cpl.
Look for Runtime Technology Package in the list of programs presented to you.
Click on Uninstall and wait for the program to be uninstalled.

This fix can definitely address the problem with the codemeter executable file.

4th Fix (Mac Removal)

What if you’re not using a Windows OS?

What if you’re using a Mac OS and you encounter a codemeter related problem?

Well, you’ll still have to remove it, but the process will be a little bit different this time.

You can follow these steps to fix Codemeter errors on your Mac computer as instructed by Wibu support:

Open the disk image for CmRuntimeUser.dmg.
If you can’t find it, go to the website of Wibu Systems then download the runtime file.
Start the CmUninstall.mkpg program which is located in the CmRunTime directory.
You may also enter this following code in the command option:

$ sudo installer -pkg /Volumes/CmRuntimeUser/CmUninstall.mpkg -target

After you do that, the codemeter should be taken out of your computer system, and you shouldn’t be able to see those weird codemeter errors anymore.

5th Fix (Linux Removal)

How about a fix for the codemeter errors that appear in your Linux OS? Fortunately, Wibu support also shares some steps on how to address this type of issue.

Follow these steps to do so:

Use the shell command [rpm -e CodeMeter] if you’re using RedHat or Fedora.
Use the shell command [dpkg -r CodeMeter] if you’re using Ubuntu or Debian.

6th Fix (Malware & Virus Scan)

Just like a lot of executable files, this one also gives the risk of a virus coming in if you don’t protect your computer properly.

That said, Errorboss recommends that you scan your computer from time to time. Also, there will be times when an executable file will contain a virus and is corrupted – which explains why there’s an error message in the first place.

So if you want to prevent your computer from contracting some kind of virus or malware, then you have to make sure you scan it from time to time.

If you see any weird virus pops out during the scan, you have to dispose of it quickly. You can use some good antiviruses such as Avast or even Windows Defender. They can spot viruses and quickly get rid of them afterward.

Forum Feedback

According to File.net, CodeMeter Runtime Server belongs to or is associated with the software: CodeMeter Runtime Kit or Authorizer Ignition Key Support or Mastercam (version X9) or Rockwell Automation CM Runtime by WIBU-SYSTEMS AG.

We also came across this interesting video:

Wibu Systems CodeMeter Manifesto Explained: Shaping Software Monetization

We examined some popular forums to get a sense of what people are discussing and discover that the primary themes related to how to remove it, where to download it, runtime kit problems, the control center, runtime server issues, what to do if it fails to start, vulnerability issues and runtime 32-bit server issues.

One person explained that it is a copy protection dongle and that he has discovered it being used by Reason 6.

Another computer owner was perplexed because he says that he didn’t install it but it began to show up on his computer. Apparently, it had installed itself surreptitiously in this Windows users operating system

Another person who purchased Zip Repair Pro says that it was installed without notification and therefore he considers it a backdoor spyware program.

Another person had an interesting experience – saying that it was installed on his personal computer alongside a parts catalog for a German computer manufacturer.

A video gamer said that it got installed when he added the NVidia GeForce graphics driver package.

Continuing with this trend, another computer user sad that he didn’t authorize it to be installed and he discovered that it doesn’t actually have an uninstall file. What this means, you’re unable to uninstall it in the traditional way- you have to manually delete the folders to eradicate it from your system.

Another person said that after he installed the Rockwell (Logix Studio) activation software, he discovered this licensing software installed as a Service on his computer. Another user advised him that in his experience it has the capacity to modify your Windows Firewall settings.

A particularly savvy computer user explained that it is a software validation license program and in his experience associated with Mastercam.

Another computer owner said that “C:PROGRAM FILES (X86)CODEMETERRuntimebinCODEMETER.EXE” tried to enable itself as an invisible autorun program after he had restarted his computer subsequent to employing Recover My Files software.

Conclusion

If you happen to see several errors that are related to the codemeter executable file, then you’re not alone. There are a lot of people who have experienced very similar situations wherein some of their functions do not work because of a codemeter.exe error message.

So what is the ultimate solution to that?

Simply remove the file that has the codemeter application. Will some functions work when you take it out? Possibly.

However, you won’t really experience them. With that said, it is actually much better to just uninstall codemeter if you don’t see any use for it. It’ll save you a lot of hassle from seeing those unwanted error messages.

Ryan is a computer enthusiast who has a knack for fixing difficult and technical software problems. Whether you’re having issues with Windows, Safari, Chrome or even an HP printer, Ryan helps out by figuring out easy solutions to common error codes.

Источник