|
U02001000 |
03'.
|
|
|
U02001001 |
01' does not exist.
|
|
|
U02001002 |
Rejected an unidentified message.
|
|
|
U02001003 |
Could not copy PIF file '&01' due to less amount of free memory.
|
|
|
U02001004 |
Could not open PIF file '&01'.
|
|
|
U02001005 |
Could not create PIF file '&01'.
|
|
U02001006 |
Cannot find job with RunID '&01'. JOB_DEL ignored.
In overload situations, a recurring job-status check and a job end may overlap. Therefore, it occasionally happens that a job-status message is sent although the job has already ended.
|
|
|
U02001007 |
User '&01' is unknown or an invalid password has been provided.
Explanation: Check the login object that has been specified for this task. The login data (user or password) are incorrect.
|
|
|
U02001008 |
User '&01' has not been granted the required login type.
|
|
|
U02001009 |
Agent cannot find file '&01'.
|
|
|
U02001010 |
Agent cannot find path '&01'.
|
|
|
U02001011 |
Invalid directory name '&01'.
|
|
|
U02001012 |
Could not create log file '&01'. Error code '&02', error description: '&03'.
|
|
U02001013 |
Job agent reported status '&02' for job '&01', return code '&03'.
|
|
|
U02001014 |
Could not find address '&01'.
|
|
|
U02001015 |
A message could not be sent. See next message.
|
|
|
U02001016 |
Job status will be routed to Server.
|
|
|
U02001017 |
It was not possible to create list socket because port number '&01' is already in use.
|
|
|
U02001018 |
Could not create list socket. Error code: '&01', error description: '&02'.
|
|
|
U02001019 |
Data overload. The message was sent after '&01' seconds.
|
|
|
U02001020 |
Cancel job '&01' with RunID '&02'.
|
|
|
U02001021 |
Could not find job with RunID '&01'. Cannot abort.
|
|
|
U02001022 |
Job '&01' with RunID '&02' already ended.
|
|
|
U02001023 |
Cancel of job '&01' with RunID '&02' was successfully initiated.
|
|
|
U02001024 |
Could not cancel job '&01' with RunID '&02'.
|
|
|
U02001025 |
Canceling the job caused error: '&01'.
|
|
|
U02001026 |
Job '&01' with RunID '&02' has been removed from the job table.
|
|
|
U02001027 |
TCP/IP-Call SELECT for connection to '&01' has been restarted.
|
|
|
U02001028 |
The event protocol monitor with thread ID '&01' was started.
|
|
|
U02001029 |
The event protocol monitor with thread ID '&01' was ended.
|
|
|
U02001030 |
The event protocol '&01' was opened.
|
|
|
U02001031 |
The event protocol '&01' was closed.
|
|
|
U02001032 |
Monitor signaled event for protocol '&01'
|
|
|
U02001033 |
Event with counter '&01' was sent to the server.
|
|
|
U02001034 |
Event with counter '&01' was processed by the server.
|
|
|
U02001035 |
Unable to open event protocol '&01', error code '&02', error description: '&03'
|
|
|
U02001036 |
Event with counter '&01' was not processed correctly.
|
|
|
U02001037 |
Function call '&01' returned error code '&02', error description: '&03'.
|
|
|
U02001038 |
Unable to monitor the event protocol '&01'
|
|
|
U02001039 |
Connection to server was broken: sending events again.
|
|
|
U02001040 |
Error in function '&01', error code '&02', error description: '&03'.
|
|
|
U02001041 |
The job was started with Process ID = '&01'
|
|
|
U02001042 |
Starting the job with user '&01', domain '&02' is not allowed.
|
|
|
U02001043 |
Check registry with key '&01'.
|
|
|
U02001044 |
Cannot access registry '&01', error code: '&02'
|
|
|
U02001045 |
Check environment variables for the process
|
|
|
U02001046 |
Cannot access environment variables, error code: '&01'
|
|
|
U02001047 |
&01: PostMessage failed, error code: &02, error description: '&03'.
Explanation: The Job messenger could not send a message to the Agent due to a computer overload. Therefore, the PostMessage is repeated several times.
|
|
|
U02001048 |
Interpreter specification is missing ini INI file.
Explanation: The Windows Job should be processed using the type "Interpreter" but no interpreter has been specified. Solution: Enter the name of the interpreter in the Agent's INI file parameter ECPEXE= (section [GLOBAL].
|
|
|
U02001049 |
Could not find command interpreter '&01'.
|
|
|
U02001050 |
File scan can not be done, cause: '&01'.
|
|
|
U02001051 |
Wrong configuration, 'cp' address or port cannot be found in configuration.
|
|
|
U02001052 |
Unable to open file '&01', reason: '&02'.
|
|
|
U02001053 |
Unable to read from file '&01', reason - '&02'.
|
|
|
U02001054 |
Output scan error, no files found for path '&01'.
|
|
|
U02001055 |
Internal error, GETFILE cannot interpret the XML message. Error code: '&01'
Explanation: Program error, or corrupted message. &01: Internal error code.
|
|
|
U02001056 |
GETFILE has received an invalid file position '&01', expected '&02'.
Explanation: Program error, timeout, lost or corrupted message. &01: File position received. &02: File position expected.
|
|
|
U02001057 |
Line is longer than the block size.
Explanation: The file is probably binary.
|
|
|
U02001058 |
No login object in the GETFILE message found.
Explanation: The agent received a GETFILE message without login object.
|
|
|
U02001059 |
Job '&01' with RunId '&02' canceled while waiting on ressources.
Explanation: The agent received a GETFILE message without login object.
|
|
|
U02001087 |
Command with RunID '&01' cannot get information for user '&02'. Error: '&03'. Command: '$04'.
|
|
|
U02001088 |
Command with RunID '&01' cannot log on as user '&02'. Error: '&03'. Command: '$04'.
|
|
|
U02001091 |
Command with RunID '&01' is canceled due to timeout. Command: '$02'.
|
|
|
U02001092 |
Command with RunID '&01' will be canceled due to lost connection with server. Running command '$02'.
|
|
|
U02001093 |
The timeout for '&01' has been set to '&02' second.
|
|
|
U02001094 |
Job '&01' requested client-wide ressource '&02'.
null
|
|
|
U02001095 |
Job '&01' requested task-specific ressource '&02'.
null
|
|
|
U02001096 |
Job '&01' uses client-wide resource '&02' - '&03'.
null
|
|
|
U02001097 |
Job '&01' use task-specific ressource '&02' - '&03'.
|