I recently upgraded to V8 and by mistake created a new Rhino account with my “pro” gmail address.
I was told to delete the old account and put all my serial numbers in the new one.
That was quite tedious already because my old Gmail address was on another Google account, and since the login process opens a new window, I kept getting lost and had over 11 links sent to my mailbox before I could finish the process.
But now, when I try to open Rhino (V7 or 8) I put my new E-mail, get a message saying my license was found, log into my new account and the I get a message stating that the account I logged in is not the one I am currently using in Rhino.
I suppose that my old account is cancelled, but some entry somewhere in a database hasn’t been updated properly.
And here I am fiddling around with endless loops instead of getting some work done.
Well, the Xylotica account is in fact a gmail account.
My osuire@gmail account is supposed to be deleted.
I added the old email (osuire@gmail) in the new account (olivier.suire@xylotica.com).
In fact, I did EXACTLY what I was told, but it doesn’t work.
Here are the two licenses I added to the new account.
The account using you xylotica address exists and that is your “Primary” address, meaning that’s the one you use to login to your account.
The gmail address was added as an “alias” so we know that address is you as well.
When you start Rhino V8 or V7, login using the xylotica.com address.
Your account is setup to send an email link to complete the login process without using a password.
After clicking the link in the email, You should be shows a license was found, click it, and Rhino will start.
Hi John, the part that doesn’t work is the one you see in the screenshot I sent in my first post.
It’s the part where I can’t use the software I paid for.
I think I see the problem.
It appears you deleted a login account, then created a new account using the same email address. Since they are different accounts, that would likely explain the problem.
This is what I’m seeing. Notice the 8 digit account IDs are different?
My guess is the local license lease files on your system were not extinguished by logging out before you made the account change. That should have been a step in the process you were given.
If you complete these steps to manually delete the local lease files, you should be able to login and get Rhino running.
Don’t skip any steps.
Use your Windows file Explorer and browse to: %appdata%\McNeel\Rhinoceros\6.0\License Manager\Licenses*
There will probably be 3 or 4 files in the folder
Delete everything in that folder
Browse to: %programdata%\McNeel\Rhinoceros\6.0\License Manager\Licenses*
There will probably be only 1 file in that folder
I would agree that our licensing user interface is way too complicated.
The underlying logic and design is really quite good.
The system allows for all the different license types and different ways they can be used.
Perhaps we will need to narrow down what the options are.
Any change like that will force us to abandon whole segments of users so we are not inclined to do it.
Problems happen when how the licenses need to be used changes, when people lose access to old email addresses, or when the importance of explicitly following specific steps in the right order are skipped or ignored.
Agreed.
We are working on trying to get everything in the same U/I container, and it’s a big job.
It’s complicated because Amazon S3, Microsoft Azure (or whatever they are calling it now), and our McNeel servers all need to be queried to get licensing to work securely and reliably.
The local license lease file is the least well understood by users, and the key to making licensing work reliably using an unreliable Internet.
It is also not explained / documented !
It might be a good idea to create a “clean slate” option within the licensing dialog that would delete all these local files to save the user the kind of experience I went through :
I did what I was told, strictly following the procedure, but spent two days in an infinite loop of death !
Hi
I wrote this when our internet licensing tools were introduced for Rhino V6.
The Cloud Zoo tools are an Internet based, floating license manager so you can float your single computer Rhino license between multiple computers.
Since you can’t be guaranteed an Internet connection 100% of the time, we use an automatically refreshing license “lease” on your computer. Here’s how it works:
When you start Rhino, Rhino calls your default Internet browser to go to your login account. It checks that you have a valid license in the Cloud Zoo associated with your account. A local license lease good for about 2 weeks is saved on your computer. This is shown in Options > Licenses as the “Offline access until…” date. Check it whenever you want.
When you start Rhino, if your local lease is 10% or more used up, and you have an Internet connection, your lease is updated automatically.
If you do not have an Internet connection when you start Rhino, the license lease refresh fails silently.
If this failure continues for several days, then Rhino will tell you that the license is going to expire in a few days if you don’t connect to the Internet.
For the vast majority of Rhino users, it is extremely rare they would not have an Internet connection at least once every couple of weeks, so this offline access system will work with the user never knowing it’s happening. It just works.
For people that use a laptop only for traveling, they will need to start Rhino on that laptop while they have an Internet connection. This will update the local license lease on that computer so Rhino can be used on the train, plane, or car, while the user is away from Internet.
Yes, it does John, until it brakes down for a silly edge case, like what happened to me.
I’m back and running.
Next license-related rant in an estimated 20 years.
When users contact us through technical support, depending on the what happened to their system and the state their license is in, we have specific instructions tailored to sort those problems. I am very hesitant to post them here for fear that people without a full understanding of the tools and differences between Rhino versions, will dig themselves into deeper problems and make getting them sorted that much more painful.
