The following tables provide a complete listing of the server C++ (VWServerException) error tuples. The tables are distinguished by the contributing interface (such as, Process Engine, Imaging Services Security, Server Application Session).
See also Java™ Exception Listings.
Error Tuple |
Description |
---|---|
213,2,300 | Internal Error -- see system log for cause of error |
213,10,500 | Could not load DLL |
213,10,504 | Could not find entry point in DLL |
213,4,550 | Write to file truncated - disk full? |
213,4,551 | File open failed |
213,1,301 | not enough available memory |
213,1,302 | memory request exceeded segment size |
213,1,303 | could not lock memory handle |
213,1,304 | Not an application |
213,1,305 | Can't watch application's memory |
213,1,306 | Can't stop watching application's memory |
213,1,307 | Can't watch global memory handle |
213,1,308 | Can't stop watching global memory handle |
213,1,309 | Can't find a procedure address |
213,1,310 | Not enough room in archiver memory buffer |
213,1,311 | Can't allocate shared memory structures. |
213,11,400 | divide by zero |
213,11,401 | square root of a negative value |
213,11,402 | underflow |
213,11,403 | overflow |
213,109,1 | Illegal service name syntax |
213,109,2 | String too long to deserialize (software version mismatch] |
213,109,3 | Bad message type received from Courier |
213,109,4 | Logon session timed out. The user should never see this error. The system should automatically re-logon the user. |
213,109,5 | RPC number is undefined |
213,109,6 | VW request made on this server, which is not a VW server |
213,109,7 | No table defined for queue/roster. If this error occurs after a new server is added to the VW service, then run transfer to fix the problem. |
213,109,8 | Queue description incomplete in all tables repository |
213,109,9 | Work performer class name not defined |
213,109,10 | No more ids available (system should retry this error). No more unique identifiers exist in memory, and the system should allocate more to recover from this error. |
213,109,11 | Work queue record is not in queue |
213,109,12 | Work queue record not locked |
213,109,13 | Work object move not completed. The system tried to move a work object from server X to server Y, but found that the work object already existed on server Y. This can occur normally for very short periods if a work object is moving from Y to X and back to Y again, and will also occur for long periods if one server of a multiple server system is restored from backups, and vwverify is not run. |
213,109,14 | Undefined field name specified |
213,109,15 | Key used in query is not an indexed field |
213,109,16 | Index name not valid for query |
213,109,17 | Can't continue this query. Queries which do adhoc sorts and queries which do not specify an index cannot be continued. Only the first 'chunk' of records may be read. Reads of additional chunks are not allowed (suggestion: see if increasing the chunk size solves your problem). |
213,109,18 | Operation not allowed at this time due to other activity. A database schema modify operation disallows this function. Database schema modify operations are transfer, remove database, reinitialize database, etc. This error is only returned to the application if an explicit request has been made to do so. By default, the VW client software will retry the failed function until the database modification is complete. |
213,109,19 | Can't open work file used to modify roster |
213,109,20 | Can't write work file used to modify roster |
213,109,21 | Can't read work file used to modify roster |
213,109,22 | Can't close work file used to modify roster |
213,109,23 | Can't change work class home server |
213,109,24 | Can't write work file used to insert into roster |
213,109,25 | Can't read work file used to insert into roster |
213,109,26 | Can't close work file used to insert into roster |
213,109,27 | Can't open work file used to insert into roster |
213,109,28 | Can't create work file used to insert into roster |
213,109,31 | vwtran program started with invalid parameters |
213,109,32 | Fatal VW Error -- see system error log |
213,109,33 | Too many work objects have been input to injectWorkObjects |
213,109,34 | Undefined class name specified |
213,109,35 | Work or Work Performer class not on this server. Note that this error is retried by the VW client software and is never seen by the applications. |
213,109,36 | Region has not been initialized (run transfer) |
213,109,37 | Class name not suffixed with '(<ServerId>)' to indicate server |
213,109,38 | Database reinitialized--all programs must log off and then log on again. The Visual WorkFlo database has been reinitialized. All programs on each computer must log off, and then log on again, because the work classes, work performer classes, etc. have all been deleted, and potentially new ones have been created. |
213,109,39 | Work queue record locked--requested operation not allowed |
213,109,40 | Invalid syntax for preselection rule |
213,109,41 | Invalid field type |
213,109,43 | No work station record found |
213,109,44 | Work queue record changed since operation started |
213,109,45 | Starting location can't be specified on query with adhoc sort |
213,109,46 | Attempt made to log message with invalid log message type |
213,109,47 | No workspace exists in region (transfer not run) |
213,109,48 | Can't initialize DB while other VW programs up on this station. Other programs can't be running on the client work station when the database is initialized. |
213,109,49 | Undefined work performer operation |
213,109,50 | Configuration error: same physical server used multiple times |
213,109,51 | No local VW Service or VW Server defined |
213,109,52 | Duplicate index name detected |
213,109,53 | Duplicate field name detected |
213,109,54 | VW tool command aborted |
213,109,55 | Invalid ascii string for a work object number |
213,109,56 | Invalid ascii string for a float |
213,109,57 | Invalid ascii string for an integer |
213,109,58 | No more view ids available |
213,109,59 | Authored repository empty (run 'save to repository' in Composer) |
213,109,60 | Create GUID failed. UuidCreate failed. |
213,109,61 | Can't lock objects on query if client side sort required. A work object can't be locked on the query if the an adhoc sort rule or a sort rule with a work performer variable (variable beginning with a '$') is used. |
213,109,62 | Region not initialized |
213,109,63 | Multiple users cannot logon with the same machine ID. All processes using the same machine ID must log on to FileNet Security Services as the same user. Either change the user, or allocate a new machine ID by specifying a different work station name. |
213,109,64 | vwclean program started with invalid parameters. Note that the vwclean program is a daemon and should not be run from the command line. |
213,109,65 | Request to modify database schema failed. Transfer, clean repository, reinitialize database, etc. is not allowed at this time. Check 'schemastatus' with 'vwtool'. If other operation active, wait for it to finish. If nothing active, recycle server and client software and try again (report need to recycle software to FileNet, this step should not be required). |
213,109,66 | Invalid entry rule |
213,109,67 | Entry rule validation failed |
213,109,68 | Security attributes disallow access |
213,109,69 | Logon attempted to Visual WorkFlo with invalid service name. An attempt was made to log on to Visual WorkFlo with a service name which was not a Visual WorkFlo service. |
213,109,70 | VW software version incompatible with database version. The version of the data in the database is not compatible with the version of the software. This error happens when new software is installed over a Beta software release, and the new software does not support the old database format, and no conversion program is available. The database must be reinitialized with the old VW software and the database must be removed, then the new VW software must be reinstalled. |
213,109,71 | VW server and client RPC protocol mismatch. The RPC protocol used between the VW client and server are not the same version. Either the VW client or the VW server software must be reinstalled with a new version. |
213,109,72 | Locking instruction invocations illegal for system queues. Calling an API locks a work object and returns the inputs and outputs to an operation is illegal when the queue is a system queue (Delay(n) and instructionSheetInterpreter(n)), because system operations (assign, branch, wait for event) do not have inputs and outputs. |
213,109,73 | Illegal query using work object number as the index. Only equality queries may be done on the work object number field. |
213,109,74 | Can't recover all users on this machine id. Logins which do not get machine ids assigned (such as internet logins) get assigned a special machine id. This machine id can't be recovered for all users of this machine id. Instead, the user id must be specified in addition to this machine id, and all work objects for the given combination of machine id & user id are recovered. |
213,109,75 | Visual WorkFlo informational message. See system log text for message contents |
213,109,76 | Servers added and deleted since last time VW server run. A server has been added and another deleted since the last time VW server software was loaded. You may not run fn_edit and both add and delete servers at the same time. You must run fn_edit twice, once to add servers, and another time to delete servers, with VW software being loaded in between these two changes to let VW update the databases. |
213,109,77 | Not logged on to VW |
213,109,78 | Transfer failed due to errors in input data The Work or Work Performer class descriptions had errors that prevented transfer from completing. |
213,109,79 | Lock work object failed: Work object not found |
213,109,80 | Lock work object failed: Work object changed since initially read A program read a work object, then tried to use this copy of the work object to lock it. But the work object had been changed since it was initially read. |
213,109,81 | Lock work object failed: Work object already locked |
213,109,82 | Lock work object failed: Can't override system lock on work object An attempt was made to override the lock on a work object, but that attempt has been disallowed because the work object is locked by the system, and system locks cannot be overridden. |
213,109,83 | Minimum index value must be specified When doing a query by the Work Object Number index, the minimum value of the index must be specified. |
213,109,84 | Maximum index value must be specified When doing a query by the Work Object Number index, the maximum value of the index must be specified. |
213,109,85 | Index values equal to the minimum must be specified When doing a query by the Work Object Number index, the query specification must include values equal to the minimum index value. |
213,109,86 | Index values equal to the maximum must be specified When doing a query by the Work Object Number index, the query specification must include values equal to the maximum index value. |
213,109,87 | The minimum value of the index must have one component When doing a query by the Work Object Number index, the number of components in the minimum value of the index must be 1. |
213,109,88 | The maximum value of the index must have one component When doing a query by the Work Object Number index, the number of components in the maximum value of the index must be 1. |
213,109,89 | The minimum value of the index must be a string or a work object number When doing a query by the Work Object Number index, the type of the minimum value of the index must be either a string that contains an ascii Work Object Number, or a binary Work Object Number. |
213,109,90 | The maximum value of the index must be the same type as the minimum When doing a query by the Work Object Number index, the type of the minimum value of the index must equal the type of the maximum value of the index. |
213,109,91 | The maximum and minimum values of the index must be the same When doing a query by the Work Object Number index, only one work object may be queried for at a time, thus the minimum and maximum values of the index must be the same. |
213,109,92 | The work space time stamp is stale The work space has been updated by transfer, so the client workstation needs to load new workspaces and a new time stamp. |
213,109,93 | Wrong object ID for workspace given when running transfer The object ID for the workspace given to transfer must be for the runtime form of a workspace. |
213,109,94 | This function is not allowed on an aggregate queue/roster |
213,109,95 | The aggregate roster or queue name is a duplicate Can't have an aggregate roster name which is the same as an aggregate queue name, or vice versa. |
213,109,96 | No event log exists for the specified event log name |
213,109,97 | An invalid substitution variable has been used in an SQL expression |
213,109,98 | Attempt to update too many environment fields records in one call |
213,109,99 | Attempt to update too many stored query records in one call |
213,109,100 | Invalid Instruction Sheet Name |
213,109,101 | Invalid WorkClass Name |
213,109,102 | Invalid Expression |
213,109,103 | Invalid Type |
213,109,104 | Empty Argument |
213,109,105 | Invalid operator |
213,109,106 | Infinite Loop Detected |
213,109,107 | All work classes in WaitForEvent must have the same home server |
213,109,108 | WaitForEvent, Waitee WorkClass specified does not have WorkObject Tag Id |
213,109,109 | Step, Invalid number of parameter for the queue operation |
213,109,110 | Invalid sub-process (launch step may have responses) |
213,109,111 | Invalid Step Processor name |
213,109,112 | Invalid Milestone Name |
213,109,113 | Invalid RuleSet Name |
213,109,114 | Missing myPortType |
213,109,115 | Missing partnerPortType |
213,109,116 | Invalid mixture of Message schema with Step parameters |
213,109,117 | Invalid Web Services message type |
213,109,118 | Invalid Invoke response (work object not found) |
213,109,119 | Missing correlation set on receive instruction |
213,109,120 | Missing Timeout map or expression (Timeout must have a map and an expression) |
213,109,121 | Missing or invalid PartnerLink® |
213,109,122 | Received an unhandled fault in an Invoke |
213,109,123 | Invalid Parameters sequence |
213,109,124 | Invalid Parameters Lexicographical level |
213,109,125 | Missing Schema or Element in Advance Receive |
213,109,126 | Unable to Correlate received Message |
213,109,127 | Invalid schema or schema file name |
213,109,128 | Version Agnostic must have partner links |
213,109,129 | Can't change from agnostic to non-agnostic |
213,109,130 | Missing version agnostic Operation |
213,109,131 | Missing version agnostic Receive |
213,109,132 | Missing version agnostic Reply |
213,109,133 | Invalid web service operation either missing receive or missing message reply |
213,109,134 | Extra reply in version agnostic interface |
213,109,135 | Change on a version agnostic fault interface |
213,109,136 | Incompatible reply with other reply for same operation or version agnostic reply |
213,109,137 | Incompatible receive with other receive for same operation or version agnostic receive |
213,109,149 | Attempt to update too many step processor records in one call |
213,109,150 | Can't switch record type in middle of a query When using stored queries, can't change the record type being read in the middle of a query. |
213,109,151 | Stored query is stale The stored query has changed since it was cached. The client stub software should refresh after this error and continue. |
213,109,152 | Invalid syntax in substitution function |
213,109,153 | Must get the instruction parameters When using a stored query in sequenced mode, only the instruction parameters may be fetched. Work objects and queue records may not be read using this query type. |
213,109,154 | Can't do explicit update of system work object fields A user can't set the system fields of a work object with an assignment statement. |
213,109,155 | Event log to inherit from is undefined An event log definition defines a derived from log, but the derived from log does not exist or has not been transferred. |
213,109,156 | F_DefaultServerId in the user environment must be an integer |
213,109,157 | This API may not be used to query this queue The BRM... APIs can't be used to query user centric queues |
213,109,158 | Invalid server id |
213,109,159 | A roster name may not be the same as a queue name |
213,109,160 | A queue name may not be the same as a roster or workclass (workflow definition) name |
213,109,161 | Can't upgrade VW software while transfer is in progress New VW software has been installed, and this software tried to auto-upgrade the database but failed because transfer was in progress. A message in the system log will indicate the region on which transfer was running. Please reinstall the prior version of VW software and complete the transfer operation, and logon to VW through any VW application to cause transfer to finish. Then reinstall the new VW software. |
213,109,162 | A string is longer than the maximum allowed blob size |
213,109,163 | Partial validation not allowed on work performer class transfer |
213,109,164 | Too many objects, retry the RPC with less objects |
213,109,165 | Index field types don't match. |
213,109,166 | SQ_* queue can only be transferred by a user with r/w permission for it. |
213,109,167 | Duplicate step processor name detected. |
213,109,168 | Access Violation. |
213,109,169 | Generic Malfunction. |
213,109,170 | Work Object Creation failure. |
213,109,171 | Queue assertion failure. |
213,109,172 | User Defined Exception. |
213,109,173 | Invalid or Lost database connection. |
213,109,174 | Retry last DB transaction. |
213,109,190 | Unable to send rules message |
213,109,191 | Unable to receive rules message |
213,109,192 | Invalid rules message |
213,109,200 | Invalid Instruction Sheet Id |
213,109,201 | Invalid Split Instruction |
213,109,202 | Timer mismatch (server time changed, or internal error) |
213,109,203 | RollBackCheckPoint without a BeginCheckPoint |
213,109,204 | Invalid operation within sequenced mode |
213,109,205 | Exceeded ISI Limit within sequenced mode |
213,109,206 | Rollback to sequenced mode from out sequenced mode |
213,109,207 | Unable to start sequenced mode |
213,109,208 | Workobject already terminating, unable to skip to terminate |
213,109,209 | WorkObject Operation is not valid in this context. WorkObjectOperation is only valid when an instruction sheet interpreter 'update' function is called. In other words, when a WobUpdateUnlocked happen. In any other case, this exception is thrown. |
213,109,210 | Destination queue is not a user centric queue This operation expects a user centric queue as the destination queue. |
213,109,211 | The user name is invalid or NULL |
213,109,212 | Invalid or null response |
213,109,213 | Reassignment not allow for this step |
213,109,214 | Work Object seems to be looping |
213,109,215 | Parent cannot be advanced because of children references |
213,109,216 | invalid branch routing |
213,109,217 | invalid while routing |
213,109,218 | Can't find the stored procedure database logon information created by vwtool's dbconfig command |
213,109,219 | Can't use the stored procedure database logon information created by vwtool's dbconfig command (too big) |
213,109,220 | Database Stored Procedure call: invalid logon or connection |
213,109,221 | Invalid or unknown database stored procedure name |
213,109,222 | Invalid parameter for database stored procedure call |
213,109,223 | Invalid parameter bind for database stored procedure call |
213,109,224 | Error calling database stored procedure |
213,109,225 | Too many (more than 1024) stored procedure parameters are specified |
213,109,226 | Database stored procedure call attempted to set a parameter value to null |
213,109,250 | Invalid object ID for persistent VW object |
213,109,251 | Object service busy on client. Shutdown all programs and try again The Object Service on the client has structures in memory which cannot be deleted. Recycle the software on the client and retry the initialize operation. |
213,109,252 | No object found for specified object id |
213,109,253 | Object service busy on server. Shutdown all programs and try again The Object Service on the server has structures in memory which cannot be deleted. Recycle software on the server and retry the initialize operation. |
213,109,254 | Attempt to update too many isolated region attributes in one call |
213,20,350 | You are not logged on. Please log on to the system first. |
213,20,351 | Missing or invalid INI file entry in Security section. |
213,20,352 | You are not logged into the server referenced in your vw.ini file. |
213,20,353 | Your VW.INI file was not found or it does not exist. |
213,20,354 | This machine is already logged on to the server as a different user. |
213,20,355 | Logon failed: The username is not valid for the requested server. |
213,20,356 | Logon failed: The password is not correct. |
213,20,357 | Logon failed: The requested server may be down. |
213,20,358 | Logon failed: You do not have the proper security to run this application. |
213,20,359 | There was an error when attempting to logon. |
213,20,360 | Deserialize failed: An unrecognized security mode is sent from client to server. |
213,20,361 | Unsupported security mode mismatch: LDAP security on client - IMS security on server. |
213,20,362 | Invalid Server: Operation can only be run at server 0. |
213,20,363 | User must have a password to logon. |
213,20,364 | Detect duplicate short name for user or group. |
213,20,365 | LDAP is not configured yet. |
213,20,366 | Invalid LDAP certificate path, see syslog for details. |
213,20,367 | Fail to initialize LDAP connection, see syslog for details. |
213,20,368 | Fail to save LDAP configuration. |
213,20,369 | No name is found for user id. |
213,20,370 | API does not support this parameter. |
213,20,371 | Fail to convert string to UTF8 format. |
213,20,372 | Invalid DNS name (eng.filenet): null. |
213,20,373 | Invalid DNS name (eng.filenet): empty str. |
213,20,374 | Invalid DNS name (eng.filenet): ends with dot. |
213,20,375 | Domain mismatch. |
213,20,376 | Bad Domain. |
213,20,377 | Fail to get SysAdminG mapped name. |
213,20,378 | Must specify full distinguished name, see syslog for details. |
213,20,379 | Fail to get SysConfigG mapped name. |
213,20,380 | DN extracted from returned LDAP record is NULL. |
213,20,381 | Invalid LDAP display or persist attribute. See syslog for details. |
213,20,382 | Domain is not in the supported list. See syslog for details. |
213,20,383 | Fail to parse SID. See syslog for details. |
213,20,384 | @SYS is an invalid user (string is reserved for internal operation). |
213,20,385 | The security back end does not support this operation. |
213,60,1001 | The Class Description Language stream specified is empty |
213,60,1002 | Expecting an opening brace |
213,60,1003 | Expecting a closing brace |
213,60,1004 | Expecting an opening bracket |
213,60,1005 | Expecting a closing bracket |
213,60,1006 | Expecting an opening parenthesis |
213,60,1007 | Expecting a closing parenthesis |
213,60,1008 | Expecting WorkClass or WorkPerformerClass keyword |
213,60,1009 | Invalid type name |
213,60,1010 | Expecting the CreateInstance keyword |
213,60,1011 | Invalid instruction sheet name |
213,60,1012 | Expecting the Properties keyword |
213,60,1013 | Expecting the PropertyName keyword |
213,60,1014 | Expecting the Choice keyword |
213,60,1015 | Expecting the Child keyword |
213,60,1016 | Expecting the TimeOut keyword |
213,60,1017 | Expecting the ResultingEventRowNumber keyword |
213,60,1018 | Expecting the WorkClass keyword |
213,60,1019 | Expecting the Operator keyword |
213,60,1020 | Expecting the Idvalue keyword |
213,60,1021 | Expecting the FieldToAssign keyword |
213,60,1022 | Expecting the Expression keyword |
213,60,1023 | Expecting the ShowNames keyword |
213,60,1024 | Expecting the IgnoreBindings keyword |
213,60,1025 | Expecting the Prompt keyword |
213,60,1026 | Expecting the Type keyword |
213,60,1027 | Expecting the Direction keyword |
213,60,1028 | Invalid value for direction |
213,60,1029 | Expecting the Length keyword |
213,60,1030 | Expecting an invert value (inverted/non_inverted) |
213,60,1031 | Expecting a float number |
213,60,1032 | Expecting a number |
213,60,1033 | Expecting a boolean (TRUE/FALSE) value |
213,60,1034 | Expecting an identifier |
213,60,1035 | Expecting an expression or string literal |
213,60,1036 | Expecting a comma |
213,60,1037 | Expecting a colon |
213,60,1038 | Expecting a semicolon |
213,60,1039 | Expecting an equal sign |
213,60,1040 | Unable to find the specified parent class |
213,60,1041 | Bad syntax in field initial value |
213,60,1042 | Unknown class type |
213,60,1043 | Unable to load the specified bitmap file |
213,60,1044 | Invalid class name |
213,60,1045 | Invalid field name |
213,60,1046 | Invalid operator |
213,60,1047 | Bitmaps cannot be read in the server |
213,60,1048 | Expecting number greater than zero |
213,60,1049 | Can't make arrays exposed fields |
213,60,1050 | Unexpected identifier |
213,60,1051 | Duplicate aggregate queue or roster name |
213,60,1052 | Expecting queue name |
213,60,1053 | Expecting keyword 'Component' |
213,60,1054 | Expecting a valid type value |
213,60,1055 | Expecting a step property keyword |
213,60,1056 | Expecting a step Parameter property keyword |
213,60,1057 | Expecting the TO keyword |
213,60,1058 | Milestone index must be in the correct sequence (start from 0 to n) |
213,60,1059 | Expecting a semicolon or a dot |
213,60,1060 | Expecting the Name |
213,60,1061 | Expecting the URL keyword |
213,60,1062 | Expecting the Height keyword |
213,60,1063 | Expecting the Width keyword |
213,60,1064 | Expecting PartnerLink Entity Keyword |
213,60,1065 | Expecting Fault Keyword |
213,60,1066 | Expecting an Invoke property keyword |
213,60,1067 | Expecting Output Keyword |
213,60,1068 | Expecting an Receive property keyword |
213,60,1069 | Expecting an Reply property keyword |
213,60,1070 | Expecting an From property keyword |
213,60,1071 | Expecting an Query property keyword |
213,60,1072 | Expecting an Propery property keyword |
213,46,2001 | invalid data types for operand(s) |
213,46,2002 | syntax error |
213,46,2003 | parser stack overflow |
213,46,2004 | bad space for scanner |
213,46,2005 | no space for scanner |
213,46,2006 | unknown compilation error |
213,46,2007 | token too large |
213,46,2008 | push-back buffer overflow |
213,46,2009 | not a record data type |
213,46,2010 | undeclared field of object (e.g. WorkObject) |
213,46,2011 | undeclared field of alternate object (e.g. WorkPerformer) |
213,46,2012 | unknown data type |
213,46,2013 | identifier must only contain alphanumeric characters or underscores |
213,46,2014 | identifier is too long |
213,46,2015 | cannot start identifier with f_ or F_ |
213,46,2016 | first character of identifier must be alphabetic |
213,45,1001 | invalid data type for operation |
213,45,1002 | invalid op-code encountered |
213,45,1003 | expression stack unexpectedly has too few items |
213,45,1004 | expression evaluation resulted in invalid stack contents |
213,45,1005 | division by zero |
213,45,1006 | attempted to use string index/length outside of string |
213,45,1007 | second and third arguments to translate function must be same length |
213,45,1008 | second argument to WorkFlo substitute function must not be empty |
213,45,1009 | argument to hex function must be even length and contain all hex digits |
213,45,1010 | invalid data type for null function |
213,45,1011 | invalid conversion data type(s) |
213,45,1012 | invalid conversion value |
213,45,1013 | unknown object type encountered |
213,45,1014 | op-code not yet implemented |
213,45,1015 | value out of range |
213,45,1016 | unknown field of object (e.g. WorkObject) |
213,45,1017 | unknown field name |
213,45,1018 | subscript out of range |
213,45,1019 | invalid operation on null value |
213,45,1020 | cannot convert value to string |
213,45,1021 | unknown field of alternate object (e.g. WorkPerformer) |
213,45,1022 | This expression may only be evaluated on the server Expressions which contain functions which retrieve information from the environment may only be executed on the server, and may not be executed on the client workstation. |
213,45,1023 | Invalid XML Schema or Schema File Name |
213,45,1024 | Invalid XML Style Sheet or Style Sheet File Name |
213,77,2001 | VWApiClient: Unknown error |
213,77,2002 | VWApiClient: Unable to convert string |
213,77,2003 | VWApiClient: Unsupported data type |
213,77,2004 | VWApiClient: Invalid variant argument |
213,77,2005 | VWApiClient: Bad array boundary |
213,77,2006 | VWApiClient: Unable to lock array |
213,77,2007 | VWApiClient: Unable to unlock array |
213,77,2008 | VWApiClient: Unable to access array element |
213,77,2009 | VWApiClient: Unable to create array |
213,77,2010 | VWApiClient: Unable to initialize Visual WorkFlo API Server |
213,76,1001 | VWApiSrv: Unknown error |
213,76,1002 | VWApiSrv: Unable to convert string |
213,76,1003 | VWApiSrv: Invalid variant argument |
213,76,1004 | VWApiSrv: Invalid sort Rule count |
213,76,1005 | VWApiSrv: Bad array boundary |
213,76,1006 | VWApiSrv: Wrong array size |
213,76,1007 | VWApiSrv: Unable to access array element |
213,76,1008 | VWApiSrv: Unsupported data type |
213,76,1009 | VWApiSrv: Unable to create array |
213,76,1010 | VWApiSrv: Unable to lock array |
213,76,1011 | VWApiSrv: Unable to unlock array |
213,76,1012 | VWApiSrv: Unable to reset variant |
213,76,1013 | VWApiSrv: Unable to destroy array |
213,75,1 | Unknown error |
213,75,2 | Invalid Work Class name |
213,75,3 | Invalid Work Object Id |
213,75,4 | Invalid Work Object field name |
213,75,5 | Invalid Context Id |
213,75,6 | Field type mismatch |
213,75,7 | Invalid Work Performer Id |
213,75,8 | Invalid Browse Id |
213,75,9 | Browse has been exhausted |
213,75,10 | Invalid Lock Id |
213,75,11 | Cannot get an 'Out' parameter |
213,75,12 | Cannot set an 'In' parameter |
213,75,13 | Object type mismatch |
213,75,14 | Invalid parameter name |
213,75,15 | Incorrect parameter type |
213,75,16 | Invalid Id |
213,75,17 | Cannot set the Work Queue fields |
213,75,18 | Invalid Work Performer class name |
213,75,19 | Insufficient security rights |
213,75,20 | Out of memory |
213,75,21 | Cannot lock memory handle |
213,75,22 | Cannot Log the message |
213,75,23 | Cannot Lock the Work Object |
213,75,24 | All Active Work Performers Deactivated - ReportToWork not allowed |
213,75,25 | Active Work Performer Deactivated - LockWorkObject not allowed |
213,75,26 | Removal of an busy Active Work Performer not allowed |
213,75,27 | Visual WorkFlo/Performer not responding - ReportToWork not allowed |
213,75,28 | Unable to establish DDE connection with Visual WorkFlo/Performer - ReportToWork not allowed |
213,75,29 | Unsupported field type |
213,75,30 | Exception already raised for Work Object |
213,75,31 | Exception undefined for Work Object class |
213,75,32 | Illegal raising of a Work Object exception |
213,75,33 | Currently no exception for Work Object |
213,75,34 | The specified bit position is not supported by LogMessage() |
213,75,35 | Invalid Work Queue field name |
213,75,36 | Invalid Logon Id |
213,75,37 | User Access Denied |
213,75,38 | Insufficient user rights on class |
213,75,39 | Invalid Work Queue Id |
213,75,40 | FPNumbers not supported by Work Object Queries |
213,75,41 | Invalid Work Object Query Session Id |
213,75,42 | Work Object Query value not set |
213,75,43 | Work Object Query has not been executed. |
213,75,44 | Work Object Query index is out of range. |
213,75,45 | Work Object Query index is no longer valid. |
213,75,46 | Invalid Browse Modifier handle. |
213,75,47 | The versions of the API are incompatible. |
213,75,48 | Illegal API call for Passive WorkPerformers |
213,75,49 | Invalid Work Object Access Handle |
213,75,50 | Unable to set field. The Work Object is not locked |
213,75,51 | The Work Object is already locked |
213,75,52 | The Work Object Access Handle was not set to allow saving |
213,75,53 | Invalid handle type |
213,75,54 | Invalid class name |
213,75,55 | Unlock of WorkObject failed |
213,75,56 | Cannot find WorkObject |
213,75,57 | Invalid instruction sheet name passed in. |
213,75,58 | Cannot call the Workflow instruction sheet. |
213,75,59 | Cannot call the Terminate instruction sheet. |
213,75,60 | All the objects have been read in. |
213,75,61 | There were no objects that met the specified query. |
213,75,62 | The option to lock the work objects returned from the queue query was set. |
213,75,63 | The option to lock the work objects returned from the queue query was not set. |
213,75,64 | Undefined class name specified |
213,75,65 | The work object must be locked to perform this operation. |
213,75,66 | The work object has been modified since browsing. |
213,75,67 | The work object has been modified since executing the query. |
213,75,68 | This process is already logged on to the system as a different user. |
213,75,69 | The user name does not exist on this system. |
213,75,70 | There was an error when attempting to logon. |
213,75,71 | Invalid Operation name passed in. |
213,75,72 | Invalid Class name ID passed in. |
213,75,73 | Invalid Operation name ID passed in. |
213,75,74 | Invalid User name ID passed in. |
213,75,75 | Invalid transfer type passed in. |
213,75,76 | Invalid CDL file name passed in. |
213,75,77 | Invalid Instruction Id passed in. |
213,75,78 | Cannot set system fields |
213,36,13 | Runtime class was not found |
213,36,42 | Can't load authoring repository |
213,36,41 | Can't load online repository |
213,36,14 | Instruction Sheet has missing Authored Workorder Ids |
213,36,15 | Instruction Sheet has duplicate Authored Workorder Ids |
213,36,16 | No Initialized Repository. Save Failed. |
213,36,17 | Workspace replaced since edit begun. Save cancelled, no changes saved. |
213,36,18 | Super class not found. Save cancelled, no changes saved. |
213,36,19 | Class has been subclassed, can't delete. |
213,36,20 | Cannot create file |
213,36,21 | Save file failed. |
213,36,22 | Super class is unknown for child class A work class or work performer class is derived from another class which does not exist in the list of class definitions. |
213,36,23 | Class not in database. (deleted since program load?) |
213,36,24 | Your .s image file's version does not match the system's version, can't load. |
213,36,25 | Work Performer was not found. |
213,36,101 | Step: Invalid Queue Name. |
213,36,102 | Step: Invalid Requested Interface. |
213,36,103 | Step: Invalid Deadline. |
213,36,104 | Step: Invalid Reminder. |
213,36,105 | Step: Invalid Participant. |
213,36,106 | Step: Invalid Response. |
213,36,107 | Step: Invalid Field Parameter. |
213,36,108 | Step: Invalid Field Parameter Type. |
213,36,109 | Step: Invalid Route Condition. |
213,36,110 | Step: Invalid Next Step Id in Route. |
213,36,111 | Step: Invalid Queue type and Participant combination. |
213,36,112 | Step: Invalid split/Join pairing. |
213,36,113 | Step: Invalid Route Release. |
213,56,564 | Invalid WorkObject Exception |
213,56,565 | Primitive InstructionSheet Not Found |
213,56,566 | Undefined WorkObject exception |
213,56,567 | Illegal WorkObject exception |
213,65,0 | internal use only - should not be seen |
213,65,7 | unknown roster specified |
213,65,8 | unknown queue specified |
213,65,9 | work object expected in queue, not found |
213,65,1000 | fatal error encountered |
213,65,1002 | program argument requires parameter |
213,65,1003 | unknown option |
213,65,1004 | expecting option specifier ('-') |
213,65,1005 | conflicting arguments |
213,65,1006 | no online configuration found - transfer not run(?) |
213,65,1009 | internal error - bad record type parameter |
213,65,1010 | invalid op code in formatRecord |
213,65,1011 | no pointer to op code in inputRecord |
213,65,1012 | unknown op code in record read by inputRecord |
213,65,1013 | no separator following type in input record |
213,65,1014 | invalid work class id number in input record |
213,65,1015 | invalid server id number in input record |
213,65,1016 | invalid tag type in input record |
213,65,1017 | new line expected at end of input record line |
213,65,1018 | sorted file different size from original |
213,65,1019 | work object has more than one highest unique id |
213,65,1020 | invalid op code in function Analyze |
213,65,1021 | invalid op code in function FixupDB |
213,65,1022 | requested queue or roster not found in database |
213,65,1023 | wrong record type - action = create |
213,65,1024 | wrong record type - action = delete |
213,65,1025 | wrong record type - action = update |
213,65,1026 | hex value for test option expected |
213,65,1027 | internal error - Q record wobnum != R record wobnum |
213,65,1028 | workspace referenced by work object does not exist |
213,65,1029 | region number expected |
213,65,1030 | must be member of SysAdmin group to read all records |
Error Tuple |
Description |
---|---|
202,200,1 | The fnc_abort function was called. There should be a core file in the /fnsw/local/tmp directory. |
202,200,2 | A signal which causes a server process to terminate with a core file has been detected. Look in the elog for more information. In addition, a core file may be examined. The core file should reside in /fnsw/local/tmp/core. |
202,0,1 | An invalid argument was passed to a SysV entry point. |
202,0,2 | The number of bytes requested from getarea were not available. |
202,0,3 | An unknown error was returned from malloc. See error log for errno. |
202,0,4 | The code version of the abstract does not match that of its client. This error will occur when a client program has not been relinked after the code in the abstract has changed on systems not using dynamically linked shared libraries. |
202,0,5 | The size of shared memory requested from getgloarea is too big. See error log for size restrictions. |
202,0,6 | The software limit of allotted shared memory segments has been exceeded. The software will need to be cycled (stopped and restarted) in order to get around this situation. Please contact your service representative when this situation occurs. |
202,0,7 | There is no shared memory available for the current process. The software will need to be cycled (stopped and restarted) in order to get around this situation. Please contact your service representative when this situation occurs. |
202,0,8 | An abstract or program has attempted to return shared memory originally allocated by another abstract. |
202,0,9 | Program error. A segmentation violation has been detected in this process. Check the error log file for a message indicating where the core file was created. Note that core files are not created on NT. If a core file exists, make sure it has a unique name so that it will not be overwritten by any future core files. Copy it to core.XXXXXX where XXXXXX represents the process id recorded in the error log, and contact your support representative. |
202,0,10 | An invalid size parameter was passed to shmget when attempting to allocate a shared memory segment. |
202,0,11 | The permissions requested by the process for the shared memory segment could not be granted by the system. |
202,0,12 | The maximum number of allowed shared memory identifiers has been exceeded. |
202,0,13 | The amount of available shared memory is not sufficient for the request. |
202,0,14 | An unknown error was returned from shmget. See error log for errno. |
202,0,15 | An invalid argument (probably the address) was passed to shmat. |
202,0,16 | The requested operating permissions were denied for the process. |
202,0,17 | The available data space was not large enough to accommodate the shared memory segment. |
202,0,18 | The number of shared memory segments mapped to the calling process would exceed the system-imposed limit. |
202,0,19 | An unknown error was returned from shmat. See error log for errno. |
202,0,20 | An unknown IPC key was passed to sysv_get_key. |
202,0,21 | The system paging space is too low, and processes may be killed until enough paging space exists to meet the current request. It is suggested that the paging space be monitored (using 'lsps -a') and adjusted to address the needs of the software. |
202,0,22 | The shared memory overhead structure has some inconsistencies. Refer to the error log file. Typically, ipc_tool/wal_ipc is inconsistent with the SysV libraries. |
202,0,23 | Invalid shm_handle. |
202,0,24 | shmat/shmdt/shmctl system error. Refer to log. |
202,0,25 | (This message tuple is not currently in use) |
202,0,26 | The Shared Memory Manager segment does not exist |
202,0,27 | Not an error. This tuple is used for tracing. |
202,0,28 | sigstack system error. Refer to error log and logged errno. |
202,0,29 | Is not a shared memory address. |
202,0,30 | Memory corruption detected refer to error log. |
202,0,31 | System realloc error. Refer to error log for errno. |
202,0,32 | This error tuple is unused and available. |
202,0,33 | Signal SIGQUIT was received. There should be a core file. |
202,0,34 | Signal SIGILL was received. There should be a core file. |
202,0,35 | Signal SIGTRAP was received. There should be a core file. |
202,0,36 | Signal SIGEMT was received. There should be a core file. |
202,0,37 | Signal SIGFPE was received. There should be a core file. |
202,0,38 | Signal SIGBUS was received. There should be a core file. |
202,0,39 | Signal SIGSYS was received. There should be a core file. |
202,0,40 | Signal SIGXCPU was received. There should be a core file. |
202,0,41 | Signal SIGXFSZ was received. There should be a core file. |
202,0,42 | Signal SIGDANGER was received. There should be a core file. |
202,0,43 | An unknown signal was received. |
202,0,44 | The entry point called has been deimplemented. |
202,0,45 | Bad magic number in the head memory link of area in Local Memory Context |
202,0,46 | Bad magic number in the tail memory link of area in Local Memory Context |
202,0,47 | fnc_getarea_lcm passed negative or zero number of bytes for area size |
202,0,48 | Zero parameter passed instead of a pointer to a pointer |
202,0,49 | Value of pointer to a pointer was illegally zero |
202,0,50 | Pointer parameter value not a multiple of 4 |
202,0,51 | Local Memory Context links are corrupt |
202,0,2001 | Failed to find the binary for a FileNET abstract (DLL) |
202,0,2002 | Abstract entry point not found while linking an abstract |
202,0,2003 | Abstract initialization function not found while linking an abstract |
202,0,2004 | SHM DLL was not able to allocate process globals correctly |
202,0,2005 | An error occurred attempting to open a shared file mapping object |
202,1,1 | An error was encountered in the semctl(2) call returning the error number (errno) logged in the system error log. |
202,1,2 | The software limit of allotted interlocks has been exceeded. The software will need to be cycled (stopped and restarted) in order to get around this situation. Please contact your service representative when this situation occurs. |
202,1,3 | An illegal interlock value has been encountered. This is either a program bug or a side-effect from a previous error. Please check the error log for more information. |
202,1,4 | A claim on an application interlock was unsuccessful. The semop(2) call failed returning the error number (errno) logged in the system error log. |
202,1,5 | The release of an application interlock was unsuccessful. The semop(2) call failed returning the error number (errno) logged in the system error log. |
202,1,6 | A reset_event on an interlock was unsuccessful. The semop(2) call failed returning the error number (errno) logged in the system error log. |
202,1,7 | A claim on a system interlock was unsuccessful. The semop(2) call failed returning the error number (errno) logged in the system error log. |
202,1,8 | The release of a system interlock was unsuccessful. The semop(2) call failed returning the error number (errno) logged in the system error log. |
202,1,9 | The software has run out of semaphore sets based on software imposed limits. The software will need to be cycled (stopped and restarted) in order to get around this situation. Please contact your service representative when this situation occurs. |
202,1,10 | The system is running out of interlocks based on system imposed limits. The software will need to be cycled (stopped and restarted) in order to get around this situation. Please contact your service representative when this situation occurs. |
202,1,11 | An error occurred while attempting to create a new semaphore set. The semget(2) call failed returning the error number (errno) logged in the system error log. |
202,1,12 | A waitshare on an interlock was unsuccessful. The semop(2) call failed returning the error number (errno) logged in the system error log. |
202,1,13 | A timeout or interrupt occurred while attempting to claim an interlock. |
202,1,14 | Semaphore key has wrapped around |
202,1,2001 | An error occurred attempting to open a system mutex object |
202,1,2002 | An error occurred attempting to create a system mutex object |
202,1,2003 | An error occurred attempting to claim a system mutex object |
202,1,2004 | An error occurred attempting to release a system mutex object |
202,1,2005 | An error occurred attempting to open a process event object |
202,1,2006 | An error occurred attempting to create a process event object |
202,1,2007 | An error occurred attempting to claim a process event object |
202,1,2008 | An error occurred attempting to free a process event object |
202,1,2009 | An error occurred attempting to open a process event object |
202,1,2010 | An error occurred attempting to create a semaphore object |
202,1,2011 | An error occurred attempting to open a semaphore object |
202,1,2012 | An error occurred attempting to claim a semaphore object |
202,1,2013 | An error occurred attempting to release a semaphore object |
202,1,2014 | An error occurred attempting to close a semaphore object |
202,2,1 | The gethostbyname() call failed returning the error number (errno) logged in the system error log. |
202,2,2 | The getservbyname() call failed returning the error number (errno) logged in the system error log. |
202,3,1 | The getssn() call failed due to the errno set in fopen(). Check the error log for the error number (errno) and/or contact your support representative. |
202,3,2 | A bad ssn has been detected. Check the error log for its (bad) value and contact your support representative. |
202,3,3 | The getssn() should not be called directly by WAL clients |
202,4,1 | Program error: abs_end_init was called without first calling abs_begin_init. |
202,4,2 | XXX_init_V error: Version mis-match. Refer to error log. |
202,4,3 | XXX_init_V error: Bad parameter passed to signal(). |
202,5,1 | A call to put_pg_globals was unsuccessful due to an error in the putenv call. This is probably not a serious error. Program continuing... |
202,5,2 | A call to get_pg_globals was unsuccessful due to an error in the getenv call. This is probably not a serious error. Program continuing... |
202,5,3 | Not an error tuple. The tuple is used for debugging. |
202,5,4 | fnsw_fork not supported for the MAC platform |
202,7,1 | killfnsw could not kill off a program |
202,8,1 | event_action log tuple. Refer to the error log |
202,8,2 | A child process has abnormally terminated. Refer to the error log |
202,6,1 | A key or value in the registry database could not be found. |
202,6,2 | Illegal path passed to fnc_path function. |
202,6,3 | The current process is not registered. |
202,6,4 | The PID is not valid when the script attempts to register. |
202,6,5 | System Error. Check error log for more info. |
202,6,6 | Permission to a particular segment was denied |
202,6,7 | FNC: An attempt to dynamically load a library failed |
202,6,8 | FNC: An attempt to initialize a dynamically loaded library failed |
202,6,9 | FNC: An illegal parameter was passed to an entry point. |
202,6,10 | FNC: An abnormal condition occurred during write activity logging operation. Refer to the error log. |
202,6,11 | FNC: An abnormal condition occurred when flushing activity log buffer. Refer to the error log. |
202,6,12 | FNC: A conflict exists with the serverConfig file |
202,6,2001 | FNC NT error - look at the log file |
202,9,1 | The FNC abstract could not open a UDP socket to send a trap |
202,9,2 | The FNC abstract could not bind to the trap socket |
202,9,3 | The FNC abstract got an error writing to the trap socket |
202,9,4 | Not really an error - just testing the trap mechanism... |
202,0,1001 | value returned by procedures that should have been declared void |
202,0,1002 | FNL: bad interlock handle: range |
202,0,1003 | FNL: bad interlock handle: interlock not in use |
202,0,1004 | FNL: global memory corrupt: bad inx in interlock validation field |
202,0,1005 | FNL: bad interlock handle: stale (previously deallocated) |
202,0,1006 | FNL: alloc pros rec: bug: illegal wait type |
202,0,1007 | FNL: bug: duplicate process id |
202,0,1008 | FNL: no memory for process record chunks |
202,0,1009 | FNL bug: process already linked into wait queue |
202,0,1010 | FNL bug: process already unlinked from wait queue |
202,0,1011 | FNL: release: kill(pid,SIGCONT) returned error |
202,0,1012 | FNL: claimt: caller error: negative timeout parameter |
202,0,1013 | FNL bug: release: empty claim q |
202,0,1014 | FNL: release: caller error: release limit exceeded |
202,0,1015 | FNL: caller error: too many releaseshare, or called before claimshare |
202,0,1016 | FNL: getinterlock: bug: bad avail interlock list |
202,0,1017 | FNL: capacity exceeded: too many interlocks |
202,0,1018 | FNL: retinterlock: caller err: interlock already deallocated |
202,0,1019 | FNL: retinterlock: caller err: interlock in use |
202,0,1020 | FNL: retinterlock: bug: nonempty claim queue |
202,0,1021 | FNL: claimshare: caller err: claim count for readers/writers > 1 |
202,0,1022 | FNL: bug: impossible condition occurred |
202,0,1023 | FNL: bug: attempt to reinitialize FNL process globals |
202,0,1024 | FNL: bug: claim count invariant condition violated |
202,0,1025 | FNL: bug: claim queue invariant condition violated |
202,0,1026 | FNL: caller bug: this process created by fork() instead of fnsw_fork() |
202,0,1027 | FNL: process being released from interlock does not respond |
202,0,1028 | FNL: bug: avail pros list/count inconsistent |
202,0,1029 | FNL: bug: avail process record dope vector allocation err |
202,0,1030 | FNL: info msg: NUM_CS_ILK too small. Increase and recompile. |
202,0,1031 | FNL: bug or corruption: per pros ilk not found in per pros ilk list |
202,0,1032 | FNL: fnl_handle_cont handler called on USE_MSGS platform |
202,0,1033 | FNL: msgrcv is in an error loop |
202,0,1034 | FNL: error returned from msgget |
202,0,1035 | FNL: bug: FNL_seed <= 0 |
202,0,1036 | FNL: bug: FNL_seed <= 0 |
202,0,1037 | FNL: bug: FNL_seed <= 0 because pid <= 0 |
202,0,1038 | FNL: wal_daemon not set done flag |
202,0,1039 | FNL: fork/exec of wal_daemon failed |
202,0,1040 | FNL: process killed while waiting on deallocated interlock |
202,0,1041 | FNL: process doomed because waiting on interlock being deallocated |
202,0,1042 | FNL: process record already deallocated |
202,0,1043 | FNL: bug: interlock not spin locked |
202,0,1044 | FNL: bug: interlock not in its per-process interlock list |
202,0,1045 | FNL: release(interlock) gives it to dead claimer process |
202,0,1046 | FNL: releaseshare(interlock) gives it to dead claimer process |
202,10,0 | One or more parameters are invalid. |
202,10,1 | The native GUID generation function failed. |
202,10,2 | The referenced GUID does not represent a valid FileNET legacy GUID. |
202,10,3 | The GUID string is invalid. |
202,10,4 | The specified object type is not valid. |
202,10,5 | A failure occurred while getting the hardware address. |
202,10,6 | A failure occurred while attempting to create the clock sequence file. This is a fatal error. Consult the software event log to determine the error number returned from the create call. |
202,10,7 | A failure occurred while attempting to open the clock sequence file. Consult the software event log to determine the error number returned from the open call. |
Error Tuple |
Description |
---|---|
15,255,1 | SPP_ErrAttnInB: Attention pkt received in-band |
15,255,2 | SPP_ErrAttnOutB: Attention pkt returned out-of-band |
15,255,3 | SPP_ErrBadHandl: Invalid protocol handle parameter |
15,255,4 | SPP_ErrBadUAddr: Invalid user address parameter |
15,255,5 | SPP_ErrBadUParm: Invalid user parameter value |
15,255,6 | SPP_ErrBadSockN: Invalid socket number in network address |
15,255,7 | SPP_ErrBadSST: Invalid data stream type value supplied |
15,255,8 | SPP_ErrBadState: Invalid connect state for operation |
15,255,9 | SPP_ErrConnTerm: Connection terminated before operation completed |
15,255,10 | SPP_ErrInvArg: Invalid argument to internal procedure |
15,255,11 | SPP_ErrInvState: Connection in wrong state for operation |
15,255,12 | SPP_ErrNewSST: Data stream type change returned |
15,255,13 | SPP_ErrNoBufAvl: Insufficient buffers available for connection |
15,255,14 | SPP_ErrNoCloseR: No reply to Close Packet received |
15,255,15 | SPP_ErrNoConn: No connection associated with this handle |
15,255,16 | SPP_ErrNoHandl: No protocol handles available |
15,255,17 | SPP_ErrNoOpenRp: No open reply received for open connect request |
15,255,18 | SPP_ErrNoEpds: Insufficient epds to complete packet operation |
15,255,19 | SPP_ErrNoQEntry: Insufficient timer queue entries |
15,255,20 | SPP_ErrNoResour: Open connection rejected; insufficient resources |
15,255,21 | SPP_ErrNotList: Invalid operation on listener protocol handle |
15,255,22 | SPP_ErrOpenData: Open connection data exceeds maxDataPktSize |
15,255,23 | SPP_ErrPkt2Big: Data for packet operation exceeds maximum |
15,255,24 | SPP_ErrQIncons: Internal inconsistency in retransmit queue |
15,255,25 | SPP_ErrWind2Big: Open transport window request exceeds max |
15,255,26 | SPP_ErrNoClRpRp: No reply received for CloseReply packet |
15,255,32 | SPP_ErrSuspCreated: Connection suspended |
15,255,33 | SPP_ErrSuspAbort: connection suspended |
15,255,34 | SPP_ErrSuspErrPkt: connection suspended |
15,255,35 | SPP_ErrSuspNoCloR SPP_ErrSusNoCloRR: connection suspended |
15,255,36 | SPP_ErrSuspNoResp: connection suspended |
15,255,37 | SPP_ErrSuspNormal: connection suspended |
15,255,38 | SPP_ErrSuspTimeout: connection suspended |
15,255,4096 | ERP_ErrUnspec: Unspecified error was detected at destination |
15,255,4097 | ERP_ErrBadChks: Bad software checksum |
15,255,4098 | ERP_ErrNoSocket: Socket does not exist at destination host |
15,255,4099 | ERP_ErrRejected: Pkt rejected at dst; insufficient resources |
15,255,4352 | ERP_ErrUnspec2: Unspecified error before reaching destination |
15,255,4353 | ERP_ErrBadChks2: Bad software checksum or other inconsistency |
15,255,4354 | ERP_ErrNoRoute: Destination host cannot be reached from here |
15,255,4355 | ERP_ErrExcINRs: Pkt passed through maximum number internet routers |
15,255,4356 | ERP_ErrPkt2Big: Packet too large to forward thru internet |
15,255,4608 | ERP_ErrBadConn: Packet send to suspended transport connection |
15,255,4609 | ERP_ErrBadIDs: Packet send to socket had bad connection ID's |
15,255,4610 | ERP_ErrBadPack: Invalidly formated spp packet sent to socket |
15,255,4611 | ERP_ErrBadPType: Bad packet type field send to spp socket |
15,255,4612 | ERP_ErrNoListen: Pkt rejected at dst as not listener socket |
15,255,4613 | ERP_ErrPkt2Sml: Pkt too small to contain minimum pkt headers |
15,255,4614 | ERP_ErrInsufRes: Pkt rejected at dst; insufficient resources |
15,255,4864 | ERP_ErrNoEpds: Unable to allocate epd to send error pkt |
15,255,8192 | COR: Unknown remote service |
15,255,8193 | COR: Remote service version mismatch |
15,255,8194 | COR: Invalid remote procedure number |
15,255,8195 | COR: Bad arguments to remote procedure |
15,255,8196 | COR: No remote server process available |
15,255,10103 | COR: Some unspecified error occurred |
15,255,12288 | An attempt was made to access a file for a network service that is either not installed or not configured on this host. (CONFIGURATION ERROR) |
Error Tuple |
Description |
---|---|
71,0,1 | Wrong version used in attempt to link to SAS |
71,0,2 | Session not found for given index. (Session probably timed out.) |
71,0,3 | Too many open sessions, cannot continue (try again later). |
71,0,4 | Function not performed because session not open (active). |
71,0,5 | Attempt to open a session which is already open. |
71,0,6 | The ideal number of sessions has been exceeded. This error tuple strictly represents a diagnostic measurement. Based upon the number of concurrent licenses, SAS will extrapolate the maximum number of expected in use SAS handles. Whenever this value is exceeded SAS will log a message every 10 minutes for as long as this extrapolated value has been exceeded. |
71,0,7 | Internal trace output (INFORMATION ONLY). |
Error Tuple |
Description |
---|---|
89,0,1 | Numeric range overflow |
89,0,2 | An input parameter has the canonical illegal numeric value. Having the canonical illegal value does not mean that the value is null. Null is the absence of a value. When one or more input numbers are invalid, the output FP_number is set to the canonical illegal value, and an error tuple is returned. |
89,0,3 | Illegal format for input number string. |
89,0,4 | Invalid numeric format mask |
89,0,5 | Invalid packed-decimal style specification |
89,0,6 | Packed-decimal digits specification out of range |
89,0,7 | An input FP_number has an illegal value other than the canonical illegal value. |
89,0,8 | An input or output FP_number pointer is not aligned on a longword boundary or is a null pointer. This is always a client software error. |
89,0,1000 | Bad version number for FP abstract |
Error Tuple |
Description |
---|---|
92,0,1 | SEC error other than in protocol definition. |
92,2,2 | The password provided does not match that in the data base. |
92,2,4 | The requested object does not have a membership intersection. |
92,2,5 | Read permission is denied. |
92,2,6 | Write permission is denied. |
92,2,7 | Append/execute permission is denied. |
92,2,8 | The user, group, or device object information could not be found. |
92,2,10 | SEC could not decode the access restrictions. |
92,2,11 | The requesting user is not logged onto the security service. |
92,2,12 | The specified language name/language id was not found. |
92,0,13 | This object contains access restrictions which are not defined here. The object you tried to access is owned by a group that is not defined on the local system. To remove this error the groups in the access restriction for this object must be defined in the local security data base. |
92,0,14 | Service logon may not be done after a SEC_logon |
92,0,15 | The specified credential could not be found in the environment during logoff. Most likely the source credential data has been overwritten (as designed). |
92,0,93 | An invalid session number was supplied. |
92,0,94 | Invalid information type field. |
92,0,95 | The name provided is not of a valid syntax. |
92,0,96 | An invalid parameter was supplied. |
92,0,97 | Access to the security data base is refused. |
92,0,98 | A duplicate logon was performed. |
92,0,99 | The user has already reached the maximum allowable number of sessions. |
92,0,100 | Cannot remove inheritance if logged on. |
92,0,101 | Too many options were passed for this data structure. |
92,0,102 | An invalid object class was specified. |
92,0,103 | An invalid device class was specified. |
92,0,104 | An invalid administrative class was specified. |
92,0,105 | The current time is not within the restricted time range. |
92,0,106 | An invalid session override value was specified. |
92,0,107 | An invalid max-sessions value was passed to SEC. |
92,0,108 | A duplicate object already exists in the data base. |
92,0,109 | The object name provided was in an incorrect format. |
92,0,110 | The comments length provided exceeded the maximum allowable length. |
92,0,111 | An invalid object filter was passed to SEC. |
92,0,112 | An invalid system filter was passed to SEC. |
92,0,113 | An invalid log field was passed to SEC. |
92,0,114 | An invalid device security value was passed to SEC. |
92,0,115 | An invalid no-function-definition-ok value was passed to SEC. |
92,0,116 | The special character designator provided is not valid. |
92,0,117 | The minimum enforced password length in the system defaults is out of range. |
92,0,118 | An invalid password aging value was passed to SEC. |
92,0,119 | An invalid number of password attempts was passed to SEC. |
92,0,120 | An invalid password-suspending time was passed to SEC. |
92,0,121 | An invalid password-memory time limit was passed to SEC. |
92,0,122 | An incorrect key_num type was passed to SEC. |
92,0,123 | The member id and group id were identical. This is illegal. |
92,0,124 | The service specified does not exist. |
92,0,125 | The device security prevents access. |
92,0,126 | The object is required to be of the user class. |
92,0,127 | The device name provided is in an incorrect format. |
92,0,128 | A bad magic number was discovered in memory. |
92,0,129 | Searching for a comment is not a supported feature. |
92,0,130 | The account has expired and is no longer valid. |
92,0,132 | A bad service name was provided. |
92,0,136 | The function call executed is not legal. |
92,0,138 | The function name provided was in an invalid format. |
92,0,139 | The calculated duration of this logon instance has been exceeded. |
92,0,140 | The device specified has exceeded its expiration date. |
92,0,141 | The group specified has exceeded its expiration date. |
92,0,142 | The number of renewal days is out of range. |
92,0,143 | The specified grace period is out of range. |
92,0,144 | The specified number of failure minutes is out of range. |
92,0,145 | The parameter specified is not a search filter. |
92,0,146 | The primary group specified was not found. |
92,0,147 | The primary group specified is not a group. |
92,0,148 | The conditional operator specified is invalid. |
92,0,149 | An invalid system option was provided. |
92,0,150 | An invalid object option was provided. |
92,0,151 | The system defaults information could not be found. |
92,0,152 | The group information could not be found. |
92,0,153 | The deleted object information could not be found. |
92,0,155 | The group-member in the data base already exists. |
92,0,156 | The specified object has already been deleted. |
92,0,157 | The specified system structure already exists in the data base. |
92,0,158 | The system option list provided is invalid. |
92,0,166 | The system language option is in an invalid format |
92,0,167 | The specified function name was not found. |
92,0,168 | The specified function member combination was not found. |
92,0,169 | The specified function name already exists. |
92,0,170 | The specified function member combination already exists. |
92,0,171 | The function ids or member ids are out-of-sync. |
92,0,172 | The specified minute range is invalid. |
92,0,173 | The specified hour range is invalid. |
92,0,174 | The specified days of week range is invalid. |
92,0,175 | The executed entry-point is not supported in this state. |
92,0,176 | The ssn stored in the handle is invalid. |
92,0,177 | The number of allowable failed password attempts has been exceeded. |
92,0,178 | The password has expired. |
92,0,179 | The specified password requires a special character. |
92,0,180 | The specified handle should be non-null. |
92,0,181 | The buffer tag definition is not of a recognized type. |
92,0,182 | The object update is denied. |
92,0,183 | The member addition is denied. |
92,0,184 | The object delete is denied. |
92,0,185 | The termination of a logon is denied due to inadequate permissions. |
92,0,186 | The password update is denied due to inadequate permissions. |
92,0,187 | The deletion of the specified member from the group is denied. |
92,0,188 | The addition of the specified object is denied. |
92,0,189 | The user does not have the permissions to add a function. |
92,0,190 | The user does not have the permissions to delete a function. |
92,0,191 | The user does not have the permissions to add a function member. |
92,0,192 | The user does not have the permissions to delete a function member. |
92,0,193 | The terminal identifier maximum has been reached for this server. |
92,0,194 | An invalid terminal identifier was detected. |
92,0,195 | The member/group relationship in the groups table is out of sync. |
92,0,197 | Changing the primary group of a group is an illegal operation. |
92,0,198 | The concurrent license limit has been reached. |
92,0,199 | The terminal name provided is in an incorrect format. |
92,0,201 | The semantic use of the password option is invalid. |
92,0,202 | It is illegal to add or update the admin group. |
92,0,203 | It is not allowable to search for an object by expiration time. |
92,0,204 | It is not allowable to add or update an object by success_where. |
92,0,205 | It is not allowable to add or update an object by failed_where. |
92,0,206 | It is not allowable to add or update an object by its failure error. |
92,0,207 | It is not allowable to search for an object by its comment field. |
92,0,208 | It is illegal to set the admin class for a non-user/system object. |
92,0,209 | It is not allowable to add or update the language of a non-user/system. |
92,0,210 | It is not allowable to set the device class for a non-device/system. |
92,0,211 | It is not allowable to change the object class of an existing object. |
92,0,212 | It is not allowable to set the maximum sessions for a device object. |
92,0,213 | It is illegal to specify a primary group for a group object. |
92,0,214 | An invalid time combination was specified for the dweek/min/hour values. |
92,0,215 | The user does not have the admin permission to read the object. |
92,0,216 | The user does not have the admin permission to read the system defaults. |
92,0,217 | The user does not have the admin permission to read the member list. |
92,0,218 | The user does not have the admin permission to read the group list. The user must be of an administrative class to view groups. |
92,0,219 | The user does not have the admin permission to read the function list. The user must be of an administrative class to view function membership. |
92,0,220 | The user does not have the admin permission to read the function members. The user must be of an administrative class to view function membership. |
92,0,221 | The length of the password provided is out of range. A password should at least have a minimum length of that specified by the system defaults and cannot have a length greater than 8 characters. |
92,0,222 | An operation on the specified file failed. An error occurred attempting to open the specified file name. |
92,0,223 | The import version contained in the import file is not recognized. The import routine expects the export file to contain a version stamp of an explicit value. |
92,0,224 | The export file has a different default character set than the import system. It is required that an export/import be performed across systems which contain the same default character set. It is not possible to convert systems across different character sets due to encrypted password incompatibilities. |
92,0,226 | The import file is in an incorrect format. When the import routine attempts to parse the export file, it expects the information to be of certain sizes and in certain locations within the export file. If it encounters a conflict, then this error will occur. It is possible that the export file is corrupt, or that it has been manually edited. |
92,0,227 | There were missing or improper import parameters. |
92,0,228 | The domain length may not exceed 20 characters in length. |
92,0,229 | The import object class conflicts with that of an existing object. When the security service imports an object, it will look for objects of the same name within the import data base. If those objects exist, then it will compare the object class. If the object class is not the same, then the import will not continue. This check exists to protect conflicting membership (ie. a user cannot be made a member of a user). |
92,0,230 | An invalid security service name was provided. This error typically occurs when the security service expects to receive the service name as a parameter, but has received nothing instead. |
92,0,231 | A user who is not SysAdmin attempted to export the security data base. For the sake of security, SEC requires that only the SysAdmin user may perform this action. This prevents any user from being able to export a data base without being authenticated. |
92,0,232 | A user who is not SysAdmin attempted to import the security data base. For the sake of security, SEC requires that only the SysAdmin user may perform this action. This prevents any user from being able to import a data base without being authenticated. |
92,0,234 | The session handle is stale. The security service was rebooted. Typically, this error is seen only internal to the security service so that the client can determine if it needs to relogon to the security service after a server reboot. |
92,0,235 | The relogon information provided is inaccurate. Once the security service issues the SEC_err_stale_session, the client SEC code will attempt to relogon to the security service. If the information which is sent to the security service from the client is incorrect, then this error will occur. |
92,0,236 | The provided admin group does not exist in the security data base. The data base object table was searched for this object, however, it was not able to be found. |
92,0,237 | The admin group option may not have an id of 0, 1 or 6. The id 0 equates to (NONE), the id 1 equates to (ANYONE) and the id 6 equates to (UNDEFINED). |
92,0,238 | The provided admin group is not a group. |
92,0,239 | The encrypted password in the data base consists of nulls. |
92,0,240 | The concurrent license is either expired or missing. |
92,0,250 | The fnfork program could not find the pid in the term_id list. |
92,0,251 | The administrator must be SysAdmin to use the PC security administration utility. |
92,0,252 | The specified session group does not exist in the security data base. |
92,0,253 | The session group supplied is not a group. |
92,0,254 | An illegal value was provided for the allow_override field. |
92,0,255 | It is illegal to add/update a session group for a group or device object. |
92,0,256 | The database name map information could not be found. |
92,0,257 | The database name information could not be found. |
92,0,258 | The FileNet to database name map information already exists. |
92,0,259 | The database map name already exists. |
92,0,260 | The dbinfo table search filter is not recognized. |
92,0,261 | The database password is in an incorrect format. |
92,0,262 | The database name provided is in an incorrect format. |
92,0,263 | The user does not have permission to delete a dbinfo record. |
92,0,264 | The user does not have permission to update a dbinfo record. |
92,0,265 | The user does not have permission to add a dbinfo record. |
92,0,266 | The user does not have permission to map to a db user. |
92,0,267 | The option specified is not valid. |
92,0,268 | It is illegal to specify a db name map for a non-user. |
92,0,269 | The pointer passed is NULL. |
92,0,270 | The number of bytes value is zero. |
92,0,271 | The requesting user is refused access to the native database. |
92,0,272 | Could not allocate global memory for terminal listing. |
92,0,273 | Could not get process create time in SEC. |
92,0,274 | Could not get process access token. |
92,0,275 | Could not get sufficient buffer for token stats |
92,0,276 | Got error in GetTokenInformation |
92,0,277 | Invalid event type |
92,0,278 | Import database level does not match current database level |
92,0,279 | Configuration error; service is remote |
92,0,280 | Could not make log directory |
92,0,281 | Could not create README in log directory |
92,0,282 | Could not write README in log directory |
92,0,283 | The Db2 information could not be found. |
92,0,284 | The DB2 acct name already exists. |
92,0,285 | DB2 password length reached maximum length. |
92,0,286 | DB2 acct name length reached maximum length. |
92,0,287 | The time between DB2 client and server is out of range |
92,0,300 | Message is for SEC information and/or debugging purposes only |
92,0,301 | Must be root or fnsw to execute SEC_convert |
92,0,302 | A bad character was detected |
92,0,303 | A duplicate name exists |
92,0,304 | A name exceeding 39 characters was found |
92,0,305 | Must be a member of group fnadmin to rebuild the security data base |
92,0,306 | Must be root to rebuild the security data base |
92,0,307 | Must be fnadmin to rebuild the security data base |
92,0,308 | User is not a member of group fnadmin, permission denied |
92,0,309 | User is not root, permission denied |
92,0,310 | User is not SysAdmin, permission denied |
92,0,311 | System command putenv failed |
92,0,312 | Invalid option in fnfork/exec |
92,0,313 | Exec() failed |
92,0,314 | Fork() failed |
92,0,315 | CreateProcess failed |
92,0,316 | Could not create SEC_anl success file |
92,0,317 | Zero session |
92,0,318 | Data segment allocation verification failed |
92,0,319 | Unable to get valid logging queue |
92,0,400 | Not an Error (just informational) |
92,0,401 | Unable to access (r|w|m) Transparent Login DataBase |
92,0,402 | User Transparent Login Credentials already deleted or do not exist |
92,0,403 | User Transparent Login Credentials are unknown |
92,0,404 | User Transparent Login name does not match the one in the TL DB |
92,0,450 | Duplicate SLU encountered |
92,0,451 | Hard limit for some SLU type reached |
92,0,452 | Unable to find time from the system |
92,0,453 | Unable to find the SLU record |
92,0,454 | SLU initialization in shared memory failed |
92,0,455 | This entry point is only supported on NT |
92,0,456 | This user interface is only supported on WAL |
92,0,457 | Debug Message, Don't worry about it |
92,0,458 | This is an information message, no errors were detected |
92,0,459 | This is an invalid SLU type |
92,0,500 | Unable to find the SLU record |
92,0,501 | Failed to open registration database |
92,0,502 | Failed to query registration database |
92,0,503 | Failed to create thread local storage index |
92,0,504 | Failed to set value for thread local storage |
92,0,505 | Failed to get value for thread local storage |
92,0,506 | The pointer passed in for user name is NULL |
92,0,507 | Error returned from LogonUI |
92,0,508 | Failed to diaplay copyright information |
92,0,509 | User already logged on to the same domain using a different name |
92,0,510 | LogonUI was cancelled |
92,0,511 | Failed to get the NT credential |
92,0,511 | The functionality requested is not supported by present version of IMS server |
Error Tuple |
Description |
---|---|
121,0,1 | GDB level does not match |
121,0,2 | Invalid option specified in GDB call |
121,0,3 | No data found for fetch |
121,0,4 | Variable not in select list |
121,0,5 | Bad GDB function address |
121,0,6 | Bad GDB logon handle |
121,0,7 | Bad GDB statement handle |
121,0,8 | Bind information not found in the list |
121,0,9 | Bad GDB configuration |
121,0,10 | Bad DBMS specific logon handle |
121,0,11 | Bad DBMS specific statement handle |
121,0,12 | Function call is out of call sequence |
121,0,13 | Number data has bad format |
121,0,14 | integer overflow |
121,0,15 | buffer overflow |
121,0,16 | duplicate in index |
121,0,17 | Statement handle for current of is invalid |
121,0,18 | Where current statement has not done fetch |
121,0,19 | Bad SQL type encountered |
121,0,20 | Bad update where current variable encountered |
121,0,21 | Fetched column value was truncated |
121,0,22 | Table is busy, in use by others |
121,0,23 | Table or view specified does not exist |
121,0,24 | Synonym to be created is already defined |
121,0,25 | invalid negative column number |
121,0,26 | all available statements are in use |
121,0,27 | user type and dbms type not compatible |
121,0,28 | nonexistent user name is referenced |
121,0,29 | name is already used by an existing object |
121,0,30 | column is already indexed |
121,0,31 | column is already defined as NOT NULL |
121,0,32 | specified index does not exist |
121,0,33 | column already exists in table |
121,0,34 | current operation has been interrupted |
121,0,35 | GDB logon was not done |
121,0,36 | Unsupported DBMS type is encountered |
121,0,37 | no public synonym |
121,0,38 | bad rowid syntax |
121,0,39 | row does not exist |
121,0,40 | datatype not supported by GDB |
121,0,41 | DBMS is not available. Errors may have been detected in the communication link between IS server and RDBMS server. Check system error log for details. |
121,0,42 | No more space in DBMS object |
121,0,43 | A fatal error is returned from DBMS |
121,0,44 | cannot modify fields in alter table command |
121,0,45 | Invalid GDB data type is specified |
121,0,46 | Version mismatch in abst_link to GDB call |
121,0,47 | Column name is missing or invalid |
121,0,48 | Empty SQL statement is passed |
121,0,49 | Sybase client library error detected. Check error log for error number and messages or if Sybase is not started, startup Sybase. |
121,0,50 | GDB encountered an internal error, see error log for detail |
121,0,51 | No error message is found |
121,0,52 | Cannot get error message from DBMS |
121,0,53 | Invalid username or password is specified for log on to RDBMS. This error can also be returned if the RDBMS is down, not available, or the max number of connections have been exceeded. If DB2 is the underlying RDBMS, make sure username and password exist and are also valid on the operating system level of the corresponding RDBMS server. |
121,0,54 | Transaction aborted by DBMS to resolve deadlock. Retry from beginning recommended. |
121,0,55 | Deadlock retry failed after number of attempts |
121,0,56 | Received multiple results sets which is unsupported |
121,0,57 | Database has rows to return when GDB does not expect them |
121,0,58 | Expected blob data when there wasn't any |
121,0,59 | Received DB-Library error. Check system log for more information |
121,0,60 | Could not bind column to variable |
121,0,61 | Could not send row to DBMS |
121,0,62 | Could not allocate space for command buffer |
121,0,63 | Could not send command to DBMS |
121,0,64 | Failed to retrieve results from DBMS |
121,0,65 | Could not write text or image data to DBMS |
121,0,66 | Failed to retrieve row from DBMS |
121,0,67 | Could not open cursor |
121,0,68 | Could not update or delete where current of cursor |
121,0,69 | Could not cancel current command |
121,0,70 | Could not initialize bulk copying |
121,0,71 | Could not close cursor |
121,0,72 | Could not bind indicator variable |
121,0,73 | Both primary and secondary passwords are invalid to connect to RDBMS. Contact Administrator to resolve the authentication problems. |
121,0,74 | Table row length exceeds the limit for the page size. The row length for the table defined in the CREATE TABLE or ALTER TABLE statement exceeds the limit for the page size of the table space. Refer to DB2 help message for detailed explanation and the appropriate user response. |
121,0,75 | User account is set with incorrect environment variables. Contact Administrator to solve this problem which may be caused by not correctly running the inst_templates script. IS will not function until this issue is resolved. If environment variable is not an issue, check system error log to confirm any other errors, such as network failures, may have been the cause. |
121,99,1 | SQL syntax error |
121,1,65534 | Oracle error occurred. Oracle error number is err_num from <GDB,1,err_num>. See Oracle documentation or run oracle 'oerr' program, if available, for error message. |
121,3,65534 | Allbase error occurred. Allbase error number is err_num from <GDB,3,err_num>. See Allbase documentation for error message. |
121,4,65534 | Allbase error occurred. Allbase error number is 100000 + err_num from <GDB,4,err_num>. See Allbase documentation for error message. |
121,5,65534 | Sybase error occurred. Sybase error number is err_num from <GDB,5,err_num>. For error message, run isql and execute a sql: 'fnsys..fn_error <err_num>' Or Check Sybase SQL Server Troubleshooting Guide. |
121,7,65534 | MSSQL error occurred. MSSQL error number is err_num from <MSSQL,7,err_num>. For error information see the Microsoft SQL Server documentation or run isqlw and execute fn_error from the FileNET database: '<database name>..fn_error <err_num>' for error message. |
121,9,65534 | DB2 error occurred. DB2 SQLCODE is the err_num from <GDB,9,err_num>. For detailed DB2 error msg info, run 'db2 ? SQLnnnnn' from cmd prompt on UNIX platforms or from DB2 'Command Window' on Windows platform, where nnnnn is the <err_num>. Prefix the err_num with 0 (zero) if it is not a 5-digit number. For example, the DB2 help msg for error tuple <121,9,513> can be queried by: - db2 ? SQL00513 |
121,10,65534 | Encountered DB2 error which was not from data source. In the corresponding FileNet syslog, identify XXXnnnnn value from the line that starts with ErrorMsg = '[IBM] ...', where XXX is the msg prefix and nnnnn is the msg no. Then, run 'db2 ? XXXnnnnn' from cmd prompt on UNIX platforms or from DB2 'Command Window' on Windows platform to query detailed DB2 error msg. For example, run the cmd below if ErrorMsg = '[IBM][CLI Driver] CLI0109E ...', - db2 ? CLI0109E |
Error Tuple |
Description |
---|---|
155,00,11 | COR main: bad version number |
155,00,02 | COR: COR table full, start garbage collecting |
155,00,129 | COR_Listen: ERROR: returning from main function |
155,00,215 | COR: error with mutex lock |
155,01,01 | COR_Close: bad cor handle |
155,01,21 | COR_Close: close connection without sending any RPC |
155,01,201 | COR_Close: unexpected response to close request |
155,01,206 | COR_Close:close failed |
155,02,01 | COR_CrAprConn: bad cor handle |
155,02,02 | COR_CrAprConn: maximum COR connections exceeded |
155,02,03 | COR_CrAprConn: not enough memory for buffer |
155,02,19 | COR_CrAprConn: bad pointer |
155,03,01 | COR_CrListener: bad cor handle |
155,03,02 | COR_CrListener: maximum COR connections exceeded |
155,03,03 | COR_CrListener: not enough memory for buffer |
155,04,01 | COR_DeListener: bad cor handle |
155,05,01 | COR_Delete: bad cor handle |
155,05,132 | COR_Delete: A sequence of context-sensitive RPCs was not terminated with a context-free RPC before the connection was closed |
155,06,01 | COR_DesAbort: bad cor handle |
155,06,08 | COR_DesAbort: bad message |
155,06,09 | COR_DesAbort: bad transaction ID |
155,06,10 | COR_DesAbort: wrong message type |
155,07,01 | COR_DesCall: bad cor handle |
155,07,06 | COR_DesCall: bad COR Call |
155,07,07 | COR_DesCall: program number or program version number in call does not match value in cor handle |
155,07,08 | COR_DesCall: bad message |
155,07,10 | COR_DesCall: wrong message type |
155,08,01 | COR_DesChoice: bad cor handle |
155,08,04 | COR_DesChoice: insufficient data |
155,09,01 | COR_DesLongWord: bad cor handle |
155,10,01 | COR_DesMove: bad cor handle |
155,10,04 | COR_DesMove: insufficient data |
155,10,19 | COR_DesMove: bad pointer |
155,11,01 | COR_DesReject: bad cor handle |
155,11,08 | COR_DesReject: bad message |
155,11,09 | COR_DesReject: bad transaction ID |
155,11,10 | COR_DesReject: wrong message type |
155,12,01 | COR_DesReturn: bad cor handle |
155,12,04 | COR_DesReturn: insufficient data |
155,12,08 | COR_DesReturn: bad message |
155,12,09 | COR_DesReturn: bad transaction ID |
155,12,10 | COR_DesReturn: wrong message type |
155,14,01 | COR_DesStruct: bad cor handle |
155,16,01 | COR_DesWord: bad cor handle |
155,17,01 | COR_IssueMsg: bad cor handle |
155,18,01 | COR_Listen: bad cor handle |
155,18,03 | COR_Listen: not enough memory for buffer |
155,18,04 | COR_Listen: insufficient data for deserialization |
155,18,08 | COR_Listen:bad message call |
155,18,09 | COR_Listen: Bad transaction ID |
155,18,18 | COR_Listen: A client opened a connection and did not send an RPC in a reasonable amount of time, so the connection was closed to free server resources. This may be caused by the design of the client, software problems on the client or server, or by network problems between the client and server. This message is usually a symptom of another problem which may or may not have any material effect on the usability of the system. |
155,18,19 | COR_Listen: bad cor handle passed through open_info struct |
155,18,22 | COR_Listen: cannot specify 2 -p options |
155,18,23 | COR_Listen: must specify either -pt or -px |
155,18,24 | COR_Listen: usage information |
155,18,25 | COR_Listen: setsockopt(SO_LINGER) failed |
155,18,26 | COR_Listen: setsockopt(SO_KEEPALIVE) failed |
155,18,27 | COR_Listen: setsockopt(SO_NODELAY) failed |
155,18,28 | COR_Listen: setsockopt(SO_RCVBUF) failed |
155,18,100 | COR_Listen:failed to change its directory |
155,18,101 | COR_Listen:can't get interlock |
155,18,102 | COR_Listen:I_RECVFD ioctl failed |
155,18,103 | COR_Listen:was not able to read from pipe |
155,18,104 | COR_Listen:accept failed |
155,18,105 | COR_Listen:listen failed |
155,18,106 | COR_Listen:open failed |
155,18,107 | COR_Listen:bind failed |
155,18,108 | COR_Listen:can't ioctl SPX_GS_DATASTREAM_TYPE to spx |
155,18,109 | COR_Listen:ioctl failed on pipe |
155,18,110 | COR_Listen:retry exceeds on pipe |
155,18,111 | COR_Listen:write failed on pipe |
155,18,112 | COR_Listen:cannot fork |
155,18,113 | COR_Listen:close failed |
155,18,114 | COR_Listen:sendfile failed |
155,18,115 | COR_Listen:break pipe failed |
155,18,116 | COR_Listen:wait on pipe failed |
155,18,117 | COR_Listen:fn_alloc_sem for loopback lock failed |
155,18,118 | COR_Listen:got data on close |
155,18,119 | COR_Listen:child died |
155,18,120 | COR_Listen:get unexpected SIGPIPE |
155,18,121 | COR_Listen:alloc failed |
155,18,122 | COR_Listen:exceed maximum queue |
155,18,123 | COR_Listen:getsockname failed |
155,18,124 | COR_Listen:getservbyname failed |
155,18,125 | COR_Listen:setsockopt(REUSE_ADDR) failed |
155,18,126 | COR_Listen:bind failed |
155,18,127 | COR_Listen:t_sync() failed |
155,18,133 | COR_Listen: The version of Courier running on this host does not support Enterprise Courier clients. Either the client should be configured to use the previous version of Courier, or the server should be updated and configured to use Enterprise Courier. |
155,18,205 | COR_Listen: cor_s_pipe() function obsolete |
155,18,209 | COR_Listen: COR_CrAprConn failed |
155,18,216 | COR_Listen:Abnormal condition |
155,18,217 | COR_Listen:Connection abruptly closed by client |
155,19,02 | COR_Open: maximum COR connections exceeded |
155,19,03 | COR_Open: not enough memory for buffer |
155,20,01 | COR_ReceiveMsg: bad cor handle |
155,20,04 | COR_ReceiveMsg: insufficient data |
155,20,11 | COR_ReceiveMsg: bad version number |
155,20,100 | COR_ReceiveMsg: unexpectedly receive a call message |
155,20,101 | COR_ReceiveMsg: unexpectedly receive a reject mesage |
155,20,102 | COR_ReceiveMsg: unexpectedly receive a return message |
155,20,103 | COR_ReceiveMsg: unexpectedly receive a abort message |
155,21,01 | COR_SerAbort: bad cor handle |
155,21,05 | COR_SerAbort: buffer overflow |
155,22,01 | COR_SerCall: bad cor handle |
155,22,05 | COR_SerCall: buffer overflow |
155,23,01 | COR_SerCoice: bad cor handle |
155,24,01 | COR_SerLongWord: bad cor handle |
155,24,05 | COR_SerLongWord: buffer overflow |
155,25,01 | COR_SerReject: bad cor handle |
155,25,05 | COR_SerReject: buffer overflow |
155,26,01 | COR_SerReturn: bad cor handle |
155,26,05 | COR_SerReturn: buffer overflow |
155,27,01 | COR_SerSequence: bad cor handle |
155,28,01 | COR_SerStruct: bad cor handle |
155,29,01 | COR_SerString: bad cor handle |
155,30,01 | COR_SerWord: bad cor handle |
155,30,05 | COR_SerWord: buffer overflow |
155,31,04 | COR_Deserialize: insufficient data |
155,31,05 | COR_Deserialize: buffer overflow |
155,33,01 | COR_BulkDataAbort: bad cor handle |
155,33,12 | COR_BulkDataAbort: no bulk data connection exists |
155,33,205 | COR_BulkDataAbort: unsupported bulk data mode |
155,34,01 | COR_BulkDataGet: bad cor handle |
155,34,14 | COR_BulkDataGet: end of message |
155,34,13 | COR_BulkDataGet: data is truncated |
155,34,11 | COR_BulkDataGet: bad version number |
155,34,15 | COR_BulkDataGet: abort message received |
155,34,16 | COR_BulkDataGet: reject message received |
155,34,10 | COR_BulkDataGet: wrong message type |
155,35,01 | COR_BulkDataPut: bad cor handle |
155,35,17 | COR_BulkDataPut: abort packet received |
155,35,11 | COR_BulkDataPut: bad version number |
155,35,16 | COR_BulkDataPut: reject message received |
155,36,01 | COR_Flush: bad cor handle |
155,37,01 | COR_GetServerID: bad cor handle |
155,40,01 | COR_RcvMsgTimeOut: bad cor handle |
155,40,04 | COR_RcvMsgTimeOut: insufficient data |
155,40,11 | COR_RcvMsgTimeOut: bad version number |
155,40,18 | COR_RcvMsgTimeOut: timer expired before message arrives |
155,40,207 | COR_RcvMsgTimeOut: select failed |
155,41,20 | COR_Init:Bad command on file serverConfig |
155,41,216 | COR_Init:Abnormal Condition |
155,41,218 | COR_Init:No such host |
155,42,130 | COR_SetContext: this function must not be called for a client-side connection |
155,42,131 | COR_SetContext: the value of the context parameter is invalid |
155,202,03 | COR_SerLongWords: not enough memory for buffer |
155,209,03 | COR_PutPacket: not enough memory for buffer |
155,209,215 | COR_PutPacket:system call failed |
155,209,217 | COR_PutPacket: connection closed prematurely |
155,210,100 | COR_init: getgloarea failed |
155,210,101 | COR_init:msem_init failed |
155,210,102 | COR_init:cannot get interlock |
155,210,103 | COR_init:gethostid failed |
155,210,104 | COR_FunCrAprCon:break pipe failed |
155,210,105 | COR_Open:SPX_GS_DATASTREM_TYPE ioctl failed |
155,210,106 | COR_FunBulkDataGet:unknown data stream type |
155,210,107 | cor_GetTableEntry:fatal error |
155,210,108 | cor_FreeTableEntry:fatal error |
155,210,109 | COR:cor_close got data; expected close reply |
155,210,110 | cor_GetNetData: address is not a valid shared memory address |
155,210,111 | COR:fn_alloc_sem for loopback lock failed |
155,210,112 | COR_GetAddress:illegal protocol |
155,210,212 | cor_rcv: got TSYSERR doing t_rcv |
155,210,216 | COR:Abnormal Condition |
155,210,217 | COR:Connection abruptly closed by client |
155,210,212 | COR:TLI error |
155,210,219 | COR:Socket error |
155,210,220 | COR:clean COR table |
155,211,100 | pipe:socket failed |
155,211,101 | pipe:open failed |
155,211,102 | pipe:I_FDINSERT failed |
155,211,103 | pipe:pipe failed |
155,211,104 | pipe:bind failed |
155,211,105 | pipe:listen failed |
155,211,106 | pipe:close failed |
155,211,107 | pipe:fattach failed |
155,211,108 | pipe:chmod failed |
155,211,109 | pipe:fstat failed |
155,211,110 | pipe:unlink failed |
155,211,111 | pipe:accept failed |
155,211,112 | pipe:connect failed |
155,211,113 | pipe:recvmsg failed |
155,211,114 | pipe:I_RECVFD failed |
155,211,115 | pipe:pid do not match |
155,211,116 | pipe:stream file does not exist |
155,211,117 | pipe:stream name does not match |
155,211,118 | pipe:not a valid pid |
155,211,216 | pipe:Abnormal Condition |
155,212,0 | COR:message reject because of invalid program number |
155,212,1 | COR:message reject because of invalid version number |
155,212,2 | COR:message reject because of invalid procedure number |
155,212,3 | COR:message reject because of bad arguments |
155,212,4 | COR:message reject because of no available resource |
155,212,128 | COR:message reject because of unspecified error |
155,212,255 | COR:message reject because of unknown error |
155,255,01 | bad cor handle |
155,255,07 | COR_Listen Received first message with wrong message type |
155,255,211 | call to obsolete serialize/deserialize choice/sequence function |
155,255,214 | protocol requested by the given net address is not supported |
155,255,215 | operating system primitive for pipe or mutex failed |
155,255,216 | abnormal condition encountered in Courier operation |
155,255,219 | Confronted socket API error |
155,255,12288 | COR_Listen: Network service device file does not exist. The network protocols for that service are either not installed or not configured |
Error Tuple |
Description |
---|---|
156,0,0 | Null or Bad parameters |
156,0,1 | Abstract link failed due to version mismatch. |
156,0,23 | The entry point is currently unimplemented. |
156,0,24 | A network related error was encountered. |
156,0,25 | An exceptional condition was encountered and logged. |
156,0,26 | Unable to locate a NCH server for the specified domain. |
156,0,27 | The NCH database does not exist (OK during initialization) |
156,0,28 | NCH_daemon received a request containing an ill-formed domain name |
156,0,29 | Unable to lookup a network address for the specified name |
156,0,30 | NCH informational message -- Not an error condition |
156,0,31 | User is not a member of the fnadmin group |
156,1,1 | Operation prevented by access controls. |
156,1,2 | Server too busy to service this request. |
156,1,3 | A required NCH server was found to be down. |
156,1,4 | Courier must be used for this operation. |
156,1,5 | Encountered an unsupported function or exception condition. |
156,2,10 | Illegal Property Value. |
156,2,11 | Syntax error in an organization field. |
156,2,12 | Syntax error in an domain field. |
156,2,13 | Syntax error in an object field. |
156,2,14 | The name's organization does not exist. |
156,2,15 | The name's domain does not exist. |
156,2,16 | The name's object does not exist. |
156,3,20 | The object exists but the property does not. |
156,3,21 | The property was found to be of the wrong type. |
156,4,30 | The operation would not change the database. |
156,4,31 | More recent information was found in the database . |
156,4,32 | The particular object would have too much data associated with it. |
156,4,33 | The server's database is full. |
156,5,0 | The server does not handle the specified domain. |
156,6,0 | The client failed the authentication checks. |
156,0,9 | The specified address protocol is not supported. |