• On TechRepublic: Why Linux will triumph over Windows
advertisement
November 2, 2009 11:52 AM PST

Ongoing Snow Leopard issue: Finder Application cannot be opened (-10810)

by Joe Aimonetti
  • Font size
  • Print
  • 4 comments
As reported over a month ago here on MacFixIt, a growing number of users are still experiencing an issue with Finder freezing when attempting to connect to shared volumes or external hard drives and work with files from those drives. Users report the issue happening with SMB Shares, connecting to servers via Finder's "Connect to Server" function, and external storage devices such as Drobo drives.

Users experience a freeze in Finder when attempting to search or work with files on their shared drives. When they Force Quit (relaunch) Finder, they receive the (-10810) error with the message that the Finder application cannot be opened. Users are forced to then reboot their machines to continue use. Apple Support Discussions forum user "fitzyjoe" reports:

I'm having the same problem - When I try to "Connect to Server" from the Finder. I select afp:///. Then, I'm prompted to authenticate. Authentication seems to complete successfully and an entry is created in /Volumes. If I try to expand the volume or do an "ls -al" in Terminal, the Finder freezes. I right-click on Finder and choose to restart it. Then, I'm hosed... Can't start a new Finder with "The Application Finder can't be opened -10810" message. If I wait long enough, the Finder restarts. The shared drive on my server is a Drobo.

Solutions?
At this point, it still looks like people are having this issue and no official fix has been released from Apple. That being said, Mac OS X 10.6.2 has seen several beta releases to developers and should be available for download soon. To further the hopes of users that have been faced with this issue, ASD user "alleksu" posted this response from Apple about a filed bug for this problem:

"This is a follow up to Bug ID# 7256664. After further investigation it has been determined that this is a known issue, which is currently being investigated by engineering. This issue has been filed in our bug database under the original Bug ID# 7152276. The original bug number being used to track this duplicate issue can be found in the State column, in this format: Duplicate/OrigBug#."


Be sure to check us out on Twitter and the CNET Mac forums.
Do you have questions, issues, or stories you would like to see on MacFixIt? Email Us.

Joe is a seasoned Mac veteran with years of experience on the platform. He reports on Macs, iPods, iPhones and anything else Apple sells. Before joining CNET, he even worked in Apple's retail stores. He's also a creative professional who knows how to use a Mac to get the job done.
Recent posts from MacFixIt
Emails staying in the drafts folder?
Computer not going to sleep immediately
UPDATED: Finder not opening files when double-clicked
Handbrake 0.9.4 adds 64-bit support
Apple releases iPhoto 8.1.1 update
S-video connection problems for MacBooks
Some assistance for the new 27-inch, Quad Core, Late 2009 iMacs
Continued problems for new iMacs
Add a Comment (Log in or register) (4 Comments)
  • prev
  • 1
  • next
by wraggj November 2, 2009 1:28 PM PST
I don't think this is really an Apple problem in general. Although there may be specific cases where it is. This is a problem that pre-dates Snow Leopard, going back at least to OSX 10.4. In recent months it has been widespread in my organization.

Ultimately the problem is often due to third party software. We had scores of computers going down with this error recently, and it turned out to be a problem with the Altiris software my organization used to keep track of computers. In other cases it has been other programs, but, I believe, the problem is always due to some software spawning many processes until the OS reaches its limit of allowed number of processes.

If you have the excellent utility "Onyx" installed (which you should) you can try some cache cleaning using it and rebuild the launch services database. That seems to have worked in many cases.

The real fix is to find the offending software. We ultimately did this by going to the terminal and typing "sudo ps -ef" which helps you find which process is being spawned many times.
Then delete the problem application, or at least clean its prefs/caches/etc.
Reply to this comment
by WhiteDog November 2, 2009 4:45 PM PST
I've been having this problem without any active network connection (other than the Internet). It happens sometimes when I'm using Adobe Lightroom, but also when I'm merely copying a file in the Finder from one location to another (on separate internal hard drives in my Mac Pro). In fact, the Snow Leopard Finder seems remarkably unstable. I hope Apple fixes the problem. As for it being caused by third party apps, when these apps and the Finder had no such problems in OS X 10.5.8, I have no doubt that Apple and Snow Leopard are to blame for the trouble. If I wanted an OS upgrade to break my existing applications I'd use Windows.
Reply to this comment
by FletcherKane November 2, 2009 5:17 PM PST
I have had this problem too. It was happening mostly when using the Audio editing program Amadeus Pro. Whenever I would access a file from an external drive that had spun down, I would get this error. Amadeus Pro has since released a bug fix that seems to have fixed this problem. (Knock on wood.)
Reply to this comment
by zink_dotmac November 3, 2009 1:55 PM PST
This has happened to me four times since clean install upgrading to Snow Leopard a few weeks back. Three times while trying to disconnect MobileMe iDisk, today for the first time trying to disconnect USB flash memory (FAT formatted). This particular USB memory had not been mounted since the SL installation.
This never happened on the same computer in either 10.4 or 10.5. Excellent stability prior to 10.6 installation (apart from first few months with 10.5).

First indication of the problem is the failure to disconnect/eject the volume. Force eject does not work and soon the spinning beach ball appears in the Finder. Other apps work, at least for a while. Typing (sudo) "ps -ef" in the Terminal gave me no clue towards the process culprit.
Restarting Finder then fails with the -10810 message.

Console Diagnostic Messages shows:
Unmount Assistant [pid]:
com.apple.message.signature: Unknown Process
com.apple.message.result: noop
com.apple.message.domain: com.apple.volumeUnmounts.openNonGUI
com.apple.message.domain_scope: com.apple.volumeUnmounts.openNonGUI
Not very helpful to me.
After restarting from an externa FW disk with 10.5.8, Disk First Aid reports a few errors that needs to be fixed.

White iMac 24", conected to the internet through an Airport Express. Only a few handful applications like, Firefox, Safari, iTunes, iWork, Adium, VirtualBox/Ubuntu and Spotify. No Amadeus Pro or Altiris.
Reply to this comment
(4 Comments)
  • prev
  • 1
  • next

Navigate MacFixIt

  • Help
  • Archives
  • Utilities
  • Forums
advertisement
Click Here

About MacFixIt

MacFixIt is CNET's troubleshooting resource for all things Mac. The information here helps you navigate the ins-and-outs of Mac ownership with how-tos, troubleshooting information, news, reviews, and more.

Add this feed to your online news reader

MacFixIt topics