We have a problem on a lanshare with 5 ethernet clients.

File Manager 4.2.1

clients feature 3 MC 4.02's (latest connection manager available)

1 3.54 client

1 2.84 client (MC both)

What happens is that especially on one 4.02 system whatever we do close a bin, open a bin close project open project is starts scanning the workspaces as something has changed.... only thing is.. nothing changed.

We made sure (with the superb help of the local office) that we have correct time sync on the 5 clients and the lanshare but to no avail.

Anyone out there that knows what could be the cause of this?

Thx..

Menno

Hi Menno,

What are computer names and user names on these systems?

Hey Jeroen thx for checking in!

System names are Avid01 Avid02 etc

User names are avid1 avid2 etc..

They are all available on the lanshare as well as user and they never troubled us until now :( what changed is they went to a more file based workflow with XD-Cam thus off line and on line workspaceces (better said low res and high res spaces) but that is about it.

Thoughts?

Menno

In my system changing computer names from avid01, avid02 to alpha, bravo, Charlie, etc... fixed a scanning issue that occurred between avid01 and avid011. Weird but true. It was a similar situation as you describe. This seems to be an bug in MC 2.x.x. In MC 3.x and later I never saw it, although that could be coincidence.

In your case I don't know if this is the problem. During scanning can you see which workspace and folder is being scanned? Is each avid always scanning its own folder or do you also see scanning of folders that do not belong to the particular avid? 

Thx Jeroen appreciate any input!

In my case it is scanning it's own folders but doing it over and over again. So i start my system (especially one of them) and open a project.. it starts to scan a few workspaces (it's called Avid4 so it scans 4.1 4.2 mxf folders)

Then i can work but the minute i close a bin or open some other bin the whole process starts again.. scanning the same workspaces again.. If yoy look at the database files you can see they have the current date and correct timestamp so that seems to be ok.

Something is invoking this scanning as if there was a need due to new added media.. i am at a loss. Systems run in perfect timesync and they are 100% clear of spyware and virus threads (quadrouple checked).

....

...

..

.

Menno

Hmmm, does it also happen when only one of the 4.0.2 systems is on and the others are off?

Just had some extra info. We cosidered upgrading the lanshare to it's latest version but the release notes only had MAC/Apple fixes so we thougth why fix it if it ain't broke. Turns out there is something that is fixd PC wise speaking in 4.2.2 (we have 4.2.1)

CAUSE:

Modification dates created on directories in the unity workspace may include erroneous data, which causes multiple validation attempts us an Avid editing application. These validation attempts cause the applicatioon to scan the workspaces when scanning should not be needed.

SOLUTION:

Upgrade to MediaNet / Lanshare v.4.1.4 -or- MediaNet / Lanshare 4.2.2. Guidelines suggest you remain in your product family. For example, you are using 4.1.3. It is suggested to go to 4.1.4. If you are using 4.2.1, it is recommended you upgrade to version 4.2.2.

So next step is upgrading the lanshare see if that resolves issues..

I will drop a line when done, obviuosly this is an evening or night job

Thx

Just to update and clear the flags on the thread, updating to the latest version available did indeed solve the issue. What bothered me was that this info was known yet not dislosed in the upgrade readme files (at least i was unable to find it!). I got it from local support office here (thank those guys!)

Menno

That's great news! thx for sharing the info on the solution.

Great news indeed Jeroen, btw we upped to version File Manager 4.2.4 which was (as usual) a walk in the park (the update itself!)

Menno