Rhino license manager initialization failed with error -200

[5p4k]

I cannot get this to work. I checked out the configuration and the video and followed through as best I could, but upon starting Rhino, I see the message Rhino license manager initialization failed with error -200, and Rhino closes itself.

I am using

• Lutris 0.5.9.1
• Mint 20.2 (based on Ubuntu 20.04)
• The system wine is installed according to these instructions, wine --version yields wine-6.0.2. I am not sure how much of that is even needed?
• The wine I am using for Rhino through Lutris is lutris-6.10-7-x86_64, which bundles wine 6.10
• I tried both with default settings and the settings you specified here for the runner and the system. After disabling all the DirectX entries, Rhino does not even start anymore.

I installed the packages through winetricks in this order

1. corefonts (from the fonts section)
2. dotnet48
3. dotnet462
4. dxvk

I then

1. set the version to Windows 10 (via winetricks)
2. installed Rhino
3. Run Rhino. It does not matter whether I do it from Lutris or from cmd.exe, it starts up, I get a glimpse of the welcome screen, and then the "-200" message and it closes itself. Nothing is printed in the console.

I was not able to find any wine_mono package (suggested in the readme) neither in apt nor in winetricks, I tried following these instructions but the installation did not succeed, when I try msiexec /i wine-mono wine-mono-6.2.0-x86.msi it does not do anything (maybe here I should be using wine64?).

Here is my winetricks.log:

win10
andale
arial
comicsans
courier
georgia
impact
times
trebuchet
verdana
webdings
corefonts
w_workaround_wine_bug-34803
remove_mono
remove_mono
winxp
dotnet40
dotnet48
remove_mono
remove_mono
remove_mono
remove_mono
remove_mono
winxp
dotnet40
dotnet45
dotnet46
dotnet461
dotnet462
w_workaround_wine_bug-24013
d3dcompiler_43
d3dx9
dxvk
win10

[5p4k]

I managed to get a log from running Rhino.exe by starting manually

export WINEPREFIX=~/3D/_Rhino3D
~/.local/share/lutris/runners/wine/lutris-6.10-7-x86_64/bin/wine cmd.exe

I did it both with wine and wine64. In the meanwhile, I think I managed to install mono-wine-6.2.0-x86.msi using wine64 following these suggestions. I am attaching the log files, the only :err: entries are these:

0120:err:ole:CoGetContextToken apartment not initialised
03c4:err:ole:CoGetContextToken apartment not initialised
03b8:err:combase:RoGetActivationFactory Failed to find library for L"Windows.Foundation.Diagnostics.AsyncCausalityTracer"

rhino32.log
rhino64.log

[cryinkfly]

@LizardM4 Thank you for your files and help! 👍 I look what happens ...

[cryinkfly]

@LizardM4 Which variant did you choose during the installation?

---

Have you solved the step 6 of my manual (Winetricks configuration) before you started Rhino 3D after the installation over the Wine console (Lutris)?

[5p4k]

1. I tried both with "Rhino account" and "This computer", no difference. I did not try Zoo.
2. If I set the renderer=no3d option, afterwards I do not even get the error message, Rhino does not start at all (or rather starts but dies immediately), I just tested it again. It does not matter whether I start it from cmd.exe or from Lutris. What is worse, is that after setting renderer=no3d, I need to restart from scratch. Even if I reset renderer to vulkan, gl, gdi, and every time I kill all wine processes, it does not work anymore.

Do you actually know how to start the Rhino licensing server? Meaning, do you know by chance what command or what binary should I kick off to start the licensing server? I suspect is something like rundll with some .NET dll from the Rhinoceros System folder. If I would know how to start the licensing server I could try to debug why it does not start.

[cryinkfly]

Okay, something more seems to be wrong with you. But with the new version of Rhino 3D I can't go any further after successfully registering.

I only see that the CrachDumper.exe and such starts, but not the program itself.

[cryinkfly]

But we can log the installer and the start of Rhino.exe.

For example:

Rhino.exe &> wine.error.log

Edit: We must input &> wine.error.log into the line Arguments

[5p4k]

I will give it a try and see if I can get a clue about what happens!

[maxlandon]

Hello guys,
I have exactly the same issue as you @LizardM4, with roughly the same logs and same stuff installed/set.
Completely new to wine/lutris and such myself, but not new to computers and Linux.
If I can help...

[dzervas]

BTW you can enable debug logging in registry HKEY_LOCAL_USER/Software/McNeel/Rhinoceros 7/DebugLog (something like that) and make the value Enabled from 0 to 1

[cryinkfly]

@dzervas I check this out. Thank you! 👍

[2ndt2nd]

Any update on this? I'm facing the same exact issue with having lutris immediately quit after switching the renderer as well.