LiveCycle ES3 Error Code Reference

Error codes may be written to log files when you are installing, configuring, or running LiveCycle ES3. For each error code, there is a probable cause and an action you can take to resolve the error. These error codes are grouped according to component or activity.

error codes

Code	ALC-DCT-002-064 ()
Type	Error
Cause	Binding of data dictionary element with name "{0}" at path "{1}" contains invalid character "{2}".
Action	Please ensure that no invalid character exists in the binding.

Code	ALC-DCT-002-065 ()
Type	Error
Cause	Binding of data dictionary element with name "{0}" at path "{1}" starts with the invalid root element.
Action	Please ensure that binding starts with valid root element.

Code	ALC-DCT-002-066 ()
Type	Error
Cause	Binding of data dictionary element with name "{0}" at path "{1}" contains invalid value - "{2}".
Action	Please ensure that binding cotains a valid value.

Code	ALC-DCT-002-067 ()
Type	Error
Cause	The values in value set of data dictionary element with name "{0}" at path "{1}" are not compatible with it's data type.
Action	Please ensure that values are compatible with data type.

Code	ALC-DCT-003-015 ()
Type	Error
Cause	Data dictionary with name: {0} is already published.
Action	A published DD can not be published again.

Code	ALC-DCT-003-016 ()
Type	Info
Cause	Data dictionary with name: {0} is already on the last published version.
Action	There is no change in the data dictionary after last publish operation, so you can not revert this data dictionary.

Code	ALC-DCT-003-017 ()
Type	Error
Cause	Error while parsing expression: {0}.
Action	Please ensure that expression follows correct syntax.

Code	ALC-DCT-003-020 ()
Type	Error
Cause	Data Dictionary Element passed to the API is non computed.
Action	Please ensure that only computed Data Dictionary Elements are passed to this API.

Code	ALC-DCT-005-001 ()
Type	Error
Cause	Error in reading localized data stream for Data Dictionary.
Action	Please contact system administrator.

Code	ALC-DCT-005-002 ()
Type	Error
Cause	Error in writing localized data stream for Data Dictionary.
Action	Please contact system administrator.

Code	ALC-DCT-005-003 ()
Type	Error
Cause	Error in exporting Localization Information.
Action	Please contact sytem administrator.

Code	ALC-DCT-005-004 ()
Type	Error
Cause	Error in importing Localization Information.
Action	Please check the format of zip file.

Code	ALC-ACM-002-206 ()
Type	Error
Cause	Repository contains updated version of used Layout or Fragment Layouts with id [{0}]. Fields/TargetAreas have been added/removed. Please reload this letter.
Action	Please reload this letter.

Code	ALC-ACM-002-207 ()
Type	Error
Cause	Repository contains updated version of used DataModule with id [{0}]. Data Dictionary reference in the DataModule has been changed. Please reload this asset.
Action	Please reload this asset.

Code	ALC-ACM-002-208 ()
Type	Error
Cause	Repository contains updated version of used DataModule with id [{0}]. Variables in the DataModule have been added/removed. Please reload this asset.
Action	Please reload this asset.

Code	ALC-ACM-002-209 ()
Type	Error
Cause	Repository contains updated version of this asset. Please reload this asset.
Action	Please reload this asset.

Code	ALC-ACM-006-002 ()
Type	Error
Cause	One or more Data Dictionary Elements have been deleted that are being used in other Templates or Data Modules.
Action	Please ensure that deleted Data Dictionary Elements are not being used in any asset.

Code	ALC-ACM-006-003 ()
Type	Error
Cause	Error in reading localized data stream for asset.
Action	Please contact system administrator.

Code	ALC-ACM-006-004 ()
Type	Error
Cause	Error in writing localized data stream for asset.
Action	Please contact system administrator.

Code	ALC-ACM-008-001 ()
Type	Error
Cause	Error in exporting Localization Information.
Action	Please contact system administrator.

Code	ALC-ACM-008-002 ()
Type	Error
Cause	Error in importing Localization Information.
Action	Please check the zip file format.

Application and Services error codes

Code	ALC-AAC-003-000 (Application and Services)
Type	Error
Cause	Required parameter was null when configuring a service or an endpoint.
Action	Specify the required parameter.

Code	ALC-AAC-004-000 (Application and Services)
Type	Error
Cause	Endpoint category with the specified name already exists.
Action	Endpoint category name must be unique. Choose a different name when adding the category.

Code	ALC-AAC-006-000 (Application and Services)
Type	Error
Cause	Error occurred when previewing archive. The archive file is corrupted or invalid, which prevents previewing the content of the LiveCycle archive (LCA) file.
Action	Re-export the LCA and then open it to review its content.

Code	ALC-AAC-007-000 (Application and Services)
Type	Error
Cause	Unexpected archive status. Archive status when import, preview or removal is successful is reported as Import Complete, Preview Complete, or Remove Complete. Any other status indicates an import error, a preview error, a removal error or an unknown error.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-AAC-008-000 (Application and Services)
Type	Error
Cause	Error importing archive. The archive is corrupt. Possible cause: components described in the application descriptor (application.xml) are not included in the archive file (.lca) or the application descriptor has an invalid entry.
Action	Re-export the LCA.

Code	ALC-AAC-009-000 (Application and Services)
Type	Error
Cause	Error removing archive.
Action	Removal of LCA content failed (for example, a process, a resource, an endpoint imported with the LCA). See the server log for more details. The forced removal of LCAs is supported and this exception would rarely be seen.

Code	ALC-AAC-010-000 (Application and Services)
Type	Error
Cause	An archive already exists with ID [application name]. The application name for imported archives must be unique.
Action	Rename application by opening the LCA file and changing the application ID in application.xml file.

Code	ALC-AAC-011-000 (Application and Services)
Type	Error
Cause	Failed to locate the archive. User attempted to perform an action with an archive ID that could not be located. The archive was deleted while the user attempted the perform the action.
Action	Reimport the archive.

Code	ALC-AAC-012-000 (Application and Services)
Type	Error
Cause	Failed to locate category. The user attempted to perform an action with a category ID that could not be located. The category was removed while the user attempted to perform the action.
Action	Add the same category again.

Code	ALC-AAC-013-000 (Application and Services)
Type	Error
Cause	Error viewing archive. An error occurred while opening a specific archive for viewing.
Action	Ensure that all archive components are deployed.

Code	ALC-AAC-014-000 (Application and Services)
Type	Error
Cause	Failed to load system context. An error occurred while attempting to retrieve the User Management system context.
Action	Log in to the Administration Console again.

Code	ALC-AAC-015-000 (Application and Services)
Type	Error
Cause	Failed to locate endpoint. User attempted to perform an action with an endpoint that could not be located.
Action	Add a new endpoint.

Assembler error codes

Code	ALC-ASM-N00-000 (Assembler)
Type
Cause	Assembler Version: {0}
Action	An information message displaying the Assembler version number.

Code	ALC-ASM-N00-001 (Assembler)
Type
Cause	{0}: {1} {2}
Action	An information message displayed during normal operations.

Code	ALC-ASM-S00-001 (Assembler)
Type	Error
Cause	DDX was null. It is required.
Action	The DDX object passed to the invoke() method was null. It is required.

Code	ALC-ASM-S00-002 (Assembler)
Type	Error
Cause	Failed to execute the DDX - error messages provided.
Action	DDX Execution error. The error message is provided along with a stack trace if available. Corrective action is based on any messages or warnings present.

Code	ALC-ASM-S00-003 (Assembler)
Type	Error
Cause	Passivating the log document failed.
Action	An error occurred while attempting to convert the job log to a com.adobe.idp.Document object to return to the client. The exception includes an error message to indicate the root cause. This error may also occur if the document storage partition is full.

Code	ALC-ASM-S00-004 (Assembler)
Type	Error
Cause	Cannot connect to the FontManager.
Action	The FontManager could not be contacted. Verify that the FontManager is properly installed. Use the JMX console to verify that it is currently running.

Code	ALC-ASM-S00-005 (Assembler)
Type	Error
Cause	Failed to acquire result content for {0} referencing {1}.
Action	An error occurred while trying to read the content for a result. The content was created, but could not be read from the disk file or input stream. This error occurs during low disk space or low memory conditions.

Code	ALC-ASM-S00-006 (Assembler)
Type	Error
Cause	Failed to passivate document for {0}.
Action	An error occurred while trying to passivate the content for a result. This error can occur if the global temporary storage directory is full or unavailable.

Code	ALC-ASM-S00-007 (Assembler)
Type	Error
Cause	Invalid result document for {0}; type was {1}.
Action	There was no result document for a result node in the DDX or its type is unknown. This is an internal logic error; report it to Customer Support.

Code	ALC-ASM-S00-008 (Assembler)
Type	Error
Cause	Invalid PDF source document for {0}.
Action	The document provided as a PDF source was invalid. Verify that the document is not corrupted or the content is PDF content.

Code	ALC-ASM-S00-009 (Assembler)
Type	Error
Cause	Invalid XDP source document for {0}.
Action	The document provided as an XDP source was invalid. Verify that the document is not corrupted or the content is an XDP containing a PDF document.

Code	ALC-ASM-S00-010 (Assembler)
Type	Error
Cause	The document named "{0}" could not be opened.
Action	The document could not be opened. A chained exception provides details on the cause. The most common causes are a corrupt document, an I/O error, or a security-related error.

Code	ALC-ASM-S00-011 (Assembler)
Type	Error
Cause	The shared DOM named "{0}" could not be cloned.
Action	The shared DOM could not be cloned. A chained exception provides details on the cause.

Code	ALC-ASM-S00-012 (Assembler)
Type	Error
Cause	An error ocurred while closing the document named "{0}".
Action	An error occurred while saving the specified document. Corrective action depends on the provided cause. The most common causes are a corrupt document, a security error, or an I/O error. Processing continues, but an exception resulting in excess memory consumption or excess file handle consumption.

Code	ALC-ASM-S00-013 (Assembler)
Type	Error
Cause	The system context could not be obtained from UserManager.
Action	The system context from UserManager was missing or unavailable. The causing exception is provided indicating an installation problem.

Code	ALC-ASM-S00-014 (Assembler)
Type	Error
Cause	The DDX does not reference the PDF source as 'inDoc' or the PDF source is missing.
Action	An error occurred executing AssemblerServiceClient.invokeOneDocument(). The given DDX does not reference the PDF source as "inDoc" or the PDF source is missing.

Code	ALC-ASM_S00_015 (Assembler)
Type	Error
Cause	The operation was successful, but generated too many documents to return. Use the invokeDDX() method.
Action	An error occurred executing AssemblerServiceClient.invokeOneDocument(). The given DDX resulted in more than one result Document.

Code	ALC-ASM-S01-004 (Assembler)
Type	Error
Cause	Failed to convert content for {0}.
Action	An error occurred while trying to convert a document for transfer into or out of this service. The cause is provided. This error occurs during low disk space or low memory conditions or by corrupted document content.

Code	ALC-ASM-W00-001 (Assembler)
Type	Warning
Cause	Invalid log level {0} specified. Using {1} instead.
Action	An invalid or unknown log level was specified. A default was used instead.

Code	ALC-ASM-W00-002 (Assembler)
Type	Warning
Cause	Log messages are being logged at the "{0}" level, which will impact performance. This setting is not recommended for production - use INFO or greater.
Action	The logging subsystem generates low-level debugging messages for this job, affecting performance.

Code	ALC-ASM-W00-003 (Assembler)
Type	Warning
Cause	Obsolete.
Action	Message W00-003 is available for reassignment.

Code	ALC-ASM-W00-004 (Assembler)
Type	Warning
Cause	Obsolete.
Action	Message W00-004 is available for reassignment.

Code	ALC-ASM-W00-005 (Assembler)
Type	Warning
Cause	The xpath expression {0} could not be evaluated. This entry will not be included in the input map.
Action	The indicated XPath expression was not found or evaluated within the process context. The corresponding entry is not included in the input map. This failure results in a fatal error if the input was required for DDX execution. If the omission was intentional, ignore this warning.

Code	ALC-ASM-W00-006 (Assembler)
Type	Warning
Cause	The input map key {0} of type {1} is an unknown type and could not be converted to a document. This entry will not be included in the input map.
Action	The indicated input map object was an unknown class and could not be converted to a com.adobe.idp.Document object. The object is not included in the input map during processing. Verify that the contents of the input map conform to the required inputs.

Code	ALC-ASM-W00-007 (Assembler)
Type	Warning
Cause	Document {0} failed to close. Cause provided.
Action	The specified document failed to close properly. A cause is provided, investigate and correct. Processing continues but future attempts to use the same document may fail.

Code	ALC-ASM_W00_008 (Assembler)
Type	Warning
Cause	Multiple XPaths : the XPath used is "{0}" from the Process URI "{1}"
Action	More than one XPath was provided (either to data or as a function). The first function XPath provided in the Query component of the Process URI takes precedence over a data XPath in the Path component. scheme:[//Authority][Path][?Query][#Fragment] process:[//[host:port][/lc-xpath-data] [?lc-xpath-function;prop=val;...][#name] Note: there are no properties identified for Process URIs at this time.

Code	ALC-ASM_W00_009 (Assembler)
Type	Warning
Cause	Invalid URL: {0}
Action	The URL syntax was invalid and could not be evaluated. The object is not included for processing resulting in a fatal error if the content referenced by the URL is required. Fix the syntax of the URL.

Code	ALC-ASM_W00_010 (Assembler)
Type	Warning
Cause	Server Signature compatibility could not be determined. Default will be used.
Action	The server signature compatibility could not be determined. The default is used.

Code	ALC-ASM-S01-001 (Assembler)
Type	Error
Cause	The {0} service failed during the {1} operation.
Action	// ASM_A01_### DocBuilder An error occurred while calling the indicated external service. A causing exception is provided. Corrective action depends on the chained exception.

Code	ALC-ASM-S01-002 (Assembler)
Type	Error
Cause	{0} service status: {1}
Action	An error occurred while calling the indicated external service. A causing exception is provided. Corrective action depends on the chained exception.

Code	ALC-ASM-S01-003 (Assembler)
Type	Error
Cause	The {0} service is not installed.
Action	An error occurred while calling the indicated external service because it does not appear to be installed. Try installing (or reinstalling) the service, and then retry the job.

Code	ALC-ASM-W01-001 (Assembler)
Type	Warning
Cause	The signature service failed to verify the signature named {0} in document {1}.
Action	An error occurred while calling the signature service to verify a signature. Check to see if the field was signed using a custom signature handler.

Barcoded Forms error codes

Code	ALC-BCF-002-001 (Barcoded Forms)
Type	Error
Cause	No image iterator for the input document. The input image format is not supported for decoding.
Action	Provide a TIFF format.

Code	ALC-BCF-002-003 (Barcoded Forms)
Type	Error
Cause	IOException: Unable to read the input document to be decoded.
Action	Verify that the input is a valid document.

Code	ALC-BCF-002-004 (Barcoded Forms)
Type	Error
Cause	PDFException: The barcode images could not be extracted from the input PDF.
Action	Verify that the input document is not a dynamic PDF.

Code	ALC-BCF-002-006 (Barcoded Forms)
Type	Error
Cause	Exception in conversion to serializable DOM.
Action	Contact Adobe Technical Support.

Code	ALC-BCF-005-006 (Barcoded Forms)
Type	Error
Cause	Error in tokenizer. There is a problem in the data decoded from the barcode.
Action	Verify that the value encoded in the barcode is properly delimited using different field and line delimiters. Ensure that field value does not contain the delimiters.

Code	ALC-BCF-010-001 (Barcoded Forms)
Type	Error
Cause	There is a problem in the data decoded from the barcode. The data does not contain a tokenizable pair for given delimiters.
Action	Verify that the value encoded in the barcode is properly delimited using different field and line delimiters.

Code	ALC-BCF-003-004 (Barcoded Forms)
Type	Error
Cause	Unable to decompress the data from barcode due to a flate decompressor error.
Action	Ensure that the data is compressed using flat compression.

Code	ALC-BCF-001-001 (Barcoded Forms)
Type	Warning
Cause	Warning logged whenever there is an unexpected behaviour in Barcoded Forms Service
Action	Contact the System administrator

Code	ALC-BCF-003-001 (Barcoded Forms)
Type	Error
Cause	Exception thrown when unable to decrypt the barcode data
Action	Verify the input files sent for barcode scanning and decoding to the Barcoded Forms Service

Code	ALC-BCF-003-002 (Barcoded Forms)
Type	Error
Cause	Exception thrown when unable to decrypt the barcode data
Action	Verify the barcodes present in the input files

Code	ALC-BCF-003-003 (Barcoded Forms)
Type	Error
Cause	Unable to decrypt the data present in the barcode
Action	Verify the barcodes present in the input files

Code	ALC-BCF-003-005 (Barcoded Forms)
Type	Error
Cause	Cannot load keystore file while decrypting data in a barcode
Action	Contact the System administrator

Code	ALC-BCF-004-001 (Barcoded Forms)
Type	Error
Cause	The barcode coordinates are out of bound. Must be a decimal between 0.0 and 1.0.
Action	Contact the System administrator

Code	ALC-BCF-006-001 (Barcoded Forms)
Type	Error
Cause	The Crypto-J JCE Provider is disabled. Unable to decrypt the encrypted barcode data.
Action	Contact the System administrator.

Code	ALC-BCF-006-003 (Barcoded Forms)
Type	Error
Cause	RC4 decryption failed. Unable to decrypt the encrypted barcode data.
Action	Contact the System administrator.

Code	ALC-BCF-006-006 (Barcoded Forms)
Type	Error
Cause	RSA decryption failed. Unable to decrypt the encrypted barcode data.
Action	Contact the System administrator.

Code	ALC-BCF-007-002 (Barcoded Forms)
Type	Error
Cause	Cannot find the SHA-1 algorithm. Used for internal processing.
Action	Contact the System administrator.

Code	ALC-BCF-009-001 (Barcoded Forms)
Type	Error
Cause	Problem while xml processing. Application encounters this error when it expects to get XML at some place during processing but gets non-xml content.
Action	Contact the System administrator

Code	ALC-BCF-009-002 (Barcoded Forms)
Type	Error
Cause	Unable to create an xml parser.
Action	Contact the System administrator

Code	ALC-BCF-009-003 (Barcoded Forms)
Type	Error
Cause	XML parser failed, IO error. Problem in xml processing in the application
Action	Contact the System administrator

Code	ALC-BCF-009-004 (Barcoded Forms)
Type	Error
Cause	XML parser failed, parser error.
Action	Check the inputs sent

Code	ALC-BCF-012-001 (Barcoded Forms)
Type	Error
Cause	Unsupported character encoding. Exception encountered during some internal processing
Action	Contact the System administrator

Code	ALC-BCF-012-002 (Barcoded Forms)
Type	Error
Cause	Data tokenizer error.Exception encountered during some internal processing
Action	Contact the System administrator

Code	ALC-BCF-012-003 (Barcoded Forms)
Type	Error
Cause	Dom Parser error.Exception encountered during some internal processing.
Action	Contact the System administrator

Central Migration Bridge service error codes

Code	ALC-CMB-001-001 (Central Migration Bridge service)
Type	Error
Cause	The specified Adobe Central Output Server installation directory is not valid or the LiveCycle user do not have appropiate permissions.
Action	Specify correct Adobe Central Output Server installation directory; where Central executables are present; in the Service Configuration. If Central executables are there at the specified location make sure that user has appropriate rights on the folders in directory path. See server logs and documentation for more details.

Code	ALC-CMB-001-002 (Central Migration Bridge service)
Type	Error
Cause	Central Executable returned with some error code.
Action	Check that correct input parameters were supplied to the service. See server logs for more details.

Code	ALC-CMB-001-003 (Central Migration Bridge service)
Type	Warning
Cause	Dump of command line parameters used to invoke the central executable.
Action	Information only; no action required.

Code	ALC-CMB-001-005 (Central Migration Bridge service)
Type	Error
Cause	Service could not find configuration file (.ini or .xci file) at the location specified.
Action	Check that the configuration files for the central executable are present in the location specified. See server logs for more details.

Code	ALC-CMB-001-006 (Central Migration Bridge service)
Type	Warning
Cause	Information on where the service is looking for the configuration files.
Action	Information only; no action required.

Code	ALC-CMB-001-007 (Central Migration Bridge service)
Type	Error
Cause	Service could not find configuration file (.ini/.xci) in the default location.
Action	Check that the configuration file exists at the default location.

Code	ALC-CMB-001-008 (Central Migration Bridge service)
Type	Error
Cause	Exception encountered in invoking central executable.
Action	Check that the Adobe Central Output Server executables are present in its Installation Directory and the installation is not corrupt.

Code	ALC-CMB-001-009 (Central Migration Bridge service)
Type	Error
Cause	Service encountered exception in running central executable.
Action	Check that correct input parameters were supplied to the service. See server log for more details.

Code	ALC-CMB-001-010 (Central Migration Bridge service)
Type	Error
Cause	Service execution was interrupted in between.
Action	See server logs for more details.

Code	ALC-CMB-001-011 (Central Migration Bridge service)
Type	Error
Cause	Service encountered error while logging Adobe Central Output Server logging information
Action	See server logs for more details.

Code	ALC-CMB-001-004 (Central Migration Bridge service)
Type	Info
Cause	Working directory location
Action	No action needed

Configuration Manager error codes

Code	ALC-LCM-000-001 (Configuration Manager)
Type
Cause	JDK version {0} does not meet minimum supported version {1}. \nConfiguration Manager cannot be launched until JDK version requirement is satisfied.
Action	Set JAVA_HOME to the supported JDK version that is listed in Preparing to Install LiveCycle Single Node or Preparing to Install LiveCycle Clustering.

Code	ALC-LCM-000-002 (Configuration Manager)
Type
Cause	JDK version {0} exceeds the maximum supported version {1}. \nConfiguration Manager cannot be launched until JDK version requirement is satisfied.
Action	Set JAVA_HOME to the supported JDK version that is listed in Preparing to Install LiveCycle Single Node or Preparing to Install LiveCycle Clustering.

Code	ALC-LCM-000-003 (Configuration Manager)
Type
Cause	JDK version {0} does not meet the supported version {1}. \nConfiguration Manager cannot be launched until JDK version requirement is satisfied.
Action	Set JAVA_HOME to the supported JDK version that is listed in Preparing to Install LiveCycle Single Node or Preparing to Install LiveCycle Clustering guide.

Code	ALC-LCM-000-010 (Configuration Manager)
Type
Cause	Installation context undeterminable. Installation may be invalid.
Action	Reinstall the Configuration Manager.

Code	ALC-LCM-000-011 (Configuration Manager)
Type
Cause	Target application server undeterminable or invalid. Installation may be invalid.
Action	Reinstall LiveCycle.

Code	ALC-LCM-000-012 (Configuration Manager)
Type
Cause	Target operating system undeterminable or invalid. Installation may be invalid.
Action	Configuration Manager determines the target application server from the OSFileSetIntendedFor property as set in the {INSTALL_ROOT}\licenses\LFS_Foundation.properties. If this value is missing or does not match a supported value, an error occurs. This error does not display in production. Action is to reinstall.

Code	ALC-LCM-000-013 (Configuration Manager)
Type
Cause	Installation context undeterminable. LCM root directory, {0}, does not exist.
Action	Happens if this directory does not exist. Will not happen in production.

Code	ALC-LCM-000-020 (Configuration Manager)
Type
Cause	Failed to launch Configuration Manager.
Action	Uninstall and reinstall LiveCycle.

Code	ALC-LCM-000-030 (Configuration Manager)
Type
Cause	Failed to load jar into classpath. Jar file {0} does not exist.
Action	Uninstall and reinstall LiveCycle.

Code	ALC-LCM-000-100 (Configuration Manager)
Type
Cause	Failed to load plugin {0}.
Action	Review the logs for more information. Uninstall and reinstall LiveCycle.

Code	ALC-LCM-010-100 (Configuration Manager)
Type
Cause	Failed to configure core.
Action	Review the logs for more information.

Code	ALC-LCM-010-110 (Configuration Manager)
Type
Cause	Failed to find credential with alias {0}
Action	Review the log and application server log for more details.

Code	ALC-LCM-010-111 (Configuration Manager)
Type
Cause	Failed to import credential {0}
Action	Review the Configuration Manager log and application server log for more details.

Code	ALC-LCM-010-112 (Configuration Manager)
Type
Cause	Failed to import credential {0}. \nInvalid password provided.
Action	Review the credential password and try retyping the password in Configuration Manager. Review the Configuration Manager log and application server log for more details.

Code	ALC-LCM-010-120 (Configuration Manager)
Type
Cause	Failed to configure.
Action	Review the Configuration Manager log and application server log for more details.

Code	ALC-LCM-010-200 (Configuration Manager)
Type
Cause	Failed to merge Ears.
Action	Review the Configuration Manager log files for details.

Code	ALC-LCM-010-201 (Configuration Manager)
Type
Cause	Failed to merge Ears. \nFile does not exist {0}.
Action	Uninstall and reinstall LiveCycle.

Code	ALC-LCM-010-300 (Configuration Manager)
Type
Cause	Failed to generate license jar.
Action	Review the Configuration Manager log files for details.

Code	ALC-LCM-030-101 (Configuration Manager)
Type
Cause	Failed to deploy EAR.\nEAR could not be found. LiveCycle must be configured before deployment.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-030-102 (Configuration Manager)
Type
Cause	Failed to deploy EAR.\n{0} does no exist in archive {1}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-030-103 (Configuration Manager)
Type
Cause	Failed to deploy EAR.\nCould not load application info from EAR: {0}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-030-110 (Configuration Manager)
Type
Cause	Failed to deploy EAR.\nCould not undeploy {0}.\nUndeploy manually using application server administration console then try again.
Action	Undeploy EAR file manually by using the application server Administration Console and then try again.

Code	ALC-LCM-030-111 (Configuration Manager)
Type
Cause	Failed to deploy EAR.\nCould not stop application {0}.\nUndeploy manually using application server administration console then try again.
Action	Undeploy EAR file manually by using application server Administration Console and then try again.

Code	ALC-LCM-030-112 (Configuration Manager)
Type
Cause	Failed to deploy EAR.\nCould not deploy {0}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-030-113 (Configuration Manager)
Type
Cause	Failed to deploy EAR.\nCould not start application {0}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-030-200 (Configuration Manager)
Type
Cause	Failed to deploy component {0}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-030-201 (Configuration Manager)
Type
Cause	Failed to deploy component.\nCannot connect to service container.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-030-202 (Configuration Manager)
Type
Cause	Failed to deploy component {0}.\nComponent archive not found on disk.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-030-203 (Configuration Manager)
Type
Cause	Failed to deploy component {0}.\nComponent not found on server.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-030-204 (Configuration Manager)
Type
Cause	Failed to deploy component.\nComponent archives could not be copied to working directory.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-030-205 (Configuration Manager)
Type
Cause	Failed to deploy component.\n{0} does no exist in archive {1}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-030-206 (Configuration Manager)
Type
Cause	Failed to deploy component.\nCould not load component info from Component: {0}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-030-207 (Configuration Manager)
Type
Cause	Failed to deploy component {0}.\nCluster member clock times may not be synchronized. Check logs and cluster configuration.
Action	Cluster member clock times not be synchronized. Review the logs and cluster configuration.

Code	ALC-LCM-030-300 (Configuration Manager)
Type
Cause	Failed to deploy LCA {0}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-030-301 (Configuration Manager)
Type
Cause	Failed to deploy LCA.\nLCA archive {0} not found on disk.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-030-302 (Configuration Manager)
Type
Cause	Failed to deploy LCA.\n{0} does not exist in archive {1}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-030-303 (Configuration Manager)
Type
Cause	Failed to deploy LCA.\nCould not load archive info from EAR: {0}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-035-200 (Configuration Manager)
Type
Cause	Component deployment failed validation for {0}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-035-201 (Configuration Manager)
Type
Cause	Component deployment failed validation for {0}.\nComponent archive not found on disk.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-035-202 (Configuration Manager)
Type
Cause	Component deployment failed validation for {0}.\nComponent component not found on server.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-035-203 (Configuration Manager)
Type
Cause	Component deployment failed validation.\nCannot connect to service container.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-035-300 (Configuration Manager)
Type
Cause	LCA deployment failed validation.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-035-301 (Configuration Manager)
Type
Cause	LCA deployment failed validation.\nLCA {0} is not deployed.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-080-100 (Configuration Manager)
Type
Cause	Failed to generate version report.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-100-000 (Configuration Manager)
Type
Cause	Failed to perform application server operation. {0}
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-100-010 (Configuration Manager)
Type
Cause	Cannot connect to application server.\nApplication server information, login information may be invalid or the server is not running or accessible.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-100-011 (Configuration Manager)
Type
Cause	Cannot connect to application server.\nApplication server host or port may be invalid.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-100-012 (Configuration Manager)
Type
Cause	Cannot connect to application server.\nAdministrator id or password may be invalid.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-100-013 (Configuration Manager)
Type
Cause	Cannot connect to application server.\nTarget server instance {0} does not exist.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-100-014 (Configuration Manager)
Type
Cause	Cannot connect to application server.\nTarget cluster instance {0} does not exist.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-100-020 (Configuration Manager)
Type
Cause	Operation timed out.\nSoap request timeout may not be configured appropriately. Refer to the WebSphere configuration documentation.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-100-030 (Configuration Manager)
Type
Cause	SSL not configured properly.\nEnsure that the certificate is accepted by the host computer.\nThis can be fixed using retrieveSigners.sh/bat.
Action	Ensure the acceptance of the certificate by the host computer.

Code	ALC-LCM-100-040 (Configuration Manager)
Type
Cause	Supported version validation failure.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-100-041 (Configuration Manager)
Type
Cause	Supported version validation failure. \nThe detected version of the target application server is {0} which does not meet the minimum supported version {1}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-100-042 (Configuration Manager)
Type
Cause	Supported version validation warning. \nThe detected version of the target application server is {0} which exceeds the supported version {1}, as known at the time of release.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-100-050 (Configuration Manager)
Type
Cause	Cannot locate server ports for WC_defaulthost or WC_defaulthost_secure in the available virtual hosts\nfor: {0}\nThis may prevent access to the server. \nRefer to the WebSphere configuration documentation.
Action	See the WebSphere Application Server configuration documentation.

Code	ALC-LCM-100-060 (Configuration Manager)
Type
Cause	Server {0} is an administration server.\nOnly managed servers should be used as LiveCycle servers.
Action	Only use managed servers as LiveCycle servers.

Code	ALC-LCM-100-070 (Configuration Manager)
Type
Cause	Server has pending changes that require a restart. Restart the server and re-run configuration.
Action	Restart the server and rerun configuration.

Code	ALC-LCM-101-013 (Configuration Manager)
Type
Cause	Cannot connect to application server.\nTarget server instance {0} does not exist.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-101-014 (Configuration Manager)
Type
Cause	Cannot connect to application server.\nTarget cluster instance {0} does not exist.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-101-020 (Configuration Manager)
Type
Cause	Failed to run JACL scripts.\nCheck logs for further details.
Action	Review the logs for further details.

Code	ALC-LCM-101-030 (Configuration Manager)
Type
Cause	Failed to parse JACL {0} stream ''{1}''
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-110-000 (Configuration Manager)
Type
Cause	Failed to configure application server.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-110-010 (Configuration Manager)
Type
Cause	Failed to configure server settings.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-110-030 (Configuration Manager)
Type
Cause	Failed to configure datasource.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-110-040 (Configuration Manager)
Type
Cause	Failed to get server info.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-110-041 (Configuration Manager)
Type
Cause	Failed to get Edit Lock. Check that no edits are occurring through admin console.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-110-042 (Configuration Manager)
Type
Cause	Server has Unactivated Changes. Check that no edits are pending through admin console.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-110-050 (Configuration Manager)
Type
Cause	Failed to get version info from application server.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-110-110 (Configuration Manager)
Type
Cause	Failed to de-configure datasource.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-110-150 (Configuration Manager)
Type
Cause	Failed to de-configure server settings.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-120-000 (Configuration Manager)
Type
Cause	Server configuration failed validation.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-120-001 (Configuration Manager)
Type
Cause	Server configuration failed validation.\nWrong No. of Web Servers {0}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-120-002 (Configuration Manager)
Type
Cause	Server configuration failed validation.\nError sending validation request.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-120-003 (Configuration Manager)
Type
Cause	Server configuration failed validation.\nHost path invalid {0}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-120-100 (Configuration Manager)
Type
Cause	Server configuration failed validation.\nJVM settings failed.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-120-101 (Configuration Manager)
Type
Cause	Server configuration failed validation.\nUnexpected Thread Count {0}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-120-102 (Configuration Manager)
Type
Cause	Server configuration failed validation.\nUnexpected Socket Reader {0}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-120-103 (Configuration Manager)
Type
Cause	Server configuration failed validation.\nUnexpected Thread Max Time {0}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-120-104 (Configuration Manager)
Type
Cause	Server configuration failed validation.\nExpected JVM arguments not found.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-120-105 (Configuration Manager)
Type
Cause	Server configuration failed validation.\nExpected Xmx setting not found.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-120-106 (Configuration Manager)
Type
Cause	Server configuration failed validation.\nExpected Xms setting not found.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-120-107 (Configuration Manager)
Type
Cause	Server configuration failed validation.\nUnexpected JTA timeout {0}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-120-300 (Configuration Manager)
Type
Cause	Data source settings failed validation.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-120-301 (Configuration Manager)
Type
Cause	Data source settings failed validation.\nFailed to find/lookup datasource {0}. The datasource may not be configured or may have failed to come online.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-120-302 (Configuration Manager)
Type
Cause	Data source settings failed validation.\nFailed to determine database type for datasource {0}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-120-303 (Configuration Manager)
Type
Cause	Data source settings failed validation.\nFailed to connect to database for datasource {0}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-120-304 (Configuration Manager)
Type
Cause	Data source settings failed validation.\nFailed to validate datasource {0}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-120-305 (Configuration Manager)
Type
Cause	Data source settings failed validation.\nCould not execute query: {0}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-130-100 (Configuration Manager)
Type
Cause	Database settings failed validation.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-130-101 (Configuration Manager)
Type
Cause	Database settings failed validation. \nUnsupported database type {0}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-130-102 (Configuration Manager)
Type
Cause	Database settings failed validation. \nDriver class {0} cannot be loaded.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-130-103 (Configuration Manager)
Type
Cause	Database settings failed validation. \nSQL error code
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-130-104 (Configuration Manager)
Type
Cause	Database settings failed validation. \nCould not execute query: {0}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-130-105 (Configuration Manager)
Type
Cause	Database settings failed validation. \nCould not find driver {0} in archive: {1}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-130-106 (Configuration Manager)
Type
Cause	Database settings failed validation. \nCannot locate Schema {0} in database {1}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-140-100 (Configuration Manager)
Type
Cause	Failed to control server.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-140-102 (Configuration Manager)
Type
Cause	Failed to start server {0}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-140-104 (Configuration Manager)
Type
Cause	Failed to stop server {0}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-140-106 (Configuration Manager)
Type
Cause	Failed to determine server type.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-200-001 (Configuration Manager)
Type
Cause	Failed to connect to LiveCycle service container. \nLiveCycle service container information or login information may be invalid or the server is not running or accessible.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-800-001 (Configuration Manager)
Type
Cause	Property file {0} does not exist
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-800-002 (Configuration Manager)
Type
Cause	Missing required property {0} for cluster topology
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-800-003 (Configuration Manager)
Type
Cause	Property {0} from property file {1} can not be empty
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-800-004 (Configuration Manager)
Type
Cause	Missing required property {0} from property file {1}
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-800-010 (Configuration Manager)
Type
Cause	Could not retrieve password for property {0}
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-999-000 (Configuration Manager)
Type
Cause	Failed to turnkey deploy.
Action	Deploy EAR files manually to JBoss by following instructions in Installing and Deploying LiveCycle for JBoss or Upgrading to LiveCycle for JBoss document.

Code	ALC-LCM-999-010 (Configuration Manager)
Type
Cause	The following ports required by {0} are still in use {1}.\nAnother instance may be running or another application may be using some of the required ports.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-999-020 (Configuration Manager)
Type
Cause	Windows turnkey service {0} does not exist.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-999-021 (Configuration Manager)
Type
Cause	Service shutdown failed for: {0}. \nUnexpected service state: {1}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-999-022 (Configuration Manager)
Type
Cause	Service shutdown failed for: {0}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-999-031 (Configuration Manager)
Type
Cause	Service startup failed for: {0}. \nUnexpected service state: {1}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-999-032 (Configuration Manager)
Type
Cause	Service startup failed for: {0}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-999-040 (Configuration Manager)
Type
Cause	JBoss did not come online.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-999-051 (Configuration Manager)
Type
Cause	Soap port missing from properties.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-999-052 (Configuration Manager)
Type
Cause	Server port missing from properties.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-999-053 (Configuration Manager)
Type
Cause	Cannot resolve pop3 path for: {0}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-999-054 (Configuration Manager)
Type
Cause	Cannot resolve driver path for: {0}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-999-055 (Configuration Manager)
Type
Cause	Weblogic domain could not be created for: {0}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-999-056 (Configuration Manager)
Type
Cause	Windows service could not be created for: {0}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-999-101 (Configuration Manager)
Type
Cause	Failed to create keystore.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-999-102 (Configuration Manager)
Type
Cause	Failed to install keystore to JBoss server {0}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-999-103 (Configuration Manager)
Type
Cause	Failed to update server.xml for JBoss server {0}.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-LCM-100-080 (Configuration Manager)
Type	Error
Cause	ListenAddress has not been set for server(s): {0}
Action	To avoid server startup issues, set the ListenAddress and restart the server(s). Refer to the documentation for additional information.

Connector for ECM error codes

Code	ALC-REP-500-000 (Connector for ECM)
Type
Cause	Invalid Uri. The Uri [{0}] should contain a valid Repository name
Action	Ensure the URI [{0}] contains a valid Repository name.

Code	ALC-REP-501-000 (Connector for ECM)
Type
Cause	Operation not supported. The Operation [{0}] is not supported by [{1}] Provider.
Action	Ensure that the operation tried is supported by the respective provider.

Code	ALC-REP-502-000 (Connector for ECM)
Type
Cause	Operation not supported on Root. The Operation [{0}] is not supported for Root object.
Action	Select a parent folder and again try the operation.

Code	ALC-REP-503-000 (Connector for ECM)
Type
Cause	Operation not supported on Repository. The Operation [{0}] is not supported on Repository level objects.
Action	Ensure that operation is valid for Repository level objects.

Code	ALC-REP-504-000 (Connector for ECM)
Type
Cause	Operation not supported on Cabinets. The Operation [{0}] is not supported on Cabinet level objects.
Action	Ensure that operation is supported on Cabinet level objects.

Code	ALC-REP-505-000 (Connector for ECM)
Type
Cause	Invalid value for attribute. The value [{0}] is invalid for attribute [{1}] in Operation [{2}]
Action	Provide a valid value to the respective attribute and retry the operation.

Code	ALC-REP-506-000 (Connector for ECM)
Type
Cause	Invalid resource Uris. The repository names should be same in [{0}] and [{1}] for [{2}] operation.
Action	Select valid resource URIs and retry the operation.

Code	ALC-REP-507-000 (Connector for ECM)
Type
Cause	Invalid Credentials. Authentication failed for User [{0}]. Verify Username / Password.
Action	Ensure that credentials provided are valid and retry the operation.

Code	ALC-REP-508-000 (Connector for ECM)
Type
Cause	Invalid Server Configuration. Access to Documentum connection broker failed with ServerName / IP [{0}] and Port number[{1}]
Action	Ensure that name of Documentum content server and port number is correct and retry the operation.

Code	ALC-REP-509-000 (Connector for ECM)
Type
Cause	Repository not available at connection broker. The Documentum connection broker [{0}] could not find a Repository [{1}]
Action	Ensure that provided repository exists on Documentum content server and retry the operation.

Code	ALC-REP-510-000 (Connector for ECM)
Type
Cause	Unknown failure has occured while authenticating connection on Username [{0}] / Repository [{1}]
Action	Ensure that the credentials provided for establishing connection to repository are correct and retry the operation.

Code	ALC-REP-600-000 (Connector for ECM)
Type
Cause	Invalid resource URI. The supplied value [{0}] is invalid.
Action	Ensure that provided resource URI is valid and retry the operation.

Code	ALC-REP-601-000 (Connector for ECM)
Type
Cause	Operation not supported. The Operation [{0}] is not supported by [{1}] Provider.
Action	Ensure that operation tried is supported by the provider.

Code	ALC-REP-602-000 (Connector for ECM)
Type
Cause	Filenet Property [{0}] not found on URI [{1}]
Action	Ensure that FileNet property provided is correct.

Code	ALC-REP-603-000 (Connector for ECM)
Type
Cause	Not a Current Version. The URI [{0}] doesn't point to current version.
Action	Ensure that settings are pointing to correct version of FileNet.

Code	ALC-REP-604-000 (Connector for ECM)
Type
Cause	Operation [{0}] only supported on Current version. The URI [{1}] doesn't point to current version.
Action	Correct the URI according to current version.

Code	ALC-REP-605-000 (Connector for ECM)
Type
Cause	Unqualified URI. The URI [{0}] should include a Object store name.
Action	Include object store in URI.

Code	ALC-REP-606-000 (Connector for ECM)
Type
Cause	Authentication failure. Username [{0}] or Password [{1}] may be invalid.
Action	Ensure that Username and Password are correct.

Code	ALC-REP-607-000 (Connector for ECM)
Type
Cause	Content Engine Configuration invalid. Connect Engine [{0}] or Port [{1}] is wrong. Check the network connectivity to Content Engine.
Action	Ensure that all content engine settings are correct.

Code	ALC-REP-608-000 (Connector for ECM)
Type
Cause	Operation not supported. The operation [{0}] is not supported on object store.
Action	Ensure that operation tried is supported on object store.

Code	ALC-REP-650-000 (Connector for ECM)
Type	Info
Cause	Work object [{0}] is locked by some other user.
Action	Information only. No action required.

Connector for Microsoft SharePoint error codes

Code	ALC-SPC-001-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	Parameter [{0}] cannot be null.
Action	The parameter mentioned in the error-code is a mandatory parameter.It should be removed.

Code	ALC-SPC-103-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	Caught Exception: {0}
Action	The Action required will depend upon the nature of nested exception mentioned in the cause.

Code	ALC-SPC-700-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	Authentication failed for [{0}]
Action	Credentials should be verified for the user.

Code	ALC-SPC-701-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	Resource does not exists at the [{0}] location.
Action	Provide the correct location for the resource/Resource might have been deleted.

Code	ALC-SPC-702-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	siteUrl [{0}] refers to a non existing host machine.
Action	Provide the correct URL for share-point server

Code	ALC-SPC-703-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	Cannot connect to [{0}]. Ensure the siteUrl specified is valid and accessible.
Action	Make sure that sharepoint server and port value is correct. Also make sure that site url is valid.

Code	ALC-SPC-704-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	Either Folder [{0}] does not exists or you have specified an invalid name for child folder [{1}].
Action	The parent/child folder names should be verified.

Code	ALC-SPC-705-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	File [{0}] is currently not checked out. Check out the file and then perform this operation
Action	Need to check out file before performing this operation.

Code	ALC-SPC-706-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	File [{0}] is already checked out.
Action	Action is not permitted when the file is already checked out.

Code	ALC-SPC-707-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	Property update for the following file [{0}] failed. Verify the property names you specified in the Map. Sharepoint Response:- [{1}]
Action	Property name specified for the file is not a valid. Provide correct property name.

Code	ALC-SPC-708-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	Document Library is required field, if Folder [{0}] is selected.
Action	The document library for the folder should also be specified.

Code	ALC-SPC-721-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	Site [{0}] does not exist or is not accessible.
Action	Verify site URL.

Code	ALC-SPC-722-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	Document Library [{0}] does not exist or is not accessible at the following site location [{1}].
Action

Code	ALC-SPC-723-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	File [{0}] does not exist or is not accessible at the following Document Library [{1}].
Action

Code	ALC-SPC-724-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	Folder [{0}] does not exist or is not accessible at the following Document Library [{1}].
Action

Code	ALC-SPC-725-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	User [{0}] does not exist for the site [{1}]. Ensure the user is a valid user and is accessible by the site.
Action

Code	ALC-SPC-726-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	Group [{0}] does not exist for the site [{1}]. Ensure the group is a valid user and is accessible by the site.
Action

Code	ALC-SPC-727-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	Role [{0}] does not exist for the site [{1}]. Ensure the user is a valid user and is accessible by the site.
Action

Code	ALC-SPC-728-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	No permissions exist for the user [{0}] at site [{1}]. Ensure the user is a valid user and has permission on the site.
Action

Code	ALC-SPC-729-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	No permissions exist for the user [{0}] at document library [{1}]. Ensure the user is a valid user and has permission on the Document library.
Action

Code	ALC-SPC-730-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	No permissions exist for the group [{0}] at site [{1}]. Ensure the group is a valid group and has permission on the site.
Action

Code	ALC-SPC-731-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	No permissions exist for the group [{0}] at document library [{1}]. Ensure the group is a valid group and has permission on the Document library.
Action

Code	ALC-SPC-732-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	No permissions exist for the role [{0}] at site [{1}]. Ensure the role is a valid role and has permission on the site.
Action

Code	ALC-SPC-733-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	No permissions exist for the role [{0}] at document library [{1}]. Ensure the role is a valid role and has permission on the document library.
Action

Code	ALC-SPC-734-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	File/Folder with given name [{0}] does not exist in Document Library [{1}]
Action

Code	ALC-SPC-741-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	Operation failed.
Action

Code	ALC-SPC-742-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	Operation failed with the following error code [{0}] and error message [{1}]. Verify there doesn't exist any extra "/" in the url displayed in error message field.
Action

Code	ALC-SPC-743-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	Operation failed with the following error code [{0}] and error message [{1}]. Verify the values of following [{2}:{3}]
Action	Verify the values of parameters mentioned in the error message

Code	ALC-SPC-744-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	Operation failed with the following error code [{0}] and error message [{1}]. Verify the values of following [{2}:{3}], [{4}:{5}], [{6}:{7}]
Action	Verify document library URL,document folder URL, and fileName URL

Code	ALC-SPC-745-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	Operation failed with the following error code [{0}] and error message [{1}]. Verify for any faulty input parameters.
Action

Code	ALC-SPC-751-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	A soap fault exception has occured. Either of input parameters specified are bad.
Action

Code	ALC-SPC-752-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	A soap fault exception has occured. Verify the values of following [{0}:{1}] .
Action	Verify the site URL

Code	ALC-SPC-753-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	Reserved error code.
Action	Reserved error code.

Code	ALC-SPC-754-000 (Connector for Microsoft SharePoint)
Type	Error
Cause	Reserved Error code.
Action	Reserved error code.

Content Services error codes

Code	ALC-CSV-030-000 (Content Services)
Type	Error
Cause	{0}
Action	A generic Content Services exception.

Code	ALC-CSV-030-001 (Content Services)
Type	Error
Cause	Authentication Failed for User: {0}.
Action	Verify the user/password combination.

Code	ALC-CSV-030-002 (Content Services)
Type	Error
Cause	Unable to locate: {0} in repository.
Action	Verify the path/id of the document.

Code	ALC-CSV-030-003 (Content Services)
Type	Error
Cause	Repository Fault.
Action	There was a problem accessing the repository. Review the logs for associated errors.

Code	ALC-CSV-030-004 (Content Services)
Type	Error
Cause	Invalid Update Version Type attribute {0}.
Action	Check the value of Update Version Type enumeration constant you are using.

Code	ALC-CSV-030-005 (Content Services)
Type	Error
Cause	Unable to retrieve content from {0}.
Action	There was a problem retrieving the content from the Content Services repository. Review the logs for associated errors.

Code	ALC-CSV-030-006 (Content Services)
Type	Error
Cause	Invalid MIME type {0}.
Action	Verify that the MIME type you are using.

Code	ALC-CSV-030-007 (Content Services)
Type	Error
Cause	Unable to invoke webscript URL {0}.
Action	The web script URL is invalid. Verify your system configuration.

Code	ALC-CSV-030-008 (Content Services)
Type	Error
Cause	Not a folder: {0}.
Action	Verify the given path/id.

Code	ALC-CSV-030-009 (Content Services)
Type	Error
Cause	Node: {0} already exists in repository.
Action	Verify that the path/id exists.

Code	ALC-CSV-030-010 (Content Services)
Type	Error
Cause	Access denied for User: {0}.
Action	User does not have permissions to perform this operation. Switch to a different user, or change the permissions for the specified user.

Code	ALC-CSV-030-100 (Content Services)
Type	Error
Cause	No Space specified while invoking {0}.
Action	You have not specified a space while performing the given operation. Verify the parameters.

Code	ALC-CSV-030-101 (Content Services)
Type	Error
Cause	No Store specified while invoking {0}.
Action	You have not specified a store while performing the given operation. Verify the parameters.

Code	ALC-CSV-030-102 (Content Services)
Type	Error
Cause	No Node name specified while invoking {0}.
Action	You have not specified a node name while performing the given operation. Verify the parameters.

Code	ALC-CSV-030-103 (Content Services)
Type	Error
Cause	No Node type specified while invoking {0}.
Action	You have not specified a node type while performing the given operation. Verify the parameters.

Code	ALC-CSV-030-104 (Content Services)
Type	Error
Cause	No Node encoding specified while invoking {0}.
Action	You have not specified a node encoding while performing the given operation. Verify the parameters.

Code	ALC-CSV-030-105 (Content Services)
Type	Error
Cause	No Content(InputStream) present while invoking {0}.
Action	You have not passed the content stream while performing the given operation. Verify the parameters.

Code	ALC-CSV-030-106 (Content Services)
Type	Error
Cause	No Content type specified while invoking {0}.
Action	You have not specified a content type while performing the given operation. Verify the parameters.

Code	ALC-CSV-030-107 (Content Services)
Type	Error
Cause	No Node ID or Path specified while invoking {0}.
Action	You have not specified a node path/id while performing the given operation. Verify the parameters.

Code	ALC-CSV-030-108 (Content Services)
Type	Error
Cause	No Relationship type specified while invoking {0}.
Action	You have not specified a relation type while performing the given operation. Verify the parameters.

Code	ALC-CSV-030-109 (Content Services)
Type	Error
Cause	No Child Node ID or Path specified while invoking {0}.
Action	You have not specified a child node id/path while performing the given operation. Verify the parameters.

Code	ALC-CSV-030-110 (Content Services)
Type	Error
Cause	No Parent Node ID or Path specified while invoking {0}.
Action	You have not specified a parent node id/path while performing the given operation. Verify the parameters.

Code	ALC-CSV-030-111 (Content Services)
Type	Error
Cause	No Source Node ID or Path specified while invoking {0}.
Action	You have not specified a source node id/path while performing the given operation. Verify the parameters.

Code	ALC-CSV-030-112 (Content Services)
Type	Error
Cause	No Target Node ID or Path specified while invoking {0}.
Action	You have not specified a target node id/path while performing the given operation. Verify the parameters.

Code	ALC-CSV-030-113 (Content Services)
Type	Error
Cause	No Template/Source Folder specified.
Action	You have not specified a Template/Source folder while performing the given operation. Verify the parameters.

Code	ALC-CSV-030-211 (Content Services)
Type	Error
Cause	There is no LiveCycle service available for the conversion of {0}.
Action	The LiveCycle server required to perform the conversion is not available. Verify that the service is active and has been deployed on the server. If the problem persists, contact your system administrator.

Code	ALC-CSV-030-212 (Content Services)
Type	Error
Cause	No data could be retrieved from the provided XML files.
Action	The LiveCycle transformation module is corrupted. Ensure that Content Services is deployed properly.

Code	ALC-CSV-030-213 (Content Services)
Type	Error
Cause	Received no response from LiveCycle while invoking {0}.
Action	There was problem invoking the given LiveCycle service component. Ensure that the component service is deployed and active.

Code	ALC-CSV-030-214 (Content Services)
Type	Error
Cause	Map does not contain any XML data.
Action	The LiveCycle transformation mapping XML is empty. Verify that Content Services is deployed properly.

Code	ALC-CSV-030-215 (Content Services)
Type	Error
Cause	Desired conversion could not be performed.
Action	There was problem while doing the conversion. Review the logs for more information.

Code	ALC-CSV-030-216 (Content Services)
Type	Error
Cause	Transformation to {0} is not supported.
Action	The transformation to given target format is not supported by Content Services.

Code	ALC-CSV-030-217 (Content Services)
Type	Error
Cause	List of input streams received after conversion is empty. It is likely that there was a problem retrieving the result of the transformation.
Action	Review the logs for any associated errors.

Code	ALC-CSV-030-011 (Content Services)
Type	Error
Cause	Failed to issue a request to Content Services ES.
Action	Verify that the Content Services webscripts are configured for the correct port. Update the Contents Services HttpPort property using Administration Console.

Code	ALC-CSV-030-012 (Content Services)
Type	Error
Cause	The value for QName cannot be null or empty.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-CSV-030-013 (Content Services)
Type	Error
Cause	The format of date string:{0} is incorrect.
Action	Ensure that the date string conforms to the ISO 8601 standard "yyyy-MM-dd'T'HH:mm:ss'Z'".

Code	ALC-CSV-030-014 (Content Services)
Type	Error
Cause	The version label {0} is invalid for node.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-CSV-030-015 (Content Services)
Type	Error
Cause	The node {0} is not versioned.
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-CSV-030-016 (Content Services)
Type	Error
Cause	The permission [{0}] is invalid for node.
Action	User does not have rights to update permissions on the node.

Code	ALC-CSV-030-017 (Content Services)
Type	Error
Cause	Null Content Access Permission passed to the access permissions list.
Action	Pass a valid (non-blank) Content Access Permission to the access permission list.

Code	ALC-CSV-030-018 (Content Services)
Type	Error
Cause	The authority [{0}] does not exist.
Action	Pass a valid authority in the operation.

Code	ALC-CSV-030-019 (Content Services)
Type	Error
Cause	CIFS not enabled for this LC instance. Provide '-Dcifs.enabled=true' as JVM argument in App-server startup script/service params.
Action	Address the issue identified in the Cause section of the log message

Code	ALC-CSV-030-020 (Content Services)
Type	Error
Cause	CIFS Root name for 'Company Home' is not configured. Provide a valid folder name for '-Dfilesystem.name=<>' JVM argument in App-server startup. Also ensure that filesystem rootPath is configured as /app:company_home in file-servers.xml file.
Action	Address the issue identified in the Cause section of the log message

Code	ALC-CSV-030-021 (Content Services)
Type	Error
Cause	Invalid Aspect [{0}]
Action	Provide a valid aspect name.

Code	ALC-CSV-030-022 (Content Services)
Type	Error
Cause	Aspect List cannot be empty
Action	Provide a non-Empty aspect list.

Code	ALC-CSV-030-023 (Content Services)
Type	Error
Cause	Integrity Error. [{0}]
Action	Address the issue identified in the Cause section of the log message

Code	ALC-CSV-030-024 (Content Services)
Type	Error
Cause	The node is locked. [{0}]
Action	Address the issue identified in the Cause section of the log message

Code	ALC-CSV-030-114 (Content Services)
Type	Error
Cause	No permission specified while invoking [{0}].
Action	Provide valid permission.

Code	ALC-CSV-030-115 (Content Services)
Type	Error
Cause	No Query object passed.
Action	Pass a query object in the search operation.

Code	ALC-CSV-030-116 (Content Services)
Type	Error
Cause	Invalid value passed for maxSize.
Action	Pass a valid integer value for maximum number of records to return in search operation.

Code	ALC-CSV-030-117 (Content Services)
Type	Error
Cause	Error creating query, operation [{0}] not allowed for type [{1}].
Action	Create a valid query statement, operator is not allowed for the attribute.

Code	ALC-CSV-030-118 (Content Services)
Type	Error
Cause	Error parsing the query.
Action	Specify a valid query statement in the search operation.

Code	ALC-CSV-030-119 (Content Services)
Type	Error
Cause	Invalid value specified for property [{0}].
Action	Pass a valid value for the property.

Code	ALC-CSV-040-100 (Content Services)
Type	Error
Cause	No Document content specified while invoking [{0}].
Action	You have not specified a content type while performing the given operation. Verify the parameters.

Code	ALC-CSV-040-101 (Content Services)
Type	Error
Cause	Review Server path not specified while invoking [{0}].
Action	You have not specified Review Server path while performing the given operation. Verify the parameters.

Code	ALC-CSV-040-102 (Content Services)
Type	Error
Cause	Review initiator not specified while invoking [{0}].
Action	You have not specified Review initiator while performing the given operation. Verify the parameters.

Code	ALC-CSV-040-103 (Content Services)
Type	Error
Cause	Mandatory reviewers not specified while invoking [{0}].
Action	You have not specified Mandatory reviewers while performing the given operation. Verify the parameters.

Code	ALC-CSV-040-104 (Content Services)
Type	Error
Cause	Reviewer email ID not specified while invoking [{0}].
Action	You have not specified Reviewer email ID while performing the given operation. Verify the parameters.

Code	ALC-CSV-040-105 (Content Services)
Type	Error
Cause	Cannot start review on [{0}]. The document is Reader Extended.
Action	Either pass a non-RE document or pass raiseExcpOnREPDF argument=false in the operation.

Code	ALC-CSV-040-200 (Content Services)
Type	Error
Cause	Cannot authenticate against Review Server. Exception : [{0}].
Action	Verify the user credentials for accessing review server.

Code	ALC-CSV-040-201 (Content Services)
Type	Error
Cause	Cannot access location on Review Server. Exception : [{0}].
Action	Verify the path/id of the document/Space on review server.

Code	ALC-CSV-040-202 (Content Services)
Type	Error
Cause	Content Services Review Server exception : [{0}].
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-CSV-040-203 (Content Services)
Type	Error
Cause	File System Review Server exception : [{0}]
Action	Address the issue identified in the Cause section of the log message

Code	ALC-CSV-040-204 (Content Services)
Type	Error
Cause	Invalid Review Server path in Content Services : [{0}]. Must be inside '/Company Home'.
Action	Provide the valid path inside /Company Home.

Code	ALC-CSV-040-205 (Content Services)
Type	Error
Cause	IO exception encountered : [{0}].
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-CSV-040-300 (Content Services)
Type	Error
Cause	XML Exception encountered : [{0}].
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-CSV-040-301 (Content Services)
Type	Error
Cause	PDF Exception encountered : [{0}].
Action	Address the issue identified in the Cause section of the log message.

Code	ALC-CSV-040-302 (Content Services)
Type	Error
Cause	Review deadline not specified in document : [{0}]. Cannot terminate review.
Action	Correct the initiator annotation XML to have deadline tag.

Code	ALC-CSV-040-303 (Content Services)
Type	Error
Cause	Review ID not specified in document : [{0}].
Action

Code	ALC-CSV-001-000 (Content Services)
Type	Error
Cause	Just in case we miss on the string in properties file. we log it under ALC-CSV-001-000
Action	Appropriate Action would either be available in the error being displayed or in the logs as this is a generic exception which would come up only in case of some unforseable scenario.

Convert PDF service error codes

Code	ALC-CNP-001-002 (Convert PDF service)
Type	Error
Cause	Invalid option value.
Action	Verify option value.

Code	ALC-CNP-001-104 (Convert PDF service)
Type	Error
Cause	Error while loading options.
Action	Contact the system administrator.

Code	ALC-CNP-001-201 (Convert PDF service)
Type	Error
Cause	Invalid Zip document.
Action	Verify the ZIP format of the document.

Code	ALC-CNP-001-202 (Convert PDF service)
Type	Error
Cause	Error creating directory.
Action	Verify the ZIP format of the document.

Code	ALC-CNP-001-305 (Convert PDF service)
Type	Error
Cause	Convert PDF does not support PDF Package (Portable Collection).
Action	Verify that the document is not a PDF Package (Portable Collection).

Code	ALC-CNP-001-306 (Convert PDF service)
Type	Error
Cause	An IO Exception occurred while obtaining the PDF document.
Action	Verify that the location of PDF is valid and then retry the operation. If the problem persists, contact the system administrator.

Code	ALC-CNP-001-308 (Convert PDF service)
Type	Error
Cause	Required input parameter missing.
Action	Enter all the required input parameters. Review the logs for details.

Code	ALC-CNP-001-401 (Convert PDF service)
Type	Error
Cause	Cannot convert PDF file to image.
Action	Verify the input PDF document format. Review the logs for details.

Code	ALC-CNP-001-402 (Convert PDF service)
Type	Error
Cause	MultipageTiff,IncludeComments, ImageSizeWidth, ImageSizeHeight, and PageRange options are not functional in the deprecated toImage API, to use these options use toImage2 API.
Action	Verify that valid options are supplied. Supported image formats are: - JPEG - JPEG2K - PNG - TIFF If you are sending MultipageTiff, IncludeComments, ImageSizeWidth, ImageSizeHeight, and PageRange options, use the "toImage2 API".

Code	ALC-CNP-001-301 (Convert PDF service)
Type	Error
Cause	Cannot convert PDF file to PostScript.
Action	Verify that the input PDF is valid flat PDF. Verify that the options sent are valid or set the option LegacyToSimplePSFlag in ToPSOptionsSpec to true to convert interactive documents to PostScript.

Code	ALC-CNP-001-302 (Convert PDF service)
Type	Error
Cause	Document is not a valid PDF document.
Action	Verify that the document is a valid PDF document which could be converted to image/ps. The document must meet the following conditions: - It is not a portable collection (PDF Package) - It is flattened (non-interactive) or set the option LegacyToSimplePSFlag in ToPSOptionsSpec to true to convert interactive documents to PostScript. - It is not encrypted

Code	ALC-CNP-001-304 (Convert PDF service)
Type	Error
Cause	Input document is not a non-interactive PDF document.
Action	Verify that the input document is a non-interactive PDF document or set the option LegacyToSimplePSFlag in ToPSOptionsSpec to true to convert interactive documents to PostScript.

Code	ALC-CNP-001-307 (Convert PDF service)
Type	Error
Cause	PDF exception.
Action	Verify that the document is a valid PDF document which can be converted to image/ps. The document must meet the following conditions: - It is not a portable collection (PDF Package) - It is flattened (non-interactive) - It is not encrypted Or set the optionLegacyToSimplePSFlag in ToPSOptionsSpec to true to convert interactive documents to PostScript.

Core error codes

Code	ALC-DSC-504-000 (Core)
Type	Error
Cause	Data Type not found
Action

Code	ALC-DSC-217-00 (Core)
Type	Error
Cause	Could not create/start dispatcher class ...
Action	Usually it's class loading issue since it cannot load the dispatcher class. Make sure packaging is correct, and all required libs are in classpath. Or it could also be endpointURI that causes the failure of dispatcher's constructor.

Core - DSC error codes

Code	com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Can't call rollback when autocommit=true (Core - DSC)
Type	Warning
Cause	Compatibility issue between JBoss 4.2 and JBoss 5.1.
Action	Do nothing. Warning is harmless.

Core - Document Manager error codes

Code	DOCS001: Unexpected exception. com.adobe.idp.DocumentError: Failed to connect to LiveCycle server via HTTP URL (Core - Document Manager)
Type	Error
Cause	This error might be occasionally encountered by java applications that invoke LiveCycle Services using LiveCycle Client SDK. This problem happens only when the client application runs under Sun JVM 1.5. The problem is typically accompanied with the following exception stack trace: java.lang.NullPointerException at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source) at com.adobe.idp.DocumentManagerClient.requestRemotePassivation(DocumentManagerClient.java)
Action	Caused by a bug in Sun JVM 1.5. Sun JVM 1.6 has fixed this problem. Upgrade your application to Sun JVM 1.6.

Code	ALC-DOCS-001-006 (Core - Document Manager)
Type	Error
Cause	"Failed to delete a file \"{0}\" after {1} attempts. " + "The file could still be locked."
Action

Code	ALC-DOCS-001-007 (Core - Document Manager)
Type	Info
Cause	Total size of unremovable files: {0}M, in the last hour: {1}M, in the last 24 hours: {2}M, in the last week: {3}M
Action

Code	ALC-DOCS-001-008 (Core - Document Manager)
Type	Info
Cause	Total unremovable files: {0}, in the last hour: {1}, in the last 24 hours: {2}, in the last week: {3}
Action

Code	ALC-DOCS-001-009 (Core - Document Manager)
Type	Warning
Cause	The following represent a sample of up to 20 of the unremovable files noted above.
Action

Code	DOCS014 (Core - Document Manager)
Type	Error
Cause	The file {0} was reported by the filesystem as missing, but recovery attempts discovered the file existed.
Action	This error message might show up in a clustered environment with GDS configured as a shared network directory. The problem is most likely due to a bug in implementation of the network file protocol. Consider upgrading to a newer version of OS or switching to a different network file protocol.

DB2 error codes

Code	ALC-DSC-000-000 (DB2)
Type	Error
Cause	com.ibm.db2.jcc.b.nm: The character "_" following "IC(19,0) NOT NULL ," is not valid.. SQLCODE=-7, SQLSTATE=42601, DRIVER=3.50.152
Action	Do not create process variable name start with “_” character when creating long-lived process on DB2 platform. Work around for process generated by archive wizard. If a long-lived process is required then the long-lived process could call a short-lived subprocess. The archive wizard can be used to generate steps on that short-lived process.

Data Manager error codes

Code	ALC-DMR-001-001 (Data Manager)
Type	Error
Cause	The proposed global document storage directory {0} does not exist or does not contain either a backup nor a restore directory. The {1} file must specify a new location of a previously used Global Document Storage directory.
Action

Code	ALC-DMR-001-002 (Data Manager)
Type	Error
Cause	Deleting Global Document Storage Root Directory redirection file {0} failed. Delete it manually. Otherwise any other method of changing the GDS root directory will fail.
Action

Code	ALC-DMR-001-003 (Data Manager)
Type	Error
Cause	An IOException was encountered while trying to reset the global document storage directory to {0} with redirect file {1}.
Action

Code	ALC-DMR-001-101" (Data Manager)
Type	Warning
Cause	The Global Document Storage Root Directory has been changed to {0}.
Action

Data Services error codes

Code	10155 (Data Services)
Type	Error
Cause	No property named property name exists in class Java Class.
Action

Code	10156 (Data Services)
Type	Error
Cause	A one-to-many or many-to-many relation must reference a java.util.Collection type (error in destination destination name).
Action

Code	10150 (Data Services)
Type	Error
Cause	Unable to access UserTransaction in DataService.
Action

Code	10151 (Data Services)
Type	Error
Cause	Association relations must be one-to-many, many-to-many, many-to-one, or one-to-one.
Action

Code	10152 (Data Services)
Type	Error
Cause	Unable to access identity field field name of an instance, check the identity configuration for destination destination name.
Action

Code	10153 (Data Services)
Type	Error
Cause	Client sent no sequence id, cannot retrieve page.
Action

Code	10154 (Data Services)
Type	Error
Cause	Pages for sequence id sequence id have expired in destination destination name.
Action

Code	10157 (Data Services)
Type	Error
Cause	The destination destination name has no identity property. Data Service destinations must have at least one identity property configured in the metadata section of the destination properties.
Action

Code	10158 (Data Services)
Type	Error
Cause	An error occurred on DataService destination destination name while processing transactional operations: the transaction could not be rolled back or committed.
Action

Code	10159 (Data Services)
Type	Error
Cause	Identity property names should be individual properties property name. Use more than one identity tag when you want to specify multiple id properties.
Action

Code	10160 (Data Services)
Type	Error
Cause	Page request made for items in a lazily loaded property failed to retrieve the parent item. Parent destination = destination name, id=property id.
Action

Code	10161 (Data Services)
Type	Error
Cause	Page request made for item with id = ''{0}''. The item was not in the cache and the adapter''s get method failed to return the item for destination = destination name that is expected to be in the requested page.
Action

Code	10162 (Data Services)
Type	Error
Cause	Error occurred completing a transaction.
Action

Code	10164 (Data Services)
Type	Error
Cause	MessageBroker with server id server id does not contain a service with class flex.data.DataService
Action

Code	10165 (Data Services)
Type	Error
Cause	Attempt to begin a DataServiceTransaction when an existing transaction was already in place.
Action

Code	10166 (Data Services)
Type	Error
Cause	Page requested does not exist in the specified sequence ''{0}'' for destination ''{1}''.
Action

Code	10167 (Data Services)
Type	Error
Cause	The destination destination name has identity properties that do not have defined types. Identity types must be defined for all properties or for no properties; not a partial set.
Action

Code	10168 (Data Services)
Type	Error
Cause	There is no current message broker to return.
Action

Code	10170 (Data Services)
Type	Error
Cause	Invalid reconnect fetch value. Valid options are valid options list
Action

Code	10171 (Data Services)
Type	Error
Cause	You are specifying a strongly-typed object ''{0}'' on the client using RemoteClass metadata and a strongly typed object ''{1}'' on the server using item-class. If you wish to have strongly typed objects on both client and server, you must specify RemoteClass(alias='server.Object') where 'server.Object' is the target item type on the server. Otherwise, remove one of the designations to specify client or server-only.
Action

Code	10171 (Data Services)
Type	Error
Cause	You are specifying a strongly-typed object client side object name on the client using RemoteClass metadata and a strongly typed object server side object name on the server using item-class. If you wish to have strongly typed objects on both client and server, you must specify RemoteClass(alias='server.Object') where 'server.Object' is the target item type on the server. Otherwise, remove one of the designations to specify client or server-only.
Action

Code	10172 (Data Services)
Type	Error
Cause	Attempt to request a page with sequence id: sequence Id for destination name destination name which the client is not subscribed to.
Action

Code	10173 (Data Services)
Type	Error
Cause	Value for extends attribute must be a comma separated list of valid destination names. Destination destination name refers to destination names referred which is not recognized as a data destination name.
Action

Code	10174 (Data Services)
Type	Error
Cause	Identity properties for all destinations in the same extends hierarchy must match. Destination destination name has id properties but extends a destination with name of Id.
Action

Code	10175 (Data Services)
Type	Error
Cause	Destination destination name extends another destination but does not specify item-class so we can tell which instances go with which destination.
Action

Code	10176 (Data Services)
Type	Error
Cause	The extends value for destination destination name should be a comma separated list of destination names. Found destination name(s) found.
Action

Code	10177 (Data Services)
Type	Error
Cause	Encountered an instance for destination with class: class name of destination that is not a sub-type of the item-class: class name of item.
Action

Code	10178 (Data Services)
Type	Error
Cause	Destination destination name has two sub-types which inherit from each other but the destinations do not extend from each other. Destination (class: class name of destination) is a super or sub type of destination name of parent destination (class: class name of parent destination).
Action

Code	10179 (Data Services)
Type	Error
Cause	Destination destination name extends from these destinations: list of parent destinations which directly or indirectly extend from it.
Action

Code	10180 (Data Services)
Type	Error
Cause	Destination destination name defined an association: name of association that refers to non-existent destination name of non-existent definition
Action

Code	10181 (Data Services)
Type	Error
Cause	Destination destination name received invalid message: name of invalid message
Action

Code	10182 (Data Services)
Type	Error
Cause	Destination destination name received request for an association property that is not defined on the server server name.
Action

Code	10183 (Data Services)
Type	Error
Cause	Updating collection property name of property did not return a valid collection: name of collection.
Action

Code	10184 (Data Services)
Type	Error
Cause	Attempt to modify collection property without a corresponding association: name of property does not have an association named name of association.
Action

Code	10185 (Data Services)
Type	Error
Cause	A destination can only extend from a single destination. Destination destination name has extends list of destinations being extended.
Action

Code	10186 (Data Services)
Type	Error
Cause	Single valued associations do not support paging - page size must be 0 for destination destination name on association name of association.
Action

Code	10187 (Data Services)
Type	Error
Cause	Page requested does not exist in the specified collection: name of collection for destination destination name.
Action

Code	10188 (Data Services)
Type	Error
Cause	Error occurred requesting page for the specified collection: name of collection for destination destination name.
Action

Code	10189 (Data Services)
Type	Error
Cause	No destination with id id of destination is registered with the DataService.
Action

Code	10190 (Data Services)
Type	Error
Cause	Assembler returned multiple items with the same id, name of Id, in a fill response for fill with the following parameters, list of parameters, for destination destination name.
Action

Code	10500 (Data Services)
Type	Error
Cause	Could not invoke sync method on data adapter for destination destination name due to the following error: error message.
Action

Code	10501 (Data Services)
Type	Error
Cause	Unable to locate a sync method for destination destination name.
Action

Code	10502 (Data Services)
Type	Error
Cause	Unable to instantiate object assembler class class name of assembler.
Action

Code	10503 (Data Services)
Type	Error
Cause	No identity sent with delete operation.
Action

Code	10504 (Data Services)
Type	Error
Cause	Unsupported DataMessage operation name of operation.
Action

Code	10505 (Data Services)
Type	Error
Cause	No identity sent with update operation.
Action

Code	10506 (Data Services)
Type	Error
Cause	ObjectAdapter class class name of object adapter could not be found.
Action

Code	10507 (Data Services)
Type	Error
Cause	Could not create ObjectAdapter class class name of ObjectAdapter.
Action

Code	10508 (Data Services)
Type	Error
Cause	Unable to locate a count method for destination destination name which matches the following parameters: list of parameters.
Action

Code	10509 (Data Services)
Type	Error
Cause	Unable to invoke a count operation on destination destination name due to the following error: error message stating the cause.
Action

Code	10510 (Data Services)
Type	Error
Cause	Unable to locate a fill method for destination destination name which matches the following parameters: list of parameters.
Action

Code	10511 (Data Services)
Type	Error
Cause	Unable to invoke a fill operation on destination destination name due to the following error: error message.
Action

Code	10512 (Data Services)
Type	Error
Cause	Unable to locate a get method for destination destination name.
Action

Code	10513 (Data Services)
Type	Error
Cause	Unable to invoke a get operation on destination destination name due to the following error: error message.
Action

Code	10514 (Data Services)
Type	Error
Cause	More than one destination name method is configured with the same argument types for destination: destination name, which is not permitted.
Action

Code	10515 (Data Services)
Type	Error
Cause	While generating methods for a data adapter, could not find parameter class class name of parameter.
Action

Code	10516 (Data Services)
Type	Error
Cause	Data adapter could not locate method name of method with parameters list of parameters on class class name.
Action

Code	10517 (Data Services)
Type	Error
Cause	Data adapter could not find sync method name of method on class class name.
Action

Code	10518 (Data Services)
Type	Error
Cause	An association tag is missing a value for either the property or destination attributes. You have configured property=name of property, association destination=destination name.
Action

Code	10519 (Data Services)
Type	Error
Cause	Hibernate destination destination name has an association to destination destination name which is not a Hibernate destination.
Action

Code	10520 (Data Services)
Type	Error
Cause	The fill method with parameters list of parameters and destination destination name returned null.
Action

Code	10521 (Data Services)
Type	Error
Cause	No parameters passed to fill method for the Hibernate assembler on destination destination name and there is no fill-method defined for zero args.
Action

Code	10522 (Data Services)
Type	Error
Cause	An HQL expression contained a named or positional parameter token, but no parameters were provided to the fill operation.
Action

Code	10523 (Data Services)
Type	Error
Cause	No Hibernate mapping was found for entity name name of entity to be persisted configured in destination destination name. Verify that your destination configuration specifies a valid item-class/, or that the destination id is a hibernate entity name in your hibernate.cfg.xml file.
Action

Code	10524 (Data Services)
Type	Error
Cause	The PROPERTY conflict mode is not useful for the delete-conflict-mode setting, specify NONE or OBJECT instead for destination Name of destination.
Action

Code	10525 (Data Services)
Type	Error
Cause	Unable to inspect fields when evaluating a query in the ASObjectAdapter
Action

Code	10526 (Data Services)
Type	Error
Cause	The ASObject Data Adapter has no back end, so when clustered it cannot be configured to share a back end
Action

Code	10527 (Data Services)
Type	Error
Cause	The ASObject Data Adapter can accept only a single parameter, in the form a selector expression, in its fill operation
Action

Code	10528 (Data Services)
Type	Error
Cause	Unique id must be specified. Identity properties specified are not found on specified object instance.
Action

Code	10529 (Data Services)
Type	Error
Cause	Unable to access the field Name of field of a strongly-typed Java object Name of java object which was passed into the ASObjectAdapter.
Action

Code	10530 (Data Services)
Type	Error
Cause	Attempt to create an item in data destination Name of destination with an identity which already exists. Identities must be unique.
Action

Code	10531 (Data Services)
Type	Error
Cause	A fill with an HQL query was attempted but no query expression was provided as the second parameter to fill for destination Name of destination.
Action

Code	10532 (Data Services)
Type	Error
Cause	A fill with an HQL query was attempted but the wrong number of arguments were supplied. We expect the args to be: fill("flex:hql", hqlExpressionString,hqlPositionalOrMapParameters). Destination is: Name of destination.
Action

Code	10533 (Data Services)
Type	Error
Cause	Data adapter could not locate fill-contains-method Name of method on class Class name with parameters 'Object[] fillParams, Object value'.
Action

Code	10534 (Data Services)
Type	Error
Cause	Data adapter has a fill-contains-method tag which is missing a name tag for fill method name of method on class Class name.
Action

Code	10535 (Data Services)
Type	Error
Cause	The fill-contains-method for class Class name did not return a boolean result - class Wrong class name was found instead.
Action

Code	10536 (Data Services)
Type	Error
Cause	The fill-contains-method for class Class name returned an error: Error message.
Action

Code	10537 (Data Services)
Type	Error
Cause	Data adapter has a fill-contains-method tag which is missing a name sub-tag for fill method Name of fill method on assembler class Name of assembler class
Action

Code	10538 (Data Services)
Type	Error
Cause	Data adapter has more than one sync-method which is not allowed. methods: List of declared sync method names.
Action

Code	10539 (Data Services)
Type	Error
Cause	Data destination Name of destination has property Name of property configured more than once which is not allowed.
Action

Code	10540 (Data Services)
Type	Error
Cause	Data adapter could not find init method Name of method on class Class name.
Action

Code	10541 (Data Services)
Type	Error
Cause	Data adapter has more than one init-method which is not allowed. methods: List of methods.
Action

Code	10542 (Data Services)
Type	Error
Cause	Unable to invoke a init method on destination Name of destination due to the following error: Error message.
Action

Code	10543 (Data Services)
Type	Error
Cause	The auto-refresh can be false only if fill-contains-method does not exist for fill method Name of fill method on assembler class Assembler class name.
Action

Code	10544 (Data Services)
Type	Error
Cause	A fill for a named Hibernate query was attempted but the wrong number of arguments was supplied. We expect two fill arguments - the name of the query and the parameters as the second argument either as an Object or an Array. Destination: Name of destination.
Action

Code	10545 (Data Services)
Type	Error
Cause	A fill for a Hibernate query was attempted with invalid parameter types. The first arg should be a string to identify the query. For HQL, the second arg is the string HQL expression, followed by parameters. For named queries parameters are the second arg. Parameters are either an array for position params, or an Object for named params. Destination: Name of destination.
Action

Code	10546 (Data Services)
Type	Error
Cause	Unable to invoke a get method for destination Name of destination because the identity property Name of identity property was not provided.
Action

Code	10547 (Data Services)
Type	Error
Cause	Unable to invoke a get method for destination Name of destination because the identity type(s) did not match. Received List of identity types sent. Expected Correct list of identity types.
Action

Code	10548 (Data Services)
Type	Error
Cause	Cannot load type Name of type for identity property Name of identity property.
Action

Code	10549 (Data Services)
Type	Error
Cause	Ambiguous fill method encountered. Incoming arguments List of incoming arguments match both fill-method: Name of first fill method and fill-method: Name of second fill method.
Action

Code	10750 (Data Services)
Type	Error
Cause	RTMPS failed to initialize because the requested keystore type, Name of keystore type, is not available.
Action

Code	10751 (Data Services)
Type	Error
Cause	RTMPS failed to initialize because the keystore file could not be found, is unreadable or the supplied password is incorrect.
Action

Code	10752 (Data Services)
Type	Error
Cause	RTMPS failed to initialize because the algorithm used to test keystore integrity can not be found.
Action

Code	10753 (Data Services)
Type	Error
Cause	RTMPS failed to initialize because not all certificates in the keystore could be loaded.
Action

Code	10754 (Data Services)
Type	Error
Cause	RTMPS failed to initialize because the algorithm, Name of algorithm, is not available.
Action

Code	10755 (Data Services)
Type	Error
Cause	RTMPS failed to initialize because the keystore password is incorrect.
Action

Code	10756 (Data Services)
Type	Error
Cause	RTMPS failed to initialize because the keystore manager factory could not initialize.
Action

Code	10757 (Data Services)
Type	Error
Cause	RTMPS failed to initialize because the truststore manager factory could not initialize.
Action

Code	10758 (Data Services)
Type	Error
Cause	RTMPS failed to initialize because the protocol, Name of protocol, is not available.
Action

Code	10759 (Data Services)
Type	Error
Cause	RTMPS failed to initialize because the keystore password file, password file, can not be found.
Action

Code	10760 (Data Services)
Type	Error
Cause	RTMPS failed to initialize because the keystore password file, password file, can not be read.
Action

Code	10761 (Data Services)
Type	Error
Cause	RTMPS could not initialize because the keystore-file/ configuration element was not provided.
Action

Code	10762 (Data Services)
Type	Error
Cause	RTMPS could not initialize because neither the keystore-password/ nor the keystore-password-file/ configuration element was provided.
Action

Code	10850 (Data Services)
Type	Error
Cause	The RTMP server has encountered a fatal exception starting up: Exception Message.
Action

Code	10851 (Data Services)
Type	Error
Cause	The RTMP server has encountered a fatal exception establishing its socket to accept client connections: Exception Message
Action

Code	11150 (Data Services)
Type	Error
Cause	An invalid license key was entered. To enable a Developer license remove the invalid license key from license.properties.
Action

Code	11151 (Data Services)
Type	Error
Cause	Beta expired.
Action

Code	11152 (Data Services)
Type	Error
Cause	MessageBroker Name of MessageBroker rejected connection from address Name of 'from' address; Developer mode addresses already in use: List of allowed addresses.
Action

Code	11153 (Data Services)
Type	Error
Cause	Maximum number of IP addresses exceeded for Developer licensed server.
Action

Code	11200 (Data Services)
Type	Error
Cause	The item of type, Name of item class, passed to the assembler does not match the assembler''s configured entity type, Name of entity class. To convert ''flex.messaging.io.amf.ASObject'' to a strong type automatically, set the item-class in the destination.
Action

Code	11201 (Data Services)
Type	Error
Cause	Hibernate HQL queries are not allowed for destination Name of destination.
Action

Code	11202 (Data Services)
Type	Error
Cause	The fill method is not defined for destination Name of destination which matches fill parameters: List of parameters
Action

Code	11203 (Data Services)
Type	Error
Cause	The fill method which returns a page of items is not defined for destination Name of destination but useFillPage for fill parameters: Provided fill parameters returned true.
Action

Code	11204 (Data Services)
Type	Error
Cause	Type Class name of identity property for identity property name of identity property must implement the equals method.
Action

Code	11205 (Data Services)
Type	Error
Cause	Type Class name of identity property for identity property name of identity property must implement the hashCode method.
Action

Code	11206 (Data Services)
Type	Error
Cause	Hibernate destination Name of destination was created automatically and is not exposed to clients for queries. If you intend to expose these queries, add an explicit destination declaration in data-management-config.xml.
Action

Code	11207 (Data Services)
Type	Error
Cause	A fill method returned object type which is not a collection. destination Name of destination params: List of parameters.
Action

Code	11207 (Data Services)
Type	Error
Cause	A fill method returned object type which is not a collection. destination Name of destination params: List of parameters provided.
Action

Code	11208 (Data Services)
Type	Error
Cause	A findItem method returned object type which is a collection. destination Name of destination params: List of parameters provided.
Action

Code	11209 (Data Services)
Type	Error
Cause	When using runtime configuration, the destination id on the assembler must be set.
Action

Code	11250 (Data Services)
Type	Error
Cause	The driver-class, Name of driver class, could not be found. Specify a valid driver-class in the configuration file.
Action

Code	11251 (Data Services)
Type	Error
Cause	The datasource, Name of data source, could not be found. Specify a valid datasource in the configuration file.
Action

Code	11252 (Data Services)
Type	Error
Cause	Database connection information for destination Name of destination must be specified in the configuration file."
Action

Code	11253 (Data Services)
Type	Error
Cause	Only one of datasource or driver-class may be set for destination Name of destination.
Action

Code	11254 (Data Services)
Type	Error
Cause	Must specify one of datasource or driver class for destination Name of destination.
Action

Code	11255 (Data Services)
Type	Error
Cause	The database connection information must specify a url for destination Name of destination.
Action

Code	11256 (Data Services)
Type	Error
Cause	An error executing SQL caused the operation to fail. If debug level logging is enabled for the SQL Assembler, details are logged on the server.
Action

Code	11257 (Data Services)
Type	Error
Cause	The named query Name of query is undefined for the Name of method method on the destination Name of destination.
Action

Code	11258 (Data Services)
Type	Error
Cause	Missing SQL for Name of destination. Add to the configuration for destination.
Action

Code	11259 (Data Services)
Type	Error
Cause	Only one of sql or procedure may be set for Operation for which sql is being generated in destination Name of destination.
Action

Code	11260 (Data Services)
Type	Error
Cause	Error in SQL for Operation used to display clear error messages in destination Name of destination. SQL must not contain ''?'' use parameter replacement tokens instead (example: #paramName# where paramName is the property of the object).
Action

Code	11260 (Data Services)
Type	Error
Cause	Error in SQL for Name of operation in destination Name of destination. SQL must not contain ''?'' use parameter replacement tokens instead (example: #paramName# where paramName is the property of the object).
Action

Code	11261 (Data Services)
Type	Error
Cause	Error in SQL for Name of operation in destination . Matching pair of # tokens not found"
Action

Code	11262 (Data Services)
Type	Error
Cause	Only one of java-class or actionscript-class may be set for destination Name of destination.
Action

Code	11263 (Data Services)
Type	Error
Cause	The name for Name of operation for fill/count in destination Name of destination must be defined.
Action

Code	11264 (Data Services)
Type	Error
Cause	The name attribute on the procedure tag for Name of procedure in destination Name of destination must be defined.
Action

Code	11265 (Data Services)
Type	Error
Cause	The procedure-type for the Name of the property of the ActionScript object that is used as the parameter value property of the Name of the procedure which uses this parameter procedure on the Name of destination destination must be one of IN, OUT, or INOUT.
Action

Code	11266 (Data Services)
Type	Error
Cause	A property-value must be specified for each procedure-param in the Name of operation for which the sql is being generated procedure, Name of procedure.
Action

Code	11267 (Data Services)
Type	Error
Cause	No parameters passed to Name of fill/count method-method for the SQL assembler on destination Name of destination and there is no Name of fill/count method-method defined for zero args.
Action

Code	11268 (Data Services)
Type	Error
Cause	The following association relations specified by the destination Name of destination are not allowed as SQL assembler does not support associations: Type of associations.
Action

Code	11300 (Data Services)
Type	Error
Cause	Operation Name of operation not supported by endpoint Name of defined endpoint.
Action

Code	11301 (Data Services)
Type	Error
Cause	Name of remoting point specified is not a valid Remoting endpoint.
Action

Code	11302 (Data Services)
Type	Error
Cause	Name of endpoint has no associated active components.
Action

Code	11303 (Data Services)
Type	Error
Cause	Operation Name of operation is long lived and must be invoked asynchronously.
Action

Code	11304 (Data Services)
Type	Error
Cause	Operation Name of operation does not have a parameter called Name of parameter.
Action

Code	11305 (Data Services)
Type	Error
Cause	The specified document URL is malformed.
Action

Code	11306 (Data Services)
Type	Error
Cause	Class Class name should not have a fieldName Field name specified.
Action

Code	11307 (Data Services)
Type	Error
Cause	All non remotely-mapped parameters must have at least one set property.
Action

Code	11308 (Data Services)
Type	Error
Cause	Class Name of class could not be loaded by any available classloader
Action

Code	11309 (Data Services)
Type	Error
Cause	Operation not supported by JobManager service.
Action

Code	11310 (Data Services)
Type	Error
Cause	strong RemotingJobID class not found.
Action

Code	11311 (Data Services)
Type	Error
Cause	Do not define any security roles in flex configuration files. All authentication and authorization is handled by Live Cycle.
Action

Code	11312 (Data Services)
Type	Error
Cause	Operation Name of operation does not expect an array input parameter.
Action

Code	11313 (Data Services)
Type	Error
Cause	Array members do not match expected array type, Type of array, for operation Name of operation.
Action

Code	11314 (Data Services)
Type	Error
Cause	Read operations are not allowed on this destination.
Action

Code	11315 (Data Services)
Type	Error
Cause	Create operations are not allowed on this destination.
Action

Code	11316 (Data Services)
Type	Error
Cause	Update operations are not allowed on this destination.
Action

Code	11317 (Data Services)
Type	Error
Cause	Delete operations are not allowed on this destination.
Action

Code	11318 (Data Services)
Type	Error
Cause	Count operations are not allowed on this destination.
Action

Code	11319 (Data Services)
Type	Error
Cause	Problem marshalling instance returned by Assembler into XML: Exception Message.
Action

Code	11320 (Data Services)
Type	Error
Cause	Problem unmarshalling XML passed in by orchestration into a strong type: Exception Message.
Action

Code	11321 (Data Services)
Type	Error
Cause	Configuration parameter Name of the parameter may not be updated at this time. Revert changes.
Action

Code	11323 (Data Services)
Type	Error
Cause	Error parsing passed in XML - Name of XML does not have a Name of element element.
Action

Code	11323 (Data Services)
Type	Error
Cause	Error parsing passed in XML - XML does not have a Name of element element.
Action

Code	11324 (Data Services)
Type	Error
Cause	Returned item has complex property Name of property and cannot be retrieved as XML. You may use a strong typed method instead.
Action

Code	11325 (Data Services)
Type	Error
Cause	DocumentReference cannot be converted because the reference type is invalid. Set the reference type on your DocumentReference object.
Action

Code	11326 (Data Services)
Type	Error
Cause	Error encountered encoding DocumentReference using charset Charsets being used.
Action

Code	11327 (Data Services)
Type	Error
Cause	DocumentReference type is set to INLINE but content passed in was empty.
Action

Code	11328 (Data Services)
Type	Error
Cause	Endpoint Name of endpoint is disabled.
Action

Code	11329 (Data Services)
Type	Error
Cause	Operation Name of operation does not support the Remoting connector.
Action

Code	11330 (Data Services)
Type	Error
Cause	Service version string must have a major and minor version separated by a period.
Action

Code	11331 (Data Services)
Type	Error
Cause	Either the major or the minor version specified in the service version string is not an integer.
Action

Code	11332 (Data Services)
Type	Error
Cause	The service version argument must be a string.
Action

Code	11333 (Data Services)
Type	Error
Cause	User must be authenticated before documents may be uploaded.
Action	Attempting to upload a document without the correct permissions to the Remoting file upload service results in the error: User must be authenticated before uploading documents. Users have two options: 1) Go to the admin UI at HOME -> Settings -> Core System -> Core Configurations and check the "Allow non secured document uploaded from Flex applications" check box. or 2) Add the user trying to complete this operation to the "Document Upload Application Users" role or give them the "Document Upload" permission.

Code	11333 (Data Services)
Type	Error
Cause	User must be authenticated before documents may be uploaded.
Action

Code	11334 (Data Services)
Type	Error
Cause	LC.FileUploadAuthenticator only supports the \"getFileUploadToken\" operation.
Action

Code	11350 (Data Services)
Type	Error
Cause	Problem locating Name of JSP page JSP: Error message.
Action

Code	11351 (Data Services)
Type	Error
Cause	Processing problem in Name of JSP page JSP: Error message.
Action

Code	11352 (Data Services)
Type	Error
Cause	Note: read-only preferences are not editable.
Action

Code	11353 (Data Services)
Type	Error
Cause	Interact with this Flex application in View mode and edit its preferences in Edit mode.
Action

Code	12000 (Data Services)
Type	Error
Cause	Failed to delete existing file: File name.
Action

Code	12001 (Data Services)
Type	Error
Cause	XFA datasets must use ''xfa'' as the prefix for the qualified element name.
Action

Code	12002 (Data Services)
Type	Error
Cause	Unable to convert xfa:dataset Document to a String.
Action

Code	12003 (Data Services)
Type	Error
Cause	Unable to obtain UTF-8 bytes from a String representation of the xfa:dataset.
Action

Code	12004 (Data Services)
Type	Error
Cause	Your current license is not sufficient for the PDF generation feature.
Action

Code	13500 (Data Services)
Type	Error
Cause	Building an SSLContext failed because no KeyStore file was defined, or the supplied KeyStore file path could not be resolved.
Action

Code	13501 (Data Services)
Type	Error
Cause	Building an SSLContext failed because the KeyStore password file, Name of password file, can not be found.
Action

Code	13502 (Data Services)
Type	Error
Cause	Building an SSLContext failed because the KeyStore password file, password file, can not be read.
Action

Code	13503 (Data Services)
Type	Error
Cause	Building an SSLContext failed because neither a KeyStore password nor password file was defined.
Action

Code	13504 (Data Services)
Type	Error
Cause	Building an SSLContext failed because a password deobfuscator must be available to process obfuscated passwords.
Action

Code	13505 (Data Services)
Type	Error
Cause	Building an SSLContext failed because the requested KeyStore type, Name of keystore type, is not available.
Action

Code	13506 (Data Services)
Type	Error
Cause	Building an SSLContext failed because the KeyStore file could not be found, is unreadable, or the supplied password is incorrect.
Action

Code	13507 (Data Services)
Type	Error
Cause	Building an SSLContext failed because the algorithm used to test KeyStore integrity can not be found.
Action

Code	13508 (Data Services)
Type	Error
Cause	Building an SSLContext failed because not all certificates in the KeyStore could be loaded.
Action

Code	13509 (Data Services)
Type	Error
Cause	Building an SSLContext failed because the algorithm, , is not available.
Action

Code	13510 (Data Services)
Type	Error
Cause	Building an SSLContext failed because the KeyStore password is incorrect.
Action

Code	13511 (Data Services)
Type	Error
Cause	Building an SSLContext failed because a KeyManagerFactory could not be initialized.
Action

Code	13512 (Data Services)
Type	Error
Cause	Building an SSLContext failed because the requested TrustStore type, Type of truststore, is not available.
Action

Code	13513 (Data Services)
Type	Error
Cause	Building an SSLContext failed because the TrustStore file could not be found, is unreadable or the supplied password is incorrect.
Action

Code	13514 (Data Services)
Type	Error
Cause	Building an SSLContext failed because the algorithm used to test TrustStore integrity can not be found.
Action

Code	13515 (Data Services)
Type	Error
Cause	Building an SSLContext failed because not all certificates in the TrustStore could be loaded.
Action

Code	13516 (Data Services)
Type	Error
Cause	Building an SSLContext failed because the TrustManagerFactory could not be initialized.
Action

Code	13517 (Data Services)
Type	Error
Cause	Building an SSLContext failed because the protocol, Name of protocol, is not available.
Action

Code	13518 (Data Services)
Type	Error
Cause	Initializing the SSLContext after construction failed due to a key management problem.
Action

Code	13519 (Data Services)
Type	Error
Cause	Invalid certificate alias Name of certificate alias has been specified. No match was found in the keystore.
Action

Code	13550 (Data Services)
Type	Error
Cause	SocketServer Id of the server cannot open a Selector for accepting new connections.
Action

Code	13551 (Data Services)
Type	Error
Cause	SocketServer Id of the server cannot bind to accept client connections on port Port number because another process has already bound the port. Ensure that multiple endpoints across all applications are not configured to use this same port.
Action

Code	13552 (Data Services)
Type	Error
Cause	The acceptor for SocketServer Id of the server has failed. Refer to this exception''s root cause for the underlying problem.
Action

Code	13553 (Data Services)
Type	Error
Cause	The Name of property property for a SocketServer component cannot be null.
Action

Code	13554 (Data Services)
Type	Error
Cause	The Name of property property for a SocketServer must be assigned before the server is started.
Action

Code	13555 (Data Services)
Type	Error
Cause	The acceptor for SocketServer Id of the server was interrupted waiting for its accept thread to start.
Action

Code	13556 (Data Services)
Type	Error
Cause	SocketServer Id of the server cannot open a Selector for managing accepted connections.
Action

Code	13557 (Data Services)
Type	Error
Cause	The reactor, Id of the reactor, for SocketServer Id of the server has failed. Refer to this exception''s root cause for the underlying problem.
Action

Code	13558 (Data Services)
Type	Error
Cause	The reactor, Id of the reactor, for SocketServer Id of the server was interrupted waiting for its thread to start.
Action

Code	13559 (Data Services)
Type	Error
Cause	SocketServer Id of the server failed to start because the required class Name of Class could not be found and instantiated. Ensure the class is on your classpath.
Action

Code	13560 (Data Services)
Type	Error
Cause	Creating SocketServer Id of the server failed because the required class Name of Class could not be found and instantiated. Ensure the class is on your classpath.
Action

Code	13561 (Data Services)
Type	Error
Cause	BindSocketAddress assignment conflict for SocketServer . The value being assigned, Value being assigned, conflicts with the existing assigned value, Existing value.
Action

Code	13562 (Data Services)
Type	Error
Cause	Invalid connection buffer type Type of buffer cannot be assigned to the Supported buffer type; specify a supported value.
Action

Code	13563 (Data Services)
Type	Error
Cause	SocketServer Id of the server failed to start because a specified cipher suite, Name of cipher suite, is not supported.
Action

Code	13650 (Data Services)
Type	Error
Cause	The endpoint, Name of endpoint, depends upon a SocketServer but a referenced SocketServer id was not defined and no dedicated SocketServer settings were defined.
Action

Code	13651 (Data Services)
Type	Error
Cause	The endpoint, Name of endpoint, is attempting to use port Port number of SocketServer Id of the server but uses a protocol that cannot be handled appropriately alongside the other endpoint(s) that have also registered to use this port. Configure this endpoint to use a different server and port.
Action

Code	13652 (Data Services)
Type	Error
Cause	The endpoint, Name of endpoint, must create an internal ProtocolHandlerFactory for use in handling data on its connections.
Action

Code	13653 (Data Services)
Type	Error
Cause	The endpoint, Name of endpoint, is using a referenced SocketServer with a protocol handler factory that does not extend DefaultProtocolHandlerFactory.
Action

Code	13654 (Data Services)
Type	Error
Cause	No endpoint is defined to service a client socket connection to port .
Action

Code	13655 (Data Services)
Type	Error
Cause	The endpoint, Name of endpoint, failed to register a bind address/port with its referenced SocketServer Server address:Server port number
Action

Code	13700 (Data Services)
Type	Error
Cause	Client Client Id is unsubscribed because the max-queue-size limit Maximum size of message queue has been reached due to the message Message Id.
Action

Code	13750 (Data Services)
Type	Error
Cause	Service does not support reliability operation: Name of operation.
Action

Code	13751 (Data Services)
Type	Error
Cause	Received a reliable message but no reliable message sequence for the client has been negotiated.
Action

Code	13752 (Data Services)
Type	Error
Cause	Client sent an unreliable message to a reliable destination.
Action

Code	13753 (Data Services)
Type	Error
Cause	Reliable messaging is only available to clients that connect to an NIO endpoint (RTMP/AMF/HTTP). The endpoint Name of endpoint the client has connected to does not support reliable messaging.
Action

Code	13800 (Data Services)
Type	Error
Cause	Gateway service Gateway service Id must define at least one gateway endpoint.
Action

Code	13801 (Data Services)
Type	Error
Cause	Gateway endpoint for gateway service gateway service Id must define at least one url.
Action

Code	13801 (Data Services)
Type	Error
Cause	Gateway endpoint for gateway service gateway service Id must define at least one url.
Action

Code	13802 (Data Services)
Type	Error
Cause	Gateway service Gateway service Id cannot connect to its configured gateway endpoint which is required for startup; make sure the endpoint is accessible from the service or set require-for-startup to false.
Action

Code	13804 (Data Services)
Type	Error
Cause	Gateway endpoint Name of endpoint is misconfigured to use a load-calculator that does not extend flex.messaging.endpoints.LoadCalculator.
Action

Code	13805 (Data Services)
Type	Error
Cause	Gateway service Gateway service Id requires an authenticated client. Login before interacting with any gateway service destinations.
Action

Code	13806 (Data Services)
Type	Error
Cause	Gateway endpoint Name of endpoint cannot create gateway session; acceptGatewaySessions property is set to false.
Action

Code	13807 (Data Services)
Type	Error
Cause	Gateway connection closed.
Action

Code	50100 (Data Services)
Type	Error
Cause	The Hibernate Type class generation failed because the class, Class name, already exists.
Action

Code	50101 (Data Services)
Type	Error
Cause	Unknown failure while generating the Hibernate Type class, Class name.
Action

Code	50102 (Data Services)
Type	Error
Cause	Error occurred while generating equals method of Hibernate Type, Class name, for Entity, Entity name. The generated method cannot be compiled.
Action

Code	50103 (Data Services)
Type	Error
Cause	Error occurred while generating hashCode method of Hibernate Type, Class name, for Entity, Entity name. The generated method cannot be compiled.
Action

Code	50104 (Data Services)
Type	Error
Cause	Error occurred while generating getter method for property, Property name, of Hibernate Type, Class name, for Entity, Entity name. The generated method cannot be compiled.
Action

Code	50105 (Data Services)
Type	Error
Cause	Error occurred while generating setter method for property, Property name, of Hibernate Type, Class name, for Entity, Entity name. The generated method cannot be compiled.
Action

Code	50106 (Data Services)
Type	Error
Cause	Error occurred while generating field for property, Property name, of Hibernate Type, Class name, for Entity, Entity name. The generated method cannot be compiled.
Action

Code	50107 (Data Services)
Type	Error
Cause	Error occurred while generating field for property, Property name, of Hibernate Type, Class name, for Entity, Entity name. Type not found, Property type.
Action

Code	50108 (Data Services)
Type	Error
Cause	Unknown failure while generating the Hibernate Type class, Class name, for Entity, Entity name. The class cannot be compiled.
Action

Code	50109 (Data Services)
Type	Error
Cause	Error occurred while generating bean info class, for Entity, Entity name. The getPropertyDescriptors method cannot be compiled.
Action

Code	50300 (Data Services)
Type	Error
Cause	Error: Unable to deploy model ''{0}'': Model already exists.
Action

Code	50301 (Data Services)
Type	Error
Cause	Error loading model Model name: Exception message.
Action

Code	50302 (Data Services)
Type	Error
Cause	Error count error(s) found while reading model Model name:\nMessages.
Action

C