I've been getting a bucket load of errors on my systems recently. I have media workspaces and seperate project workspaces on the ISIS.  I regularly get an

"exception get media domain type () - unable to get domain type because locater is null "

I made a new project which solved it for a while but the error came up again. I have tried the following

Making a new ISIS user ,Deleting the system as a device ,trashing MC state ,Using different user settings ,Switching the system off ,Deleting the databases , using bins from the attic.

Has anyone else come across this ?

I'm running version 1.4 using xw8000s.

Thanks for any help or advice in advance

What are the editors doing when this error crops up?

Errors appear on one project or several different projects?  And you deleted the media database files?  That error seems like corruption.

Sorry I didn't answer your reply jdw I've been snowed under and just making everything work by a thread. The editors can be doing anything from just cutting to rendering or viewing material.

The errors come on different workspaces and projects. Try and repeat certain things to force the error but I can't. I at one point I made a new workspace and put all the media on that , then deleted all precomputes in case it was linked to bad renders etc.

This worked which made me believe this was the problem but when it happened another time I repeated this and it didn't solve the problem. Another time I made a new project on a new project workspace and put all the bins in there this also worked once but didn't work another time.

I deleted the user and device before which cured it but then another time this didn't work.

Basically the cure is hit and miss and no particular pattern can be shown as a trigger point.

All very frustrating but hey if it was easy it wouldn't be 'fun' .

Doubt this is the problem, but just to check, how many clients and what resolution?  And while we're at it, how many engines etc?

32 clients out of a possible 36 , 12 @ 2:1 15 @ dv25  with the remaining 15:1. We have two engines with 32 tb of storage.

That is pretty much as far as my knowledge of ISIS can take me.  You are within the limits of ISIS throughput.  You are connecting to each engine directly (no switches involved).  If it is affecting each of the 32 clients then it seems like it would be a system director thing--if it is affecting a consistent group of clients connected to a specific engine then maybe it is within the engine hardware.  We weren't having any problems with 1.4 (except slowness) but we did upgrade to 1.5.1 without any problems (still slow though).  Might be worth a shot.  Also, can you talk to Avid?

It's time to run switch diagnostics,  and if you have anything questionable or in failure,  to call Avid.

With Isis,  you change, and you wait,  you can't jump headlong into things..

JDS

 jdw & Doc Thanks very much for your help. Have either of you seen any bugs with 1.5.1  that I should be aware of , no matter how small.

We haven't experienced any bugs with 1.5.1.  We did lose a blade during the upgrade because the firmware update failed.  Other than that, we are good.

I have a reoccurance of the above I'm going to try and update to 1.5.1 ASAP.

Avid you can be so cruel.