Monday, February 16, 2015

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

 

It was lit when it deactivated while I was editing.  On other systems where a dongle was on a hub, long before the apps manager existed, I had to move the dongle off the hub to the front of the mac pro and the behavior stopped.  My current problem requires restarting the computer after it happens.  That is different behavior than I've experienced in the past.  I'd really like to understand why the the licensing tab is blank in apps manager on all but the startup drive I blasted the dongle on.  I think I'm not understanding the functionality of the apps manager licensing tab as it doesn't seem to represent current attached dongle info.  I must be wrong in assuming the license tab would act like a real time dongle dump of any attached dongle given what I'm seeing on my system.



---In avid-l2@yahoogroups.com, <bogdan_grigorescu@...> wrote :

just do a basic check and see if the dongle is still lit when it craps out

cheers,
BG



From: "bigfish@... [Avid-L2]" <Avid-L2@yahoogroups.com>
To: Avid-L2@yahoogroups.com
Sent: Monday, February 16, 2015 10:34 AM
Subject: Re: [Avid-L2] Re: Leaving Avid project open but inactive yields Licensing Activation Issue?

 
The dongle was blasted with the latest applications manager so I doubt that is the problem and the error message is not related to dates like other people have gotten.  It works and then just decides to error out.  I was able to unplug the dongle with Avid running and move it from the hub to the front USB connection without Avid crashing or quitting so I guess the dongle is checked on start up and then periodically while running.  I'm guessing that when it periodically checks there is something keeping it from seeing the dongle at that moment.  The fact that I only see dongle info on the one startup drive that I blasted it on might be a factor two.  When I go to the licensing tab of apps manager it is blank on the two startup drives that I didn't blast the dongle on.  I would have thought the licensing tab would be reporting on what dongle is connected to the computer but perhaps it's just a history of activity related to licensing.  What if I blasted my other dongle on this computer would that dongle info only show up on the computer and startup drive it was blasted on?


---In avid-l2@yahoogroups.com, <mactvman@...> wrote :

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@... [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: bigfish@pacbell.net
Reply via web post Reply to sender Reply to group Start a New Topic Messages in this topic (7)

.

__,_._,___

No comments:

Post a Comment