Search the Community
Showing results for tags 'error 263'.
Found 1 result
A number of customers of time-based licenses contacted us lately about this issue. We are terribly sorry about this inconvenience, and I can but apologize for this embarrassment. I'm currently trying to collect as much information as possible to make sure that we understand why this happens to so many people, and what we can do in order to prevent it from happening again (for obvious reasons). For that, I need your help! Please Start the "CmDUST" program that is being installed along with the CodeMeter runtime software on every compmuter. After the program is done it will open a window of the Windows Explorer with the file "CmDust-Result.log" Please go to C:\ProgramData\CodeMeter\logs ... See all the files named "CmActDiagLog.... .log" - please zip 'em up. Attach the zip file as well as the CmDust log to an email that you send to Support@Wibu.de (and put me on CC, please). They will analyze the case as soon as possible, and get back to you (and me) with recommendations. At this point we want to understand what exactly is going on. A possible source of interference could be an anti-virus program preventing the proper initialization of the CodeMeter service. Sometimes it is enough to just restart the CodeMeter service. To do so, type in "Services" to find the app that lets you review all of them. Sort by name, locate the CodeMeter Runtime Server, and right-click it, then select "restart" and see if that helps with the virtual CodeMeter container that is currently listed in your CodeMeter Control Center window, probably as "broken" (serial number 128-xxxxxxxxxx, in red color). Which version of Windows 10, if at all, do you have? Home, or Professional? Win 10 only: If Professional, have you selected to be in the fast, or in the slow ring for Windows feature updates? I could imagine that it's the recent "Anniversary Update" that may have ruined things. But at this point it's all speculation.