Message Reference > W Message Codes > WSP Messages
  

WSP Messages

WSP_33002 Failed to get attribute <attribute name>.

Explanation:
A session attribute for the Web Services Provider source or target contains inconsistencies.
User Response:
Contact Informatica Global Customer Support.

WSP_33006 The mapping contains more than one Web Services Provider source.

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.

WSP_33007 The mapping contains more than one Web Services Provider target.

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.

WSP_33008 Out of memory.

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.

WSP_33009 Valid Real-time options key is not found, unable to run this Web Service session. Please obtain a valid real-time options key.

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.

WSP_34007 Failed to build the acknowledgement message.

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

WSP_34008 Failed to parse the message.

Explanation:
The Integration Service received an invalid message from the Web Services Hub.
User Response:
Verify the client application program.

WSP_34010 Failed to build the data message.

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.

WSP_34011 Failed to build the eof message.

Explanation:
The Integration Service encountered an error processing the end of file.
User Response:
Check the session log for related messages.

WSP_34014 Failed to init connection, status code <code>, error message <error message>.

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.

WSP_34015 Failed to deinit connection, status code <code>, error message <error message>.

Explanation:
The Integration Service encountered an error disconnecting from the Web Services Hub.
User Response:
Check the additional error message for more information.

WSP_34016 Failed to read data, status code <code>, error message <error message>.

Explanation:
The Integration Service encountered an error reading from the Web Services Hub.
User Response:
Check the additional error message for more information.

WSP_34017 Failed to write data, status code <code>, error message <error message>.

Explanation:
The Integration Service encountered an error writing to the Web Services Hub.
User Response:
Check the additional error message for more information.

WSP_34018 Failed to flush data, status code <code>, error message <error message>.

Explanation:
The Integration Service encountered an error flushing to the Web Services Hub.
User Response:
Check the additional error message for more information.

WSP_34019 Failed to serialize data, error message <error message>.

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.

WSP_34020 Failed to deserialize data, error message <error message>.

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.

WSP_34030 Must have workflow context to run this session.

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.

WSP_34034 Error occurred while retrieving service information from repository.

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.

WSP_35001 Cache folder attribute cannot be fetched for reader partition <partition number>.

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

WSP_35002 Cache folder specified for reader partition <partition number> is invalid.

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.

WSP_35003 Reader partition <partition number> failed to register for recovery.

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

WSP_35005 Reader partition <partition number> failed to cache message.

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.

WSP_35006 Reader partition <partition number> failed to truncate message cache to last serialized message: <message text>.

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.

WSP_35008 Reader partition <partition number> failed to flush the cache: <message text>.

Explanation:
The Integration Service encountered an error flushing the message cache.
User Response:
Check the additional error message for more information.

WSP_35010 Reader partition <partition number> failed to unregister for recovery.

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

WSP_35012 Failed to close checkpoint.

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.

WSP_35013 XML parser <partition ID> initialization failed.

Explanation:
The Integration Service encountered an error initializing the XML parser.
User Response:
Check the session log for related messages.

WSP_35015 Flat file parser <partition ID> initialization failed.

Explanation:
The Integration Service encountered an error initializing the flat file reader.
User Response:
Check the session log for additional messages.

WSP_35017 XML parser <partition ID> parse failed.

Explanation:
The Integration Service encountered an error parsing the XML file.
User Response:
Check the session log for additional messages.

WSP_35018 File parser <partition ID> fetch failed.

Explanation:
The Integration Service encountered an error parsing the flat file.
User Response:
Check the session log for additional messages.

WSP_35019 XML parser <partition ID> deinitialization failed.

Explanation:
The Integration Service encountered an error deinitializing the XML parser.
User Response:
Check the session log for additional messages.

WSP_35020 Error in populating message fields.

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

WSP_35021 MsgCount cannot be greater than 1 for two-way Non-WS Aware service.

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.

WSP_36002 Writer target <target name> partition <partition number> failed to initialize flat file generator.

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.

WSP_36003 Writer target <target name> partition <partition number> failed to initialize XML generator.

Explanation:
The Web Services Provider Writer for XML could not create the XML target file.
User Response:
Check the session log for additional messages.

WSP_36004 Writer target <target name> group <target group> partition <partition number> failed to process flat file 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.

WSP_36005 Writer target <target name> group <target group> partition <partition number> failed to process XML messages.

Explanation:
The Web Services Provider Writer for XML failed to process the XML message.
User Response:
Check the session log for additional messages.

WSP_36006 Writer target <target name> group <target group> partition <partition number> failed to process end of file.

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.

WSP_36007 Writer target <target name> group <target group> partition <partition number> failed to process end of XML.

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.

WSP_36008 Invalid cache folder in writer target partition <target name> partition <partition number>.

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.

WSP_36010 Get message key <key> failed.

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