Log Errors
Log errors are errors that are not related to the implementation of a service. Log errors are written to the xUML service log and are indicating e.g. a configuration problem. They cannot be caught by the modeler.
Overview of the Error Domains
Click an error domain to go to the list of errors of that domain. Click a context to go to the documentation of the selected topic.
Error Domain | Context |
---|---|
Add-on messages | |
Core messages | |
Lisence messages | |
Service messages | |
Timer Service | |
Domain ADDLM
Domain | Error Code | Description |
---|---|---|
|
| Loading the addon failed. |
|
| The repository is not correctly set up. |
|
| Loading addon failed, no getname symbol. |
|
| Loading addon failed, no initialize symbol. |
|
| Loaded addon sucessfully. |
|
| Found unexpected element for AddOn section. |
|
| Found unexpected element for root section. |
|
| Expected root element. |
|
| AddOn element is not complete. |
|
| Failed to read and parse repository. |
|
| Initializing addon failed. |
|
| Initializing addon failed. |
Domain AWSS3LM
Domain | Error Code | Description |
---|---|---|
|
| Missing operation definition. |
| 1 | Missing connection definition. |
| 2 | Duplicated connection entry. |
| 3 | Unknown element. |
| 4 | Missing attribute. |
| 5 | Unexpected known child element. |
| 6 | No negative port allowed. |
| 7 | Missing source bucket parameter. |
| 8 | Missing source object parameter. |
| 9 | Missing target bucket parameter. |
|
| Missing file path parameter. |
|
| Missing data for upload. |
|
| Missing version parameter. |
|
| Missing recursive parameter. |
|
| AWS SDK logging. |
|
| Output stream factory called multiple times. |
Domain BELM
Domain | Error Code | Description |
---|---|---|
|
| A given key could not be found in the tabfile. |
|
| A given unique key is found more than once in a tabfile. |
|
| No specification for the requested mapping found. |
|
| backendcomponents.tab not found. |
|
| No factory registered for the requested component type. |
|
| No factory registered for the requested function type. |
|
| The accessor factory has not been registered. |
|
| No connection manager for the requested source found. |
|
| Component can not be unregistered. |
|
| Function can not be unregistered. |
|
| No specification found for the requested function. |
|
| Minimal parameter count for the function not reached. |
|
| The component factory is already registered. |
|
| The function factory is already registered. |
|
| The connection manager is already registered. |
|
| Found unexpected element for Component section. |
|
| Found unexpected element for root section. |
|
| Expected root element. |
|
| Component element is not complete. |
|
| Failed to read and parse component repository file. |
|
| Duplicate definition for component. |
|
| Component is unknown. |
|
| Initializing component failed. |
|
| The service is already registered. |
|
| Function used by a mapper is not found. |
|
| Failed to parse security repository file. |
|
| Found unexpected element for SecurityInterceptorClass section. |
|
| Found unexpected element for AccessRules section. |
|
| Component referenced in AccessRules section not found. |
|
| Component reference in AccessRules section is missing. |
|
| Found unexpected element for AccessRule section. |
|
| Found unexpected operation name for Security Interceptor |
|
| Missing operation name for Security Interceptor |
|
| Missing component ID for Security Interceptor |
|
| Failed to load security repository file. |
|
| The service is shutting down. |
|
| The service was shut down. |
|
| The fingerprint of the repository does not match license. |
|
| Initializing service failed. |
|
| Found unexpected element for DataItem section. |
|
| Failed to parse names repository file. |
|
| Duplicate definition for named item. |
|
| Failed to resolve component failed. |
|
| Service is restarting. |
|
| Failed to handle change. |
|
| The source attribute is missing for an entry of mapping. |
|
| The target attribute is missing for an set or append entry of mapping. |
|
| A mapping has no id attribute. |
|
| Root element must be "Dump" of file "Base/dump.tab". |
|
| Transaction ID is truncated. |
|
| Stack size exceeded limit. |
|
| Unexpected value of 'action' for function. |
|
| Error creating map writer for mapper. Repository is corrupted. |
|
| Required Data Item is missing in the repository. |
|
| Creating repository failed. |
|
| Creating resouce manager failed. |
|
| Could not load all required addons. |
|
| Initializing resource manager failed. |
|
| Required XML Data Item is missing in the repository. |
|
| Fallback message. |
|
| Unexpected element in classic logger repository. |
Domain CTRLLM
Domain | Error Code | Description |
---|---|---|
|
| The adapter repository is not correctly set up. |
|
| Different element expected. |
|
| Root expected. |
|
| Failed to read and parse file. |
|
| System is not set up. |
|
| No session available. |
|
| Reading request failed. |
|
| The listener could not start. |
|
| Log command processed |
|
| Writing response failed. |
|
| The Logger is restarting. |
|
| Invalid logger configuration |
|
| Missing component parameter |
Domain DIRLM
Domain | Error Code | Description |
---|---|---|
|
| Can't open dataitem tab. |
|
| A mandatory column is empty. |
|
| The position in the data item is already in use. |
|
| Meta data error, attribute key used twice. |
|
| Default value does not match data type. |
|
| The dataitem associated with attribute can't be resolved. |
|
| Meta data error, operation key used twice. |
|
| Root element must be "DataItems". |
|
| The parent DataItem cannot be resolved. |
|
| Missing data item id. |
|
| Data item does not exist. |
|
| Attribute index is invalid. |
|
| Unknown element when parsing serialization tabfile. |
Domain FLOWLM
Domain | Error Code | Description |
---|---|---|
|
| illegal object type |
|
| no configuration for sequence |
|
| not enough configuration lines for sequence (<2) |
|
| the flow has not been initialized correctly: the start step is not defined. |
|
| could not find next step |
|
| could not find a called subcomponent |
|
| The id of the operation is not unique. |
|
| The 'variableIndex' is missing at step. |
|
| The decision has a condition without an expression. |
|
| Session cancelled. |
Domain FSADLM
Domain | Error Code | Description |
---|---|---|
|
| Found unexpected element for Read section. |
|
| Found unexpected element for root section. |
|
| Root expected. |
|
| Failed to read and parse file. |
|
| Found unexpected element for Write section. |
|
| Found unexpected element for Status section. |
|
| Found unexpected element for Remove section. |
|
| Found unexpected element for CreateDirectory section. |
|
| Found unexpected element for ReadDirectory section. |
|
| Found unexpected element for ReadLine section. |
|
| Found unexpected element for Rename section. |
|
| Found unexpected element for Append section. |
|
| Found unexpected element for Close section. |
|
| Duplicated request name. |
|
| Found unexpected element for Close section. |
Domain FUBLM
Domain | Error Code | Description |
---|---|---|
|
| Compare operator is of unknown type. |
Domain FUCLM
Domain | Error Code | Description |
---|---|---|
|
| Can not convert this value from string to blob. |
|
| Can not convert this value from string to boolean. |
|
| Can not convert this value from string to datetime. |
|
| Can not convert this value from string to float. |
|
| Can not convert this value from string to integer. |
|
| The type of the item to create is unknown. |
|
| The class of the item to create is unknown. |
|
| Constructor function has unsupported type. |
Domain FUDLM
Domain | Error Code | Description |
---|---|---|
|
| Found unexpected element for ConvertRecordToDateTime section. |
|
| Found unexpected element for ConvertDateTimeToRecord section. |
|
| Found unexpected element for root section. |
|
| Failed to read and parse. |
|
| Expected root element. |
|
| Function is not properly set up. |
|
| Function is not properly set up. |
|
| Function is unknown in the FUD repository. |
|
| Accessor for request is unknown. |
|
| Function is unknown in the FUD repository. |
|
| Accessor for function is unknown. |
|
| Function is not properly set up. |
|
| Function is unknown in the FUD repository. |
|
| Accessor for request is unknown. |
|
| Function is not properly set up. |
|
| Function is unknown in the FUD repository. |
|
| Accessor for request is unknown. |
|
| Found unexpected element for ConvertTimeTicksToDateTime section. |
|
| Found unexpected element for ConvertDateTimeToTimeTicks section. |
Domain KAWKAADLM
Domain | Error Code | Description |
---|---|---|
| 0 | Initializing Kafka AddOn. |
|
| Cannot read Kafka Producer adapter. The file does not exist or is otherwise not readable. |
|
| Cannot read Kafka Producer connections. The file does not exist or is otherwise not readable. |
|
| Cannot find Kafka Producer definition in the tabfiles. |
|
| Found unexpected element in the tabfiles. |
| 5 | A tabfile entry is missing a required attribute or the attribute is empty. |
|
| User-supplied Kafka configuration property has a named setting in the model. |
|
| Kafka configuration property has been set more than once. Either the user supplied it twice, or they use a property that has dedicated setting. |
|
| A connection definition has configuration options not recognised by the runtime. |
|
| A connection has been requested at runtime that has no static definition. |
|
| A message from the Kafka driver. |
|
| A warning message from the Kafka driver. |
|
| An important message from the Kafka driver, indicating an error. |
|
| Committing transaction reported an error. Transaction might have not been committed. |
|
| Aborting transaction reported an error. Transaction might still be open. |
Domain LCELM
Domain | Error Code | Description |
---|---|---|
|
| Failed to read and parse instance file. |
|
| Unexpected instance element found. |
|
| Instance root expected. |
|
| License repository not available. |
|
| License root expected. |
|
| Failed to read and parse license file. |
|
| No license path. |
|
| License key is missing from repository. |
|
| Using valid license. |
|
| Using demo license. |
|
| Instance license is invalid. |
|
| License signature is missing from repository. |
|
| License signature is invalid. |
|
| Public key is damaged while validating. |
|
| License id is missing from repository. |
|
| License signature encoding is invalid. |
|
| License ticker is not available. |
|
| Machine name to license mismatch |
|
| Machine name or key missing |
|
| License key expired |
|
| Service exceeds licensed concurrency |
|
| License limited to specific services, this service is not licensed. |
|
| A license based on a dongle is not supported on this platform. |
|
| Cached licence expiration date reached. Checking for renewed licence. |
Domain MEMADLM
Domain | Error Code | Description |
---|---|---|
|
| Expected Name for element. |
|
| Unexpected element. |
Domain MLM
Domain | Error Code | Description |
---|---|---|
|
| The repository path is invalid. |
|
| Loading the addon failed. |
|
| No child element expected. |
|
| Can't access repository file. |
|
| No system info available while opening repository file. |
|
| Unexpected element found. |
| 7 | Failed to read and parse 'features' repository. |
|
| Failed to parse errors repository. |
|
| BUG: %s |
|
| Malformed input. |
|
| Bad port number. |
|
| Unsupported scheme. |
|
| Setting URL part failed. |
Domain MONGOADLM
Domain | Error Code | Description |
---|---|---|
|
| Initializing MongoDB AddOn failed. |
|
| Unexpected tabfile element. |
|
| Duplicated entry for %s in MongoDB connection configuration. |
|
| Missing required attribute for tabfile entry. |
|
| Duplicated entry for %s in MongoDB adapter configuration. |
|
| MongoDB connection repository file is not accessible. |
|
| cannot parse {} without metadata. |
|
| Associated connection not found for adapter. |
|
| No pool for connection. |
|
| Missing adapter definition. |
|
| Commit failed. |
|
| Rollback failed. |
|
| Object to be serialized into MongoDB document is missing metadata. |
|
| Unknown simple type to serialize (please report a bug). |
|
| Multiple update specifications provided. |
|
| Incompatible update specifications provided. |
|
| Options parameter has incorrect type. |
|
| Query string document for operation is missing. |
|
| Handle parameter for fetch operation is missing. |
|
| Handle parameter for fetch operation has incorrect type. |
|
| Handle id for fetch operation is missing. |
|
| Missing required adapter parameter. |
|
| Input document for operation is missing. |
|
| Pipeline for operation is missing. |
|
| Source string for parsing is missing. |
|
| Source record for composing is missing. |
|
| Format for composing is missing or has wrong type. |
|
| Options for composing are missing or have wrong type. |
|
| Unrecognized composer mode '{}'. |
Domain PSADLM
Domain | Error Code | Description |
---|---|---|
|
| Warning: Missing database name to store persistent states, using memory instead. |
|
| State engine failed to connect to database. |
|
| Type used in persistent state does not exist in the base repository. |
|
| Persistent state dataitem is declared twice. |
|
| Persistent state signal is declared twice. |
|
| Component used in persistent state does not exist in the base repository. |
|
| Persistent state is declared twice. |
|
| Dataitem referenced in persistent state is unknown. |
|
| Persistent state transition is declared twice. |
|
| Signal referenced in persistent state is unknown. |
|
| State referenced by transition is unknown. |
|
| Initial persistent state transition can't have a timeout. |
|
| Persistent state command is declared twice. |
|
| Persistent state command not found |
|
| Signal definition is incomplete. |
|
| Persistent flow name is used twice. |
|
| State referenced as parent is unknown. |
|
| Flow referenced as submachine flow is unknown. |
|
| Persistent state search is missing SQL statement. |
|
| Error while parsing SQL command (e.g. search handles) |
|
| Persistent state transition has more then one timeout. |
|
| Lost connection to persistent state database. Will try to automatically reconnect. |
|
| Reconneted to persistent state database. |
|
| Reconnect to persistent state database failed. Will try again to reconnect. |
|
| Can't open database to dump persistent states. |
|
| Failed to init backup database. |
|
| The PersistentStateService stops processing new events. |
|
| Can not open a new persistent state database connection to compensate. |
|
| Could not parse signal data. The signal will be deleted and will not be processed. |
|
| Can not do consistency check after reconnect because other database transactions are still in progress. If you get duplicate key errors then restart the service to force the consistency check. |
|
| Persistent state high availability switch is active with retry timeout. |
|
| Database connection not available. |
|
| Detected changes to primary key of object. Those changes will be lost. |
|
| Detected objects for which no metadata exist in the repository. Correct the problem either by restoring class definitions in the model or by deleting corresponding objects. |
|
| Failed to complete Persistent State event action. |
|
| Failed to commit Persistent State object after performing doActivity. Object will stale in state. |
|
| Persistent state engine manages transaction isolation levels by itself. Please set it 'DBMS default' for PS connection. |
|
| Failed to store engine startup time. |
|
| Failed to store engine shutdown time. |
|
| Failed to prepare Persistent State SQL commands. |
|
| Failed to dump Persistent State database. |
|
| Failed to restore Persistent State database. |
|
| Failed to set initial PRAGMA statements on the Persistent State Database. |
|
| Persistent State object deleted while having %zd events pending. |
|
| Unknown element in PS control repository. |
|
| Found duplicated component in PS control repository. |
|
| Found unnamed component in PS control repository. |
|
| State handle not found. Probably the adapter has been called outside of PS context. |
|
| Cannot parse object data. |
Domain RESTLM
Domain | Error Code | Description |
---|---|---|
|
| Constructing REST_AddOn |
|
| Service already exists in the repository. |
|
| Service has not been found in the repository. |
|
| Unrecognized tabfile element when parsing REST Service repository. |
|
| Service description is invalid. |
|
| Value has wrong format. |
|
| Message is unknown to the repository. |
|
| Reading request failed, subsystem error. |
|
| Sending response failed, socket error. |
|
| Cannot generate any of the expected output formats. |
|
| Unknown input format. |
|
| Failed to convert. |
|
| Failed to parse request body. |
|
| Failed to retrieve required type metadata. The repository is broken. |
|
| Failed to read and parse HTDOC repository. The repository is broken. |
|
| Request has no data. |
|
| Response code is empty in the repository (tabfile is corrupt). |
|
| Response cannot be serialized because it's not of complex type. |
|
| The repository meta data does not match the actual thing. |
|
| Repository format is too old. |
|
| Duplicated error metadata. |
|
| REST Error metadata has not been found in the repository. |
|
| Expected Record but found Array or the other way around. |
|
| Found connection without id when parsing REST Connections repository. |
|
| Found more than one connection with id. |
|
| Connection not found in repository. |
|
| Found more than one request with name. |
|
| Unknown HTTP method. |
|
| Request not found in repository. |
|
| Unknown parameter location. |
|
| Unsupported conversion. |
|
| Cannot understand "Content-Type, trying JSON format. |
|
| Skipping set output parameter because of HTTP error or metadata mismatch. |
|
| Path variable is missing. |
|
| Path variable is empty. |
|
| Multiple values provided for a non-array parameter. |
|
| Invalid repository parameter. |
|
| Duplicated definition of parameter to request. |
|
| No field in class. |
|
| Expected no body but received bytes. Response will not be parsed. |
|
| Failed to start. |
|
| Unrecognized header role. |
|
| Client does not accept any of declared response content types. |
|
| Request content type not declared as accepted by the service. |
|
| Response content type not declared as possible output for a response code. |
|
| Response Content-Type header is empty. |
|
| Empty value for declared 'content-type' element. |
|
| Empty value for declared 'accept' element. |
|
| Response Content-Type header is empty. |
Domain SAPADLM
Domain | Error Code | Description |
---|---|---|
|
| Found unexpected element for Request section. |
|
| Found unexpected element for root section. |
|
| Expected root element. |
|
| Request element is not complete. |
|
| Failed to read and parse file. |
|
| Found unexpected element for root section. |
|
| Expected root element. |
|
| Failed to read and parse file. |
|
| Connection to SAP could not be established. |
|
| An error occurred while waiting for an SAP event. |
|
| Invalid service type. |
|
| Parsing request failed. |
|
| The function name is unknown in the SARS repository. |
|
| Found unexpected element for request section. |
|
| Found unexpected element for root section. |
|
| Expected root element. |
|
| Request element is not complete. |
|
| Failed to read and parse request repository file. |
|
| Found unexpected element for TRFCCallbacks section. |
|
| Composing request failed. |
|
| Issuing callback failed. |
|
| The value for the IsTransacted element is not valid. |
|
| Handling request failed. |
|
| Authentication child element expected. |
|
| Connection to SAP could not be established. Will retry to connect and will report successful connect with info message. |
|
| Function already exists. |
|
| Failed to install transaction handles. |
|
| Failed to install generic server function. |
|
| SAP structure name is too long. |
|
| ProgramID not given. |
|
| Constructing SAP_AddOn using sapnwrfcsdk-7.20 |
|
| Failed to read and parse file. |
|
| Unknown setting for SAP. Runtime too old? |
|
| Expected root element. |
|
| Unrecognised value for setting. |
|
| The value is not valid for the PoolSize element. It must be a number and greater than 0. |
|
| Values set. |
Domain SRVLM
Domain | Error Code | Description |
---|---|---|
|
| Wrong repository version. |
|
| Starting up. |
|
| Startup done. |
|
| No system info available. |
|
| Shutting down... |
|
| Shutdown complete. |
|
| Controller startup failed. |
|
| Backend initialization failed. |
|
| No license subsystem. |
|
| Information about shutdown signals. |
|
| Found deadlock dump. |
|
| Using experimental nightly build. |
|
| Functionality ... requires xUML Runtime ... or newer. |
|
| Functionality ... is fully supported with xUML Runtime ... or newer. Some settings or options may be ignored. |
|
| The repository cannot be run with this xUML Runtime version. |
|
| Could not initialize logger. |
|
| Could not load license file. |
Domain SSILM
Domain | Error Code | Description |
---|---|---|
|
| Found unexpected element for Event section. |
|
| Found unexpected element for root section. |
|
| Expected root element. |
|
| Event element is not complete. |
|
| Failed to read and parse file. |
|
| DataItem repository is missing. |
|
| SOAP repository is missing. |
|
| Frontend repository is missing. |
Domain SSPLM
Domain | Error Code | Description |
---|---|---|
|
| The matching DIR_Attribute ist not found in the Data Item Repository. |
|
| The attribute was defined twice. |
|
| Can't find a dataitem that was referred to from SOAP type mapping. |
|
| Can't open types.tab |
|
| Can't opne dataitem.tab |
|
| A mandatory dataitem column is empty. |
|
| A mandatory types column is empty. |
|
| The position in the data item is already in use. |
|
| The given XML type is invalid. |
|
| Found unexpected element for Message section. |
|
| Found unexpected element for root section. |
|
| Expected root element. |
|
| Composer message element is not complete. |
|
| Failed to read and parse file. |
|
| Found unexpected element for Message section. |
|
| Found unexpected element for root section. |
|
| Expected root element. |
|
| Composer message element is not complete. |
|
| Failed to read and parse file. |
|
| Found unexpected element for MessageSet section. |
|
| Found unexpected element for MessageSet section. |
|
| Composer message set element is not complete. |
|
| Composer message set element is not complete. |
|
| Composer message set missing attribute startsAt for element HeaderDataItem |
|
| The matching DIR_DataItem ist not found in the Data Item Repository. |
|
| Composer found cyclic dependency between objects. |
|
| Root element must be "SOAP". |
Domain TIMADLM
Domain | Error Code | Description |
---|---|---|
|
| Event expected. |
|
| Root expected. |
|
| Event child element not expected. |
|
| Failed to read and parse file. |
|
| Launching thread failed. |
|
| Mandatory Event element missing. |
|
| Event dropped, queue is full. |
|
| Found unexpected element for Trace section. |
Domain XMLFLM
Domain | Error Code | Description |
---|---|---|
|
| Failed to open parser repository. |
|
| Failed to open composer repository. |
|
| A mandatory column is empty in the parser repository. |
|
| A mandatory column is empty in the composer repository. |
|
| Unknown request while initializing xml parser |
|
| Unknown accessor t while initializing xml parser |
|
| Unknown request while initializing xml composer |
|
| Unknown accessor t while initializing xml composer |
Domain XMLLM
Domain | Error Code | Description |
---|---|---|
|
| The native XML parser reported an error during parsing. |
|
| The native XML parser reported a warning during parsing. |
|
| The native XML parser reported a fatal error during parsing. |
|
| The native XML parser reported an XML error. |
|
| The native XML parser reported an internal parser error. |
|
| Could not open file for read. |
|
| Read error. |
|
| File is too large. |
|
| Could not stat file. |
|
| Could not get system info. |
|
| The native XML parser reported an error during parsing. |
|
| The native XML parser reported a warning during parsing. |
|
| The native XML parser reported a fatal error during parsing. |
|
| The native XML parser reported an XML error. |
|
| The native XML parser reported an internal parser error. |
|
| Can't parse empty buffer. |
|
| The matching DIR_Attribute ist not found in the Data Item Repository. |
|
| The attribute was defined twice. |
|
| Can't open request tab. |
|
| Can't open dataitem tab. |
|
| A mandatory dataitem column is empty. |
|
| A mandatory request column is empty. |
|
| The position in the data item is already in use. |
|
| Found unexpected element for Message section. |
|
| Found unexpected element for root section. |
|
| Expected root element. |
|
| Composer message element is not complete. |
|
| Failed to read and parse file. |
|
| Found unexpected element for Message section. |
|
| Found unexpected element for root section. |
|
| Expected root element. |
|
| Composer message element is not complete. |
|
| Failed to read and parse file. |
|
| Repository file uses unsupported encryption. |
|
| Failed to decrypt repository. |
|
| The matching DIR_DataItem ist not found in the Data Item Repository. |
|
| Composer found cyclic dependency between objects. |
|
| Parsing repository file. |
|
| The XML_DataItem is not found in the XML Data Item Repository. |
|
| MIME: invalid starting point for XML parser. |
|
| MTOM/XOP did not find content. |
|
| MIME: invalid value of Content-Type type parameter in root of message. Message will be parsed as SOAP with attachments. |
Related Pages: