Realise this problem has cropped up a few years back.

https://community.avid.com/forums/t/80248.aspx?PageIndex=4

It takes 4 minutes wait for Avid 2018.2 to wakeup from this issue.

Apart from disconnecting the network which does seem to free this system up to go. Is there any settings or known fix for this. 

It didn't happen in the earlier systems MC2018.1. Any help would be appeciated.

Rob

Rob

Are you able to clear the cache in the appman and does that make a difference?

marianna

Thanks Marianna for your response.

I haven't cleared the cache in the App at all. Previously I completey removed the cache manually from the avid file in the c' drive, MC, 'AMA management folder'. Initially that didn't change anything and the problem still existed.

This morning i opened the program from a complete shutdown with my NAS off (but ethernet connected) and without any other changes and AVID system booted up without any delay.

I am not sure if this has,

a. Resolved the issue, by the clearing of the AMA Management cache manually previously, then by starting the PC from a shutdown; or

b. Having the NAS off from startup has stopped AVID from accessing any volume files via ethernet port. 

Does the AppManager do the same as removing the AMA management cache files?

At the moment I will monitor the result and report back.

So the latest update Is:

Having the NAS on and ethernet connected whilst booting up Avid creates this issue with the volume manager. 

So the only change I did to my system was to to update to AVID 2018.2 from version 2018.1

Thanks

Update: Clearing the Application Manger did not reslove the issue either. 

One thing Rob

AppMan 2018.2 was just released and fixes a bug relating to networks

MCCET-2291. When Media Composer and Application Manager were running, WIFI speed dropped significantly.

Can you try to update to that..... so MC 2018.2 and AppMan 2018.2 are in sync.

Marianna

Thanks again Marianna

I have had AppMan and Avid up to date. Re-synced but problem exits.

The issue is hard wired network and not wifi. As I don't use wifi for networking.

I can definately stop the issue by removing the network cable or leaving the network cable in and turning off the NAS. Avid boots up within seconds.  Otherwise it takes almost 4 minutes waiting before it boots in. 

Rob

I am going to have engineering take a look see.  Can you email me or message me thru here your email address and system ID

Marianna

Have emailed you. Rob

Hi Folks, 

I got this issue with MC2018.7, Appman 2018.8. Is there a fix, i'm on Nexis so disconnecting the network is not an option.

Best regards, 

David

Hi all,

we see the same behaviour here on win10 and MC2018.12.1 .

hanging while  "initializing Avid Media Access Volume Manager" until you disable network (LAN).

So i could narrow it down to nablet AMA plugin (nablet_XAVC_XDCAM_AMA_Plugin_Setup_Win_4.5.8.2070)

after uninstalling this plugin, it was working fine again.

I am interested in your problem as I still have my issue unresolved. However there is a workaround if you still get the problem.

AVID or nablet is trying to read all the volume files from my NAS. So to speed up the AVID loading. I switch off, or  disconnect the network cable before avid boots up. Once avid loads it works without issue and then I reconnect the network again.

If you leave the network on. Avid can take about 4.5 minutes to boot up. It seems to hang when it's reading all the (AMA?) files on the NAS. But it will get there if your network is still attached, but with the boot delay as I mentioned earlier.

MaritzSG, what are you using for your nablet now? Have you downgraded, removed nablet or using something else?

I would love to know if your issue is resolved or like me, you just put up with it hanging until it does it's thing.

My issue occurred some time before Avid 2018.2. So I don't know if I introduced something into the equation or AVID (perhaps Nablet), software did in later updates. Hence my interest in your problem.

Rob

Hi Rob,

disabling the network is not a choice in my case as we have more than 60 workstations in our company.

right now i do not have an alternative for nablet. I could see this issue on my test systems that i set up to use with win10.

there might be a way to disable this "AMA Search" through console, but I'm not sure about that.

i will do some more tests and validate the nablet plugin on another machine and maybe try aan older nablet version.

i will post it here

**

Edit:

so it is definetely nablet in my case. this guy is causing issues nablet_XAVC_XDCAM_AMA_Plugin_Setup_Win_4.5.8.2070

this version is working:

nablet_XAVC_XDCAM_AMA_Plugin_Setup_Win_4.5.0.1252

BR

Moritz