Sunday, February 15, 2015

Re: [Avid-L2] Re: Leaving Avid project open but inactive yields Licensing Activation Issue?

 

8.0.3 or 8.3?  License app and dongle made a big change at 8.3, wherein a part of the information required to make the dongle work is the dates of your service contract coverage, which gets burned onto the dongle.  Once the dongle gets properly updated to a "8.3" compatible dongle, everything is OK, and mine work all the way back to MC 5.5. I am guessing you have a dongle burned with the earlier version of 8.x Application manager and that is the cause of the issue.

The dates thing is to accommodate the ability to authorize any version up to the expire date of your service contract.

If you dongle dump, you should see a set of dates in the dongle data.  If not, you are not fully updated to current authentication.

Dave Hogan
Burbank, CA




On Sunday, February 15, 2015 3:23 PM, "bigfish@pacbell.net [Avid-L2]" <Avid-L2@yahoogroups.com> wrote:


 
So now after editing a couple hours the Activation Error just pops up and quits Avid.  I'm going to move my dongle from a hub to the front of the macpro usb just to see.  I've had other systems that lost the dongle on hubs before.  This still doesn't explain why the licensing tab is blank.  I wonder if the fact that I blasted the dongle while I was running on the new SSD PCIE partition has some factor here.  If Microsoft Office loses it's activation when carbon copy cloned to the SSD perhaps there is under the hood aspect that links application manager too some part that is different between an SSD on the PCIE and an internal SATA drive.  Obviously Avid sees the dongle enough to launch initially but what's breaking the activation while I'm editing.  Anybody know if application manager periodically takes a system snap shot to make sure things are all good?  I'm attaching the error message


__._,_.___

Posted by: Dave Hogan <mactvman@yahoo.com>
Reply via web post Reply to sender Reply to group Start a New Topic Messages in this topic (3)

.

__,_._,___

No comments:

Post a Comment