Applescript fails with error (-600) when launched over ssh on Mavericks

Question

I\'ve tried searching for this, and have seen others with similar problems but don\'t seem to have found an answer anywhere....

I have an AppleScript that I am tryin

Answer 1

Arrrrgh! I don't want this to be the answer, but after trying just about everything, this now seems to be working after a restart.... My guess is that something in appleeventsd got confused (although restarting just appleeventsd on its own didn't fix anything). After a restart osascript seems to be behaving again. I'm still not convinced this is fully fixed, but it does seem to be working for the moment...

Answer 2

System Events is a really finicky asshat component of OS X. Here is my method for getting around that dreaded "Application isn't running -600" error:

set app_name to "System Events"
set the_pid to (do shell script "ps ax | grep " & (quoted form of app_name) & "$
if the_pid is not "" then do shell script ("kill -9 " & the_pid)

tell application "System Events"
-- activate  
end tell

I kill "System Events" with a kill -9 and then relaunch it.

Answer 3

for me this happened when I tried to open gitk. Changing back to the branch I was on before, and gitk was able to open again

Answer 4

I got the same error when I was unable to do GUI Scripts, but changing the System Preferences > Security & Privacy > Privacy > Accessibility settings for that specific app and adding a delay 0.5 between each line corrected it!

Answer 5

I was confused by this message "for System Events" not working in newer versions of Mac OS X from the command line:

osascript -e 'tell application "System Events" to display dialog "Build finished"'

It turns out the syntax of Applescript is (changed to?) just:

osascript -e 'display dialog "Build finished"'

Answer 6

Application isn’t running(-600) is an operating system error.

An operating system error is an error that occurs when AppleScript or an application requests services from the Mac OS. They are rare, and often there is nothing you can do about them in a script, other than report them.