XMLW Messages

Explanation:	The function that initializes the XML environment returned a failure code.
User Response:	Verify the XML environment is set up correctly, such as the environment variables are set properly, the .dll files are in the correct location on Windows or the shared libraries on UNIX, and the supporting .dat files are present.

XMLW_31002 An error occurred while trying to initialize XML manager.

Explanation:	The Integration Service failed to create and initialize objects.
User Response:	See the previous error message for the reasons for the failure.

XMLW_31003 An error occurred while trying to uninitialize XML environment.

Explanation:	The Integration Service failed to deinitialize the XML environment.
User Response:	See the previous error message for the reasons for the failure.

XMLW_31004 The field <field name> with repository ID <ID number> should not belong to XML group <group number> named <group>.

Explanation:	The set of fields that belong to the XML group in the message is in an incorrect group.
User Response:	Check the target definition in the Designer to verify the position of the fields belonging to the group. Or contact Informatica Global Customer Support.

XMLW_31005 XML group <group> does not have any fields.

Explanation:	Every XML group must have at least one field. The repository has inconsistencies.
User Response:	Import the target again. Or, contact Informatica Global Customer Support.

XMLW_31006 There already was a row inserted into output for the topmost group. Rejecting the row# <row number>.

Explanation:	The topmost group must have only one row of data since the XML file can have only one root.
User Response:	Make sure that the data to this group is limited to one row.

XMLW_31007 Row# <row number> has a NULL PK value for XML group <group>.

Explanation:	The XML Writer received data for a primary key that is null.
User Response:	The primary key cannot be null. Check the data and the mapping for inconsistencies. Run the Debugger.

XMLW_31008 Row# <row number> has a NULL FK value for NOT TOPMOST XML group <group>.

Explanation:	The foreign key is null and cannot find the parent row. The child group rows must attach to the parent group by primary-foreign key relationships.
User Response:	Check the data and the mapping for inconsistencies. Run the Debugger.

XMLW_31009 Unexpected error processing schema definition <schema definition>.

Explanation:	When the Integration Service attempted to recreate the XML target definition structure from the metadata, it encountered an error while parsing.
User Response:	Contact Informatica Global Customer Support.

XMLW_31010 Unexpected error occurred while trying to set the value of the element <XML element> with XML mapping <XML Map> to <value>.

Explanation:	Internal error. You tried to set a value for the element. Some reasons might be that the value is incorrect or the process ran out of memory.
User Response:	Contact Informatica Global Customer Support.

XMLW_31011 An error occurred while trying to convert the data for field <field name> repository ID <ID number> of the row <row number> to text.

Explanation:	The XML Writer failed to convert the data into text.
User Response:	Check previous messages in the log for more information. Then contact Informatica Global Customer Support.

XMLW_31012 Cannot register XML group <group> for target <target instance> - no corresponding group definition found in the target.

Explanation:	Internal error. The target requested a group that does not exist.
User Response:	Contact Informatica Global Customer Support.

XMLW_31013 Unknown (or illegal) attribute value <value> for attribute <attribute name>. Check repository for possible data corruption.

Explanation:	Neither the first nor the last values were saved in the repository due to repository inconsistencies.
User Response:	Contact Informatica Global Customer Support.

XMLW_31014 Unexpected error while generating XML text for the row being removed from the DOM tree. Row's PK value is <value>.

Explanation:	The XML writer encountered errors while generating code for values.
User Response:	Run the Debugger to check the data for inconsistencies. Contact Informatica Global Customer Support.

XMLW_31016 Unknown error generating the output XML text.

Explanation:	The Integration Service encountered an error while trying to generate XML output.
User Response:	Run the Debugger to check the data. Contact Informatica Global Customer Support.

XMLW_31017 The mapping text <mapping text> for field <field name> of the XML target <target instance> is not valid for target's code page <code page>. Failed character code is <character number in Unicode>.

Explanation:	At initialization time, the Integration Service found that the text in the mapping is not in the target code page.
User Response:	Check that the XML mapping is compatible with the target code page.

XMLW_31018 Unexpected error occurred while initializing the XML output generator.

Explanation:	Internal error.
User Response:	Contact Informatica Global Customer Support.

XMLW_31019 Error initializing output file for XML target <target name>.

Explanation:	The XML Writer failed to create an output file.
User Response:	Check that the path to the output file exists and is accurate. Verify the disk space is sufficient. Verify write permissions to the output file.

XMLW_31020 Cannot find an XML group for the incoming block of rows. Fatal error.

Explanation:	The XML Writer cannot find the appropriate group corresponding to the block of data.
User Response:	Run the session again. If it fails, contact Informatica Global Customer Support.

XMLW_31021 Error occurred while processing EOF for the XML target <target instance> group <group>.

Explanation:	The XML Writer encountered errors when processing the end of file (EOF) for the group.
User Response:	Contact Informatica Global Customer Support.

XMLW_31022 Fatal error while flushing to file <file name>. System error message is <error message>.

Explanation:	When writing to file, the XML Writer failed with the operating system message.
User Response:	Check file write permissions, disk space, and that the path to the file exists. Check the operating system error message and contact the system administrator.

XMLW_31023 Error initializing XML DOM object.

Explanation:	Internal error.
User Response:	Contact Informatica Global Customer Support.

XMLW_31024 Error transferring staged file for XML target <target instance> using FTP.

Explanation:	The Integration Service could not transfer the XML file by FTP.
User Response:	Verify FTP permissions, directory path, network connection, and that the FTP server is running. Run the session again.

XMLW_31026 Fatal error opening file <file name> for XML output.

Explanation:	The XML Writer failed to open the file. Some reasons could be that the file did not have write permissions. The path to the file is incorrect.
User Response:	Check file write permissions, directory path, disk space, and that the file exists.

XMLW_31027 Fatal error closing XML output file <file name>. System error message is <error message>.

Explanation:	The XML Writer could not close the XML output file. Some reasons could be that the file did not have write permissions. The path to the file is incorrect.
User Response:	Check the operating system message for more information.

XMLW_31029 Cannot locate XML init/deinit functions in the DLL <.dll file name>.

Explanation:	The XML .dll file does not contain the initialization and deinitialization functions.
User Response:	Verify that the .dll file is the correct file shipped with the product. If it is incorrect, contact Informatica Global Customer Support.

XMLW_31030 FK field <field name> for group <group> has to be projected, i.e. there has to be an input field for it.

Explanation:	The foreign key must be connected in the mapping.
User Response:	Check that the mapping and that the foreign key are connected. Contact Informatica Global Customer Support.
Explanation:	The target is not defined as a flat file or XML target. It is an undefined object.
User Response:	Contact Informatica Global Customer Support.

XMLW_31040 Field <field name> of the *ROOT* XML group <group> is projected while the PK field is not.

Explanation:	Internal error. If the Primary Key is not connected, none of the fields must be connected. If the Primary Key is connected, other fields may be connected.
User Response:	Connect the PK field of the root group.

XMLW_31041 FK of the group <group> and PK of the parent group <group> should both either have an input field or not.

Explanation:	Internal error. If you connect the Primary Key of the root group, then the Foreign Key of all the immediate child groups must be connected, unless the child group fields do not have input values. If the Primary Key is not connected, none of the fields may be connected.
User Response:	Validate the mapping and run the session again. Or contact Informatica Global Customer Support.

XMLW_31043 FK is the only projected field from group <group>.

Explanation:	You are running a session against a mapping with an XML target. The foreign key in the named group is the only projected field in that group.
User Response:	Edit the mapping to project additional fields into the named group.

XMLW_31047 MQ error occurred while flushing XML output.

Explanation:	The Integration Service could process XML data from the WebSphere MQ queue.
User Response:	Verify that the WebSphere MQ environment settings are correct, that the queue you specified in the queue connection properties exists, and that the connection properties are valid.

XMLW_31056 Fatal error opening WebSphere MQ queue <queue> for XML output.

Explanation:	The Integration Service could not open the WebSphere MQ queue.
User Response:	Verify that the WebSphere MQ environment settings are correct, that the queue you specified in the queue connection properties exists, and that the connection properties are valid.

XMLW_31059 Fatal error returned while closing XML document <target name> after incremental flush/commit.

Explanation:	The Integration Server could not close the XML target file. The file might not have write permissions or the path to the file is incorrect.
User Response:	Check previous error messages for more information.

XMLW_31060 Fatal error <error number> occurred while flushing XML output <target name>.

Explanation:	The XML Writer failed to write data to a target file.
User Response:	Check file write permissions, disk space, and that the path to the file exists. Check other error messages for more information.

XMLW_31061 Fatal error <error number> occurred while closing XML document <target name>.

Explanation:	The XML Writer could not close the XML target file. The file might not have write permissions or the path to the file is incorrect.
User Response:	Check previous error messages for more information.

XMLW_31063 Fatal error <error number> occurred while opening file list <target>.

Explanation:	The XML Writer failed to open the file list. The file might not have write permissions or the path to the file is incorrect.
User Response:	Check the file write permissions, the directory path, disk space, or if the file exists.

XMLW_31064 Fatal error transferring local file <file name> into remote location <path> using FTP. The file list will not be produced.

Explanation:	The Integration Service could not transfer the XML file by FTP to produce a file list at the remote location.
User Response:	Verify FTP permissions, the directory path, network connections, and that the FTP server is running.

XMLW_31065 Fatal error <error number> opening an FTP connection for a file list <file name>.

Explanation:	The Integration Service failed to open an FTP connection for a source using a file list.
User Response:	Verify FTP permissions, the directory path, network connections, and that the FTP server is running. Check other error messages for more information.

XMLW_31066 Fatal error <error number> while generating file list.

Explanation:	The Integration Service failed to generate a file list. The file might not have write permissions or the path to the file is incorrect.
User Response:	Check the file write permissions, the directory path, disk space, or if the file exists. Check previous error messages for more information.

XMLW_31078 Error: ‘Output XML on Flush/Commit’ option for the MQ session is no longer supported. Open this mapping in the designer and edit the XML target instance. Change the value of ‘On Commit’ property to ‘Create New Document’.

Explanation:	You are using an upgraded MQ session that uses the Output XML on Flush/Commit attribute. PowerCenter no longer supports this option.
User Response:	Open the mapping. Edit the XML target instance. Clear the Output XML on Flush/Commit option. Choose the Create New Document option for the On Commit property.

XMLW_31079 Error: Unknown On Commit attribute value in target <target name>. Check repository for possible corruption.

Explanation:	You are using an upgraded XML session that uses the Output XML on Flush/Commit attribute. PowerCenter no longer supports this option.
User Response:	Open the mapping. Edit the XML target instance. Clear the Output XML on Flush/Commit option. Choose the Create New Document option for the On Commit property.

XMLW_31080 Error: Orphans were encountered.

Explanation:	The Integration Service encountered child rows that have no parents in the XML Generator transformation.
User Response:	To avoid failing a session with orphan rows, set the Orphan Row Handling session property to “Ignore.” The Integration Service ignores the orphan rows.

XMLW_31086 Row <row number> in XML group <group> has more than one non-NULL hierarchical foreign key value. This row will be dropped.

Explanation:	When a row has two possible parents, one of the foreign keys in the row must be NULL.
User Response:	None.

XMLW_31089 Error: The cache size <cache size> specified for XML target <target name> exceeds the 32-bit address space. It cannot be more than <cache size> on a 32-bit server.

Explanation:	The Integration Service uses a data cache to store XML row data while it generates an XML document. The cache size is the sum of all the groups in the XML target instance. The XML target cache is too large.
User Response:	Reduce the target cache size in the XML target properties.

XMLW_31090 Unable to create index file <file name>.

Explanation:	The Integration Service failed to create the cache index for the XML cache.
User Response:	Check the file write permissions, the directory path, disk space. Check previous error messages for more information.

XMLW_31091 Error: Index file operation error <error number>.

Explanation:	The Integration Service failed to write the cache index for the XML cache.
User Response:	Check the file write permissions, the directory path, disk space. Check previous error messages for more information.

XMLW_31092 Error: Encountered an error while generating the XML document.

Explanation:	The XML Writer failed to write data to a target file.
User Response:	Check file write permissions, disk space, and that the path to the file exists. Check other error messages for more information.

XMLW_31093 Error: Encountered an error while establishing type hierarchical relationship.

Explanation:	The session could not process XML data for a child view because there is no data for the parent view.
User Response:	Check the data for inconsistencies, or change the mapping.

XMLW_31108 Error: An appropriate start row was not found for XML root group <group> with circular reference. No output was generated.

Explanation:	If the data has multiple root rows with circular references, but none of the root rows has a null foreign key, the Integration Service cannot find a start row.
User Response:	Verify the source data has one row going to the root that is not a child of another group.

XMLW_31110 Error: Duplicate row detected for single occurring group <group>, with parent group <parent group>.

Explanation:	The Integration Service detected a duplicate row in a group.
User Response:	To avoid failing the session for duplicate rows, set the Duplicate Row Handling session property to First Row or Last Row for the target.

XMLW_31118 Error: The FK field <foreign key> for the XML derived group <group> in XML Target <target name> is not projected. No output rows for the group can be generated due to missing base type information.

Explanation:	The session failed because the foreign key in a derived XML group has no data.
User Response:	Add a link to the foreign key in the mapping.

XMLW_31210 Fatal error transferring local file <file name> into remote location <path> using SFTP. The file list will not be produced.

Explanation:	The Integration Service could not transfer the XML file by SFTP to produce a file list at the remote location.
User Response:	Verify SFTP permissions, the directory path, network connections, and that the SFTP server is running.

XMLW_31211 Fatal error opening remote list file <file name> using SFTP.

Explanation:	The Integration Service failed to open an SFTP connection for a source using a file list.
User Response:	Verify SFTP permissions, the directory path, network connections, and that the SFTP server is running. Check other error messages for more information.