I recently upgraded to a Pascal-based graphics card (while keeping a second Maxwell card) and upgraded my Octane Render version from 3.03.1 to 3.03.2. Literally five minutes earlier before the upgrade everything worked perfectly, I installed the new version and now I get the message: Account not Authenticated - SSO sign in was canceled.
So click activate and get: You are currently signed into your OTOY account but not connected to the OctaneLive Server.
I click Go Online and get: You are currently signed into your OTOY Account.
Good, wonderful...
Still not activated in the plugin.
So I load the stand-alone and get: Could not get a licence because your SSO Session has expired.
I click OK and enter my password.
Error message above repeats.
Did I mention this was working perfectly literally five minutes before?
Yes, I downgraded back to 3.03.1 and the error still occurs. No, there is no other version of OctaneRender installed. This seems to be a server-side issue, not client side.
License server down?
Does this company even have real tech support and not just a blind email box and a joke of a forum? When I pay $650 for a piece of software I kind of expect actual support from actual people in a timely manner and not just being told to go to a forum or wait three days for an email. If I wanted to go to a forum for support just to get ignored I'd be using a piece of garbage open source product like LuxRender. At least there terrible support is the price you pay for the product being "free." (For that matter the developer of the Reality plug for LuxRender tends to respond with minutes or an hour tops.)
Last ditch I got it to work, no help from oToy. I deleted the OctaneRender license folder in AppData, which is a minor thing but a few steps further than I'd like to have to take given there's automated system for managing the licenses AND there's no FAQ anywhere on the site or forum suggesting doing that.
Hi panton41,
This is a bug that we've come across ourselves and that has already been fixed in the current version of the SDK 3.03.2 which plugin developers are using for releasing all new versions of their respective plugins.
This affects users using offline licensing mode when moving from 3.02 to 3.03.1 as the licensing data needs to be renewed. If your SSO session would have expired, the plugin didn't have any means to renew the session and you would get that error message.
The solution you found would work but it'd probably be easier for other users coming across this to just open Standalone (any version from 3.03.x) once, which should ask you for your password and renew the SSO session. New plugins supporting SDK 3.02.2 will to exactly this same thing, so this should not happen anymore.
Best,
This is a bug that we've come across ourselves and that has already been fixed in the current version of the SDK 3.03.2 which plugin developers are using for releasing all new versions of their respective plugins.
This affects users using offline licensing mode when moving from 3.02 to 3.03.1 as the licensing data needs to be renewed. If your SSO session would have expired, the plugin didn't have any means to renew the session and you would get that error message.
The solution you found would work but it'd probably be easier for other users coming across this to just open Standalone (any version from 3.03.x) once, which should ask you for your password and renew the SSO session. New plugins supporting SDK 3.02.2 will to exactly this same thing, so this should not happen anymore.
Best,