PowerExchange for JMS Messages

Explanation:	You wanted to import a repository object that represents a JMS source or target definition from an XML file. However, the datatype for the specified field in the XML file is invalid. The XML file may have been modified.
User Response:	Import the repository object from a new XML file. Avoid editing the XML file before importing.

Field <field name> is invalid because JMS source field does not allow “NOTNULL.”

Explanation:	You wanted to import a repository object that represents a JMS source definition from an XML file. However, the specified field in the XML file is set to Not Null. The XML file may have been modified.
User Response:	Import the repository object from a new XML file. Avoid editing the XML file before importing.

Header field <field name> is missing.

Explanation:	You wanted to import a repository object that represents a JMS source definition from an XML file. However, you attempted to import an XML file that represents a JMS target.
User Response:	If an XML file represents a JMS source definition, you must import it as a JMS source definition.
Explanation:	You wanted to import a repository object that represents a JMS target definition from an XML file. However, you attempted to import an XML file that represents a JMS source.
User Response:	If an XML file represents a JMS target definition, you must import it as a JMS target definition.
Explanation:	A header field is missing. The XML file may have been modified.
User Response:	Import the repository object from a new XML file. Avoid editing the XML file before importing.

The JMS body field name is invalid.

Explanation:	You wanted to import a repository object that represents a JMS source or target definition from an XML file. However, a JMS body field name is invalid. The XML file may have been modified.
User Response:	Import the repository object from a new XML file. Avoid editing the XML file before importing.

The JMS property field value is invalid.

Explanation:	You wanted to import a repository object that represents a JMS source or target definition from an XML file. However, the value for a JMS property field is invalid. The XML file may have been modified.
User Response:	Import the repository object from a new XML file. Avoid editing the XML file before importing.

Message body field is missing.

Explanation:	You wanted to import a repository object that represents a JMS source or target definition in Bytes message, Text message, or Map message format from an XML file. However, the XML file contains no body fields. The XML file may have been modified.
User Response:	Import the repository object from a new XML file. Avoid editing the XML file before importing.

The object contains an invalid message body type.

Explanation:	You wanted to import a repository object that represents a JMS source or target definition from an XML file. However, the XML file contains an invalid message body type. The XML file may have been modified.
User Response:	Import the repository object from a new XML file. Avoid editing the XML file before importing.

The object has an invalid field category <category>.

Explanation:	You wanted to import a repository object that represents a JMS source or target definition from an XML file. However, there is an invalid category for a message field in the XML file. The XML file may have been modified.
User Response:	Import the repository object from a new XML file. Avoid editing the XML file before importing.

The object has an invalid header field.

Explanation:	You wanted to import a repository object that represents a JMS source or target definition from an XML file. However, the XML file contains an invalid header field. The XML file may have been modified.
User Response:	Import the repository object from a new XML file. Avoid editing the XML file before importing.

The object has an invalid header field map value.

Explanation:	You wanted to import a repository object that represents a JMS source or target definition from an XML file. However, the XML file contains an invalid map value for a header field. The XML file may have been modified.
User Response:	Import the repository object from a new XML file. Avoid editing the XML file before importing.

The object is a Bytes Message, but the body field name is invalid.

Explanation:	You wanted to import a repository object that represents a JMS source or target definition in Bytes message format from an XML file. However, the body field name in the XML file is invalid. The XML file may have been modified.
User Response:	Import the repository object from a new XML file. Avoid editing the XML file before importing.

The object is a Bytes Message, but the datatype for the body field is invalid.

Explanation:	You wanted to import a repository object that represents a JMS source or target definition in Bytes message format from an XML file. However, the datatype for the body field in the XML file is invalid. The XML file may have been modified.
User Response:	Import the repository object from a new XML file. Avoid editing the XML file before importing.

The object is a Text Message, but the body field name is invalid.

Explanation:	You wanted to import a repository object that represents a JMS source or target definition in Text message format from an XML file. However, the body field name in the XML file is invalid. The XML file may have been modified.
User Response:	Import the repository object from a new XML file. Avoid editing the XML file before importing.

The object is a Text Message, but the datatype for the body field is invalid.

Explanation:	You wanted to import a repository object that represents a JMS source or target definition in Text message format from an XML file. However, the datatype for the body field in the XML file is invalid. The XML file may have been modified.
User Response:	Import the repository object from a new XML file. Avoid editing the XML file before importing.

The precision is invalid.

Explanation:	You wanted to import a repository object that represents a JMS source or target definition from an XML file. However, the precision for a field is invalid. The XML file may have been modified.
User Response:	Import the repository object from a new XML file. Avoid editing the XML file before importing.

Unknown error happened.

Explanation:	The Designer encountered an unknown error. The Repository Service might not be running.
User Response:	Make sure the Repository Service is running. If necessary, start the Repository Service.
Explanation:	The repository may contain inconsistencies.
User Response:	Contact Informatica Global Customer Support.

The datatype assigned to the field <field name> is invalid.