10810 Error Osx
Contents |
a reboot. From what I've gathered by searching around on the web, Error 10810 occurs when the Launch Services framework has some sort 10810 error finder of meltdown, causing the Mac OS X Kernel to run out of available
The Application Finder Can't Be Opened 10810 Error
threads for anymore processes to launch. In the event that some process has got errant and is in some infinite the application finder can't be opened 10810 fix loop of launching and hoarding threads, this will cause a rather lovely barrage of error dialog boxes (see screenshot below). If you start getting Error 10810 in OS X, you likely won't
"10810" "finder" "disown"
be able to launch any other application (Finder included) and so the best thing you can do is to reboot your Mac. Yes, rebooting the Mac will fix the error - kind of lame, but it works. If you are continuously plagued by this error, then you may be using some buggy software that is launching itself into a gazillion threads causing Mac OS X to failed with error 10810 for the file freak out. If anyone has additional information or troubleshooting tips regarding this error, feel free to chime in. For what it's worth, simply killing and restarting the Finder was not sufficient in my experience to resolve the error, which is why a complete reboot of the Mac was necessary. Enjoy this tip? Subscribe to the OSXDaily newsletter to get more of our great Apple tips, tricks, and important news delivered to your inbox! Enter your email address below: Related articles: Fix Mac App Store Error @@errorNum@@Fix Mac App Store Error 100Fix "Error Establishing Database a Connection" When Using AbsintheFix the App Store "MZFreeProductCode .ClientCannotRedeemIosApp_explanation" Promo Code Redemption Error Posted by: William Pearson in Mac OS X, Troubleshooting 30 Comments » Comments RSS Feed Patrick McMahon says: February 9, 2010 at 5:21 pm I run into this every so often in Snow Leopard, to the point where I have to perform a hard restart. I noticed, on accident, yesterday that if I kick off Spotlight via Command+Space, and click on Show All, it will sometimes kick the Finder back into motion and restore my desktop icons, etc. Reply Aqilah says: September 18, 2012 at
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us
10810 Zip Code
Learn more about Stack Overflow the company Business Learn more about hiring developers
The Application Finder Can't Be Opened 10810 Snow Leopard
or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack the application finder can't be opened 600 Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Applescript Error -10810 up vote 4 down vote http://osxdaily.com/2010/02/09/mac-error-10810/ favorite I have an Applescript that runs fine on my Macbook Retina but fails on a Mac Mini. Both are running MacOS 10.9.2. After peeling the onion a bit I'm able to reproduce the problem with a one-line Applescript: tell application "MidiPipe" to activate On the Mini that throws the error: An error of type -10810 has occurred. On the Macbook the MidiPipe application opens. MidiPipe works http://stackoverflow.com/questions/23398435/applescript-error-10810 normally on the Mini when started from the Finder or from Launchpad. Google provides no insight into this error. osx applescript share|improve this question asked Apr 30 '14 at 21:35 Richard Milewski 142210 Is the Mini running the same version of MidiPipe? –Digital Trauma Apr 30 '14 at 22:40 Have you tried removing and reinstalling MidiPipe on the mini? Perhaps a botched install is to blame? –Digital Trauma Apr 30 '14 at 22:41 add a comment| 2 Answers 2 active oldest votes up vote 2 down vote accepted Well, I found this: http://www.thexlab.com/faqs/error-10810.html and this: http://osxdaily.com/2010/02/09/mac-error-10810/ and this: http://forums.adobe.com/thread/1389805 . At least one of these suggests a RAM problem. But just to make sure you've tried every weird variation, have you tried the following: 1) using a full path: tell application "Full:Path:To:MidiPipe.app" --(probably "YourHDName:Applications:MidiPipe.app"? 2) using an actual tell block: tell application "MidiPipe"--or full path activate end tell 3) using the Finder: tell application "Finder" to open "Full:Path:To:MidiPipe.app" 4) using shell: do shell script "open /Applications/MidiPipe.app" ? share|improve this answer answered Apr 30 '14 at 22:41 CRGreen 2,0481517 Trying to figure out how to put line breaks into these comments while holding a
Google Apps QI B.A.S. Information Technology Contact Me The Infamous OS X execution error: An error of type -10810 has occurred. (-10810) This error seems to appear often when I am using http://jacobsalmela.com/infamous-execution-error-error-type-10810-occurred-10810/ osascript for automating things. This error is a bit of a mystery as hundreds of users will say. In addition, it is not even listed in the MacErrors.h file found at: /System/Library/Frameworks//CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/Headers/MacErrors.h 1 /System/Library/Frameworks//CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/Headers/MacErrors.h After a lot of searching, I found some possible reasons why this error occurs: there is not a GUI, but one is required-even if being run as root access to the application assistive devices is not enabled the process table is full (i.e. fork bombs or zombie processes) LaunchServices has some sort of failure Since I mostly deal with scripting and automation, this post will be more about that and not so much about the Finder not being able to open because of this error. There Is Not A GUI, But One Is Required This error the application finder sometimes appears when running a script that requires a GUI, but the script is being run as root. The solution here is to get the current user and substitute as them. First, you need to get the current user and store that value in a variable, which can be done a number of ways: currentUser=$(stat -f "%Su" /dev/console) # Alternate ways to get the currently logged in user currentUser=$(who | grep console | awk '{print $1}') currentUser=$(logname) currentUser=$(ls -l /dev/console | cut -d " " -f4) currentUser=$(printf "get State:/Users/ConsoleUser\nd.show" | scutil | awk '/kCGSSessionUserNameKey/ {print $3}') 123456 currentUser=$(stat -f "%Su" /dev/console)# Alternate ways to get the currently logged in usercurrentUser=$(who | grep console | awk '{print $1}')currentUser=$(logname)currentUser=$(ls -l /dev/console | cut -d " " -f4)currentUser=$(printf "get State:/Users/ConsoleUser\nd.show" | scutil | awk '/kCGSSessionUserNameKey/ {print $3}') Then you can run the script under that user's context: su "$currentUser" -c "your commands here" 1 su "$currentUser" -c "your commands here" When running as root, another method is to use bsexec . I found this method useful with terminal-notifier. loggedInUser=$( ls -l /dev/console | awk '{print $3}' ) loggedInPID=$( ps -axj | awk "/^$loggedInUser/