Explanation | An invalid username was passed into the process creation parameters. The user does not appear to exist on the system. |
Action | A valid user name needs to be entered into the process creation parameters. |
Explanation | An invalid group name was passed into the process creation parameters. The group does not appear to exist on the system. |
Action | A valid group name needs to be entered into the process creation parameters. |
Explanation | An invalid working directory was passed into the process creation parameters. The working directory does not appear to exist on the system or the user id running the process does not have access to the directory. |
Action | A valid working directory needs to be entered into the process creation parameters. |
Explanation | An invalid executable was passed into the process creation parameters. The executable either does not exist or is not executable by the current user. |
Action | A valid executable needs to be entered into the creation parameters. Check the executable and its execution permissions |
Explanation | An invalid priority was passed into the process creation parameters. The operating system would not accept it. |
Action | A valid process priority needs to be entered into the creation parameters. |
Explanation | An invalid process group was passed into the process creation parameters. The operating system would not accept it. |
Action | A valid process group needs to be entered into the creation parameters. |
Explanation | Some files the process needs for execution were not accessible by the process. This is commonly log files (redirects of standard out and error, or directories they reside in) that are not set readable and writable to the use rid that will be running the process that will access them. |
Action | Check the standard out and error redirection files and their directories to make sure they're readable and writable by the user id that will be running the process. |
Explanation | The operating system refused to create a new process due to too many file handles already being open. |
Action | Increase the maximum number of allowable file handles, or reduce the number of active processes on the system. |
Explanation | The operating system refused to create a new process due to lack of memory to contain the new process. |
Action | Reduce the memory usage on the system. |
Explanation | A non-existent PID was passed into the process code to bind to for monitoring. |
Action | A valid PID needs to be passed to the binding call. |
Explanation | A failure in termination has occurred. |
Action | Manually kill it through the operating system mechanisms under a user with authority to terminate the process. |
Explanation | The parameters used to terminate a process appear invalid or null, therefore termination cannot be done. |
Action | No user action. |
Explanation | A failure in termination has occurred. |
Action | Manually kill it through the operating system mechanisms. |
Explanation | A failure in termination has occurred. |
Action | Manually kill it through the operating system mechanisms. |
Explanation | Some files that the process needs to run are not accessible. These files are commonly log files that are not readable and writeable to the user ID that runs the process. |
Action | Check the standard out and error redirection files and the parent directories to make sure that these files are readable and writeable by the user ID that runs the process. |
Explanation | Some files that the process needs to run are not accessible. These files are commonly log files that are not readable and writeable to the user ID that runs the process. |
Action | Check the standard out and error redirection files and the parent directories to make sure that these files are readable and writeable by the user ID that runs the process. |
Explanation | This can occur if the system activity is too high for a process to be created within a specific time limit. The general time limit for the process to initialize is two minutes. If the process cannot be initialized during that time, then a CreateProcessTimeoutException is thrown and the creation is canceled. This is because generally if a process cannot initialize within the time limit then there is not enough system resources to adequately run the new process. |
Action | Check the CPU, memory, and overall system load characteristics for processes which are monopolizing machine resources. Also check the system limit settings for values that may be affecting the number of processes, CPU usage, and memory size that processes are allowed. |