Explanation: | A session attribute for the Web Services Provider source or target contains inconsistencies. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | You tried to run a session that contains more than one Web Services Provider source. |
User Response: | Edit the mapping to ensure that it contains only one Web Services Provider source. |
Explanation: | You tried to run a session that contains more than one Web Services Provider output target. |
User Response: | Edit the mapping to ensure that it contains only one Web Services Provider output target. The mapping can contain multiple fault targets and multiple instances of one output target. |
Explanation: | The Integration Service machine is out of memory. |
User Response: | Check memory usage of the machine. Other processes may be using too much memory. Close unnecessary applications and restart the system. You might want to increase swap space. |
Explanation: | The Real-time license is expired, or you have not applied the license key to the license file. |
User Response: | Apply the current Real-time license key to the license file. If you do not have a current license, contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The Integration Service received an invalid message from the Web Services Hub. |
User Response: | Verify the client application program. |
Explanation: | The Integration Service encountered an error creating the message to send to the Web Services Hub. The message may contain inconsistent data. |
User Response: | Check the session log for related messages. Run the Debugger to view data. |
Explanation: | The Integration Service encountered an error processing the end of file. |
User Response: | Check the session log for related messages. |
Explanation: | The Integration Service encountered an error initializing a connection to the Web Services Hub. |
User Response: | Check the additional error message for more information. |
Explanation: | The Integration Service encountered an error disconnecting from the Web Services Hub. |
User Response: | Check the additional error message for more information. |
Explanation: | The Integration Service encountered an error reading from the Web Services Hub. |
User Response: | Check the additional error message for more information. |
Explanation: | The Integration Service encountered an error writing to the Web Services Hub. |
User Response: | Check the additional error message for more information. |
Explanation: | The Integration Service encountered an error flushing to the Web Services Hub. |
User Response: | Check the additional error message for more information. |
Explanation: | The Integration Service could not write the message to the recovery cache. The Integration Service machine might be low on available disk space. |
User Response: | Check the additional error message for more information. Verify available space on the Integration Service machine. |
Explanation: | The Integration Service could not read the message from the recovery cache. The message might be invalid. |
User Response: | Check the additional error message for more information. |
Explanation: | You tried to run the Debugger against a mapping or a reusable session that has Web Service Provider source or target. |
User Response: | You must run the Debugger against the session instance in the workflow that contains the service information. |
Explanation: | The Web Services Hub encountered an error retrieving service information from the repository. |
User Response: | Use the Workflow Manager to verify that the Web Services Hub is registered to the repository. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The recovery cache folder specified for the XML source configured to use the Web Services Provider Reader for XML is either invalid or it does not exist. |
User Response: | Verify the recovery cache folder name and location. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | You are running a session in recovery mode, and the Integration Service failed to cache the Web Services Provider message. The Integration Service might have written only part of the message to the recovery cache before the session failed. |
User Response: | Check the session log for related messages. |
Explanation: | The session failed, and the Integration Service was unable to truncate the partial message in the cache. |
User Response: | Check the additional error message for more information. |
Explanation: | The Integration Service encountered an error flushing the message cache. |
User Response: | Check the additional error message for more information. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The Integration Service could not commit messages to the target when it reached the terminating condition specified in the session properties. The session failed. |
User Response: | Check the session log for additional messages. |
Explanation: | The Integration Service encountered an error initializing the XML parser. |
User Response: | Check the session log for related messages. |
Explanation: | The Integration Service encountered an error initializing the flat file reader. |
User Response: | Check the session log for additional messages. |
Explanation: | The Integration Service encountered an error parsing the XML file. |
User Response: | Check the session log for additional messages. |
Explanation: | The Integration Service encountered an error parsing the flat file. |
User Response: | Check the session log for additional messages. |
Explanation: | The Integration Service encountered an error deinitializing the XML parser. |
User Response: | Check the session log for additional messages. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The request-response session contains a flat file or XML source with the reader type changed to Web Services Provider reader. The Web Services Hub can process one message for each session. If the message count is greater than 1 for this type of session, the session fails. |
User Response: | Configure the message count to 1 in the reader properties. |
Explanation: | The Web Services Provider Writer for flat files could not create the target flat file. |
User Response: | Check the session log for additional messages. |
Explanation: | The Web Services Provider Writer for XML could not create the XML target file. |
User Response: | Check the session log for additional messages. |
Explanation: | The Web Services Provider Writer for flat files failed to process the flat file message. |
User Response: | Check the session log for additional messages. |
Explanation: | The Web Services Provider Writer for XML failed to process the XML message. |
User Response: | Check the session log for additional messages. |
Explanation: | The Web Services Provider Writer for XML encountered an error processing the end of file (EOF) for the target group. |
User Response: | Check the session log for additional messages. |
Explanation: | The Web Services Provider Writer for XML failed to send the XML message to the Web Services Hub. |
User Response: | Check the session log for additional messages. |
Explanation: | The XML target cache folder specified in the session properties is either invalid or it does not exist. |
User Response: | Verify the XML cache folder name. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |