The following are error, warning, and informational codes for the iConsole log file:
Reason:
An incorrect CMS name was specified during a login.
Reason:
An invalid IIS Session was specified during an operation.
Reason:
Not currently used.
Reason:
The search definition file was not valid XML. <details> will list the syntax and semantic validation errors.
Reason:
Indicates that the installation of a search definition file was successful.
Reason:
Indicates that some search definitions could not be installed.
Reason:
Indicates how many search definitions were successfully published. <details> lists the names of these published search definitions.
Reason:
Indicates how many search definitions were successfully published and how many were not published. <details> lists the names of each of these search definitions.
Reason:
Indicates how many search definitions were successfully unpublished. <details> lists the names of these unpublished search definitions.
Reason:
Indicates how many search definitions were successfully unpublished and how many were not unpublished. <details> lists the names of each of these search definitions.
Reason:
Indicates how many search definitions were successfully uninstalled. <details> lists the names of each of these search definitions.
Reason:
An attempt was made to move or delete a search that is referenced by a saved or derived search.
Reason:
Indicates a search definition was successfully updated with new details, e.g. name or description.
Reason:
Indicates a customized search was successfully saved.
Reason:
Indicates a customized search was not saved because a search of that name already exists.
Reason:
Indicates a number of customized searches were successfully deleted. <details> lists the names of these search definitions.
Reason:
Indicates how many customized searches were successfully deleted and how many were not deleted. <details> lists the names of each of these search definitions.
Reason:
Indicates a successful execution of a search query.
Reason:
Indicates a failure to access the specified search. <details> lists the names of these search definitions. This often occurs for a saved or derived search where the baseline search that it was created from has been moved or deleted.
Reason:
Indicates an unsuccessful execution of a search query. <details> contains more information about the specific nature of the problem (for example, a database error message).
Reason:
Shown when the displayed search results have timed out and have been removed from the cache to save machine resources.
Reason:
The XML document being processed for an operation was not valid XML. This is an internal error indicating that the XML passed to a Web Service failed validation.
Reason:
Search definition parameters can be assigned a position in the call to the stored procedure. If there are 'n' arguments for the stored procedure, the position specified must be between 1 and 'n'.
Reason:
Two parameters in the search definition have been assigned the same position for the call to the stored procedure.
Reason:
Successful installation of one or more search definitions. <details> lists the names of each of these search definitions.
Reason:
Unsuccessful installation of one or more search definitions. <details> lists the names of each of these search definitions.
Reason:
Not currently used.
Reason:
The product was not licensed to allow for content searching.
Reason:
The search database specified in the search definition was not a type supported.
Reason:
The user password expired.
Reason:
The user did not have the privileges needed to access the requested iConsole function.
Reason:
A search was canceled by the user before it had completed.
Reason:
The software version could not be determined (as part of the compatibility check between iConsole and CMS server).
Reason:
The iConsole version was not compatible with the CMS version.
Reason:
An invalid pointer was passed to a method as part of the operation. Usually caused by a previous failure in the infrastructure.
Reason:
The http context could not be accessed (in order to get to the .Net cache).
Reason:
The .Net cache could not be accessed from the http context.
Reason:
The Infrastructure service was not responding.
Reason:
The user attempted to install a file that was not a valid XML file.
Reason:
Not currently used.
Reason:
Not currently used.
Reason:
Not currently used.
Reason:
Not currently used.
Reason:
Not currently used.
Reason:
While a content search was executing, an external event caused the content database to fail to respond within a reasonable time.
Reason:
A user successfully logged on.
Reason:
A user failed to log on.
Reason:
A user password could not be checked if it was still valid due to a problem with the infrastructure or CMS.
Reason:
The password supplied during a logon attempt has expired.
Reason:
A user logged out of the iConsole.
Reason:
An audit mail was successfully sent.
Reason:
An audit mail could not be sent.
The iConsole page could not be loaded and the session was closed.
Reason:
Not currently used.
Reason:
Not currently used.
Reason:
Not currently used.
Reason:
Not currently used.
Reason:
The iConsole webservice version was not compatible with the local infrastructure version.
Reason:
The iConsole front-end web server established a connection with the webservice.
Reason:
Not currently used.
Reason:
Not currently used.
Reason:
Displayed when the webservice is first loaded.
Reason:
Displayed when the webservice is shut down.
Reason:
MAPI could not be initialized.
Reason:
The session was not valid.
Reason:
The datastore services interface was not retrieved. This means that information e.g. event data could not be retrieved from the CMS database.
Reason:
The event interface was not retrieved. This means that event information could not be retrieved from the CMS database.
Reason:
The wellknown string interface could not be retrieved. This means that certain text, e.g. audit field value strings, could not be retrieved from the CMS database.
Reason:
Information about the CMS associated with the session could not be found in the list of cached information in the webservice.
Reason:
Information about the CMS associated with the session could not be found in the list of cached information in the webservice.
Reason:
The event audit interface could not be retrieved. This means that auditing operations could not be performed.
Reason:
The user interface could not be retrieved. This means that user associated operations could not be performed.
Reason:
The user group interface could not be retrieved. This means that group associated operations could not be performed.
Reason:
An error occurred while retrieving the data from an event blob or attachment stream.
Reason:
The number of strings of a particular category was different to the expected number, indicating a problem with the database table.
Reason:
The string containing audit configuration information was in an invalid format.
Reason:
A search was started.
Reason:
A user failed to log on using single sign on.
Reason:
A list policy setting could not be retrieved from the user policy.
Reason:
An enumerated policy setting could not be retrieved from the user policy.
Reason:
A policy setting name could not be determined from the supplied display name. This indicates a misnamed setting in the BasicUserAdmin.xml file.
Reason:
A policy setting display name path could not be determined from the supplied internal name. This indicates an error in the webservice policy processing code.
Reason:
The id of the edited policy was not valid. This indicates an error in the webservice policy processing code.
Reason:
The policy was not loaded successfully and could not be edited. This indicates an error in the infrastructure policy code.
Reason:
An edited policy setting could not be updated because the setting could not be retrieved from policy. This indicates an error in the infrastructure policy code.
Reason:
An edited policy setting could not be updated because the setting could not be retrieved from policy. This indicates an error in the infrastructure policy code.
Reason:
An edited policy setting could not be updated because the setting could not be retrieved from policy. This indicates an error in the infrastructure policy code.
Reason:
An edited policy list setting could not be updated because the list column was not specified in the BasicUserAdmin.xml file.
Reason:
An edited policy setting could not be updated because the column tag was not specified in the BasicUserAdmin.xml file.
Reason:
A numeric policy setting could not be retrieved from the user policy.
Reason:
A text policy setting could not be retrieved from the user policy.
Reason:
A Boolean policy setting could not be retrieved from the user policy.
Reason:
The iConsole would not connect to the Wigan File system to access the search definitions.
Reason:
The remote CMS could not be contacted. This usually indicates a problem with that CMS machine, or connectivity to it.
Reason:
The content database could not be contacted. This usually indicates a problem with that machine, or connectivity to it.
Reason:
The content database could not be contacted. This usually indicates a problem with that machine, or connectivity to it.
Reason:
The content database could not be contacted. This usually indicates a problem with that machine, or connectivity to it.
Reason:
A subgroup with the specified name could not be found in the specified user group. This indicates a problem in the BasicUserAdmin.xml file.
Reason:
A new issue could not be created as part of an audit operation because the database returned a zero value for the new issue id. This indicates a problem with the infrastructure or CMS database.
Reason:
An issue could not be updated as part of an audit operation because the database returned a zero or invalid value for the issue id. This indicates a problem with the infrastructure or CMS database.
Reason:
A search definition had an invalid parameter type.
Reason:
Not currently used.
Reason:
Not currently used.
Reason:
Displayed when a search is run to show the search criteria.
Reason:
Displayed when a search completes to show how long it took and how many results were returned.
Reason:
Displayed when a search fails to complete. <details> will contain a reference to a later error code.
Reason:
The security ID configuration was incorrect for a search.
Reason:
The Security ID facility was not configured correctly. Either the registry setting 'UserSIDAttribute' could not be read, or was blank.
Reason:
The Security ID facility was configured, but the search definition did not specify a column to contain the Security ID.
This message is displayed to the user, so gives less technical detail.
Reason:
The search definition did not have a $SID column defined in the results and SID checking is enabled.
In contrast to the previous message, this error message is written to the log file for the benefit of the administrator.
Reason:
The security ID returned in a set of search results did not match any of the allowed IDs in the user's security ID list.
This message is displayed to the user, so gives less technical detail.
Reason:
The security ID returned in a set of search results did not match any of the allowed IDs in the user's security ID list.
In contrast to the previous message, this error message is written to the log file for the benefit of the administrator.
Reason:
A search query ID was not found in the cached list of queries, possibly due to it having timed out already.
Reason:
Information for a specified session could not be found in the information cached in the webservice.
Reason:
The infrastructure did not return a default CMS name for populating the iConsole connect page. This usually indicates a problem with the infrastructure.
Reason:
An attempt was made to associate multiple users to an issue, and the underlying CMS schema does not support this feature.
Reason:
An unsuccessful attempt was made to associate multiple users to an issue.
Reason:
A search was canceled by the user using the cancel button on the progress popup.
Reason:
Information logged about the total number of records when a user with unlimited search capability requests an unlimited search.
Reason:
Warning displayed after an email is released from quarantine, but a quarantine manager service is not registered.
Reason:
Shown when the information required to support auditing operations has not yet been configured in the administration console.
Reason:
A policy setting was not updated because the supplied display value was not found in the list of enumerated items. This indicates a problem with the BasicUserAdmin.xml file.
Reason:
A policy setting was not updated because the supplied index value was not found in the list of enumerated items. This indicates a problem with the BasicUserAdmin.xml file.
Reason:
Shown when the iConsole searches are being upgraded.
Reason:
Shown when the iConsole searches need to be upgraded.
Reason:
Message logged when the iConsole searches upgrade starts.
Reason:
Message logged when the iConsole searches upgrade completes successfully.
Reason:
Message logged when the iConsole searches upgrade fails to complete successfully.
Reason:
Message logged when the iConsole searches are being upgraded.
Reason:
Message logged when the iConsole searches upgrade completes successfully.
Reason:
Message logged when the iConsole searches upgrade fails to complete successfully.
Reason:
The iConsole Front-end web server was unable to contact the iConsole Application server. This indicates a problem with the webservice or connectivity to the webservice machine (if the web server is on a separate machine).
Reason:
Shown when a content search fails to run. <details> contains the error message returned from the content database.
Reason:
Searching by groups was requested for a content search but the content proxy did not support the feature.
Reason:
Not currently used.
Reason:
Shown when search results are exported from the iConsole in a variety of formats, e.g. csv.
Reason:
Shown when an export of search results from the iConsole were requested, but no format was specified. This is probably due to an error in the search definition.
Reason:
An attempt to export search results failed. This is usually a result of an error in the format stylesheet or the post processor. <details> contains the error messages returned from the transform engine or post‑processor.
Reason:
Search results could not be displayed because the search identifier specified did not belong to the current session.
Reason:
An attempt was made to get the temporary copy of a modified search, but it had been discarded because it had not been used recently.
Reason:
Searching by users by ID was requested for a content search but the content proxy did not support the feature.
Reason:
A zip file used to encompass the content of a mail could not be created in a temporary folder on the webservice machine. A possible cause of this could be insufficient permissions to the windows temp folder.
Reason:
Not currently used.
Reason:
Shown when an audit button operation is started.
Reason:
Shown when an audit button operation completes.
Reason:
Shown when an audit button operation completes.
Reason:
Searching for file events was requested for a content search but the content proxy did not support the feature.
Reason:
The custom search definition being saved was empty.
Reason:
Not currently used.
Reason:
A search file upgrade failed.
Reason:
The iConsole session tracking initialization failed.
Reason:
The default preferences file could not be retrieved from the CMS database.
Reason:
The default preferences file failed XML validation. This indicates a problem with the file itself.
Reason:
Reading the default preferences file caused an XML error. This indicates a problem with the file itself.
Reason:
Failed to read the user's preferences file: <details> Default preferences have been used.
Reason:
The user preferences file could not be retrieved from the CMS database.
Reason:
A search definition file could not be retrieved from the CMS database due to an error. <details> contains further information.
Reason:
A search definition file could not be retrieved from the CMS database because its name could not be determined. <details> contains further information.
Reason:
The user preferences file could not be retrieved from the CMS database.
Reason:
Shown after an attempt to delete one or more search definitions. <details> contains further information.
Reason:
The WebServiceThreadpoolSize registry setting could not be applied.
Reason:
An error occurred that had not been anticipated in the named module. <details> contains details of the nature of the error.
Reason:
An error occurred while processing XML data that had not been anticipated. A traceback of the location of the problem is given along with specific details of the error.
Reason:
An unexpected exception was thrown.
Copyright © 2014 CA.
All rights reserved.
|
|