Why can it log in to my account and get a license for Rhino 7, but not the license for Rhino 8 which is in exactly the same place?
(Same message in both V7 and V8)
Really? It just managed to find the server and get the V7 license…
I’m sorry you’re having problems.
From that same computer, can you login to your account using the Web tool?
https://www.rhino3d.com/licenses?controller=home
Then click on the license Team name and can you see the licenses?
Of course. The V6, V7, V8 licenses are always there in my team. They are 30 seat NFR licenses.
Here’s the funny thing -
Rhino V8 is closed. I see this:
…indicating all of the 30 seats are available
Now I open Rhino V8. I see this:
Cloud Zoo now tells me that one license has been taken. But V8 tells me it couldn’t refresh the lease. That makes no sense at all, as it just did communicate with the Cloud Zoo, and the Cloud Zoo now indicates that one license is in use, which is obviously the instance of V8 I just opened.
No, not “of course”.
There is a process to identify the problem.
I get it you’re frustrated. I AM TOO, FFS!
First I checked our servers to make sure our systems are up. They are.
Next I asked you to check to see from your computer, if you could drill down all the way to see if you could see your licenses using the Web tools. This exercises the access to all three sets of servers including Microsoft, Amazon, and our own. You reported that worked.
Next in the process is Rhino’s ability to write and update local license lease related files. This seems to be where the problem is.
I can’t tell if it’s an issue with local folder rights or Rhino’s process is out of sync and reporting issues.
I’m trying to step through where the problem might be.
If it were me, and if Rhino will still open, check the “access until” date in Options > Licenses. How many days out is it?
Also check the Notations panel. Does it accurately report being unable to update the license lease?
Those are the next steps. Depending on what you find, I may have additional things for you to do.
If that fails, I’ll ask @aj1 and @will to have a look at the server side logs to see what they can find.
Hey John,
I am not frustrated… Simply trying to get a handle on this recurring issue - which really isn’t one in fact, because I’ve never had Rhino refuse to open because it couldn’t get a license. At some point - I never know when because I don’t check the notifications panel all that regularly - it just “fixes itself”.
I understand you have your procedure to follow. I generally try to do my “due diligence” before posting here, which means I checked the obvious possibilities - the ones I know in any case.
Yes, I would agree - it did get a license from the cloud zoo, but somehow locally it refused to acknowledge that fact. Therefore I surmise this is more a problem with Rhino itself and not necessarily the Cloud Zoo system.
I did make a screenshot of that yesterday evening but forgot to post it. Here is the one from today - one day less ‘on the clock’, 12 days left. That means it has been this way for a week already and I hadn’t noticed. Several computer restarts since then.
Corresponds more or less with the info from Options>Licenses - 10 April - around 13 days.
Yep, still there today:
And from my Rhino account:
(this is the only machine I have Rhino running on right now)
That’s all the info I have… Except to add that the Rhino 7 license is in the same place as the Rhino 8 license and it doesn’t report a problem.
The V6, V7, and V8 license file is in the same folder, but V8 also has an additional “ra_cache.txt” file in:
%appdata%\McNeel\Rhinoceros\8.0
Delete: ra_cache.txt
For your specific issue now, I would try deleting that file and starting V8 again.
Hi (Again!),
I’m jumping in here to comment that I think one key thing to note here is the error No such host is known. This implies a DNS issue with your computer, because essentially the DNS resolution for cloudzoo.rhino3d.com is not working.
What this means in layman terms is that Rhino cannot connect to cloudzoo.rhino3d.com to refresh a lease because of a DNS issue.
So, perhaps something has changed in the way your PC connects to the internet? New router, new software update, new anti virus?
Doing what JB suggests won’t hurt, but it probably won’t fix the problem.
I have actually never seen this exact issue in the wild before.
I do totally agree with you that it is very strange that Rhino can communicate with Cloud Zoo, but the request to renew a lease fails with a DNS error.
I suppose that if you click “Try Again” the same error happens as well?
Except V7 on the same computer has no trouble communicating with the cloud zoo and getting its license refreshed. So IMO, that message is spurious.
Nope.
Tried previously and it didn’t work. Now it worked and V8 got its license.
But doubly confusing that, despite the DNS issue, Rhino was seemingly able to open a websocket connection to Cloud Zoo (the usage shows up in the licenses portal when Rhino is running).
I wonder if the debug logs would show anything? (see My Documents/RhinoDebugMessages.txt after enabling it with the attached reg file)
rh8_debug_logging.reg.zip (732 Bytes)
It is spurious, I concur. That said, Rhino 8 uses a different version of .NET which the Cloud Zoo part of the licensing code is written in. It could be that the underlying network APIs do something slightly different that results in this error.
I was not present for V8 development, so another remote possibility is that something in our own code could have changed in V8 to cause this error.
But… it works now?
Seems that way. But this happens periodically, I have posted a few times about it.
@will will installing the debug logger help now that it finally got a license or not?
Did it ever happen in V7?
It might have… My memory is not that clear about it. I’ll try to do a search for my posts here…
Yep:
V7 - Unable to refresh license
V6 ! - Unable to refresh licences - #6 by Helvetosaur
Interesting. It’s the exact same issue. So it’s likely not related to new code changes, but something with the network setup.
You can use _TestEnableDebugLogging to disable it and re-enable it when you next see this issue.