License problem

[kubbek]

My renders are aborted today with information:

Could not obtain a license (-7): unrecognized license server response (old license version?)

I run the newest license serwer on one machine with online license and have dongle on the second one. Both get this alert.

Any clues what is going on?

Best regards,
Jakub

[vladimir.nedev]

Have you installed new versions of any V-Ray integration or the license server before this happened ?

Greetings,
Vladimir Nedev

[kubbek]

No, it just started in the middle of the day. It worked fine before.

[vladimir.nedev]

Can you open https://my.chaosgroup.com/ ?

Greetings,
Vladimir Nedev

[kubbek]

Yes and it is working now. Earlier I even reinstalled license server but it had problems with connection (I had no problems with internet connection though)

[vladimir.nedev]

So, it gave you this error even on the machine using a dongle ?
Is the dongle running through the online license server ?

Greetings,
Vladimir Nedev

[kubbek]

The dongle is visible inside online license site so I guess it is managed by it. I saw on twitter that you had some issues with online license servers but I thought that the dongle license shouldn't be affected by that...

[vladimir.nedev]

The dongle is visible inside online license site so I guess it is managed by it. I saw on twitter that you had some issues with online license servers but I thought that the dongle license shouldn't be affected by that...

Yes, it should've used the dongle.
Can you check, if you have the dongle subsystem enabled.
And also send me the diagnostic logs, I will forward them to the online licensing team, so they could take a look at them. Maybe they can figure out what went wrong.
See image:



Send the logs to vladimir.nedev[at]chaosgroup[dot]com

Greetings,
Vladimir Nedev

[kubbek]

I attach diagnostic log and screenshots from license server. It seems it doesn't see V-Ray for Modo license on my dongle.

Best regards,
Jakub

[vladimir.nedev]

The dongle looks normal actually. Excerpt from this page : http://forums.chaosgroup.com/showthr...371#post674371

IMPORTANT : Previously DONGLE builds required only the V-Ray Render Node 3.0 Beta license, so users, that were using dongles previously, will need to ask support to
reprogram the dongle to include the V-Ray 3.0 for Modo Beta license.

So, basically, if you want to continue using the dongle, you need to ask support to add the V-Ray 3.0 for Modo Beta license.

The nightly builds still don't ask for this GUI license though (they will very soon). Maybe you downloaded the official 3.01.01 build ?

Greetings,
Vladimir Nedev

[vladimir.nedev]

Oh wait, I didn't look at it close enough, the V-Ray Render Node 3.0 Beta license expired on 10 Jan 2016, that's why it didn't engage.
So, you can ask support to add the V-Ray 3.0 for Modo Beta license and extend the V-Ray Render Node 3.0 Beta license to your dongle.

Edit: or you can try/test the borrow/offline license feature, in order to be sure that any outages won't affect you.

Greetings,
Vladimir Nedev

[Alyssa555Mn]

License pr

Think i have found the problem with why the RSS feed stopped working
i will look at the code this weekend to see if i can fix it

[kubbek]

Today I experianced another online license problem. I am using windows 10 and probably after some update my license server lost information about being activated on my machine. After I noticed that V-Ray for Modo is not working giving me license error I opened license server page and saw that my machine was "not activated". Just enabled it but it is not very convenient and can cause troubles to many users.

Greetings,
Jakub

[vladimir.nedev]

Today I experianced another online license problem. I am using windows 10 and probably after some update my license server lost information about being activated on my machine. After I noticed that V-Ray for Modo is not working giving me license error I opened license server page and saw that my machine was "not activated". Just enabled it but it is not very convenient and can cause troubles to many users.

Greetings,
Jakub

This might happen if the files in "C:\Program Files\Common Files\ChaosGroup" are corrupted/deleted somehow.
I am not sure a Windows update can cause that.

Greetings,
Vladimir Nedev