Messages U35xx

[U00003501][U00003502][U00003503][U00003504][U00003505][U00003506][U00003507][U00003508][U00003509][U00003510][U00003511][U00003512][U00003513][U00003514][U00003516][U00003517][U00003518][U00003519][U00003520][U00003521][U00003522][U00003523][U00003524][U00003525][U00003526][U00003528][U00003529][U00003530][U00003531][U00003532][U00003533][U00003534][U00003535][U00003536][U00003537][U00003538][U00003539][U00003540][U00003541][U00003542][U00003543][U00003544][U00003545][U00003546][U00003547][U00003548][U00003549][U00003550][U00003551][U00003552][U00003555][U00003556][U00003557][U00003558][U00003560][U00003561][U00003562][U00003563][U00003565][U00003566][U00003567][U00003568][U00003587][U00003588][U00003589][U00003590][U00003591][U00003592][U00003593][U00003594][U00003595][U00003596][U00003597][U00003598][U00003599]
U00003501 01'.

An internal error occurred. Please contact the IT support.
U00003502 01'

An internal error occurred. Please contact the IT support.
U00003503 01'

An internal error occurred. Please contact the IT support.
U00003504 UDUDB PGE: OPST UPD missing

An internal error occurred. Please contact the IT support.
U00003505 UCUDB PGE: Overflow of internal HSTMT area

An internal error occurred. Please contact the IT support.
U00003506 UCUDB: ODBC VAR missing in SQLDRIVERCONNECT or invalid!

Possible reasons: * Missing ODBC VAR in the DB connection string * The DB connection string contains invalid values -> Please enter a valid connection string.
U00003507 UCUDB PGE: Table is not in DBTAB, Table: '&01'

An internal error occurred. Please contact the IT support.
U00003508 UCUDB PGE: Number of Y parameters <0 or >9

An internal error occurred. Please contact the IT support.
U00003509 UCUDB PGE: Overflow in table TLEN

An internal error occurred. Please contact the IT support.
U00003510 UCUDB: Entry in IDS automatically created: '&01', '&02', '&03', '&04'
U00003511 UDUDB PGE: Table not in DBTAB, Prefix: '&01'

An internal error occurred. Please contact the IT support.
U00003512 UCUDB PGE: Overflow table DB-FADR

An internal error occurred. Please contact the IT support.
U00003513 UCUDB: Not all HSTMT have been closed: Number = '&01'

An internal error occurred. Please contact the IT support.
U00003514 UCUDB: Too many OPST calls!

An internal error occurred. Please contact the IT support.
U00003516 UCUDB: Affected lines in function '&01' = '&02'

An internal error occurred. Please contact the IT support.
U00003517 UCUDB: Invalid DB-STMT IND: '&01' at OPC: '&02'

An internal error occurred. Please contact the IT support.
U00003518 UCUDB: Invalid value in Boolean field '&01'.

An internal error occurred. Please contact the IT support.
U00003519 UCUDB: Field is too long for UNICODE conversion.

An internal error occurred. Please contact the IT support.
U00003520 UCUDB: Type conversion not supported! Field '&01'

An internal error occurred. Please contact the IT support.
U00003521 UCUDB: SQL Stmnt is not zero terminated: '&01'.

An internal error occurred. Please contact the IT support.
U00003522 UCUDB: Database closed. Total time for DB calls: '&01' seconds.

Explanation: This information is helpful for the UC4 Support when analyzing problems.
U00003523 UCUDB: Maximum time required for a DB call: '&01'.

Explanation: This information is helpful for the UC4 support team when analyzing problems.
U00003524 UCUDB: ===> Time critical DB call! OPC: '&01' time: '&02'
U00003525 UCUDB: ===> '&01'
U00003526 UCUDB: Database version ('&01') does not match your program version ('&02').

Reason: * You use incompatible versions. -> Initial data, Server processes and DialogClients must have the same version or hotfix.
U00003528 UCUDB: Database is not in the internal status 'ready' but '&01'.

Explanation: Programs can only work with the database if it is in the status 'ready'. The database can have following states: * U (undefined): there is already no schema in the database * L (empty): the schema is loaded, but there are no records in the tables * I (initial): the schema and initial data is loaded * R (ready): the schema, initial and default data is loaded * E (error): There are parts of the schema, initial or default data loaded into the database, but the state of the database is not consistent. This state can occur if the load process of the database was terminated abnormally. -> Please call the UC4 support.
U00003529 UCUDB: Invalid parameter version '&01'. Current version is '&02'.

Reason: Check if you use the correct version of the UCUDB.DLL.
U00003530 UCUDB: Incorrect initialization of DBTAB at index '&01'.

An internal error occurred. Please contact the IT support.
U00003531 UCUDB: Error while checking data source (e.g. code conversion or driver problem, see log file).

Explanation: When defining the data source, the option code conversion must be deactivated. Otherwise, data will be falsified. Solution: Modify the definition of the data source. The button "Options" displays additional fields. Code conversion must be deactivated. In case of Oracle there could be a problem with the settings of the character set. The character sets of the database and the client have to be equal, otherwise the data would be converted. -> Please check the settings of the database and the client in the registry: HKEY_LOCAL_MACHINE/SOFTWARE/ORACLE Key NSL_LANG The values of NSL_LANG have to be equal. If a correction in the registry is not possibly, there is a other way to solve the problem. Create an environment variable NSL_LANG on the client machine. These overwrites the settings of the registry.
U00003532 UCUDB: Checking data source ...
U00003533 UCUDB: Check of data source finished: No errors. Performance CPU/DB: '&01'/'&02'
U00003534 *******************************************************************
U00003535 DB INFO: '&01'
U00003536 UCUDB: FATAL DATA BASE ERROR: Re-connection will be attempted in 10 seconds.

The connection to the database is broken. Attempt to reconnect will be made in 10 seconds. After re-connecting the processing will continue.
U00003537 UCUDB - RECONNECT: DB call '&01': Return code: '&02'.
U00003538 UCUDB: Re-connection to database successful. Processing will continue.
U00003539 UCUDB - DB Check: Error in rollback

Explanation: When opening the database, UC4 checks if the DB driver is able to perform a correct rollback operation. This verification failed. Solution: Use a DB driver that is released for UC4.
U00003540 UCUDB: ODBC tracing is active - Trace will be stopped now
U00003541 UCUDB: WARNING - ODBC tracing is switched on.
U00003542 UCUDB: Field '&01' is not returned with the expected length '&02'. Result = '&03'. Please check ODBC settings 'Padding'.
U00003543 UCUDB: The database saves date/time incorrectly. Stored: '&01', Read: '&02'. Please use a corrected driver.
U00003544 UCUDB: Reference values tested with Windows 2003 on XEON 1500 MHz: CPU 813865, DB 470
U00003545 UCUDB: Opening database ...
U00003546 UCUDB PGE: Overflow in table TAB

An internal error occurred. Please contact the IT support.
U00003547 UCUDB PGE: Overflow in table FIELD

An internal error occurred. Please contact the IT support.
U00003548 UCUDB PGE: Table '&01' does not exist in TABLE TAB.

An internal error occurred. Please contact the IT support.
U00003549 UCUDB: '&01' '&02' calls took '&03' sec.
U00003550 UCUDB: The combination SQL server 7.0 and ODBC driver 6.5 is not supported. This driver supports Archer fields only up to 255 byte. Please install an appropriate ODBC driver.
U00003551 SQL Server,3565,DB2,3560,Oracle,3555
U00003552 Info: Start number =DB Lost, Start+1=Deadlock, Start+2 = Duplicate

null
U00003555 8,376,470,600,1012,1013,1033,1034,1041,1089,1460,1461,1502,1536,1632,1654,3114,3113,3130,3135,8001,8102,12154,12571,12592,24324,22922,25402,25405,25408,25425,30036
U00003556 60,1460,1461,1555
U00003557 1,2292
U00003558 54
U00003560 -30081,-904,-1224,-9999,-1,-964
U00003561 -911,-913
U00003562 -803,-532
U00003563 -9999
U00003565 4,11,14,21,53,64,109,233,240,258,596,983,1105,3303,3618,5128,6002,6005,9002,10054
U00003566 1205,601,3926,3971,3988
U00003567 2601,2607,2627,547
U00003568 1222
U00003587 UCUDB: Optimized delete for eh-subtable '&01' not possible.
U00003588 The Automation Engine has noticed that an internal transaction for '&01' (RunID '&02') can be optimized. Please send the server log and object definition to Automic Support.
U00003589 UCUDB: Unknown field type '&01' at field '&02'.
U00003590 UCUDB - DB error: '&01', '&02', '&03', '&04'

Explanation: This message serves information purposes in the case of a cold start.
U00003591 UCUDB - DB error info: OPC: '&01' Return code: '&02'

A database error occurred. Please contact UC4 Support.
U00003592 UCUDB - Status: '&01' Native error: '&02' Msg: '&03'

Explanation: This message serves information purposes in the case of a cold start.
U00003593 UCUDB PGE: error at SQL error Ref '&01'

An internal error occurred. Please contact the IT support.
U00003594 UCUDB Ret: '&01' opcode: '&02' SQL Stmnt: '&03'

An internal error occurred. Please contact the IT support.
U00003595 UCUDB: Join in 'Select for update' Statement: '&01'
U00003596 UCUDB: Memory allocation error (length: &01, location: '&02').
U00003597 UCUDB: Table '&01' is not in PrimaryKeyTable
U00003598 UCUDB: Primary key value is not in PrimaryKeyTable
U00003599 UCUDB: Invalid ODBCVAR. ODBC with DB2 or ORACLE not supported!