4 Replies Latest reply: Aug 23, 2013 8:29 AM by Claidheamdanns
jeremy handel Level 2 Level 2 (200 points)
so I wanted to finally start playing with folder actions but I've run into a problem right out of the gate:

when I enter "configure folder actions" the folder actions setup app hangs with a spinning beachball and I start getting "connection failed. server may not exist or is not operational" errors.

checking console yields the following:

4/24/09 12:50:21 PM /Applications/AppleScript/Folder Actions Setup.app/Contents/MacOS/Folder Actions Setup[359]

CPSGetProcessInfo(): This call is deprecated and should not be called anymore.

4/24/09 12:50:21 PM /Applications/AppleScript/Folder Actions Setup.app/Contents/MacOS/Folder Actions Setup[359]

CPSPBGetProcessInfo(): This call is deprecated and should not be called anymore.

then it just sits.

has anyone ever seen anything like this? I'm totally lost.

thanks in advance.

The Ocho, Mac OS X (10.5.6)
  • 1. Re: Folder actions problem
    Simon Wellings Level 1 Level 1 (0 points)
    I've just had a similar problem and noticed in console:

    07/05/2009 17:18:25 com.apple.launchd[82] (com.apple.FolderActions.folders) Path monitoring failed on "/Volumes/downloads/sabnzbd": No such file or directory

    The folder action was nothing to do with this volume but once I'd mounted it, all was good again. Don't know if this will help in your situation.
  • 2. Re: Folder actions problem
    McDon Level 1 Level 1 (0 points)
    I have the same problem but I am unable to re-mount the network folder. Now I'm blocked out of folder actions setup because I just get the beach ball as it continues to look for the network folder that is simply no longer available. It won't give up and stop searching.
  • 3. Re: Folder actions problem
    John Morrison, Architect Level 1 Level 1 (0 points)

    I am having the same problem and cannot find a fix on the forums.  Did you by chance get this working?

  • 4. Re: Folder actions problem
    Claidheamdanns Level 1 Level 1 (0 points)

    I'm getting this same problem, and like one of the other posters, I can't mount the offending network drive, because it no longer exists.

     

    Did anyone find a solution to this?