Skip to content
Request a Quote Request a Trial
Request a Quote Request a Trial

CodeMeter Control Center: License Failure in TracePro, OSLO, and RayViz Due to Service Shutdown

Question

How can I resolve the License Failure resulting from the Codemeter service shutting down?

Synopsis

License failure - TracePro, OSLO, RayViz - CodeMeter service shuts down

Symptoms

  • TracePro,OSLO, or RayViz is running at the moment the Codemeter service shuts down
    • License Not Available message
  • Launching TracePro, OSLO, or RayViz when the Codemeter service has already shut down
    • Possible Error Messages:
      • GetAllWibuLicenseKeys: CmAccess2(local): returned xxx     Called from line yyy of LamLicenseContext.cpp
      • Unknown Error(100012): CmContainer / WibuKey runtime system is not installed!
    • Past Error Messages:
      • Code Integrity Check Failed
      • GetAllWibuLicenseKeys: CmAccess2(local): returned xxx    Called from line yyy of WibuLicenseUtils.cpp

Solution

CodeMeter (created by Wibu Systems AG) is the licensing software used in TracePro, OSLO, and RayViz. The problem occurs when the CodeMeter Service is not running. The first step is to restart the services:
  • launch the CodeMeter Control Center (Windows Start Menu / CodeMeter)
  • select Process from the menu, Stop the service
  • select Process from the menu, Start the service

If this is successful, you should see "CodeMeter is started" at the bottom of the screen, and your license number should appear in the list of licenses. Please try launching TracePro, OSLO, or RayViz The restart of the service may be sufficient.

However, if the CodeMeter service continues to shut down, the probable cause is that some antivirus or security software incorrectly perceives that CodeMeter is a virus or security threat, and it intentionally shuts the service down.

A quick test is to disconnect from the internet and the company network, then temporarily disable the potentially conflicting software. Run TracePro for a while, long enough to be convinced that the problem is no longer occurring. That result strongly suggests that the disabled software is the cause of the original problem.

The final solution may be:

  • add CodeMeter.exe to the software's white list
  • wait for updates of the software
  • replace the software
  • run TracePro, OSLO, or RayViz with the software disabled and the computer disconnected from the internet and the company network

Current Solution - A customer has reported that " VMWare Carbon Black Cloud Endpoint Standard" caused this problem.

Historical Solution - Customers reporting this error in TracePro 7.5 around 2015 were running the F-Secure antivirus software, and resolved the problem by disabling the F-Secure "DeepGuard Advanced Process Monitoring" function.