WSH Messages

Explanation:	The Web Services Hub could not access the workflow because the workflow is not configured as a web services workflow.
User Response:	Use a valid web services workflow.

WSH_502 Failed to initialize the repository <repository name>: <error message>.

Explanation:	The Web Services Hub could not initialize the repository.
User Response:	See the additional error message for more information.

WSH_505 Failed to fetch repository data during initialization: <error message>.

Explanation:	The Web Services Hub could not retrieve data from the repository during initialization.
User Response:	See the additional error message for more information.

WSH_516 Service <web service name>: Start of workflow <workflow name> located in folder <folder name> repository <repository name> failed with error <error message>.

Explanation:	The Web Services Hub could not start the web service workflow.
User Response:	See the additional error message for more information.

WSH_520 Failed to wait for workflow to complete: <error message>.

Explanation:	The Web Services Hub aborted the workflow before the workflow completed.
User Response:	See the additional error message for more information.

WSH_521 Workflow <workflow name> in folder <folder name> failed to complete. Workflow notification handler is invoked.

Explanation:	The web service workflow encountered an internal error and failed.
User Response:	Review the notification. Resolve the issue and restart the workflow.

WSH_522 Failed to fetch details of the workflow <workflow name>, in folder <folder name> while fetching data for the repository <repository name> : <error message>.

Explanation:	The Web Services Hub could not retrieve the details of the workflow from the repository.
User Response:	See the additional error message for more information.

WSH_523 Failed to update data cache for folder <folder name> in the repository <repository name> : <error message>

Explanation:	The Web Services Hub could not update the folder cache.
User Response:	See the additional error message for more information.

WSH_524 Failed to update data cache for workflow <workflow name>, in the folder <folder name> in the repository <repository name> : <error message>.

Explanation:	The Web Service Hub could not update the workflow cache.
User Response:	See the additional error message for more information.

WSH_526 Failed to fetch repository data for the repository <repository name> : <error message>.

Explanation:	The Web Services Hub could not retrieve the data for the repository.
User Response:	See the additional error message for more information.

WSH_530 Failed to update data cache for repository <repository name> : <error message>.

Explanation:	The Web Services Hub could not update the data cache for the repository.
User Response:	See the additional error message for more information.

WSH_535 Web Services Hub initialization failed : <error message>.

Explanation:	The Web Services Hub could not be initialized.
User Response:	See the additional error message for more information.

WSH_547 Service <web service name>: Failed to initialize service proxy.

Explanation:	The Web Services Hub could not create the web service proxy for the web service workflow.
User Response:	Review the workflow log for more information. Restart the web service workflow.

WSH_553 Failed to find service proxy for the Service <web service name>.

Explanation:	The Web Services Hub could not find the web service proxy for the web service workflow.
User Response:	Review the workflow log for more information. Restart the web service workflow.

WSH_557 Service <web service name>: Failed to activate the service workflow with error <error message>.

Explanation:	The Web Services Hub could not activate the web service workflow.
User Response:	See the additional error message for more information.

WSH_567 Request <request instance ID>: Invocation timed out for Service <web service name>. Sending the response containing SOAP fault to the client.

Explanation:	The web service request has timed out. The Web Services Hub will return a SOAP fault message to the client.
User Response:	Review the workflow log for more information. Restart the web service workflow.

WSH_572 Request <request instance ID>: Client request is no longer active. Discarding the response message from the WS Writer.

Explanation:	The Web Services Hub discarded the response message because the client request is no longer active.
User Response:	Resend the web service request.

WSH_578 Request <request instance ID> Client IP <client IP address>: Request message for the Service <web service name> failed with error <error message>.

Explanation:	The Web Services Hub could not process the web service request.
User Response:	See the additional error message for more information. Resend the web service request.

WSH_601 Service <web service name>: Failed to start the workflow with error <error message>.

Explanation:	The Web Services Hub could not start the workflow.
User Response:	See the additional error message for more information. Resolve the problem and restart the web service workflow.

WSH_606 Failed to connect to LM Server <domain name>:<integration service name> : <error message>.

Explanation:	The Web Services Hub could not connect to the PowerCenter Integration Service.
User Response:	See the additional error message for more information.

WSH_608 Failed to execute task <task name> : <error message>.

Explanation:	The Web Services Hub could not run the task in the web service workflow.
User Response:	See the additional error message for more information.

WSH_617 Invocation failed for <request instance ID> with client IP <client IP address> using Service <web service name> with instance id <DTM instance ID>. Sending SOAP fault in response.

Explanation:	The Web Services Hub could not start the web service using the PowerCenter Integration Service and the web service instance and returned a SOAP fault message to the client.
User Response:	Review the SOAP fault message. Resolve the issue and resend the web service request.

WSH_622 Service <web service name>: Failed to update/add service proxy in the folder <folder name> in repository <repository name>.

Explanation:	The Web Services Hub could not update or add the web service proxy to the folder in the repository.
User Response:	Review the Repository Service log for more information.

WSH_706 Failed to connect to the repository <repository name> : <error message>.

Explanation:	The Web Services Hub could not connect to the repository.
User Response:	Review the login details. Resolve the issue and log in again.

WSH_721 Failed to start workflow for <workflow name>.

Explanation:	The Web Services Hub could not start the workflow.
User Response:	Review the workflow log for more information. Restart the web service workflow.

WSH_731 Failed to update the service proxy list: <error message>.

Explanation:	The Web Services Hub could not update the web service proxy list.
User Response:	See the additional error message for more information.

WSH_1005 Service <web service name> is not available.

Explanation:	The web service workflow is not enabled.
User Response:	Enable the service and restart the web service workflow.

WSH_1006 Content sent is invalid.

Explanation:	The content of the SOAP message in the web service request is not valid.
User Response:	Correct the message and resend the web service request.

WSH_1007 Caller is not authorized to invoke the service.

Explanation:	The Web Services Hub could not start the protected web service because the login credentials were invalid.
User Response:	Correct the login information and restart the web service workflow.

WSH_1010 Schema for prefix <namespace prefix> could not be found.

Explanation:	The Web Services Hub could not find the namespace prefix for the schema. The WSDL used for the web service source or target might not be valid.
User Response:	Import the web service source and target definitions from the WSDL again and create another web service workflow.

WSH_1011 Web Services Provider source or target contains incompatible versions of metadata.

Explanation:	The versions of the web service source and target metadata are not compatible. The source and target must be compatible.
User Response:	Use the same method to create the source and target definitions in a web service workflow. Use the same encoding style for the input and output messages.

WSH_1012 Web Services Provider source or target contains an invalid type.

Explanation:	A datatype in the web service source or target schema is not valid.
User Response:	Create the web service source and target with the correct datatype.

WSH_1013 Web Services Provider source or target contains an invalid key. Expected Key: [key name].

Explanation:	The web service source or target contains a key column that is not valid.
User Response:	Review the workflow log for more information. Create the web service source and target with the correct key columns.

WSH_1014 Web Services Provider source or target does not contain a required key.

Explanation:	The web service source or target does not contain the required key.
User Response:	Review the workflow log for more information. Create the web service source and target with the appropriate primary or foreign key.

WSH_1016 The web service workflow <workflow name> does not exist or is invalid.

Explanation:	The Web Services Hub could not find the web service workflow in the repository.
User Response:	Verify that the workflow is a valid web service and restart the web service workflow.

WSH_1017 Invalid schema name : Schema <XML schema name> is not imported by the WSDL for the service workflow <workflow name>.

Explanation:	The Designer could not import the source or target from the WSDL because of a schema name that is not valid.
User Response:	Review the repository log for more information. Reimport the source and target from the WSDL.

WSH_1026 Failed to read from input stream.

Explanation:	The Web Services Hub could not read the web service request message.
User Response:	Verify that the PowerCenter Integration Service is running. Resend the web service request.

WSH_1027 Failed to parse the MIME message.

Explanation:	The Web Services Hub could not parse the MIME message.
User Response:	Use the correct MIME type if you include a MIME attachment in the web service request.

WSH_1070 Request <request instance ID> ClientIP <client IP address>: Failed to read client message for Service <web service name> with payload of size <payload size>.

Explanation:	The Web Services Hub could not read the message from the client.
User Response:	Verify that the PowerCenter Integration Service is running. Resend the web service request.

WSH_1071 Request <request instance ID> ClientIP <client IP address>: Failed to decode client encoding for Service <web service name>.

Explanation:	The Web Services Hub could not translate the SOAP encoding of the message in the request.
User Response:	Verify that the encoding style is valid and that the source and target have the same encoding style.

WSH_1072 Request <request instance ID> ClientIP <client IP address>: Reading client message for Service <web service name> failed with error <error message>.

Explanation:	The Web Services Hub could not read the message in the web service request.
User Response:	See the additional error message for more information. Verify that the PowerCenter Integration Service is running. Resend the web service request.

WSH_1077 Failed to send Request <request instance ID> with ClientIP <client IP address> to the service workflow instance.

Explanation:	The Web Services Hub could not send the web service request.
User Response:	Check the connection between the Web Services Hub and the PowerCenter Integration Service. Resend the web service request.

WSH_1078 Request <request instance ID> ClientIP <client IP address>: Failed to send client reply for Service <web service name> with error <error message>.

Explanation:	The Web Services Hub could not send the response to the client.
User Response:	See the additional error message for more information. Resend the web service request.

WSH_1079 Service <web service name>: Web service source connection has been reset due to error <error message>.

Explanation:	The connection to the web service source was reset because of the error described in the message.
User Response:	See the additional error message for more information. Check the connection between the Web Services Hub and the PowerCenter Integration Service. Resend the web service request.

WSH_1084 Request contains invalid encoding.

Explanation:	The encoding style of the message in the web service request is not valid.
User Response:	Correct the message encoding style and resend the request.

WSH_1104 Service statistics operation <operation name> failed with error <error message>.

Explanation:	The web service operation failed.
User Response:	See the additional error message for more information.

WSH_1124 Service <web service name>: Cannot find schema for namespace <namespace>.

Explanation:	The Web Services Hub could not find the namespace schema.
User Response:	Verify that the namespace included in the message is correct and resend the request.

WSH_1126 Service <web service name>: Request or response with attachment is not supported for RPC encoding style.

Explanation:	You cannot include an attachment in a request or response message that uses the RPC SOAP binding.
User Response:	To include an attachment in a request or response message, use MIME binding.

WSH_1127 Service <web service name>: Inconsistent binding namespace between Web Service Provider source and target.

Explanation:	The binding style for the source and target messages must be the same.
User Response:	Change the binding style for the source or target so that they match.

WSH_1128 Service <web service name>: Binding namespace not set.

Explanation:	The request message does not include a binding namespace. The binding namespace is required in a request message.
User Response:	Set the binding namespace in the message and resend the request.

WSH_1129 Service <web service name>: Message <message> has empty content.

Explanation:	The SOAP message included in the request does not have any content.
User Response:	Add content to the message and resend the request.

WSH_1137 The folder <folder name> does not exist in repository <repository name>.

Explanation:	The folder name is not valid and cannot be found in the repository.
User Response:	Use a valid folder name.

WSH_1138 Invalid service timeout is specified for workflow <workflow name>. The default value <timeout value> is used.

Explanation:	The timeout value set for the workflow is not valid. The Web Services Hub will use the default timeout value.
User Response:	If you do not want to use the default value, set the timeout property to a valid value and restart the web service workflow. Or set the value to 0 to disable the timeout period. Negative values are not valid. Restart the web service workflow.

WSH_1140 Invalid maximum instance run per hub is specified for workflow <workflow name>. The default value <Maximum Run Count Per Hub value> is used.

Explanation:	The value for the Maximum Run Count Per Hub property of the workflow is not valid. The Web Services Hub will use the default value.
User Response:	If you do not want to use the default value, set the Maximum Run Count Per Hub property of the workflow to a valid value. Negative values are not valid. Restart the web service workflow.

WSH_1141 Invalid service time is specified for workflow <workflow name>. The default value <service time threshold value> is used.

Explanation:	The value set for the Service Time Threshold property of the workflow is not valid. The Web Services Hub will use the default value.
User Response:	If you do not want to use the default value, set the Service Time Threshold property of the workflow to a valid value. Negative values are not valid. Restart the web service workflow.

WSH_1142 Folder <folder name> is incorrectly formatted. Please use '[repository_name:]folder_name' and the repository name is required when the hub is associated with multiple repositories.

Explanation:	The format for the folder name provided is not valid. If the Web Services Hub is associated with multiple repositories, the repository name must be provided with the folder name in the format <repository name>:<folder name>.
User Response:	Correct the folder name to include the repository name and restart the workflow.

WSH_1143 Repository <repository name> is not associated with Web Service hub.

Explanation:	The repository is not associated with the Web Services Hub. The Web Services Hub requires an associated repository.
User Response:	Use a repository that is associated with the Web Services Hub.

WSH_1149 Nonce and created values are required for a PasswordDigest request .

Explanation:	The web service request uses a digested password but the password does not include the nonce value or the created timestamp.
User Response:	Modify the request so that the UsernameToken element in the SOAP message contains values for the Nonce and Created elements.

WSH_1150 The nonce value provided has been used. Provide a new nonce value for this login.

Explanation:	The web service request uses a digested password but the password includes a nonce value that is not valid because it has been used.
User Response:	Nonce values can be used only once. Modify the request so that the UsernameToken element in the SOAP message contains a new Nonce value.

WSH_1151 The created timestamp provided has expired or has been modified.

Explanation:	The web service request uses a digested password but the password includes a created timestamp value that is not valid because it has expired or was modified.
User Response:	Modify the request so that the UsernameToken element in the SOAP message contains a new created timestamp value.

WSH_1152 Nonce and created values must not be specified for a PasswordText request.

Explanation:	The web service workflow uses a text password but the password includes a nonce value and created timestamp. The nonce value and created timestamp cannot be used with a text password.
User Response:	Modify the request so that the UsernameToken element in the SOAP message does not contain values for the Nonce and Created elements.

WSH_1153 The password request is of an unknown type. The request must be a PasswordDigest or PasswordText request.

Explanation:	The password Type attribute contains an invalid value.
User Response:	Modify the request so that the Type attribute of the Password element in the SOAP message contains the value PasswordText or PasswordDigest based on the type of password you want to use. If the attribute is not set, the Web Services Hub uses the password type PasswordText.

WSH_1154 The login information provided is not valid.

Explanation:	The user account information in the UsernameToken element in the SOAP message is not valid.
User Response:	Modify the request so that the UsernameToken element in the SOAP message contains the correct login values.

WSH_95063 Could not log in to the repository <repository name> with the specified username and password.

Explanation:	This occurs when you use a user name or password that is not valid to connect to a repository to perform a batch web service operation.
User Response:	Use a valid user name and password to log in to the repository.