We do see the issue from time to time, however, now that that project is mostly wrapped out, it happens much less frequently. We spent weeks working with support and they were never able to isolate an issue, but as it happens less frequently, I'm inclined to believe there was a media corruption that was causing the Delayed write failure. Unfortunately

[quote user="kkordisch"] Try setting the Search DB to the local. We had the same issue and that fixed it. [/quote] Thanks I'll give it a shot. This needs to be done manually for each user and each project they open correct? It's not a user setting that will move project to project?

We'll take a look at that, however, these projects aren't any larger then anything we've been dealing with in the past. Each episode is isolated in it's own project too.

Hi all, We're having a number of occurances of our team members seeing the following error: delayed write failure for file '_SearchDB_' Our NEXIS is running 18.6.1.14 and all our clients are also up to date. All are Mac users running High Sierra with Media Composer 2018.5. Running a path diag from every machine is showing averages over 100mb

Hi, We upgraded our NEXIS unit to 18.6.0.8 last week and also upgraded all of our clients to 18.6.0.8. Since the upgrade to the new Mangement Console, we're noticing that the "Unused Space" listed does not match the "Free Space" listed on the client's NEXIS Client. I've attached screen grabs of an example partition.

We've also started getting Avid Nexis Delayed write failures with an Errcode of 0x66. We're running Macs with 10.11.6 and 10.12.6, MC 2018.5, and Avid Nexis Client 18.3.0.7 EDIT: Confirming that ScriptSync is active on the machines we've had the issue with.

Thanks Bob, Yes I was definitely trying to do it on our Macs. I might be able to find a PC I could use, but out of curiousity, does the Data Migration Tool directly transmit data from the ISIS to the NEXIS, or does it have to pass through the PC client? Basically I'm asking it it's faster then using something like chronosync and taking advantage

Thanks Dom, Running the Migration Tool with out the client manager open still results in the same error of needing ISIS 5000 or 7000 installed. I'll probably just end up using chronosync to migrate the partions. Thanks

Thanks Jeroen. I'm familiar with utilities like beyond compare or rsync. I was hoping the Data Migration utility would actually take advantage 10GbE connection between the NEXIS and ISIS rather then having to run the data migration through one of the 1Gb connected bays. Side question, is it possible to install the NEXIS client on the ISIS itself

Hi All, We just had a new NEXIS E4 and SDA installed today and it's up and running on the same address space as our existing ISIS 5000. The reason for the install was that we were filling up the ISIS and running out of space. I see that the recommended method for migrating a partition from the ISIS (4.7.8) to the NEXIS (7.11.0.8) is to use the Avid