(cross posted on Creative Cow - hope you don't mind)
Strange issue that came up today. Here's the background:
10 seats of FCPX 10.3.4 connected via 1GigE (through a switch) to a Jellyfish server. (3 seats directly connected at 10GigE.). Libraries live on the server in their own folder. Media on the sever in a different folder (with subfolders). Media is a mix of ProRes HD, XDCam 35, some 4k, etc.
Everything working as expected until today. Suddenly 2 users were unable to export some of their sequences. Attempting to share with any preset resulted in nothing - no export dialogue at all. Command+E also did nothing. No sequences in the library would export.
Sequences in a different library open on the same machine would export. Also, opening the sequences in the non-exporting library on another system worked fine.
Two different users had this happen to them in one afternoon. Restarting FCP did not help. Restarting the Mac did not help. Will try restarting FCP and deleting preferences, but I'm not hopeful.
I am at a loss to explain or fix this odd behavior.
You can submit a ticket on the LumaForge support portal, they usually respond immediately. But I don't think the issue is with your shared storage or your network. Especially since you say that it is related to one single Library AND that the problematic users can not access the Share menu in FCP X.
There are a few instances in which sharing can become disabled in FCP X. Just Google "FCPX cannot share" and you will find quite a lot of different answers.
But do submit a ticket to LumaForge and someone will contact you to start troubleshooting the issue, even if it has nothing to do with the server.
I defere to the expertise of the Ronny and others with regards to a multi-seat set up.
That said, I have occasionally had issues where we could not export. Sometime it seems to be cause by a plug in, sometime by a corrupt file (Digital Rebellion's Corrupt Clip Finder has save my bacon on more than one occasion).
Also, these basics troubleshooting tips might help: delete render files in the project and also the event.
You can also try creating a brand new library, a brand new project and the copying in the timeline from the "Corrupt non-exporting" project.
Lastly, and this shouldn't happen but it does: render the timeline completely before exporting. Just recently that solved a similar problem for me. It reduces the load on the computer when exporting something with a lot of layers or filters
I agree - I don't think the problem is on the server end. Having Googled the issue, as you suggested, I suspect corrupt renders or a bad file.
One of the users who had the problem reports no problems today. Only difference is he moved his connected clips (over a slug) down into the primary storyline today. Maybe just a coincidence. Maybe it forced a new render or something.
What puzzles me is that I could export his sequences just fine from my system when he could not from his system. But I'll keep an eye on this issue.
Corrupt or partial render files can indeed cause such issues. That's one of the reasons why we advise not to leave Background Rendering on because background rendering creates new render files any time you make a change to a clip. And when you get too many unused or partial render files for the same clip, you can get onto trouble when trying to export your edit. This is the case with any kind of editing software.
What many people do to avoid this, is to delete all render files prior to exporting and then share the un-rendered timeline. Or delete all render files, re-render the timeline, then share.
Keep us posted and don't hesitate to contact Lumaforge support should the problem occur again.