Ipocc Error Numbers en

IP Office Contact Center TTrace
Error Numbers Reference

Release 9.0.2
Issue 1.0
February 2014
IP Office Contact Center Trace Error Numbers 1

Contents
About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Errors sort by number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
002.000.1000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
003.000.1000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
004.000.1000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
006.000.0001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
007.000.1000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
008.000.1000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
009.000.1000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
010.000.0100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
013.000.1000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
019.000.1000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
030.003.0001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
041.000.1000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
042.000.1000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
043.000.1000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
046.000.0001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
047.000.1000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
052.000.1000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
054.000.0001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
110.009.0900 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
111.009.0900 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
114.014.0101 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
115.015.0101 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
201.000.0001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
242.000.0001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
243.000.0001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
244.000.0001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49


2013 Avaya Inc. All Rights Reserved.
Notice
While reasonable efforts have been made to ensurethat the information in this
document is complete and accurate at the time of printing, Avaya assumes no
liability for any errors. Avaya reserves the right to make changes and
corrections to the information in this document without the obligation to notify
any person or organizationof such changes.
Documentation disclaimer
"Documentation" means information published by Avaya in varying mediums
which may include product information, operating instructions and performance
specifications that Avaya generally makes available to users of its products.
Documentation does not include marketing materials. Avaya shall not be
responsible for any modifications, additions,or deletions to the original
published version of documentation unless such modifications, additions, or
deletions were performed by Avaya. End User agrees to indemnify and hold
harmless Avaya, Avaya's agents, servants, and employees against all claims,
lawsuits, demands and judgments arising out of, or in connection with,
subsequent modifications, additions or deletions to this documentation, to the
extent made by End User.
Link disclaimer
Avaya is not responsible for the contents or reliability of any linked websites
referenced within this site or documentation provided by Avaya. Avaya is not
responsible for the accuracy of any information, statement or content provided
on these sites and does not necessarily endorse the products, services, or
information described or offered within them. Avaya does not guarantee that
these links will work allthe time and has no control over the availability of the
linked pages.
Warranty
Avaya provides a limited warranty on itshardware and Software ("Product(s)" ).
Refer to your sales agreement to establish the terms of the limited warranty. In
addition, Avayas standard warranty language, as well as information regarding
supportfor this Product while under warranty is available to Avaya customers
and other parties through the Avaya Support website:
http://support.avaya.com
Please note that if you acquired the Product(s) from an authorized Avaya
Channel Partner outside of the United States and Canada, the warranty is
provided to you by said Avaya Channel Partner and not by Avaya. "Software"
means computer programs in object code, provided by Avaya or an Avaya
Channel Partner, whether as stand-alone products or pre-installed on hardware
products, and any upgrades, updates, bug fixes, or modified versions.
Licenses
THE SOFTWARE LICENSE TERMS AVAILABLEON THE AVAYA WEBSITE,
HTTP://SUPPORT.AVAYA.COM/LICENSEINFO ARE APPLICABLE TO
ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA
SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR
AN AUTHORIZED AVAYA CHANNEL PARTNER (AS APPLICABLE) UNDER A
COMMERCIAL AGREEMENT WITH AVAYA OR AN AUTHORIZED AVAYA
CHANNEL PARTNER. UNLESS OTHERWISE AGREED TO BY AVAYA IN
WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE
WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA
AFFILIATE OR AN AVAYA AUTHORIZED AVAYA CHANNEL PARTNER;
AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU
AND ANYONE ELSE USING ORSELLING THE SOFTWARE WITHOUT A
LICENSE. BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE,
OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF
AND THE ENTITY FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR
USING THE SOFTWARE (HEREINAFTER REFERRED TO
INTERCHANGEABLY AS "YOU" AND "END USER", AGREE TO THESE
TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT
BETWEEN YOU AND AVAYA INC. OR THE APPLICABLE AVAYA AFFILIATE
"AVAYA".
Avaya grants you a license within the scope of the license types described
below. Where the order documentation does not expressly identify a license
type, the applicable license will be a Designated System License. The
applicable number of licenses and units of capacity for which the license is
granted will be one (1), unless a different number of licenses or units of
capacity is specified in the documentation or other materials available to you.
Designated Processor means a single stand-alone computing device.
Server means a Designated Processor that hosts a software application to be
accessed by multiple users.
License type(s)
Designated System(s) License (DS). End User may install and use each
copy of the Software only on a number of Designated Processors up to the
number indicated in the order. Avaya may require the Designated Processor(s)
to be identified in the order by type, serial number, feature key, location or other
specific designation, or to be provided by End User to Avaya through electronic
means established by Avaya specifically for this purpose.
Concurrent User License (CU). End User may install and use the Software on
multiple Designated Processors or one or more servers, so long as only the
licensed number of Units are accessing and using the Software at any given
time. A Unit means the unit on which Avaya, at its sole discretion, bases the
pricing of its licenses and can be, without limitation, an agent, port or user, an
e-mail or voice mail account in the name of a person or corporate function
(e.g., webmaster or helpdesk), or a directory entry in the administrative
database utilized by the Software that permits one user to interface with the
Software. Units may be linked to a specific, identified Server.
Copyright
Except where expressly stated otherwise, no use should be made of materials
on this site, the Documentation, Software, or hardware provided by Avaya. All
content on this site, the documentation and the Product provided by Avaya
including the selection, arrangement and design of the content is owned either
by Avaya or its licensors and is protected by copyright and other intellectual
property laws including the sui generis rights relating to the protection of
databases. You may not modify, copy, reproduce, republish, upload, post,
transmit or distribute in any way any content, in whole or in part, including any
code and software unless expressly authorized by Avaya. Unauthorized
reproduction, transmission, dissemination, storage, and or use without the
express written consent of Avaya can be a criminal, as well as a civil offense
under the applicable law.
Virtualization
Each vAppliance will have its own ordering code.Note that each instance of a
vAppliance must be separately ordered.If the end user customer or Business
Partner would like to install2 of the same type of vAppliances, then 2
vAppliances of that typemust be ordered.
Each Product has its own ordering code. Note that each instance of a Product
must be separately licensed and ordered. "Instance" means one unique copy
of the Software. For example, if the end user customer or Business Partner
would like to install 2 instances of the same type of Products, then 2 Products
of that type must be ordered.
hird-party components
Third Party Components mean certain software programs or portions thereof
included in the Software that may contain software (including open source
software) distributed under third party agreements (Third Party Components),
which contain terms regarding the rights to use certain portions of the Software
(Third Party Terms). Information regarding distributed Linux OS source code
(for those Products that have distributed Linux OS source code) and identifying
the copyright holders of the Third Party Components and the Third Party Terms
that apply is available in the Documentation or on Avayas website at: http://
support.avaya.com/Copyright. You agree to the Third Party Terms for any such
Third Party Components.
Note to Service Provider
The Product may use Third Party Components that have Third Party Terms
that do not allow hosting and may need to be independently licensed for such
purpose.
Preventing Toll Fraud
Toll Fraud is the unauthorized use of your telecommunications system by an
unauthorized party (for example, a person who is not a corporate employee,
agent, subcontractor, or is not working on your company's behalf). Be aware
that there can be a risk of Toll Fraud associated with your system and that, if
Toll Fraud occurs, it can result in substantial additional charges for your
telecommunications services.
Avaya Toll Fraud intervention
If you suspect that you are being victimized by Toll Fraud and you need
technical assistance or support, call Technical Service Center Toll Fraud
Intervention Hotline at +1-800-643-2353 for the United States and Canada. For
additional support telephone numbers, see the Avaya Support website: http://
support.avaya.com.Suspected security vulnerabilities with Avaya products
should be reported to Avaya by sending mail to: securityalerts@avaya.com.
The trademarks, logos and service marks (Marks) displayed in this site, the
Documentation and Product(s) provided by Avaya are the registered or
unregistered Marks of Avaya, its affiliates, or other third parties. Users are not
permitted to use such Marks without prior written consent from Avaya or such
third party which may own the Mark. Nothing contained in this site, the
Documentation and Product(s) should be construed as granting, by implication,
estoppel, or otherwise, any license or right in and to the Marks without the
express written permission of Avaya or the applicable third party.
Avaya is a registered trademark of Avaya Inc.
All non-Avaya trademarks are the property of their respective owners, and
Linux is a registered trademark of Linus Torvalds in the U.S. and other
countries.
Downloading documents
For the most current versions of documentation, see the Avaya Support
website:
http://support.avaya.com
Contact Avaya Support
See the Avaya Support website: http://support.avaya.com for product notices
and articles, or to report a problem with your Avaya product.
For a list of support telephone numbers and contact addresses, go to the
Avaya Support website: http://support.avaya.com, scroll to the bottom of the
page, and select Contact Avaya Support.
About this document

About this document
This document contains information about error numbers of an IP Office Contact Center system.
6 IP Office Contact Center Trace Error Numbers

Errors sort by number

The following list shows the errors sort by number. The list shows the number, a description and the name
of the appropriate component.
Error number Description Component
002.000.1000 Error while starting. db_srv
002.000.1001 Was not able to get database ref. will try again db_srv
002.000.1002 Was not able to insert into 'DBServerVersion' table db_srv
002.000.1003 Was not able to register 'ccid_generator' at naming service.
will try again
db_srv is stopped
db_srv
002.000.1004 Was not able to register 'log_server' at naming service. will try
again
db_srv
002.000.1005 Was not able to register 'DB' at naming service. will try again. db_srv
002.000.1006 Was not able to register 'statistic' at naming service. will try
again.
db_srv
002.000.1007 Fetching sybase error log failed db_srv
002.000.1008 Was not able to create session for retrieving sybase error log.
will try again
db_srv
002.000.2000 Starting db_srv db_srv
002.000.2001 db_srv is up and running db_srv
002.000.2002 Stopping db_srv db_srv
002.000.2003 db_srv is stopped db_srv
003.000.1000 Error while starting. lna_srv
003.000.1001 Was not able to get database ref. will try again lna_srv
003.000.1002 Was not able to register 'LNASrv' at naming service. will try
again
lna_srv
003.000.1008 Was not able read required registrations from database. will
try again
lna_srv
003.000.2000 Starting lna_srv lna_srv
003.000.2001 lna_srv is up and running lna_srv
003.000.2002 Stopping lna_srv lna_srv
003.000.2003 lna_srv is stopped lna_srv
004.000.1000 Access to database failed kernel
004.000.1001 Access to taskserver manager failed kernel

004.000.1002 Access to process observable of vectors failed kernel
004.000.1003 Access to corba name service failed
Check namingservice, startparameter, or network setting
kernel
004.000.1004 The values for shared mamory at the database are invalid kernel
004.000.1005 Access to reconstructor failed kernel
004.000.1100 An invalid task type is used for an operation kernel
004.000.1101 However an object for a specific task type is missing while it
shoulb be used
kernel
004.000.1102 However there is no object for the specified object id. kernel
004.000.1200 Access to a specific database table failed kernel
004.000.1201 Load from a database table failed kernel
004.000.1202 A mandatory record is not available in the database kernel
004.000.1300 Registration at a specific observer failed kernel
004.000.1301 De registration at ... kernel
004.000.1400 A clip data server signaled a specific address more than once kernel
004.000.1500 A unknown datakind is used on a public interface kernel
004.000.1800 External distribution is unavailable kernel
004.000.1850 Reconstructor process for offline task statistik reconstruction is
unavailable
kernel
004.000.2000 This specific TS has been registered more than once kernel
004.000.2001 The TS provides an unknown tasktype kernel
004.000.2002 The provided TS proxy is not accessible kernel
004.000.2003 Another TS already provides this not mergable Vep kernel
004.000.2004 There is a conflict between VEP and PEP kernel
004.000.2005 Taskserver: Does not provide Object. kernel
004.000.2006 Corba call failed kernel
004.000.2007 Taskserver request timeout kernel
004.000.2008 No taskserver with this Id is available kernel
004.000.2009 Proxy throws exception kernel
004.000.2010 EmailTS changed TCId of TC during reconstruction kernel
004.000.3000 Unknown event kernel
004.000.3001 Unexpected event kernel
004.000.3002 Invalid event content kernel
004.000.3003 Unexpected state kernel

004.000.3100 Event/operation not allowed because object is out of service kernel
004.000.3101 Task/TC-specific kernel
004.000.3200 Agent-specific kernel
004.000.3201 Agent log state kernel
004.000.3202 Must be InService to signOn.. kernel
004.000.3300 No more shared memory for object. kernel
004.000.3301 An object is already stored at shared memory kernel
004.000.4000 task1=" << taskId << " vanished. kernel
004.000.4001 task1=" << taskId << " does not have a NetMaster. kernel
004.000.4002 Timeout for the reservation of a relocation topic kernel
004.011.0001 lad_srv is starting. kernel/custident
004.011.0002 Loading of initial data kernel/custident
004.011.0003 Startup finished kernel/custident
004.011.0004 Reconnecting the LNA-Server kernel/custident
004.011.0005 Reconnect of LNA-Server finished. kernel/custident
004.011.0101 No license BCCLCIdent available kernel/custident
004.011.0102 No database, please check the DB-Server kernel/custident
004.011.0103 No reachable DB-server, please check the DB-Server kernel/custident
004.011.0104 No valid DB-table proxies kernel/custident
004.011.0105 No valid registration kernel/custident
004.011.0106 No connectin to LNA-Server kernel/custident
004.011.0107 Invalid address type for address=" << searchAddress) kernel/custident
004.011.0108 Invalid address check address=" << address kernel/custident
004.011.0109 Address=" << normalizedAddress << " already registered kernel/custident
006.000.0001 lad_srv is starting. lad_srv
006.000.0002 lad_srv is started. lad_srv
006.000.0003 lad_srv is stopping. lad_srv
006.000.0101 No DB server lad_srv
006.000.0102 Waiting another minute for valid database. lad_srv
006.000.0103 Waiting another minute for valid kern. lad_srv
006.000.0104 kernel does not provide the last agent data server interface. lad_srv
006.000.0105 No kernel or adapter available. lad_srv

007.000.1000 SUCCESS: Successfully initialized the ORB vectors
007.000.1001 FAILURE: Initialization of ORB failed. Exiting... vectors
007.000.1002 SUCCESS: Successfully registered at ORB naming service. vectors
007.000.1003 FAILURE: Registration of the vectors process at ORB naming
service failed.
vectors
007.000.1100 SUCCESS: Database server successfully connected. vectors
007.000.1101 FAILURE: Binding the database server failed. vectors
007.000.1102 FAILURE: Binding the database server failed. vectors
007.000.1103 FAILURE: Getting a database session failed. vectors
007.000.1104 FAILURE: Getting a database session failed. vectors
007.000.1105 SUCCESS: Successfully loaded static Objects from the
database server.
vectors
007.000.1106 FAILURE: Loading static objects from the database server
failed.
vectors
failed.
vectors
007.000.1108 FAILURE: Connection to database server lost. vectors
007.000.1109 SUCCESS: Successfully reconnected the database server. vectors
007.000.1110 FAILURE: Reconnecting the database server failed. vectors
007.000.1200 SUCCESS: Notification server successfully connected. vectors
007.000.1201 FAILURE: Binding the notification server failed. vectors
007.000.1202 FAILURE: Registering observer for change notifications failed. vectors
007.000.1203 FAILURE: Registering observer for change notifications failed. vectors
007.000.1204 FAILURE: Registering observer for ask notifications failed. vectors
007.000.1205 FAILURE: Registering observer for ask notifications failed. vectors
007.000.1206 FAILURE: Connection to notification server lost. vectors
007.000.1207 SUCCESS: Successfully reconnected the notification server. vectors
007.000.1208 FAILURE: Reconnecting the notification server failed. vectors
007.000.1300 SUCCESS: Kernel successfully connected. vectors
007.000.1301 FAILURE: Binding the kernel manager failed. vectors
007.000.1302 FAILURE: Connecting the kernel failed. vectors
007.000.1303 FAILURE: Kernel not yet ready. Waiting... vectors
007.000.1304 FAILURE: Calling vector destination at kernel failed. vectors
007.000.1305 SUCCESS: Reconnect of vector destination successful. vectors

007.000.1306 FAILURE: Reconnect of vector destination failed. vectors
007.000.1307 FAILURE: Access to tag modification object in kernel failed. vectors
007.000.1308 FAILURE: Connection to kernel lost. vectors
007.000.1309 SUCCESS: Successfully reconnected the kernel. vectors
007.000.1310 FAILURE: Reconnecting the kernel failed. vectors
007.000.2000 SUCCESS: Startup finished. Process is now up. vectors
007.000.2001 MESSAGE: Initiating Shutdown ... vectors
007.000.2002 FAILURE: Initialization of process resulted in an exception.
Exiting...
vectors
007.000.2100 MESSAGE: Taskflow group activation started... vectors
007.000.2101 MESSAGE: Taskflow group activation successful. vectors
007.000.2102 MESSAGE: Taskflow group activation failed. vectors
007.000.2103 MESSAGE: Taskflow group syntax check started... vectors
007.000.2104 MESSAGE: Taskflow group syntax check successful. vectors
007.000.2105 MESSAGE: Taskflow group syntax check failed. vectors
007.000.2106 MESSAGE: Taskflow element activation started... vectors
007.000.2107 MESSAGE: Taskflow element activation successful. vectors
007.000.2108 MESSAGE: Taskflow element activation failed. vectors
007.000.2109 MESSAGE: Taskflow element syntax check started... vectors
007.000.2110 MESSAGE: Taskflow element syntax check successful. vectors
007.000.2111 MESSAGE: Taskflow element syntax check failed. vectors
008.000.1000 Access to corba name service failed statistic_srv
008.000.1001 Access to config database failed statistic_srv
008.000.1002 Access to statistic database failed statistic_srv
008.000.1003 Access to theDBSession failed statistic_srv
008.000.1004 Database session Bye command failed statistic_srv
008.000.1005 Database session (theDBSession) Bye command failed statistic_srv
008.000.1006 Lost Connection to <process/object> statistic_srv
008.000.1100 Invalid configuration. An invalid task type is used for an
operation
statistic_srv
008.000.1101 Invalid configuration. However an object for a specific task
type is missing while it should be used
statistic_srv
008.000.1102 Invalid configuration. However there is no object for the
specified object id
statistic_srv

008.000.1103 Invalid configuration. However there is no default object (AG,
Topic, Team or Agent)
statistic_srv
008.000.1104 Invalid configuration. The Agentgroup has the invalid agType
'0', valid is only '1'
statistic_srv
008.000.1105 Invalid configuration. Loaded an invalid object ID for the given
object from DB
statistic_srv
008.000.1106 Invalid configuration. The configuration couldn't load from CC
database
statistic_srv
008.000.1107 A notification call from lna_srv causes a configuration error statistic_srv
008.000.1108 The startup failed, break down and exits statistic_srv
008.000.1200 Access to a specific database table failed statistic_srv
008.000.1201 Load from a database table failed statistic_srv
008.000.1202 A mandatory record is not available in the database statistic_srv
008.000.1203 Lost statistic data. Unable to write into <name>Stat table statistic_srv
008.000.1300 Registration at a specific observer failed statistic_srv
008.000.1301 De registration at ... statistic_srv
008.000.1500 An unknown datakind is used on a public interface statistic_srv
008.000.2000 Startup finished successfully, application is running statistic_srv
008.000.2001 Process is stopping statistic_srv
008.000.2002 Process is stopped an exits statistic_srv
008.000.2003 Process startup is running statistic_srv
008.000.2004 Process startup is finished statistic_srv
008.000.2005 Process is connecting to <process/object> statistic_srv
008.000.2006 Process is connected to <process/object> statistic_srv
008.000.2007 Process is reconnected to <process/object> statistic_srv
009.000.1000 Access to corba name service failed monitor_Srv
009.000.1001 Access to config database failed monitor_Srv
009.000.1002 Access to statistic database failed monitor_Srv
009.000.1003 Access to theDBSession failed monitor_Srv
009.000.1004 Database session Bye command failed monitor_Srv
009.000.1005 Database session (theDBSession) Bye command failed monitor_Srv
009.000.1006 Lost Connection to <process/object> monitor_Srv
009.000.1100 Invalid configuration. An invalid task type is used for an
operation
monitor_Srv

009.000.1101 Invalid configuration. However an object for a specific task
type is missing while it should be used
monitor_Srv
009.000.1102 Invalid configuration. However there is no object for the
specified object id
monitor_Srv
009.000.1103 Invalid configuration. However there is no default object (AG,
Topic, Team or Agent)
monitor_Srv
009.000.1104 Invalid configuration. The Agentgroup has the invalid agType
'0', valid is only '1'
monitor_Srv
009.000.1105 Invalid configuration. Loaded an invalid object ID for the given
object from DB
monitor_Srv
009.000.1106 Invalid configuration. The configuration couldn't load from CC
database
monitor_Srv
009.000.1107 A notification call from lna_srv causes a configuration error monitor_Srv
009.000.1108 The startup failed, break down and exits monitor_Srv
009.000.1200 Access to a specific database table failed monitor_Srv
009.000.1201 Load from a database table failed monitor_Srv
009.000.1202 A mandatory record is not available in the database monitor_Srv
009.000.1203 Lost statistic data. Unable to write into <name>Stat table monitor_Srv
009.000.1300 Registration at a specific observer failed monitor_Srv
009.000.1301 De registration at ... monitor_Srv
009.000.1500 An unknown datakind is used on a public interface monitor_Srv
009.000.2000 Startup finished successfully, application is running monitor_Srv
009.000.2001 Process is stopping monitor_Srv
009.000.2002 Process is stopped an exits monitor_Srv
009.000.2003 Process startup is running monitor_Srv
009.000.2004 Process startup is finished monitor_Srv
009.000.2005 Process is connecting to <process/object> monitor_Srv
009.000.2006 Process is connected to <process/object> monitor_Srv
009.000.2007 Process is reconnected to <process/object> monitor_Srv
010.000.0100 The corba connection to the db-server cannot be established.
Check wether the db-server is running and wether the
hostname is correct
tr_Srv
010.000.0101 The logfile <name> connot be closed tr_Srv
010.000.0102 The internal datatype <type> is not supported. Programming
error
tr_Srv

010.000.0103 The needed license cannot be found. Check wether thew
license server is running and the apropiate license exists
tr_Srv
010.000.0104 The database table 'TaskType' cannot be read. Check wether
it exists and the db-server is running
tr_Srv
010.000.0105 The database table 'TRGeneral' cannot be read. Check
wether it exists and the db-server is running
tr_Srv
010.000.0106 The report with the id <id> is defined twice. Configuration
error. Check Configuration
tr_Srv
010.000.0107 The report with the id <id> shall be activated but is not defined.
Configuration error. Check Configuration
tr_Srv
010.000.0108 The server has an unexpected internal state, so he cannot
activate the report. Restart may help
tr_Srv
010.000.0109 The report with the id <id> shall be deactivated but is not
defined. Configuration error. Check Configuration
tr_Srv
deactivate the report. Restart may help
tr_Srv
010.000.0111 The report with the id <id> shall be deleted but is not defined.
Configuration error. Check Configuration
tr_Srv
delete the report. Restart may help
tr_Srv
010.000.0113 Error while shutdown. The task reporting server is going to
finish while reports are running
tr_Srv
010.000.0114 Cannot open the database session. Check wether the
db-server is running
tr_Srv
010.000.0115 Cannot open the database session. Check wether the
db-server is running
tr_Srv
010.000.0116 The database table 'ServerVersion' cannot be written. Check
wether it exists and the db-server is running
tr_Srv
010.000.0117 The database table 'TRLevelParameter' cannot be written.
Check wether it exists and the db-server is running
tr_Srv
010.000.0118 Internal programming error tr_Srv
010.000.0121 NOT USED tr_Srv
010.000.0122 vInit - getting stat hold time from db failed - deletion of
customer data will not work.
tr_Srv
010.000.0123 DeleteCustData: StatHoldTime cannot be converted. Deletion
of data will not work
tr_Srv

010.000.0124 The server is unble to register for notification at a database
tabel
tr_Srv
010.000.0125 No connection to licenseserver available. tr_Srv
010.000.0200 An sql statement is missing in the TRLevelStmt table. Check
the configuration
tr_Srv
010.000.0201 Reading a report initialily from the database and storing it
internally fails. Programming error
tr_Srv
010.000.0202 Reading a changed report from the database and storing it
internally fails. Programming error
tr_Srv
010.000.0203 An sql statement fragment is stored with an index not between
0 and 20. Check the configuration.
tr_Srv
010.000.0204 A paremeter desscription is stored with an position that does
not fit to the sql statement. Check the configuration
tr_Srv
010.000.0205 The sql statement are not concatenated in the right order.
Programming error
tr_Srv
010.000.0206 An user defined task tag should be used for level 2. This
function is not supported up to now. Change configuration.
tr_Srv
010.000.0207 An user defined task tag should be used for level 3. This
function is not supported up to now. Change configuration.
tr_Srv
010.000.0208 The sql data type is not supported. Change Configuration. tr_Srv
010.000.0209 The sql data type is not supported for a counter. Change
Configuration.
tr_Srv
010.000.0210 The sql data type is not supported for a timestamp Change
Configuration
tr_Srv
010.000.0211 The sql data type is not supported for a task id. Change
Configuration
tr_Srv
010.000.0212 The sql data type is not supported for a bit counter. Change
Configuration
tr_Srv
010.000.0213 The sql data type is not supported for a enumeration counter.
Change Configuration
tr_Srv
010.000.0214 The sql data type is not supported for a tag Change
Configuration
tr_Srv
010.000.0216 An attribute with that name is not supported. Change
Configuration
tr_Srv
010.000.0217 Acounter with that name is not supported. Change
Configuration
tr_Srv
010.000.0218 A char or binary column is configured with column width 0.
Change configuration.
tr_Srv

010.000.0219 The number of parameters in the sql statement does not fit to
the configured parameters. Change Configuration.
tr_Srv
010.000.0220 A binary column for a task id has been configured with column
width other than 8. Change configuration.
tr_Srv
010.000.0400 The connection to the statistic server fails. Check wether the
statistic server is running
tr_Srv
010.000.0401 The statistic server cannot be bound as a corba object. Check
wether the statistic server is running. Restart statistic server
and task reporting server.
tr_Srv
010.000.0402 The statistic server cannot be bound as a corba object. Check
wether the statistic server is running. Restart statistic server
and task reporting server.
tr_Srv
010.000.0403 The statistic server cannot be bound as a corba object via
observation. Check wether the statistic server is running.
Restart statistic server and task reporting server.
tr_Srv
010.000.0404 The statistic server cannot be bound as a corba object via
observation. Check wether the statistic server is running.
Restart statistic server and task reporting server.
tr_Srv
010.000.0405 A dataobject with unknown type is received from the statistic
server. It will be ignored
tr_Srv
010.000.0406 A data object has been received from the statistic server, but it
cannot be interpreted. It will be ignored.
tr_Srv
010.000.0407 A report cannot be registered at the statistic server, because it
cannot be reached. The task reporting server will try to
reconnect to the statistic server and register the report.
tr_Srv
010.000.0408 A report cannot be deregistered at the statistic server,
because it cannot be reached. The task reporting server will
try to reconnect to the statistic server and deregister the
report.
tr_Srv
010.000.0409 The statistic server can be reached, but it is in a state, where
further communication is not possible. The task reporting
server will try later.
tr_Srv
010.000.0410 The statistic server cannot be reached. Check wether the
statistic server is running.
tr_Srv
010.000.0411 The statistic server cannot be reached. Programming error tr_Srv
010.000.0412 The start or stop of a report is not possible, because the
statistic server cannot be reached. Try again, when statistic
server runs.
tr_Srv
010.000.0413 The statistic server cannot be reached during startup. The task
reporting server will try again after 1 second.
tr_Srv
010.000.0414 A report cannot be registered at the statistic server. tr_Srv

010.000.0415 A report cannot be deregistered at the statistic server. tr_Srv
010.000.0416 A user defined tag cannot be found. Programming error tr_Srv
010.000.0417 The trial to start a report at the statistic server received an
error. See the error message from the statistic server
tr_Srv
010.000.0418 The trial to stop a report at the statistic server received an
error. See the error message from the statistic server
tr_Srv
010.000.0500 A data record shall be written in the customer database, but
the connection is not available
tr_Srv
010.000.0501 Creating a command to write a data record in the customer
database failed. May be out of memory
tr_Srv
010.000.0502 Configuration error: there are more parameters configured as
needed in the sql statement
tr_Srv
010.000.0503 Configuration error: there are less parameters configured as
needed in the sql statement
tr_Srv
010.000.0504 Configuration error: a parameter is configured with a negative
parameter number
tr_Srv
010.000.0505 Configuration error: a parameter is configured twice tr_Srv
010.000.0506 Configuration error:a a given parameter has an illegal
parameter type
tr_Srv
010.000.0507 Configuration error:a a given parameter has an illegal sql type tr_Srv
010.000.0508 Configuration error:a a given parameter has an illegal C type tr_Srv
010.000.0600 Connection to ODBC database failed, check URL, user,
password
tr_Srv
010.000.0601 Allocating an ODBC statement handle failed tr_Srv
010.000.0602 Allocating an ODBC statement handle failed, while trying to
read procedure infos
tr_Srv
010.000.0603 Allocating an ODBC statement handle failed, while reading a
task id
tr_Srv

execute an sql statement directly
tr_Srv
read column infos
tr_Srv
010.000.0606 Preparing an ODBC statement failed tr_Srv
010.000.0607 Binding an ODBC parameter failed tr_Srv
010.000.0608 Executing an ODBC statement failed tr_Srv
010.000.0609 Trying to execute an ODBC statement durning database
shutdown
tr_Srv
010.000.0610 An ODBC function is called and returned SQL_ERROR tr_Srv
010.000.0611 An ODBC function is called and returned SQL_NEED_DATA tr_Srv
010.000.0612 An ODBC function is called and returned
SQL_STILL_EXECUTING
tr_Srv
010.000.0613 An ODBC function is called and returned SQL_NO_DATA tr_Srv
010.000.0614 An ODBC function is called and returned
SQL_INVALID_HANDLE
tr_Srv
010.000.0615 An ODBC function is called and returned with unknown result tr_Srv
010.000.0616 The ODBC function SQLNumParams() is called and returned
an error
tr_Srv
010.000.0617 Trying to get column infos returned an error tr_Srv
010.000.0618 Trying to get procedure infos returned an error tr_Srv
010.000.0619 Trying to get a task id returned an error tr_Srv

010.000.0620 Trying to bind columns to read a task id returned an error tr_Srv
010.000.0621 Trying to execute an sql statement returned an error tr_Srv
010.000.0622 Trying to execute an sql statement to get a task id returned an
error
tr_Srv
010.000.0623 Calling the ODBC function SQLSetConnectAttr() returned an
error
tr_Srv
010.000.0624 Calling the ODBC function SQLEndTran() returned an error tr_Srv
010.000.0625 Calling the ODBC function SQLColumns() returned an error tr_Srv
010.000.0626 Calling the ODBC function SQLProcedureColumns() returned
an error
tr_Srv
010.000.0700 The creation of a log file failed, check disk space tr_Srv
010.000.0701 The creation of a overflow log file failed, check disk space tr_Srv
010.000.0702 The creation of a overflow temporal log file failed, check disk
space
tr_Srv
010.000.0703 The creation of a overflow retry log file failed, check disk
space
tr_Srv
010.000.0704 Checking the file size of a log file failed, check disk space tr_Srv
010.000.0705 Checking the file size of a 'don't retry' log file failed, check disk
space
tr_Srv
010.000.0706 Reading file information for a log file while starting the data
transformation failed
tr_Srv
010.000.0707 Reading file information for a log file while stopping the data
transformation failed
tr_Srv
010.000.0708 Setting the file pointer to the start of the file failed, check disk
space
tr_Srv
010.000.0709 Setting the file pointer to the start of the 'don't retry' file failed,
check disk space.
tr_Srv

010.000.0710 Setting the file pointer to the start of the file failed, check disk
space.
tr_Srv
010.000.0711 Creating a 'don't retry' log file failed. Check the disk space. tr_Srv
010.000.0712 Writing a data record to the log file failed.Check the disk
space.
tr_Srv
010.000.0713 Writing a data record to the log file failed.Check the disk
space.
tr_Srv
010.000.0714 Creating a log file failed. Check the disk space. tr_Srv
010.000.0715 Opening a log file failed. tr_Srv
010.000.0716 Error while reading a log file tr_Srv
010.000.0717 Error while checking size of a log file tr_Srv
010.000.0718 Error while checking size of a temporal log file tr_Srv
010.000.0719 Error while checking size of a retry log file tr_Srv
010.000.0720 A log file cannot be deleted tr_Srv
010.000.0721 Data transfer from file to database is stopped, but there are
more data records in the file
tr_Srv
010.000.0997 A CORBA exception is caught. Look for the reason in the
<comment>
tr_Srv
010.000.0998 The application run out of memory tr_Srv
010.000.0999 An exception is caught. Programmng error. tr_Srv
013.000.1000 Error while starting. Will try again. annax
013.000.1001 Was not able to get db ref. Will try again. annax
013.000.1002 Was not able to contact lna server. Will try again. annax
013.000.1003 Was not able to contact monitor_srv. Will try again. annax
013.000.1004 Was not able to open Com Port. annax
013.000.1005 Was not able to create database session. Will try again. annax
013.000.1006 Configuration of display failed. annax
013.000.2000 STATE: Starting annax server. annax
013.000.2001 STATE: Annax server is up and running. annax

013.000.2002 STATE: Terminating annax server. annax
013.000.2003 STATE: Annax server is stopped. annax
013.000.2004 STATE: No displays configured at all. annax
013.000.2005 STATE: Connected to db_srv. annax
013.000.2006 STATE: Connected to lna_srv. annax
013.000.2007 STATE: Connected to monitor_srv. annax
013.000.2008 STATE: A restart was requested. annax
013.000.2009 STATE: Display is up and running. annax
013.000.2010 STATE: Reloading displays. annax
013.000.2011 STATE: No content configured for display. annax
019.000.1000 SUCCESS: Successfully initialized the ORB. VU Man
019.000.1001 FAILURE: Initialization of ORB failed. Exiting... VU Man
019.000.1002 SUCCESS: Successfully registered at ORB naming service. VU Man
019.000.1003 FAILURE: Registration of the vectors process at ORB naming
service failed.
VU Man
019.000.1100 SUCCESS: Database server successfully connected. VU Man
019.000.1101 FAILURE: Binding the database server failed. VU Man
019.000.1102 FAILURE: Binding the database server failed. VU Man
019.000.1103 FAILURE: Getting a database session failed. VU Man
019.000.1104 FAILURE: Getting a database session failed. VU Man
019.000.1105 SUCCESS: Successfully loaded static Objects from the data-
base server.
VU Man
failed.
VU Man
failed.
VU Man
019.000.1108 FAILURE: Connection to database server lost. VU Man
019.000.1109 SUCCESS: Successfully reconnected the database server. VU Man
019.000.1110 FAILURE: Reconnecting the database server failed. VU Man
019.000.1200 SUCCESS: Notification server successfully connected. VU Man
019.000.1201 FAILURE: Binding the notification server failed. VU Man
019.000.1202 FAILURE: Registering observer for change notifications
failed.
VU Man

019.000.1203 FAILURE: Registering observer for change notifications
failed.
VU Man
019.000.1204 FAILURE: Registering observer for ask notifications failed. VU Man
019.000.1205 FAILURE: Registering observer for ask notifications failed. VU Man
019.000.1206 FAILURE: Connection to notification server lost. VU Man
019.000.1207 SUCCESS: Successfully reconnected the notification server. VU Man
019.000.1208 FAILURE: Reconnecting the notification server failed. VU Man
019.000.1300 Not used in VUManager vu
019.000.1400 SUCCESS: License server successfully connected. vu
019.000.1401 FAILURE: Connecting the license server failed. Exiting... vu
019.000.1402 FAILURE: Failed to allocate the required license. vu
019.000.1403 FAILURE: Failed to release the allocated license. vu
019.000.1500 SUCCESS: Task server successfully connected. vu
019.000.1500 SUCCESS: Task server manager successfully connected. vu
019.000.1501 FAILURE: Binding the task server manager failed. vu
019.000.1502 FAILURE: Connecting the task server failed. vu
019.000.1503 FAILURE: Task server not yet ready. Waiting... vu
019.000.1504 FAILURE: Connection to task server lost. vu
019.000.1504 FAILURE: Connection to task server manager lost. vu
019.000.1505 SUCCESS: Successfully reconnected the task server. vu
019.000.1506 FAILURE: Reconnecting the task server failed. vu
019.000.2000 SUCCESS: Startup finished. Process is now up. vu
019.000.2001 MESSAGE: Initiating Shutdown ... vu
019.000.2002 FAILURE: Initialization of process resulted in an exception.
Exiting...
vu
019.000.2100 MESSAGE: Starting up a voice unit '<vuname>'. vu
019.000.2101 FAILURE: Starting up voice unit '<vuname>'. vu
019.000.2102 SUCCESS: Successfully started voice unit '<vuname>'. vu
019.000.2103 MESSAGE: Shutting down voice unit '<vuname>'. vu
019.000.2104 FAILURE: Shutting down voice unit '<vuname>' failed. vu
019.000.2105 SUCCESS: Successfully shut down voice unit '<vuname>'. vu
019.000.2106 FAILURE: Configuration error of voice unit '<vuname>'. vu

019.000.2107 FAILURE: Failed to download scripts of voice unit
'<vuname>'.
vu
019.000.2108 FAILURE: Failed to start heart beat controller of voice unit
'<vuname>'.
vu
019.000.2109 FAILURE: Failed to download scripts of voice unit
'<vuname>'.
vu
019.000.2110 FAILURE: Failed to download voice messages of voice unit
'<vuname>'.
vu
030.003.0001 At least on service license (FAX3, VOICE, SIGISDN, FOD) is
needed to start working.
CommGW
030.003.0002 One Service is configured, but there is no license. Please
change configuration or add license
CommGW
030.003.0003 WavToPhone can't register in naming service. Check
networkconnection and executing of omni nameservice.
CommGW
030.003.0004 Path configuration in file commgw/config/giRealspeak.cfg is
wrong. Check path to tts engine.
CommGW
030.003.0005 Registry configuration of TTS engine is wrong. CommGW
030.003.0006 Too many inbound lines are configurated. Check netport
configuration and telephone hardware / configuration of CAPI
CommGW
030.003.0007 There is a netport configurated that doesn't exists. Check
netport configuration and telephone hardware / configuration
of CAPI
CommGW
030.003.0008 There is no netport configuration. Check netport configuration. CommGW
030.003.0009 Check system if capi driver is installed. CommGW
030.003.0010 There are problems to load a hal dll. Check if hal allready is
running as service or some third party software is missing.
CommGW
030.003.0011 There are problems to load a hal dll. Check if hal allready is
running as service or some third party software is missing.
CommGW
030.003.0020 There are failures in scope application, check hal warning for
further information and correct the failures.
CommGW
030.003.0021 There are failures in scope application, check hal warning for
further information and correct the failures.
CommGW
030.003.0022 A scope application doesn't start working, that's a failure a
scope application should work all the time. Call support.
CommGW
030.003.0023 A scope application stopped working, that's a failure a scope
application should only stop on shutdown. Call support.
CommGW
030.003.0030 Timing Problem. Tui session is allready destroyed. Call
support.
CommGW
support.
CommGW

support.
CommGW
support.
CommGW
support.
CommGW
030.003.0040 A request (fax or voice) without content was sended. CommGW
030.003.0041 the wave file in a voice request has wrong format, CCITT
A-Law 8 Bit mono 8kHz is needed.
CommGW
030.003.0042 A tts engine is needed, when textual requests should be
readout at telephone.
CommGW
030.003.0043 All ums-tts-line licenses are in use. More ums-tts-line licenses
are needed.
CommGW
030.003.0044 Check preselection configuration. CommGW
030.003.0050 Check imap login name and password. CommGW
030.003.0051 Check network connection. CommGW
030.003.0060 Check network connection. Ckeck mapi version. CommGW
030.003.0061 Check network connection. Ckeck mapi version. CommGW
030.003.0062 Can't get out off office message via mapi. Check mapi error. CommGW
030.003.0066 Problems with mapi connection. Check mapi error. CommGW
030.003.0068 Problems with mapi document. CommGW
030.003.0080 Problems with a tiff file. Check convert manager. Call support. CommGW
030.003.0081 There are problems with fax receive fooder feature. Check fax
receive fooder configuration.
CommGW
030.003.0099 The needed diskspace in commgw/temp directory is too less.
Free diskspace.
CommGW
030.003.0101 Problems with connection to ums server. Check cpierror. CommGW

030.003.0108 A document could not delivered to account, no postmaster is
configured. The document will be saved locally. Check
cpierror.
CommGW
030.003.0109 A warnmessage could not delivered to account, no postmaster
is configured. The warnmessage will be saved locally. Check
cpierror.
CommGW
030.003.0111 This feature have to be switched on in registry. Shutting down
after DB failure of ums server.
CommGW
030.004.0001 Registry configuration wrong. Check registry configuration. DialUpNumberPool
030.004.0002 Nameservice problems. Check omniNameService. DialUpNumberPool
030.004.0003 Other problems. Call Support. DialUpNumberPool
030.021.0010 The SMTP Connector couldn't initialize the GSI-Library.
Please call support.
SMTP-Connetcor
030.021.0011 The SMTP Connector couldn't disconnect correctly from GSI
while GSI initializiation is active at other thread.
SMTP-Connetcor
030.021.0012 An error occured at stopping the SMTP Connector. Please
check network connection or relay host parameter.
SMTP-Connetcor
030.021.0013 An error occured at stopping the SMTP Connector. Please call
support.
SMTP-Connetcor
030.021.0020 The SMTP port is used by an other software module. The
SMTP connector can't receive some SMTP messages. Please
check configuration and other SMTP modules.
SMTP-Connetcor
030.021.0021 A standard exception occured at receiving SMTP messages.
SMTP-Connetcor
030.021.0022 The SMTP acceptor failed with an unknown exception. The
SMTP Connector stopped. Please call support.
SMTP-Connetcor
030.021.0030 The relay host has no authentification method we support.
Please check the configuration parameter of the relay host.
SMTP-Connetcor
030.021.0031 An error occured at sending a mail to the relay host. Please
check the error text for more information.
SMTP-Connetcor

030.021.0032 An error occured at sending a mail to the relay host. The
SMTP Connector will try sending again later. Please check the
error text for more information.
SMTP-Connetcor
030.021.0033 An error occured at sending a delivery report to the relay host.
Please check the error text for more information.
SMTP-Connetcor
030.021.0034 An error occured at sending a delivery report to the relay host.
The SMTP Connector will try sending again later. Please
check the error text for more information.
SMTP-Connetcor
030.021.0040 The received message can't be saved to the UMR/C3000 DB,
because no GSI interface is active. Please call support.
SMTP-Connetcor
030.021.0041 The error text was generated by saving the new message to
the UMR/C3000 DB. Please check the error message for
more information.
SMTP-Connetcor
030.021.0050 The tag parser library failed with an unknown error. Please
check message token or call support.
SMTP-Connetcor
030.021.0051 The tag parser library failed with the given error string. Please
check message token.
SMTP-Connetcor
030.021.0052 The tag parser library failed with an unknown exception. The
POP3/IMAP4 Client stopped. Please check message token or
call support.
SMTP-Connetcor
030.021.0053 Saving new messafe to UMR/C3000 DB failed, because GSI
interface isn't ready. Please call support.
SMTP-Connetcor
030.021.0054 The result string of getting UMR/C3000 DB filllevel has not the
correct format. Please call support.
SMTP-Connetcor
030.021.0055 The UMR/C3000 DB has reached maximum size. No more
messages will be written to the C3000 DB by the POP3/
IMAP4 Client. Check UMR DB.
SMTP-Connetcor
030.021.0056 An error occured at routing a new message to a recipient. SMTP-Connetcor
030.021.0057 An error occured at sending a new service message. SMTP-Connetcor
030.021.0950 Check the modul configuration in registry. The key C3KIDENT
is missing.
SMTP-Connetcor
030.021.0951 Check the modul configuration in registry. Found key ID
instead expected key C3KIDENT.
SMTP-Connetcor
030.021.0952 Check the modul configuration in registry. The value for
parameter POLLING is out of range [1s..3600s].
SMTP-Connetcor
030.021.0953 An error occured in communication to the C3000-Server. SMTP-Connetcor
030.021.0955 An error occured in communication to the C3000-Server while
accept an request to get a Mimemessage from C3000-Server.
SMTP-Connetcor
query specified request data to get a Mimemessage from
C3000-Server.
SMTP-Connetcor

getting the specified document to get a Mimemessage from
C3000-Server.
SMTP-Connetcor
getting addressdata for specified user to get a Mimemessage
from C3000-Server.
SMTP-Connetcor
getting addressdata by mailsystem-id for send to
C3000-Server. Please check sender values in s-file.
SMTP-Connetcor
030.021.0961 An error occured in communication to the C3000-Server
creating a document from mimedata for send to
C3000-Server.
SMTP-Connetcor
sending a created document to the target.
SMTP-Connetcor
030.021.0965 An error occured in communication to the C3000-Server at
routing a mime-message to the postmaster. Get the
postmaster address failed.
SMTP-Connetcor
getting addressdata by mailsystem-id (from order-file *.s) for
routing a document to an user. Please check sender values in
s-file.
SMTP-Connetcor
030.021.0967 Getting address for specified mailsystem-id to route document
to user failed.
SMTP-Connetcor
030.021.0970 Set status read for specified document at C3000 server failed. SMTP-Connetcor
030.021.0971 Set status success for specified document at C3000 server
failed.
SMTP-Connetcor
030.021.0972 Set status failed for specified document at C3000 server
failed.
SMTP-Connetcor
030.021.0973 Set status tried for specified document at C3000 server failed. SMTP-Connetcor
030.021.0975 Release request at C3000 server failed. SMTP-Connetcor
030.021.0976 Checking existance of smtp address failed. SMTP-Connetcor
030.021.0977 Getting mailsystem-Ids for specified address from
C3000-Server failed.
SMTP-Connetcor
030.021.0978 Getting the postmaster id from C3000-Server failed. SMTP-Connetcor
030.021.0980 Create new document from Mime failed while route document
to address.
SMTP-Connetcor
030.021.0981 Route document to address failed at C3000-Server. SMTP-Connetcor

030.021.0990 Error in communication to C3000-Server checking for
acknowledges failed.
SMTP-Connetcor
030.021.0991 Call to SendMimeMessageToMailsystem failed. Refer to
detailed log-messages from this module.
SMTP-Connetcor
030.022.0010 The POP3/IMAP4 Client couldn't initialize the GSI-Library.
POP3/IMAP4-Client
030.022.0011 The POP3/IMAP4 Client couldn't disconnect correctly from
GSI while GSI initializiation is active at other thread.
POP3/IMAP4-Client
030.022.0012 Checking the C3000 DB filllevel couldn't be done because GSI
interface isn't ready.
POP3/IMAP4-Client
030.022.0013 The result string of getting C3000 DB filllevel has not the
correct format. Please call support.
POP3/IMAP4-Client
030.022.0014 The C3000 DB has reached maximum size. No more
messages will be written to the C3000 DB by the POP3/
IMAP4 Client. Check UMR DB.
POP3/IMAP4-Client
030.022.0015 Saveing a new message to the C3000 DB couldn't be done
because GSI interface isn't ready. Please call support.
POP3/IMAP4-Client
030.022.0016 An error occured at routing a new message to a recipient. POP3/IMAP4-Client
030.022.0017 An error occured at sending a new service message to a
recipient.
POP3/IMAP4-Client
030.022.0018 The tag parser library failed with an unknown error. Please
check message token or call support.
POP3/IMAP4-Client
030.022.0019 The tag parser library failed with the given error string. Please
check message token.
POP3/IMAP4-Client
030.022.0020 The tag parser library failed with an unknown exception. The
POP3/IMAP4 Client stopped. Please check message token or
call support.
POP3/IMAP4-Client
030.022.0021 An error occured at stopping the POP3/IMAP4 Client. Please
call support.
POP3/IMAP4-Client
030.022.0030 The configuration of this UMR mail account has an unknown
protocol type (only POP3 or IMAP4 is allowed). So don't check
this mail account for new mails. Please check mail account
configiuration for this account.
POP3/IMAP4-Client
030.022.0031 Reading UMR mail accounts from BCC DB server failed with
given error string. Please check configuration parameter.
POP3/IMAP4-Client
030.022.0032 Reading C3000 mail accounts from C3000 configuration failed
with given error string. Please check configuration parameter.
POP3/IMAP4-Client
030.022.0033 Can't check this mail account because no protocol type is
defined. Please check mail account configiuration for this
account.
POP3/IMAP4-Client
030.022.0035 A standard exception occured at checking the mail accounts.
POP3/IMAP4-Client

030.022.0036 The mail service checker failed with an unknown exception.
The POP3/IMAP4 Client stopped. Please call support.
POP3/IMAP4-Client
030.022.0200 The IMAP4 connection has an error. The mail server {sever
name} is not reachable on the IMAP4 port. Please check
mailbox configuration parameter or network connection.
POP3/IMAP4-Client
030.022.0201 IMAP4-Connection to mail server returns with command NO
and response code and text. Please check mailbox
configuration parameter.
POP3/IMAP4-Client
030.022.0202 IMAP4-Connection to mail server returns with command BAD
and response code and text. Please check mailbox
configuration parameter.
POP3/IMAP4-Client
030.022.0205 The IMAP4 connection has an error. The mail server doesn't
accept the user name. Please check mailbox configuration
parameter or network connection.
POP3/IMAP4-Client
030.022.0206 IMAP4-Login at mail server doesn't accept login and returns
with command NO and response code and text. Please check
mailbox configuration parameter.
POP3/IMAP4-Client
030.022.0207 IMAP4-Login at mail server doesn't accept login and returns
with command BAD and response code and text. Please
check mailbox configuration parameter.
POP3/IMAP4-Client
030.022.0210 The IMAP4 connection has an error. Creating the mail move
folder failed. Please check mailbox configuration parameter or
network connection.
POP3/IMAP4-Client
030.022.0211 IMAP4-Create at mail server doesn't allow to create the mail
move folder and returns with command BAD and response
code and text. Please check mailbox configuration parameter.
POP3/IMAP4-Client
030.022.0215 The IMAP4 connection has an error. The SELECT command
for the inbox folder failed. Please check network connection.
POP3/IMAP4-Client
030.022.0216 IMAP4-Select at mail server can't select the inbox and returns
with command NO and response code and text. Please check
the mailbox at the mail server.
POP3/IMAP4-Client
030.022.0217 IMAP4-Select at mail server can't select the inbox and returns
with command BAD and response code and text. Please
check the mailbox at the mail server.
POP3/IMAP4-Client
030.022.0220 The IMAP4 connection has an error. The SEARCH command
for all UNSEEN mails in the inbox folder failed. Please check
network connection.
POP3/IMAP4-Client
030.022.0221 IMAP4-Search at mail server can't search for all unseen mails
in the inbox and returns with command NO and response code
and text. Please check the mailbox at the mail server.
POP3/IMAP4-Client
030.022.0222 IMAP4-Search at mail server can't search for all unseen mails
in the inbox and returns with command BAD and response
code and text. Please check the mailbox at the mail server.
POP3/IMAP4-Client
030.022.0225 The IMAP4 connection has an error. The FETCH command
for the message size of the next mail failed. Please check
network connection.
POP3/IMAP4-Client

030.022.0226 IMAP4-Fetch the size of a mail at mail server can't get the mail
size from the inbox and returns with command NO and
response code and text. Please check the mailbox at the mail
server.
POP3/IMAP4-Client
030.022.0227 IMAP4-Fetch the size of a mail at mail server can't get the mail
size from the inbox and returns with command BAD and
server.
POP3/IMAP4-Client
030.022.0228 The requested message is to large. The mail isn't saved to the
UMR DB. Please check the mailbox at the mail server.
POP3/IMAP4-Client
030.022.0230 The IMAP4 connection has an error. The FETCH command to
get the message content of the next mail failed. Please check
network connection.
POP3/IMAP4-Client
030.022.0231 The mail can't be saved to the UMR DB. Please check UMR
DB or DB server
POP3/IMAP4-Client
030.022.0232 IMAP4-Fetch the mail content at mail server can't get the mail
content and returns with command NO and response code
POP3/IMAP4-Client
030.022.0233 IMAP4-Fetch the mail content at mail server can't get the mail
content and returns with command BAD and response code
POP3/IMAP4-Client
030.022.0235 The IMAP4 connection has an error. The mail can't be copied
to the move folder. Please check network connection.
POP3/IMAP4-Client
030.022.0236 IMAP4-Copy the mail to the move folder can't copy the mail to
the move foldercontent and returns with command NO and
server.
POP3/IMAP4-Client
030.022.0237 IMAP4-Copy the mail to the move folder can't copy the mail to
the move foldercontent and returns with command BAD and
server.
POP3/IMAP4-Client
030.022.0240 The IMAP4 connection has an error. The flags of the mail can't
be changed in the inbox of user {user name}. Please check
network connection.
POP3/IMAP4-Client
030.022.0241 The IMAP4 connection has an error. This message may be
lost, because writing it to the UMR-DB failed and SEEN flag
can't be reseted. The mail is still in the inbox of the user, but is
marked as SEEN. Please check network connection.
POP3/IMAP4-Client
030.022.0242 IMAP4-Store the mail with a new message flag failed and
returns with command NO and response code and text.
Please check the mailbox at the mail server.
POP3/IMAP4-Client
030.022.0243 The IMAP4 protocol returned NO at changing message flag.
This message may be lost, because writing it to the UMR-DB
failed and SEEN flag can't be reseted. The mail is still in the
inbox of the user, but is marked as SEEN. Please check the
mailbox at the mail server.
POP3/IMAP4-Client

030.022.0244 IMAP4-Store the mail with a new message flag failed and
returns with command BAD and response code and text.
Please check the mailbox at the mail server.
POP3/IMAP4-Client
030.022.0245 The IMAP4 protocol returned BAD at changing message flag.
This message may be lost, because writing it to the UMR-DB
failed and SEEN flag can't be reseted. The mail is still in the
inbox of the user, but is marked as SEEN. Please check the
POP3/IMAP4-Client
030.022.0250 The IMAP4 connection has an error. The mail can't be
expunge from the inbox of user {user name}. Please check
network connection.
POP3/IMAP4-Client
030.022.0252 IMAP4-Expunge the marked mail failed and returns with
command NO and response code and text. Please check the
POP3/IMAP4-Client
030.022.0254 IMAP4-Expunge the marked mail failed and returns with
command BAD and response code and text. Please check the
POP3/IMAP4-Client
030.022.0260 The IMAP4 connection has an error. The logout from the inbox
of user {user name} failed. Please check network connection.
POP3/IMAP4-Client
030.022.0261 IMAP4-Logout from the inbox failed and returns with
command NO and response code and text. Please check the
POP3/IMAP4-Client
030.022.0262 IMAP4-Logout from the inbox failed and returns with
command BAD and response code and text. Please check the
POP3/IMAP4-Client
030.022.0300 The POP3 connection has an error. The mail server {sever
name} is not reachable on the POP3 port. Please check
mailbox configuration parameter or check network connection.
POP3/IMAP4-Client
030.022.0301 The POP3 protocol has an error. Connectiong the mail server
{sever name} on the POP3 port failed with error code {num}:
{text}. Please check mailbox configuration parameter
POP3/IMAP4-Client
030.022.0302 The POP3 connection has an error. The USER request to
logon for user {user name} on the mail server failed. Please
check network connection.
POP3/IMAP4-Client
030.022.0303 The POP3 protocol has an error. The USER request to logon
for user {user name} on the mail server failed with error code
{num}: {text}. Please check mailbox configuration parameter
POP3/IMAP4-Client
030.022.0304 The POP3 connection has an error. The PASS request with
the password for user {user name} on the mail server failed.
Please check network connection.
POP3/IMAP4-Client
030.022.0305 The POP3 protocol has an error. The PASS request with the
password for user {user name} on the mail server failed with
error code {num}: {text}. Please check mailbox configuration
parameter
POP3/IMAP4-Client
030.022.0306 The POP3 connection has an error. The STAT request to
receive the number of messages in the mailbox of user {user
name} failed. Please check network connection.
POP3/IMAP4-Client

030.022.0307 The POP3 protocol has an error. The STAT request to receive
the number of messages in the mailbox of user {user name}
failed with error code {num}: {text}. Please check the mailbox
at the mail server.
POP3/IMAP4-Client
030.022.0308 The POP3 connection has an error. The LIST request to
receive the size of the message in the mailbox of user {user
POP3/IMAP4-Client
030.022.0309 The POP3 protocol has an error. The LIST request to receive
the size of the message in the mailbox of user {user name}
at the mail server.
POP3/IMAP4-Client
030.022.0310 Error in the result of the list command The list command
returns not the size of the requestet message. Please check
the mailbox at the mail server.
POP3/IMAP4-Client
030.022.0311 The requested message is to large. The mail isn't saved to the
UMR DB. Please check the mailbox at the mail server.
POP3/IMAP4-Client
030.022.0312 The POP3 connection has an error. The RETR request to
receive the message from the mailbox of user {user name}
failed. Please check network connection.
POP3/IMAP4-Client
030.022.0313 The POP3 protocol has an error. The RETR request to receive
the message from mailbox of user {user name} failed with
error code {num}: {text}. Please check the mailbox at the mail
server.
POP3/IMAP4-Client
030.022.0314 The mail can't be saved to the UMR DB. Please check UMR
DB or DB server
POP3/IMAP4-Client
030.022.0315 The POP3 connection has an error. The DELE request to
mark the message for deletion in the mailbox of user {user
POP3/IMAP4-Client
030.022.0316 The POP3 protocol has an error. The DELE request to mark
the message for deletion in the mailbox of user {user name}
at the mail server.
POP3/IMAP4-Client
030.022.0317 The POP3 connection has an error. The QUIT request for
logoff from the mailbox of user {user name} failed. The marked
for deletion messages aren't deleted. Please check network
connection.
POP3/IMAP4-Client
030.022.0318 The POP3 protocol has an error. The QUIT request for logoff
from the mailbox of user {user name} failed with error code
{num}: {text}. The marked for deletion messages aren't
deleted. Please check the mailbox at the mail server.
POP3/IMAP4-Client
is missing.
POP3/IMAP4-Client
POP3/IMAP4-Client
POP3/IMAP4-Client

030.022.0953 An error occured in communication to the C3000-Server. POP3/IMAP4-Client
POP3/IMAP4-Client
C3000-Server.
POP3/IMAP4-Client
C3000-Server.
POP3/IMAP4-Client
from C3000-Server.
POP3/IMAP4-Client
POP3/IMAP4-Client
C3000-Server.
POP3/IMAP4-Client
POP3/IMAP4-Client
POP3/IMAP4-Client
s-file.
POP3/IMAP4-Client
to user failed.
POP3/IMAP4-Client
030.022.0970 Set status read for specified document at C3000 server failed. POP3/IMAP4-Client
failed.
POP3/IMAP4-Client
failed.
POP3/IMAP4-Client
030.022.0973 Set status tried for specified document at C3000 server failed. POP3/IMAP4-Client
030.022.0975 Release request at C3000 server failed. POP3/IMAP4-Client
030.022.0976 Checking existance of smtp address failed. POP3/IMAP4-Client
POP3/IMAP4-Client

030.022.0978 Getting the postmaster id from C3000-Server failed. POP3/IMAP4-Client
to address.
POP3/IMAP4-Client
030.022.0981 Route document to address failed at C3000-Server. POP3/IMAP4-Client
POP3/IMAP4-Client
030.022.0991 Call to SendMimeMessageToMailsystem failed. Refer to
detailed log-messages from this module.
POP3/IMAP4-Client
041.000.1000 The archive process is going to start RoD Archie
041.000.1001 The archive process has started properly and will work RoD Archie
041.000.1002 The archive process is going to stop RoD Archie
041.000.1003 The archive process has finished properly RoD Archie
041.000.1004 The archive process establsihed the connection to the
observation service
RoD Archie
041.000.2000 A Corba dialogue failed RoD Archie
041.000.2001 Unable to connect to CORBA Naming Service. Check
hostname and port.
RoD Archie
041.000.2002 The archive process is already running. Stop the running
intance of the archive process
RoD Archie
041.000.2003 Unable to connect to observation service. Check hostname
and port.
RoD Archie
041.000.2004 The connection to the observation service is broken. Check
wether it is running.
RoD Archie
041.000.2005 Try to archive the document database failed RoD Archie
041.000.2006 The response for a Corba request cannot be sent. RoD Archie
041.000.2007 While archiving a database error occurred. See the database
error message, which is added to this message
RoD Archie
041.000.2008 A database error ocurred while backup is done RoD Archie
041.000.2009 A database error ocurred while restore is done RoD Archie
041.000.2010 The database library cannot be initialized. Maybe it is missing RoD Archie
041.000.2011 The library <lib_name> cannot be initialized. Maybe it is
missing
RoD Archie
041.000.3000 An unexpected error occured. RoD Archie
042.000.1000 The CommandExecuter process is going to start Rod Cex
042.000.1001 The CommandExecuter process has started properly and will
work
Rod Cex

042.000.1002 The CommandExecuter process is going to stop Rod Cex
042.000.1003 The CommandExecuter process has finished properly Rod Cex
042.000.2000 A Corba dialogue failed Rod Cex
hostname and port.
Rod Cex
042.000.2002 The CommandExecuter process is already running. Stop the
running intance of the archive process
Rod Cex
042.000.2003 The CommandExecuter process tried to start another
programm, but this failed. Maybe, the program to dtart is
missing
Rod Cex
042.000.3000 An unexpected error occured. Rod Cex
043.000.1000 The rodomat process is going to start RoDoMatC
043.000.1001 The rodomat process has started properly and will work RoDoMatC
043.000.1002 The rodomat process is going to stop RoDoMatC
043.000.1003 The rodomat process has finished properly RoDoMatC
043.000.1004 The rodomat process establsihed the connection to reposerv
process via the observation service
RoDoMatC
043.000.2000 A Corba dialogue failed RoDoMatC
hostname and port.
RoDoMatC
043.000.2002 The connection to the reposerv process via observation
service is broken. Check wether it is running.
RoDoMatC
043.000.2003 Unable to connect to the reposerv process via observation
service. Check hostname and port.
RoDoMatC
043.000.3000 An unexpected error occured. RoDoMatC
046.000.0001 Starting Texttemplate/Autoreplyadmin TextTemplate
Admin
046.000.0002 Texttemplate/Autoreplyadmin started TextTemplate
Admin
046.000.0003 Stopping Texttemplate/Autoreplyadmin... TextTemplate
Admin
046.000.0004 Texttemplate/Autoreplyadmin stopped. TextTemplate
Admin
046.000.0010 Reconnected to {0} TextTemplate
Admin
046.000.0014 Connection to external process failed. Process is not running
or CORBA nameservice is not configured properly.
TextTemplate
Admin
046.000.0015 Connection to external process lost. Ensure process is
running.
TextTemplate
Admin

046.000.0021 Invalid configuration. See details. TextTemplate
Admin
046.000.0023 Component raised an error. See component's logs for details. TextTemplate
Admin
047.000.1000 The Reposerv process is going to start Rod RepoServ
047.000.1001 The Reposerv process has started properly and will work Rod RepoServ
047.000.1002 The Reposerv process is going to stop Rod RepoServ
047.000.1003 The Reposerv process has finished properly Rod RepoServ
047.000.1004 The Reposerv process establsihed the connection to the
observation service
Rod RepoServ
047.000.2000 A Corba dialogue failed Rod RepoServ
hostname and port.
Rod RepoServ
047.000.2002 The Reposerv process is already running. Stop the running
intance of the archive process
Rod RepoServ
047.000.2003 The directory <directory> cannot be created. Check disk
space and write protection
Rod RepoServ
047.000.2004 Unable to connect to observation service. Check hostname
and port.
Rod RepoServ
047.000.2005 The connection to the observation service is broken. Check
wether it is running.
Rod RepoServ
047.000.2006 Lost connection to the archive process. Check wether it is
running.
Rod RepoServ
047.000.2007 This error message is not used in UMR Rod RepoServ
047.000.2008 The response for a Corba request cannot be sent. Rod RepoServ
047.000.2009 A progress update event cannot be sent. Maybe, connection is
broken.
Rod RepoServ
047.000.2010 An error event cannot be sent. Maybe, connection is broken. Rod RepoServ
047.000.2011 The database library cannot be initialized. Maybe it is missing Rod RepoServ
047.000.2012 The library <lib_name> cannot be initialized. Maybe it is
missing
Rod RepoServ
047.000.3000 An unexpected error occured. Rod RepoServ
052.000.1000 Couldn't register its TaskStatisticAdapter at corba
nameservice
Reconstructor
052.000.1001 Couldn't register its TaskHistoryAdapter at corba nameservice Reconstructor
052.000.1002 Couldn't read reconstruction-files Reconstructor
052.000.1003 Treat calls as emails. ONLY TESTING ALLOWED.. Reconstructor
052.000.1700 Reconstructor has shut down Reconstructor

052.000.1701 Reconstructor ends all unused tasks due to timeout or
user-request
Reconstructor
052.000.1800 Tracing by request Reconstructor
052.000.2000 Corba exception during try to connect kern Reconstructor
052.000.2001 Could not register observer at kerns observable Reconstructor
052.000.2700 Reconstructor has connected kern Reconstructor
052.000.2701 Lost connection to kern Reconstructor
052.000.2702 Kern connected TaskHistoryIf Reconstructor
052.000.2703 Kern lost connection to TaskHistoryIf Reconstructor
052.000.3000 Do we have more than one s_srvs? Mon_srv may not connect
reconstructor
Reconstructor
052.000.3700 statistic_srv has connected reconstructor Reconstructor
052.000.3701 Lost connection to statistic_srv Reconstructor
052.000.4000 Can't create directory for reconstruction data Reconstructor
052.000.4001 Can't find/open directory of reconstruction data Reconstructor
052.000.4002 Error reading file Reconstructor
052.000.4003 Error reading file. no Directory? Reconstructor
052.000.4004 Error opening file. Reconstructor
052.000.4700 Read TaskIds of active/deactivated tasks from directory Reconstructor
052.000.4701 Finished reconstructing active tasks; deactivateds still under
reconstruction
Reconstructor
052.000.4702 Finished reconstructing active/deactivated tasks Reconstructor
053.000.0001 Server has started. C3000 Server
053.000.0002 License has expired. C3000 Server
053.000.0003 Internal error. C3000 Server
053.000.0004 Server is stopping. C3000 Server
053.000.0005 Server has stopped. C3000 Server
053.000.0006 Configuration has errors. C3000 Server
053.000.0007 Error while checking licenses, make sure license exists and
license server is available.
C3000 Server
053.000.0008 Network problem, make sure network connection is available
and remote component is running.
C3000 Server
053.000.0009 Some required components where not installed (e.g. missing
dll).
C3000 Server
054.000.0001 Conversion failed. See corresponding log message for details. UMS Convert

066.000.0999 server detected unexpected ui connection loss
check network connection or client system
ChatTaskServer
066.000.1000 error loading settings, perhaps the properties file is missing
check installation, reinstall
ChatTaskServer
066.000.1001 error initializing basic application environment, perhaps
installation is corrupt
check installation, reinstall
ChatTaskServer
066.000.1100 error running ORB
check network connection and corba settings
ChatTaskServer
066.000.1101 error connecting Database
check network connection and corba settings, ensure
Database is running
ChatTaskServer
066.000.1102 error connecting Taskserver Manager
check network connection and corba settings, ensure
Taskserver Manager is running
ChatTaskServer
066.000.1103 error connecting XMPP Server
check network connection and XMPP settings, ensure XMPP
Server is running
ChatTaskServer
066.000.1200 server is out of resources
check memory and thread consumption, report if there seems
to be a resource leak
ChatTaskServer
110.009.0900 Gateway got connection to the ums server GSI
110.009.0901 Scanning for new messages from ums server is working
properly
GSI
110.009.0902 Scanning for new acknowledges from ums server is working
properly
GSI
is missing.
GSI
GSI
GSI
110.009.0953 An error occured in communication to the C3000-Server. GSI
110.009.0954 Gateway lost connection to ums server. Check if server is
stopped or netw
GSI
GSI
C3000-Server.
GSI

C3000-Server.
GSI
from C3000-Server.
GSI
110.009.0959 Scanning for new messages from ums server is stopped
because connection to ums server has been lost. It will
continue when connection is reestablished. Check if server is
stopped or network connection is broken.
GSI
GSI
C3000-Server.
GSI
GSI
GSI
s-file.
GSI
to user failed.
GSI
110.009.0970 Set status read for specified document at C3000 server failed. GSI
failed.
GSI
failed.
GSI
110.009.0973 Set status tried for specified document at C3000 server failed. GSI
110.009.0975 Release request at C3000 server failed. GSI
110.009.0976 Checking existance of smtp address failed. GSI
GSI
110.009.0978 Getting the postmaster id from C3000-Server failed. GSI

to address.
GSI
110.009.0981 Route document to address failed at C3000-Server. GSI
GSI
110.009.0991 Scanning for new acknowledges from ums server is stopped
GSI
110.009.0992 An error occured delivering document from ums server to the
external mailsystem
GSI
111.009.0900 Gateway got connection to the ums server FSI
111.009.0901 Scanning for new messages from ums server is working
properly
FSI
111.009.0902 Scanning for new acknowledges from ums server is working
properly
FSI
is missing.
FSI
FSI
FSI
111.009.0953 An error occured in communication to the C3000-Server. FSI
111.009.0954 Gateway lost connection to ums server. Check if server is
stopped or netw
FSI
FSI
C3000-Server.
FSI
C3000-Server.
FSI
from C3000-Server.
FSI
111.009.0959 Scanning for new messages from ums server is stopped
FSI

FSI
C3000-Server.
FSI
FSI
FSI
s-file.
FSI
to user failed.
FSI
111.009.0970 Set status read for specified document at C3000 server failed. FSI
failed.
FSI
failed.
FSI
111.009.0973 Set status tried for specified document at C3000 server failed. FSI
111.009.0975 Release request at C3000 server failed. FSI
111.009.0976 Checking existance of smtp address failed. FSI
FSI
111.009.0978 Getting the postmaster id from C3000-Server failed. FSI
to address.
FSI
111.009.0981 Route document to address failed at C3000-Server. FSI
FSI
111.009.0991 Scanning for new acknowledges from ums server is stopped
FSI

111.009.0992 An error occured delivering document from ums server to the
external mailsystem
FSI
111.010.0001 Acknowledge scan in toC3000 directory stopped because
connection to C3000-Server failed. It will continue when
connection is reestablished. Check if server is stopped or
network connection is broken.
FSI
111.010.0002 Operate acknowledge file failed. File is moved to the error
directory. See detailed logmessages and check values in file.
FSI
111.010.0003 Error copying acknowledge file to error directory. Check
configuration and directory.
FSI
111.010.0004 Can't create file in configured error directory. FSI
111.010.0005 Found acknowledge with unknown id. Discard file. Maybe the
document is already delete by an routing rule.
FSI
111.010.0010 Request scan in toC3000 directory stopped because
connection to C3000-Server failed. It will continue when
connection is reestablished. Check if server is stopped or
network connection is broken.
FSI
111.010.0020 Creation of data file in fromC3000 directory failed. Add no
filename tag in order file (*.s).
FSI
111.010.0030 State of request in C3000 system changed but creation of
acknowledge file in fromC3000 directory failed.
FSI
111.010.0040 Creation of file failed. See further logmessages for details. FSI
111.010.0100 FSI successfully started FSI
111.010.0101 Stopping FSI process FSI
111.010.0102 FSI has been stopped FSI
111.010.0103 Requestscan in toC3000 directory is working properly FSI
111.010.0104 Acknowledge scan in toC3000 directory is working properly FSI
111.010.0110 License error. Can't start FSI gateway. Check your license
configuration
FSI
114.014.0101 Gateway has started. PrGW
114.014.0102 Gateway is stopping. PrGW
114.014.0103 Gateway has stoped. PrGW
114.014.0104 Gateway has break. PrGW
114.014.0105 Gateway has continued. PrGW
114.014.0201 Document (DocID Nr. ReqID) is empty. Document can not be
printed.
PrGW
114.014.0202 Document (DocID Nr. ReqID) no valid format available.
Document can not be printed.
PrGW

114.014.0203 Document can not be printed by the appropriate printer. The
error description explains the concrete reason of this error in a
more detailed way.
PrGW
114.014.0204 Printer not connected. Document can not be printed. It should
be proved if the computer is connected with the appropriate
printer. It should be proved if the appropriate printer is
declared as target in routing rule. It should be proved if
gateway has the right to use this printer.
PrGW
114.014.0301 Document (DocID Nr. ReqID) is printed by the appropriate
printer.
PrGW
115.015.0101 Gateway has connected with C3000 server C3000 Address
Import
115.015.0102 Gateway has disconnected with C3000 server C3000 Address
Import
115.015.0103 Gateway signed on C3000 server C3000 Address
Import
115.015.0104 Gateway has started. C3000 Address
Import
115.015.0105 Gateway is stopping. C3000 Address
Import
115.015.0106 Gateway has stoped. C3000 Address
Import
115.015.0107 Gateway has break. C3000 Address
Import
115.015.0108 Gateway has cotninued. C3000 Address
Import
115.015.0201 Gateway could not connect with C3000 server. Examine the
network.
C3000 Address
Import
115.015.0202 Gateway has not signed on C3000 server. Check username
and password. Prove if the user has got administrators rights
for C3000.
C3000 Address
Import
115.015.0203 Service not licensed. Check the licence. C3000 Address
Import
115.015.0301 Gateway could not open file. Prove if this file exists. C3000 Address
Import
115.015.0302 Dat-file has no header. Analyse this file in error directory. C3000 Address
Import
115.015.0303 Analyse ini-file, inimod-file, dat-file C3000 Address
Import
115.015.0304 Analyse inimod-file C3000 Address
Import
115.015.0401 Data could not be modified (CPI-error) C3000 Address
Import

115.015.0402 Data could not be added (CPI-error) C3000 Address
Import
115.015.0403 Data for the demanded user could not be found (CPI-error) C3000 Address
Import
115.015.0404 Demanded user could not be deactivated for C3000
(CPI-error)
C3000 Address
Import
115.015.0405 Demanded user could not be activated for C3000 (CPI-error) C3000 Address
Import
115.015.0406 Routing rule could not be imported (CPI-error) C3000 Address
Import
115.015.0501 Gateway has found and open file. C3000 Address
Import
115.015.0502 Dat-file was imported successfully. The info-message contains
information about the total amount of data record, successfully
imported data record, successfully imported routing rulers
C3000 Address
Import
201.000.0001 System-misconfiguration UMR Taskserver
201.000.0002 Check if DB-Server is running... UMR Taskserver
201.000.0003 Check if UMS-Server(ClientAdapter) is running... UMR Taskserver
201.000.0004 Check if TaskserverManager-Server is running... UMR Taskserver
201.000.0005 Check if DB-Server is running... UMR Taskserver
201.000.0006 Configuration-mismatch. UMR Taskserver
201.000.0007 Mailbox at UMS_Server unreachable. Mailbox really exist ? UMR Taskserver
201.000.0008 Configuration-mismatch. UMR Taskserver
242.000.0001 Starting UMRClientAdapter... UmrClientAdapter
242.000.0002 UMRClientAdapter started UmrClientAdapter
242.000.0003 Stopping UMRClientAdapter... UmrClientAdapter
242.000.0004 UMRClientAdapter stopped UmrClientAdapter
242.000.0010 Reconnected to {0} UmrClientAdapter
242.000.0011 Error occured initializing process. Check configuration file. UmrClientAdapter
242.000.0012 Check that database is running. Check that
databaseconnection is configured properly in propertyfile.
UmrClientAdapter
242.000.0013 A databaseexception occured executing action specified in
placeholder '{0}'. Refer to database manual regarding
message in placeholder '{1}'.
UmrClientAdapter
UmrClientAdapter
running
UmrClientAdapter

242.000.0016 CreateError was thrown by observation. This error occured in
class described in placeholder'{0}'. Maybe a remoteprocess is
not running.
UmrClientAdapter
242.000.0017 Error occured registering object at CORBA nameservice.
Ensure that nameservice is running.
UmrClientAdapter
242.000.0018 Error occured starting CORBA mainloop. Check CORBA
nameservice configuration.
UmrClientAdapter
242.000.0019 An error occured initializing CORBA . Check CORBA
UmrClientAdapter
242.000.0101 JPIException was thrown by C3000 Server executing action
specified in placeholder '{0}'. Refer to cpi manual regarding
message in placeholder '{1}'.
UmrClientAdapter
242.000.0102 Error occured initializing processobservatopm. Check CORBA
UmrClientAdapter
242.000.0103 Connection to C3K-LNA Server failed. Process is not running
UmrClientAdapter
242.000.0104 Check that dll configured in propertyfile is in classpath. UmrClientAdapter
242.000.0105 Internal error UmrClientAdapter
242.000.0106 Check configuration. Jar-Archive containing specified class
must be in classpath.
UmrClientAdapter
242.000.0107 Check configuration. Jar-Archive containing specified class
must be in classpath.
UmrClientAdapter
242.000.0108 Systemcomponent for decryption is missing UmrClientAdapter
242.000.0109 Systemcomponent for decryption is missing UmrClientAdapter
242.000.0110 Error occured in archive adapter. Refer to specific message in
placeholder '{0}'.
UmrClientAdapter
242.000.0111 Internal error. UmrClientAdapter
242.000.0112 CORBA call failed. Probably a server process is not running.
See message for further details.
UmrClientAdapter
UmrClientAdapter
243.000.0001 Starting UMRWebClient... UmrWebClient
243.000.0002 UMRWebClient started UmrWebClient
243.000.0003 Stopping UMRWebClient... UmrWebClient
243.000.0004 UMRWebClient stopped UmrWebClient
243.000.0010 Reconnected to {0} UmrWebClient
243.000.0011 Error occured initializing process. Check configuration file. UmrWebClient

243.000.0012 Check that database is running. Check that
databaseconnection is configured properly in propertyfile.
UmrWebClient
UmrWebClient
running
UmrWebClient
not running.
UmrWebClient
243.000.0017 Error occured registering object at CORBA nameservice.
Ensure that nameservice is running.
UmrWebClient
UmrWebClient
243.000.0019 An error occured initializing CORBA . Check CORBA
UmrWebClient
243.000.0020 Invalid configuration. Missing specified entry. Check config
propertyfile.
UmrWebClient
243.000.0101 Internal error. UmrWebClient
UmrWebClient
UmrWebClient
243.000.0104 Systemcomponent for decryption is missing UmrWebClient
243.000.0105 UMRClientadapter threw 'InvalidOperation' for
'loginToCallcenter'. Possibly Clientadapter is running in
C3000-Mode. Please check configuration file.
UmrWebClient
243.000.0106 Operation could not be performed. See UISessionmanager
log for details.
UmrWebClient
243.000.0107 Check if licenseserver is running. UmrWebClient
243.000.0108 Check licenseserver configuration UmrWebClient
243.000.0109 Version mismatch between licenses and umrwebclient. UmrWebClient
243.000.0110 Check licenseserver configuration. UmrWebClient
244.000.0001 Starting UISessionManager... UISessionManager
244.000.0002 UISessionManager started UISessionManager
244.000.0003 Stopping UISessionManager... UISessionManager
244.000.0004 UISessionManager stopped UISessionManager
not running.
UISessionManager

UISessionManager
UISessionManager
244.000.0102 Internal error. UISessionManager


Index
Index
A
annax . . . . . . . . . . . . . . . . . . . . . . . 20
C
C3000 Address Import . . . . . . . . . . . . . . . 43
C3000 Server . . . . . . . . . . . . . . . . . . . 37
ChatTaskServer . . . . . . . . . . . . . . . . . . 38
CommGW. . . . . . . . . . . . . . . . . . . . . 23
custident . . . . . . . . . . . . . . . . . . . . . . 9
D
db_srv . . . . . . . . . . . . . . . . . . . . . . . 7
DialUpNumberPool . . . . . . . . . . . . . . . . 25
F
FSI . . . . . . . . . . . . . . . . . . . . . . . . 40
G
GSI . . . . . . . . . . . . . . . . . . . . . . . . 38
K
kernel . . . . . . . . . . . . . . . . . . . . . . . 8, 9
L
lad_srv . . . . . . . . . . . . . . . . . . . . . . . 9
lna_srv . . . . . . . . . . . . . . . . . . . . . . . 7
M
monitor_Srv . . . . . . . . . . . . . . . . . . . . 12
P
POP3/IMAP4-Client . . . . . . . . . . . . . . . . 28
PrGW. . . . . . . . . . . . . . . . . . . . . . . 42
R
Reconstructor . . . . . . . . . . . . . . . . . . . 36
RoD Archie. . . . . . . . . . . . . . . . . . . . . 34
Rod Cex . . . . . . . . . . . . . . . . . . . . . . 34
Rod RepoServ . . . . . . . . . . . . . . . . . . . 36
RoDoMatC. . . . . . . . . . . . . . . . . . . . . 35
S
SMTP-Connetcor . . . . . . . . . . . . . . . . . . 25
statistic_srv . . . . . . . . . . . . . . . . . . . . 11
T
TextTemplate Admin . . . . . . . . . . . . . . . . 35
tr_Srv . . . . . . . . . . . . . . . . . . . . . . . 13
U
UISessionManager . . . . . . . . . . . . . . . . . 46
UMR Taskserver . . . . . . . . . . . . . . . . . . 44
UmrClientAdapter . . . . . . . . . . . . . . . . . 44
UmrWebClient . . . . . . . . . . . . . . . . . . . 45
V
vectors. . . . . . . . . . . . . . . . . . . . . . . 10
vu . . . . . . . . . . . . . . . . . . . . . . . . . 22
VU Man . . . . . . . . . . . . . . . . . . . . . . 21
X
XMPP . . . . . . . . . . . . . . . . . . . . . . . 38

Index

Index

Index

Ipocc Error Numbers en

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Ipocc Error Numbers en

Загружено:

Авторское право:

Доступные форматы

IP Office Contact Center TTrace

Error Numbers Reference

Вам также может понравиться