I am persistently distracted by this "problem connecting to the server" issue... My Mac will work fine & be free of this problem for as long as I avoid FCPX. The moment I launch Final Cut Pro X, however, the issue resumes. When Mavericks was released I was foolish enough to believe that wiping my system and starting anew would eliminate the problem (and a couple of others)... Alas, it must have returned along with some project or configuration I inadvertently imported from my previous configuration. Therein, I had avoided using the migration tool & specifically opted to manually install all my software... again... and reconfigure everything... again... ugh...
As it turns out, it was a near immediate announcement made, upon launching FCPX, whereby the issue manifested the error message. I stumbled onto a post suggesting that there might be an external resource (i.e. the server in question) referenced in one of my projects, event libraries, or media assets... Seems logical & probable. A search on the server name, IP address, possible protocol scheme names (smb://, afp://), relevant keywords & all of that, failed to expose a thing. This problem is clearly affecting many, many, many... based on the scope of topics wherein others have shared their (nearly) identical issues. This particular issue is quite difficult to articulate (outside of the obvious), and therein, seems even more challenging to nail down.
My hope is that we may collectively narrow the root cause & expose a resolution.
Does anyone know how to generate a (comprehensive) asset report for all projects, events, and media resources referenced in FCPX's project & events library? Perhaps such a tactic may help to reveal the underlying issue... (or at least those of us who's issue may be rooted therein)
Anyone?