Mac Error Code -600 — Process Not Found
About Mac Error Code -600
Mac error code -600 means the required process or application could not be found, typically during inter-process communication. This guide covers everything you need to know about this topic, including common causes, step-by-step solutions, and answers to frequently asked questions.
Here are the key things to understand: procNotFound — target process does not exist. Common with Apple Events and AppleScript. Application may have crashed or not launched. Can occur when automating tasks between apps. Understanding these fundamentals will help you diagnose and resolve this issue more effectively.
The most common reasons this occurs include: Target application is not running. Application crashed during communication attempt. AppleScript referencing wrong application name. Sandbox restrictions preventing inter-app communication. Identifying the root cause is the first step toward finding the right solution.
To resolve this, follow these recommended steps: Ensure the target application is open and running. Restart the application and retry. Check AppleScript application name spelling. Grant automation permissions in System Preferences > Privacy. If these steps do not resolve the issue, consider consulting additional resources or a qualified professional.
This article is part of our Mac Error Codes collection on Error Codes Wiki. We provide comprehensive, up-to-date information to help you find solutions quickly.
Quick Answer
What is a process not found error?
macOS tried to communicate with an app that is not running or cannot be found.
Overview
Mac error code -600 means the required process or application could not be found, typically during inter-process communication.
Key Details
- procNotFound — target process does not exist
- Common with Apple Events and AppleScript
- Application may have crashed or not launched
- Can occur when automating tasks between apps
Common Causes
- Target application is not running
- Application crashed during communication attempt
- AppleScript referencing wrong application name
- Sandbox restrictions preventing inter-app communication
Steps
- 1Ensure the target application is open and running
- 2Restart the application and retry
- 3Check AppleScript application name spelling
- 4Grant automation permissions in System Preferences > Privacy