Jesse Jost Posted January 24, 2020 Posted January 24, 2020 Hi all, Thanks for your reports on yesterday's authorization issue. We're happy to report the SG team resolved it quickly once it was diagnosed. We apologize for any setbacks or concerns the outage may have caused. This was a momentary server side issue, so no resolution was possible from the desktop side, either from BandLab Assistant or CbB. Bottom line: CbB is no longer launching as "Not Activated". Such issues are infrequent, typically affecting only fresh installations as they tend to get resolved quickly. Please note that the team is taking steps to minimize the likelihood of this reoccurring in the future. All being well otherwise, the Bakers continue to crank away on the next release - looking forward to sharing some great stuff soon to come! Have a great weekend! The Bakers 3 2
Xoo Posted January 25, 2020 Posted January 25, 2020 (edited) It's still occurring now. UPDATE: Solved by one of the Cakewalk support guys (very quickly too!). I had to delete the existing hidden auth files on my machine for CbB then re-authorise. Edited January 25, 2020 by Kevin Perry 1
Noel Borthwick Posted January 25, 2020 Posted January 25, 2020 @Kevin Perry deleting files shouldn't be necessary. Just choose refresh activation from BandLab assistant and it will automatically reauthorize the application. The original issue was caused by a server outage and would only have affected new installations. Were you installing to a new PC?
Xoo Posted January 25, 2020 Posted January 25, 2020 Nope. Old PC that's worked until 2(?) days ago. Reauthorisation had no effect. Even restoring from a >2 day old backup put it into unauthorised and unauthorisable mode.
Noel Borthwick Posted January 25, 2020 Posted January 25, 2020 Was it running an old build of Cakewalk? Also what specfic error code did you get? The issue we're discussing here was a case that only affected new installs.
Xoo Posted January 25, 2020 Posted January 25, 2020 2020.01 early release first noticed. Then (I guess) 2019.11 on reversion.
Xoo Posted January 26, 2020 Posted January 26, 2020 I copied the authorisation files from an image to try to find out the error code (I didn't note it down at the time) and the old files no longer generate the error. Go figure.
Noel Borthwick Posted January 27, 2020 Posted January 27, 2020 That sounds like a local problem then independent of this thread - perhaps your machine identity changed.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now