BASE

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

Major	Minor	Message	Details
BASE	0001	TokenizedOutputStream received an illegal terminated buffer.	Contact support.
	0002	Illegal status of buffer.	Check the logs for more information or contact support.
	0003	Illegal store size (smaller than zero).	Contact support.
	0004	Failed to expand the buffer.	Contact support.
	0005	No valid token stored.	Check the logs for more information.
	0006	Exception occurred during parsing the header.	Check the logs for more information.
	0007	Cookie manager found unknown cookie rule.	Check the logs for more information.
	0008	Cookie manager found unknown cookie rule.	Check the logs for more information.
	0009	You have to specify either 'size:' or 'time:' as rotation policy. Ignoring the rotation policy.	Check the configuration of the AuditFilter.
	0010	You can't specify 'size:' and 'time:' as rotation policy. Ignoring the rotation policy.	Check the configuration of the AuditFilter.
	0011	Rotation size is not a number.	Check the configuration of the AuditFilter.
	0012	Maximum size is not a number.	Check the configuration of the AuditFilter.
	0013	The value for rotation time is not valid. Only 'hourly', 'daily', or 'monthly' permitted. Ignoring value.	Check the configuration of the AuditFilter.
	0014	Failed to clean up output stream: bytes pending.	Contact support.
	0015	Failed to clean up output stream: IOException occurred.	Check the logs for more information.
	0016	Failed to clean up output stream: Exception occurred.	Check the logs for more information.
	0017	Failed to clean up output stream: unknown exception occurred.	Contact support.
	0018	Invalid arguments (no buffer or negative length).	Contact support.
	0019	Invalid arguments (no buffer, no null-terminations, or negative length)	Contact support.
	0020	Parsing pending buffer failed.	Check the logs for more information.
	0021	Parsing input failed.	Check the logs for more information.
	0022	Failed to expand the buffer.	Check the logs for more information.
	0023	Disabling parsing in tolerant mode.	Contact support.
	0024	Illegal size for buffer.	Contact support.
	0025	Invalid terminated buffer.	Contact support.
	0026	Not enough data for parsing.	Check the logs for more information.
	0027	IllegalArgumentException occurred.	Check the logs for more information.
	0028	IOException caught during writing in PipedHttpServletResponseWrapper.	Contact support.
	0030	HTMLTagParser error: Illegal character after closing tag name.	Check the logs for more information.
	0032	Too many attributes, a maximum of ISIWEB4_MAX_HTML_TAG_ATTRIBUTES are supported	Contact support.
	0033	Illegal character found in HTML fragment.	Check the logs for more information.
	0034	Failed to parse date, exception occurred.	Check the logs for more information.
	0035	Found unknown escape character. Ignoring it.	Check the logs for more information.
	0036	Received an unsupported Content-Encoding.	The body may not be rewritten.
	0037	Received an unsupported Content-Encoding.	The body may not be rewritten.
	0038	Received 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.
	0039	HTMLDecoder: unsupported charset.	Contact support.
	0040	Decoding failed, could not not convert to given charset.	Check the logs for more information or contact support.
	0041	Not valid charset reference.	Check your configuration.
	0042	Not valid charset reference.	Check your configuration.
	0043	Caught an IOException while substituting attribute value	Check the logs for more information or contact support.
	0045	No 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.
	0046	Exception occurred during the initialization of SecurityManager.	Contact support.
	0047	Failed to clean up SecurityManager.	Contact support.
	0048	Unsupported encoding.	Check your configuration.
	0049	Unsupported encoding.	Check your configuration.
	0050	Input not null-terminated.	Contact support.
	0051	Unexpected Parsing-Code for option-tag	Check the logs for more information.
	0052	Error while parsing HTML fragment.	Check the logs for more information.
	0053	Error while parsing HTML fragment.	Set the parsing mode to "tolerant" if you want to recover gracefully.
	0054	No valid tag found, parsing will be aborted.	Check the logs for more information.
	0055	Prefix in buffer is longer than marker	Check the logs for more information or contact support.
	0056	Illegal parsing state while trying to complete a buffer.	Check the logs for more information.
	0057	Illegal store size.	Check the logs for more information.
	0058	Failed to expand the buffer.	Contact support.
	0059	Failed to parse: No valid tag stored.	Check the logs for more information or contact support.
	0060	no implementation found	This 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.
	0061	Provider_1_0::notifyProvider failed	Contact support.
	0062	Provider_1_0::notifyProvider failed FATAL	Contact support.
	0063	can't decode some base62 input. Invalid format	Contact support.
	0064	unknown Request-Source. One of 'AUTH', 'ENV', 'PARAM', 'HEADER', 'SESSION', or 'CONST' expected	Check your configuration (especially the web.xml file).
	0065	unsupported source	Check your configuration (especially the web.xml file).
	0066	enumname has already been added	Contact support.
	0067	enumname missing	Contact support.
	0068	enumname not found	Check your configuration (especially the web.xml file).
	0069	the setupAndRegister() has already been called	Contact support.
	0070	no mutex-manager defined. Did you call setupAndRegister().	Contact support.
	0071	the new file could not be reloaded	The 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.
	0072	can't add any file any more. The setupAndRegister() has already been called	Contact support.
	0073	Pragma: block-begin'/'Pragma: block-end' is not supported for the given attribute	Check your configuration (especially the web.xml file).
	0074	due to an internal error, you have to set 'Pragma: break' for the given attribute	Set 'Pragma: break' for the given attribute and Contact support.
	0075	a given value is not a number	Check your configuration (especially the web.xml file).
	0076	a given value is not valid	Check your configuration (especially the web.xml file).
	0077	the normalizedStr is not a valid	Check your configuration (especially the web.xml file).
	0078	unknown boolean	Check your configuration (especially the web.xml file).
	0079	the object has an invalid class (expected: ChainFromConfigBuilder)	Contact support.
	0080	an empty file is not allowed if 'ExpectedClassName' or 'ExpectedFilterName' is configured. All request passing through this filter will be blocked	This 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.
	0081	Invalid configuration. All request passing through this filter will be blocked	This 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.