Skip to main content
Version: 7.2402.x.x RR

BASE

The next table lists all error codes related to the isiweb base classes.

MajorMinorMessageDetails
BASE0001TokenizedOutputStream received an illegal terminated buffer.Contact support.
0002Illegal status of buffer.Check the logs for more information or contact support.
0003Illegal store size (smaller than zero).Contact support.
0004Failed to expand the buffer.Contact support.
0005No valid token stored.Check the logs for more information.
0006Exception occurred during parsing the header.Check the logs for more information.
0007Cookie manager found unknown cookie rule.Check the logs for more information.
0008Cookie manager found unknown cookie rule.Check the logs for more information.
0009You have to specify either 'size:' or 'time:' as rotation policy. Ignoring the rotation policy.Check the configuration of the AuditFilter.
0010You can't specify 'size:' and 'time:' as rotation policy. Ignoring the rotation policy.Check the configuration of the AuditFilter.
0011Rotation size is not a number.Check the configuration of the AuditFilter.
0012Maximum size is not a number.Check the configuration of the AuditFilter.
0013The value for rotation time is not valid. Only 'hourly', 'daily', or 'monthly' permitted. Ignoring value.Check the configuration of the AuditFilter.
0014Failed to clean up output stream: bytes pending.Contact support.
0015Failed to clean up output stream: IOException occurred.Check the logs for more information.
0016Failed to clean up output stream: Exception occurred.Check the logs for more information.
0017Failed to clean up output stream: unknown exception occurred.Contact support.
0018Invalid arguments (no buffer or negative length).Contact support.
0019Invalid arguments (no buffer, no null-terminations, or negative length)Contact support.
0020Parsing pending buffer failed.Check the logs for more information.
0021Parsing input failed.Check the logs for more information.
0022Failed to expand the buffer.Check the logs for more information.
0023Disabling parsing in tolerant mode.Contact support.
0024Illegal size for buffer.Contact support.
0025Invalid terminated buffer.Contact support.
0026Not enough data for parsing.Check the logs for more information.
0027IllegalArgumentException occurred.Check the logs for more information.
0028IOException caught during writing in PipedHttpServletResponseWrapper.Contact support.
0030HTMLTagParser error: Illegal character after closing tag name.Check the logs for more information.
0032Too many attributes, a maximum of ISIWEB4_MAX_HTML_TAG_ATTRIBUTES are supportedContact support.
0033Illegal character found in HTML fragment.Check the logs for more information.
0034Failed to parse date, exception occurred.Check the logs for more information.
0035Found unknown escape character. Ignoring it.Check the logs for more information.
0036Received an unsupported Content-Encoding.The body may not be rewritten.
0037Received an unsupported Content-Encoding.The body may not be rewritten.
0038Received the Content-Encoding-header when the OutputStream has already been created.The body may not be rewritten.HINT: Make sure there is no DeflateFilter between the backend and the filter that generated the error.
0039HTMLDecoder: unsupported charset.Contact support.
0040Decoding failed, could not not convert to given charset.Check the logs for more information or contact support.
0041Not valid charset reference.Check your configuration.
0042Not valid charset reference.Check your configuration.
0043Caught an IOException while substituting attribute valueCheck the logs for more information or contact support.
0045No resource for verifier configured.Check the parameter SectokenVerifierCert in the context parameter section context-paramof the web.xml file. Most probably one of the certificates is invalid or empty. Check the log for further details.
0046Exception occurred during the initialization of SecurityManager.Contact support.
0047Failed to clean up SecurityManager.Contact support.
0048Unsupported encoding.Check your configuration.
0049Unsupported encoding.Check your configuration.
0050Input not null-terminated.Contact support.
0051Unexpected Parsing-Code for option-tagCheck the logs for more information.
0052Error while parsing HTML fragment.Check the logs for more information.
0053Error while parsing HTML fragment.Set the parsing mode to "tolerant" if you want to recover gracefully.
0054No valid tag found, parsing will be aborted.Check the logs for more information.
0055Prefix in buffer is longer than markerCheck the logs for more information or contact support.
0056Illegal parsing state while trying to complete a buffer.Check the logs for more information.
0057Illegal store size.Check the logs for more information.
0058Failed to expand the buffer.Contact support.
0059Failed to parse: No valid tag stored.Check the logs for more information or contact support.
0060no implementation foundThis error can occur if you use a remote session store and no application ID (application-id) has been configured as context parameter (context-param) in the web.xml file. For more information, see the Limitations chapter in MySQLSessionStoreServlet.
0061Provider_1_0::notifyProvider failedContact support.
0062Provider_1_0::notifyProvider failed FATALContact support.
0063can't decode some base62 input. Invalid formatContact support.
0064unknown Request-Source. One of 'AUTH', 'ENV', 'PARAM', 'HEADER', 'SESSION', or 'CONST' expectedCheck your configuration (especially the web.xml file).
0065unsupported sourceCheck your configuration (especially the web.xml file).
0066enumname has already been addedContact support.
0067enumname missingContact support.
0068enumname not foundCheck your configuration (especially the web.xml file).
0069the setupAndRegister() has already been calledContact support.
0070no mutex-manager defined. Did you call setupAndRegister().Contact support.
0071the new file could not be reloadedThe file of a dynamic file parameter could not be loaded. Possible causes: syntax error in the file, permission problems, etc. Check the log for more details.
0072can't add any file any more. The setupAndRegister() has already been calledContact support.
0073Pragma: block-begin'/'Pragma: block-end' is not supported for the given attributeCheck your configuration (especially the web.xml file).
0074due to an internal error, you have to set 'Pragma: break' for the given attributeSet 'Pragma: break' for the given attribute and Contact support.
0075a given value is not a numberCheck your configuration (especially the web.xml file).
0076a given value is not validCheck your configuration (especially the web.xml file).
0077the normalizedStr is not a validCheck your configuration (especially the web.xml file).
0078unknown booleanCheck your configuration (especially the web.xml file).
0079the object has an invalid class (expected: ChainFromConfigBuilder)Contact support.
0080an empty file is not allowed if 'ExpectedClassName' or 'ExpectedFilterName' is configured. All request passing through this filter will be blockedThis error occurs only during startup. If the configured ConfigFile in a DynamicConfigFilter is empty, then all requests going through this DynamicConfigFilter are blocked (status-code 500). Valid content can be added on a running instance, and if there is no configuration error in the new file, the proxy automatically maps this new filter.
0081Invalid configuration. All request passing through this filter will be blockedThis error occurs only during startup. If the configured ConfigFile in a DynamicConfigFilter contains an error, then all requests going through this DynamicConfigFilter are blocked (status-code 500). Valid content can be added on a running instance, and if there is no configuration error anymore, the proxy automatically maps this new filter.