Argent Queue Engine Error Codes
This article explains the error codes produced by the Argent Queue Engine.
When you attempt to control a Job you are restricted from or if you attempt to exceed a Queue limit, the Argent Queue Engine provides an error code to explain the condition.
Below is the list of Argent Queue Engine error codes and their meanings:
Code | Meaning |
0 | No error. |
1 | An unhandled error occurred in the Argent Queue Engine service while carrying out the work request. Please have an Administrator check the System Event Log on Queue Engine server computer. |
2 | Access to the system is denied by W200x Security; check your rights and privileges. |
3 | Access to queue denied; check your rights and privileges. |
4 | Access to job denied; check your rights and privileges. |
5 | Access to one or more jobs in the queue is denied; check your rights and privileges. |
6 | Access to the queue specified for re-queuing jobs to is denied; check your rights and privileges. |
7 | Duplicate queue name. |
8 | Invalid queue name. |
9 | The length of time to retain completed jobs is invalid. |
10 | The queue is full. |
11 | The queue is closed. |
12 | The job is already in the queue. |
13 | No such job exists. |
14 | The job is executing. |
15 | The job is not executing. |
16 | No such queue exists. |
17 | The file already exists. |
18 | The filename is invalid. |
19 | No default queue is defined. |
20 | Invalid queue priority. |
21 | Pending job count exceeds the limit. |
22 | The executing jobs limit is too high. |
23 | The queue is already started. |
24 | The queue is already stopped. |
25 | The queue is already open. |
26 | The queue is already closed. |
27 | The system is already paused. |
28 | The system is not paused. |
29 | The system is paused. |
30 | The queue specified to re-queue jobs to does not exist. |
31 | The queue specified to re-queue jobs to is closed. |
32 | The queue specified to re-queue jobs to is full. |
33 | Jobs cannot be re-queued to the same queue that is being deleted; queue not deleted. |
34 | The specified product log file size limit is too large. |
35 | The specified product log file size limit is too small. |
36 | The maximum number of links already exist. (not used any more) |
37 | The queue system is full. |
38 | An un-terminated string was passed as a parameter – missing trailing quote. |
39 | Unable to open or create the file. |
40 | The log size limit is invalid. |
41 | The queue job retention time is invalid. |
42 | An “Every” time was specified without an “After” time being specified. |
43 | The job file was not found. |
44 | The user does not have permission to access the job file; check your rights and privileges. |
45 | The job file is invalid. |
46 | The user is not granted network logon access to the system where the job file is located. |
47 | The job file path was not found. |
48 | The filename of the job file contains an incorrect, misspelled, or invalid network name. |
49 | Argent Queue Engine service cannot access the job file. Check the System Event Log on the Argent Queue Engine server computer for details. |
50 | The failure job file was not found. |
51 | The user does not have permission to access the failure job file; check your rights and privileges. |
52 | The failure job file is invalid. |
53 | The user is not granted network logon access to the system where the failure job file is located; check your rights and privileges. |
54 | The failure job file path was not found. |
55 | The filename of the failure job contains an incorrect, misspelled, or invalid network name. |
56 | Argent Queue Engine service cannot access the failure job file. Check the System Event Log on the Argent Queue Engine server computer for details. |
57 | The success job files was not found. |
58 | The user does not have permission to access the success job file; check your rights and privileges. |
59 | The success job file is invalid. |
60 | The user is not granted network logon access to the system where the success job file is located. |
61 | The success job file path was not found. |
62 | The filename of the success job contains an incorrect, misspelled, or invalid network name. |
63 | Argent Queue Engine service cannot access the success job file. Check the System Event Log on the Argent Queue Engine server computer for details. |
64 | The user’s SID does not match the SID created by logging on the user at the Argent Queue Engine server computer. |
65 | No domain controller is available to log on the user at the Argent Queue Engine server computer. |
66 | Argent Queue Engine was unable to log on the user because the logon was not granted by the local security policy on the Argent Queue Engine server computer. |
67 | Argent Queue Engine was unable to log on the user because the logon type was not granted by the local security policy on the Argent Queue Engine server computer. If the job has a password, then the “Log on locally” user right is required. If the job has no password, then the “Log on as a batch job” user right is required. |
68 | Argent Queue Engine service was unable to log on the user on the Argent Queue Engine server computer. The password or other information may be incorrect. |
69 | Argent Queue Engine service was unable to log on the user on the Argent Queue Engine server computer because of a policy restriction on the user’s account. |
70 | Argent Queue Engine service was unable to log on the user on the Argent Queue Engine server computer because the authentication package was not found. |
71 | Argent Queue Engine service was unable to log on the user on the Argent Queue Engine server computer because of an unhandled logon error. Check the System Event Log on the Argent Queue Engine server computer for more information. |
72 | The security descriptor is not valid. |
73 | The security descriptor does not contain a Discretionary Access Control List (DACL). |
74 | The security descriptor is not in self-relative format. |
75 | The queue contains one or more executing jobs. |
76 | The startup job number is invalid. |
77 | The startup job condition is invalid. |
78 | The startup job time limit is invalid. |
79 | The startup job file was not found. |
80 | Argent Queue Engine service does not have access to the startup job file. |
81 | The startup job file is invalid. |
82 | Argent Queue Engine service is not granted network logon access to the system where the startup job file is located; check your rights and privileges. |
83 | The startup job file path was not found. |
84 | The filename of the startup job file contains an incorrect, misspelled, or invalid network name. |
85 | The Argent Queue Engine service cannot access the startup job file. Check the System Event Log on the Argent Queue Engine server computer for details. |
86 | Error connecting to Queue Engine service. |
87 | Error sending work request to Queue Engine service. |
88 | Error reading reply from Queue Engine service. |
89 | A string was too long. |
90 | A parameter was invalid. |
91 | Memory could not be allocated; computer may be overloaded or too small. |
92 | This operation is not supported in this version of Queue Engine. |
93 | There were too many connections or server sessions for Queue Engine service to check access to a file. |
94 | Argent Queue Engine service is not running. Start Queue Engine service from the Control Panel applet “Services”. |
95 | Argent Queue Engine service, or NT’s RPC, is too busy to accept the work request. |
96 | A job submitted to run under an alternate account (an account other than the submitting user’s) requires the password for the alternate account. |
97 | The job is already paused. |
98 | The job is not paused. |
99 | The operation timed out. |
100 | Error creating overlapped event structure. The computer may be too small or overloaded; check system resource availability. |
101 | Error waiting for asynchronous I/O. A critical I/O operation did not complete as expected within an acceptable time; check network is running correctly. |
102 | Not all data was read from the socket. Make sure the Argent Queue Engine service is correctly and completely installed, and that TCP/IP is running correctly |
103 | Not all data was written to the socket. Make sure Queue Engine is correctly and completely installed, and that TCP/IP is running correctly. |
104 | Error reading from the service socket, check TCP/IP is running correctly |
105 | Error writing to the service socket, check TCP/IP is running correctly. |
106 | Error waiting for asynchronous I/O. An attempt to wait for an expected I/O failed. Use the Instant Help button to contact Argent Software for support. |
107 | Invalid password. |
108 | Network access denied; check your rights and privileges. |
109 | General network error, check TCP/IP and the network. |
110 | The job file network path was not found. |
111 | The success job file network path was not found. |
112 | The failure job file network path was not found. |
113 | Argent Queue Engine license has expired. Please email Keys@Argent.com for a new key. |
114 | Argent Queue Engine event %0x197ca0. Use the Instant Help button to contact Argent Software. |
115 | Use the Instant Help button to contact Argent Software. |
116 | The user identification is not correct for the socket connection to the Argent Queue Engine service. Please check the following:
|
117 | This user profile has been created to restrict access to this user account. |
118 | This user profile restricts access to the computer at certain times of the day. Please consult your account administrator. |
119 | The user is not permitted to access the account from this workstation. |
120 | The account password has expired. |
121 | The account has been disabled. |
122 | Network Resource jobs require a password. |
123 | The default log directory parameter (%1) was blank or invalid; Could not create queue. |
124 | Invalid protocol revision level. Please check if the Argent Queue Engine is installed properly. |
125 | Invalid protocol request. Please check if the Argent Queue Engine is installed properly. |
126 | Failed to initialize WINSOCK DLL. TCP/IP protocol must be installed and running. |
127 | Invalid CRC. Please check if the Argent Queue Engine is installed properly. |
128 | Failed to access the Argent Queue Engine server. The Argent Queue Engine server may be off-line, or service stopped, or network problem; check W200x event log. |
129 | Operation permission is denied because by the Argent Queue Engine security setup. |
130 | Internal Error. Use the Instant Help button to contact Argent Software. |
131 | The job number is invalid. |
132 | User does not have the privilege to control job. |
133 | The job is executing or has ended. |
134 | The job has already been executed. |
135 | Failed to create a temporary working file; check rights and that sufficient disk free space exists. |
136 | Incompatible API version. You may try to connect to higher version of engine with lower version of GUI. Please check if the Argent Queue Engine is installed properly. |
137 | The job is not in held mode. |
138 | The current default queue cannot be explicitly deleted. A replacement default queue should be set. |
139 | Failed to create log directory. |
140 | Exceeding live socket limit. |
141 | Failed to logon user. Please verify user, domain and password. |
142 | Failed to resolve host name. It can be a network issue or DNS issue. |
143 | Fatal CodeBase error. |
144 | Failed to access the Argent Queue Engine server registry. W200x server denies network access of its registry by default. |
145 | Exceed licensed Job Limit. |
146 | Failed to access job log file. |
147 | No mapped Unix account |
148 | Failed to logon to Unix Queue Engine |
149 | System is halt due to severe system problem. Queue won’t accept any job submission until system is rebooted. |
150 | Failed to load Job file. |
151 | Failed to double the size of the job table. |
152 | Failed to double the size of the job template table. |
153 | Unhandled exception error. |