|
U00003400 |
Server '&01' version '&02' (changelist '&03') started.
|
|
|
U00003401 |
Server '&01' version '&02' ended normally.
|
|
|
U00003402 |
Library '&01' was successfully loaded.
|
|
|
U00003403 |
Server routine '&01' was found at address '&02'.
|
|
U00003404 |
Unable to load library '&01'. Error code: '&02'.
Explanation: A .dll file could not be loaded. Possible reasons: * the .dll file could not be found * the .dll file has the wrong version * a .dll file required by the .dll library could not be found or has the wrong version. -> check if the library is installed on your computer -> check the dependencies of the library, thereby using the tool "depends.exe" on the UC4 CD (\tools\no_supp\).
|
|
|
U00003405 |
Server routine '&01' not found.
An internal error occurred. Please contact IT support.
|
|
|
U00003406 |
Client connection '&01' from '&02' has logged on to the Server.
|
|
|
U00003407 |
Client connection '&01' from '&02' has logged off from the Server.
|
|
|
U00003408 |
Library '&01' was successfully unloaded.
|
|
|
U00003409 |
'&01' memory successfully allocated (address = '&02', length = '&03').
|
|
|
U00003410 |
Server '&01' version '&02' ended abnormally.
|
|
|
U00003411 |
Server routine '&01' reported error '&03' during '&02' processing.
An internal error occurred. Please contact IT support.
|
|
|
U00003412 |
Agent '&01' logged on (Client connection='&04', Encoding='&05').
|
|
|
U00003413 |
Socket call '&01' returned error code '&02'.
An internal error occurred. Please contact IT support.
|
|
|
U00003414 |
Server routine '&01' was not found in Server '&02'.
An internal error occurred. Please contact IT support.
|
|
|
U00003415 |
No connection to client connection '&01'.
|
|
|
U00003416 |
Server or Agent '&01' not found.
|
|
|
U00003417 |
No more memory could be allocated.
|
|
U00003418 |
Message was not completely received ('&01' bytes missing).
|
|
|
U00003419 |
'&01' bytes were allocated with mem ID '&02'.
|
|
|
U00003420 |
'&01' bytes with mem ID '&02' were released.
|
|
|
U00003421 |
WARNING: The memory with mem ID '&02' and '&01' bytes was not released.
|
|
|
U00003422 |
WARNING: Cannot load conversation memory '&01' for server routine '&02'.
|
|
|
U00003423 |
A Server with the name '&01' already exists.
|
|
|
U00003424 |
An Agent of the name '&01' already exists.
Explanation: Names of UC4 components such as Server processes and Agents must be unique. Solution: Assign a different name in the Agent's INI file parameter name=. The length of this name is limited to 32 characters.
|
|
|
U00003425 |
Logon of the Agent '&01' caused a reconnect.
|
|
|
U00003426 |
A message with the length '&01' could not be received.
|
|
|
U00003427 |
Creating dump '&01'.
|
|
|
U00003428 |
The dump has successfully been created.
|
|
|
U00003429 |
Connection to Agent '&01' shall be closed.
|
|
|
U00003430 |
The connection to Agent '&01' was not found.
|
|
|
U00003431 |
Cannot interpret the message with the ID '&01'.
|
|
|
U00003432 |
Termination of Server '&01' initiated.
|
|
|
U00003433 |
Server was started with INI file '&01'.
|
|
|
U00003434 |
Server routine '&01' required '&02' minutes and '&03' seconds for processing.
|
|
|
U00003435 |
In the Server routine '&01', a DEADLOCK occurred '&02' times.
|
|
|
U00003436 |
Error in socket processing. '&01' event returned error '&02'.
An internal error occurred. Please contact the IT support.
|
|
|
U00003437 |
The connection to '&01' is blocked at the moment.
|
|
|
U00003438 |
Error in connection '&01'. '&02' function: Error '&03'
|
|
|
U00003439 |
Retrying to send to partner '&01' ('&02' msg. in stack).
|
|
|
U00003440 |
Caused by timer event, Server routine '&01' will be called.
|
|
|
U00003441 |
A message with ID '&02' should be sent after '&01'.
|
|
|
U00003442 |
A message with ID '&02' will be sent at '&01'.
|
|
|
U00003443 |
Socket statistics for Agent '&01': Sent '&02', '&03' Bytes; Received '&04', '&05' Events, '&06' Bytes
|
|
|
U00003444 |
The asynchronous select was restarted for the connection to '&01'.
|
|
|
U00003445 |
The message with ID '&01' has now been sent.
|
|
|
U00003446 |
Connection to SNMP agent has successfully been established.
|
|
|
U00003447 |
Connection to SNMP agent could not be established (Code '&01').
|
|
|
U00003448 |
Connection to SNMP agent successfully closed.
|
|
|
U00003449 |
Output to the TRACE file is finished.
|
|
|
U00003450 |
The TRACE file was opened with the switches '&01'.
|
|
|
U00003451 |
Fatal error in server routine '&01'.
An internal error occurred. Please contact support.
|
|
|
U00003452 |
Exception code: '&01'
|
|
|
U00003453 |
The serve-routine transaction '&01' was started.
|
|
|
U00003454 |
The server-routine transaction '&01' was ended.
|
|
|
U00003455 |
The server-routine transaction '&01' has been taken over.
|
|
|
U00003456 |
WARNING: The '&01' memory with mem ID '&02' was not released.
An internal error occurred. Please contact the IT support.
|
|
|
U00003457 |
ATTENTION: Please report the following error to the Automic Software development department.
Explanation:An internal error occurred. Please contact Automic Support.
|
|
|
U00003458 |
The message '&01' is marked as repeatable but contains no call back information.
|
|
|
U00003459 |
Dialog '&01' logged on (Client connection='&02').
|
|
|
U00003460 |
The Agent or partner '&01' should be terminated
|
|
|
U00003461 |
WARNING: The memory list with Mem ID '&01' has not been released.
|
|
|
U00003462 |
Shutdown of server '&01' initiated.
|
|
|
U00003463 |
Thread (ID='&01') for server monitoring was started.
|
|
|
U00003464 |
Thread (ID='&01') for server monitoring has been ended.
|
|
|
U00003465 |
Database error occurred at '&01', error code='&02'
|
|
|
U00003466 |
Database information occurred at '&01'.
|
|
|
U00003467 |
A server named '&01' is already running.
|
|
|
U00003468 |
A maximum of '&01' servers may run in parallel.
|
|
|
U00003469 |
Database connection will be interrupted.
|
|
|
U00003470 |
Database connection has been re-established.
|
|
|
U00003471 |
The Server '&01' has successfully been initialized, *** R E A D Y F O R R U N ***
|
|
|
U00003472 |
Connection to Server '&01' has been closed.
|
|
|
U00003473 |
Connection to SNMP agent has been ended abnormally.
|
|
|
U00003474 |
Error when sending to the SNMP agent, error code '&01'
|
|
|
U00003475 |
Server '&01' is the primary server of the system '&02'.
Explanation: Each UC4 system has several Server processes, one of which is the primpary work process (PWP). If the PWP fails, one of the other work processes assumes its tasks, thus becoming the primary work process.
|
|
|
U00003476 |
Mem ID '&01' already exists, a new Mem ID will be created.
Explanation: * A memory block should be saved but the calculated Mem ID already existed. This could be a memory leak. Please send the relevant part of the logging to the IT support.
|
|
|
U00003477 |
The connection between the Agents '&01' and '&02' is about to be interrupted.
|
|
|
U00003478 |
The Agent '&01' is about to establish a connection to the Agent '&02'.
|
|
|
U00003479 |
Logging was changed.
Explanation: The point in time for changing the logging depends on the settings made in the UC4 variable UC_SYSTEM_SETTINGS. You may specify the time with the entries CHANGE_LOGGING_DAYS and CHANGE_LOGGING_MB. Settings may also be changed on a temporary basis. They are then valid until the Server processes are restarted.
|
|
|
U00003480 |
The Service Manager restarted the Server automatically.
|
|
|
U00003481 |
The connection to partner '&01' is about to be disconnected.
|
|
|
U00003482 |
Server shutdown in progress, delayed sending is not permitted.
|
|
|
U00003483 |
XML connection with ID '&01' accepted.
|
|
|
U00003484 |
XML connection with ID '&01' closed.
|
|
|
U00003485 |
XML port '&01' successfully created.
|
|
|
U00003486 |
ListenSocket with port number '&01' successfully created.
|
|
|
U00003487 |
ListenSocket with port number '&01' could not be created.
|
|
|
U00003488 |
Server '&01' was started as instance '&02'.
|
|
|
U00003489 |
Server '&01' logged on (Client connection='&04').
|
|
|
U00003490 |
Connection to '&02' initiated, client connection '&01'
|
|
|
U00003491 |
There is a time difference of '&01' or '&02' seconds to the Primary Server.
Explanation: Time gaps between the Server processes are measured and balanced in intervals. Pay attention that times set on different computers comply with each other in order to avoid discrepancies.
|
|
|
U00003492 |
Server has been started on Host '&01' ('&02') with process ID '&03'.
|
|
|
U00003493 |
Connection to the system '&01' via '&02' initiated.
|
|
|
U00003494 |
Connection to the system '&01' via '&02' has been established.
|
|
|
U00003495 |
System '&01' does not correspond to the system '&02' of partner '&03'.
|
|
|
U00003496 |
Connection to system '&01' could not be established with partner '&02'.
|
|
|
U00003497 |
System name '&01' is longer than '&02' characters.
Explanation: Enter a different name for the UC4 system in the UC4 Server's INI file and restart it.
|
|
|
U00003498 |
System name '&01' contains the invalid character '&02'.
Explanation: A maximum of 8 characters may be used for the name of the UC4 system. Use letters from A-Z and numbers from 0-9. Enter a different name for the UC4 system in the INI file of the Server (parameter system=). Then restart the Server.
|
|
|
U00003499 |
Administrator command '&01' received.
|