Troubleshooting Informatica Error Messages and Resolution – Part 439

SQLServerF1

The following messages might appear when running Web Services Provider sessions:
WSP_33002Failed to get attribute <attribute name>.
Cause:A session attribute for the Web Services Provider source or target contains inconsistencies.
Action:Contact Informatica Technical Support.

WSP_33006The mapping contains more than one Web Services Provider source.
Cause:You tried to run a session that contains more than one Web Services Provider source.
Action:Edit the mapping to ensure that it contains only one Web Services Provider source.
WSP_33007The mapping contains more than one Web Services Provider target.
Cause:You tried to run a session that contains more than one Web Services Provider output target.
Action: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_33008Out of memory.
Cause:The Integration Service machine is out of memory.
Action: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_33009Valid Real-time options key is not found, unable to run this Web Service session. Please obtain a valid real-time options key.
Cause:Your Real-time license is either expired, or you have not applied the license key to the license file.
Action:Apply the current Real-time license key to the license file. If you do not have a current license, contact Informatica Technical Support.
WSP_34007Failed to build the acknowledgement message.
Cause:Internal error.
Action:Contact Informatica Technical Support.

Above are list of Informatica Error Messages or Warnings received while performing certain operation against Informatica related products.

What are Informatica Error Messages?

Informatica error codes are a set of error codes for use by all Informatica products. Every Informatica error message returned by Informatica, is self explanatory and contains the object name in cases where required.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Informatica Error Code Messages or Warning Messages on Windows and Linux Operating Systems.

 

Troubleshooting Informatica Error Messages and Resolution – Part 438

WSH_95027Repository <repository name> is not configured at the Web Services Hub.
Cause:This occurs when you try to use a repository, which is not configured at the Web Services Hub.
Action:Either configure the Web Services Hub for this repository or use a repository, which is configured at the Web Services Hub.

WSH_95029Folder <folder name> does not exist.
Cause:This occurs when you specify an invalid folder name in a function call of the Metadata Web Service.
Action:Specify a valid folder name.
WSH_95030Workflow <workflow name> does not exist.
Cause:This occurs when you specify an invalid workflow name in a function call of the Metadata Web Service.
Action:Specify a valid workflow name.
WSH_95032Invalid SOAP header in request.
Cause:This occurs when you send a header element which does not conform to the header element schema.
Action:Use a valid SOAP header element as defined in the schema.
WSH_95034Repository error.
Cause:This occurs while you are querying repositories using the Metadata Web Service APIs and an internal repository error occurs.
Action:Look at the extended details to find out the problem.
or
Action:Contact Informatica Technical Support.
WSH_95035Invalid SOAP request.
Cause:This occurs when you pass a null SOAP message in the request.
Action:Send the SOAP request as the Web Services Hub WSDL file dictates.

WSH_95041Depth <depth> is not valid. Depth should be a positive integer value.
Cause:This occurs when you give an invalid depth in the GetAllTaskInstances function call.
Action:Specify a depth value greater than zero.
WSH_95042Invalid request parameter. LoginRequest object cannot be null.
Cause:This occurs when you pass a null LoginRequest object in the Login function call.
Action:Specify a valid LoginRequest object.
WSH_95056Unable to delete the Repository <repository name>. This repository is not configured at WSH.
Cause:You tried to delete a repository that is not configured the Web Services Hub.
Action:Use a repository name configured in the WSHConfig.xml.
WSH_95064Failed to fetch folder <folder name>.
Cause:This occurs when you pass an invalid folder name in task or workflow related operations such as StartWorkflow.
Action:Specify a valid folder name.
WSH_95065Failed to fetch workflow <workflow name>.
Cause:This occurs when you pass an invalid workflow name in workflow related operations such as StartWorkflow.
Action:Specify a valid workflow name.

Above are list of Informatica Error Messages or Warnings received while performing certain operation against Informatica related products.

What are Informatica Error Messages?

Informatica error codes are a set of error codes for use by all Informatica products. Every Informatica error message returned by Informatica, is self explanatory and contains the object name in cases where required.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Informatica Error Code Messages or Warning Messages on Windows and Linux Operating Systems.

 

Troubleshooting Informatica Error Messages and Resolution – Part 437

SQLServerF1

WSH_95027Repository <repository name> is not configured at the Web Services Hub.
Cause:This occurs when you try to use a repository, which is not configured at the Web Services Hub.
Action:Either configure the Web Services Hub for this repository or use a repository, which is configured at the Web Services Hub.

WSH_95029Folder <folder name> does not exist.
Cause:This occurs when you specify an invalid folder name in a function call of the Metadata Web Service.
Action:Specify a valid folder name.
WSH_95030Workflow <workflow name> does not exist.
Cause:This occurs when you specify an invalid workflow name in a function call of the Metadata Web Service.
Action:Specify a valid workflow name.
WSH_95032Invalid SOAP header in request.
Cause:This occurs when you send a header element which does not conform to the header element schema.
Action:Use a valid SOAP header element as defined in the schema.

WSH_95034Repository error.
Cause:This occurs while you are querying repositories using the Metadata Web Service APIs and an internal repository error occurs.
Action:Look at the extended details to find out the problem.
or
Action:Contact Informatica Technical Support.
WSH_95035Invalid SOAP request.
Cause:This occurs when you pass a null SOAP message in the request.
Action:Send the SOAP request as the Web Services Hub WSDL file dictates.
WSH_95041Depth <depth> is not valid. Depth should be a positive integer value.
Cause:This occurs when you give an invalid depth in the GetAllTaskInstances function call.
Action:Specify a depth value greater than zero.
WSH_95042Invalid request parameter. LoginRequest object cannot be null.
Cause:This occurs when you pass a null LoginRequest object in the Login function call.
Action:Specify a valid LoginRequest object.

Above are list of Informatica Error Messages or Warnings received while performing certain operation against Informatica related products.

What are Informatica Error Messages?

Informatica error codes are a set of error codes for use by all Informatica products. Every Informatica error message returned by Informatica, is self explanatory and contains the object name in cases where required.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Informatica Error Code Messages or Warning Messages on Windows and Linux Operating Systems.

 

Troubleshooting Informatica Error Messages and Resolution – Part 436

SQLServerF1

WSH_95001Invalid request parameter. Folder name cannot be null.
Cause:This occurs when you pass a null folder name in a function call that requires folder name.
Action:Specify a valid folder name.
WSH_95002Invalid request parameter. Workflow name cannot be null.
Cause:This occurs when you pass a null workflow name in a function call that requires a workflow name.
Action:Specify a valid workflow name.

WSH_95003Invalid request parameter. Task instance path cannot be null.
Cause:This occurs when you pass a null task instance path in a function call that requires task instance path.
Action:Specify a valid task instance path.
WSH_95006Request mode <request mode> is not valid. Valid request modes are NORMAL or RECOVERY.
Cause:This occurs when you pass an invalid request mode in a function call that takes request mode as a parameter.
Action:Specify a valid request mode. Valid request modes are NORMAL or RECOVERY.
WSH_95007Invalid request parameter. Request mode cannot be null.
Cause:This occurs when you pass a null request mode in a function call that takes request mode as a parameter.
Action:Specify a valid request mode. Valid request modes are NORMAL or RECOVERY.

WSH_95008Monitor server mode <monitor server mode> is not valid. Valid selections are ALL, RUNNING, or SCHEDULED.
Cause:This occurs when you pass an invalid monitor server mode in the MonitorDIServer function call.
Action:Specify a valid monitor server mode. Valid selections are ALL, RUNNING, or SCHEDULED.

Above are list of Informatica Error Messages or Warnings received while performing certain operation against Informatica related products.

What are Informatica Error Messages?

Informatica error codes are a set of error codes for use by all Informatica products. Every Informatica error message returned by Informatica, is self explanatory and contains the object name in cases where required.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Informatica Error Code Messages or Warning Messages on Windows and Linux Operating Systems.

 

Troubleshooting Informatica Error Messages and Resolution – Part 435

SQLServerF1

WSH_514Exception occurred while execution of initialize function of LMConnetor for LM Server <master process service>: <detailed error message>
Cause:The Web Services Hub could not communicate with the Integration Service and failed when attempting to start a web service enabled workflow. The error message provides further details of the error.
Action:Review the error message and verify that the Integration Service is running.

WSH_570User authorization failed for service <service name>, for user <user name>: <detailed error message>
Cause:The user does not have privileges to start the web service. The error message provides further details of the error.
Action:Verify that the user has the correct privileges for the web service you are trying to run.
WSH_719 Session task <session task name> is invalid.
Cause:The service workflow is valid, but the Session task is invalid. When you validate a workflow, the Workflow Manager does not validate the session.
Action:Validate the Session task, and correct the cause of any validation message. Then, validate and save the workflow to run the service.

WSH_801Service <service name> does not have the license.
Cause:You have not assigned a valid PowerCenter license object to the Web Services Hub.
Action:Assign a license to the Web Services Hub.
WSH_1028UserName and/or password are not provided for protected service.
Cause:The web service client message does not include the repository user name and password.
Action:Verify that the repository name and password are included in every web service client message.
WSH_1031UserName or Password specified for the protected service are incorrect.
Cause:The repository user name and password included in the web service client message is not correct.
Action:Enter a valid repository user name and password.
WSH_95000Web Services Hub ERROR.
Cause:Internal error at the Web Services Hub.
Action:See the Extended Details in the SOAP fault message to determine the problem.
or
Action:Contact Informatica Technical Support.

Above are list of Informatica Error Messages or Warnings received while performing certain operation against Informatica related products.

What are Informatica Error Messages?

Informatica error codes are a set of error codes for use by all Informatica products. Every Informatica error message returned by Informatica, is self explanatory and contains the object name in cases where required.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Informatica Error Code Messages or Warning Messages on Windows and Linux Operating Systems.

 

Troubleshooting Informatica Error Messages and Resolution – Part 434

WSC_42013Cannot load Java class <Java class name>.
Cause:A CLASSPATH entry is missing or inaccurate.
Action:Make sure that the CLASSPATH contains the JAR files that PowerCenter Connect for Web Services requires.
or
Cause:The JDK version is incorrect.
Action:Check the version of the installed JDK.
or
Cause:The PATH setting is incorrect.
Action:Make sure the PATH settings are correct.

WSC_42021Failed to load the library <library name>.
Cause:The PATH setting is incorrect.
Action:Make sure that the PATH settings are correct.
WSC_42022Failed to get the address of function <library name>.
Cause:The PATH setting is incorrect.
Action:Make sure that the PATH settings are correct.
or
Cause:The version of the PowerCenter library that appears first in the PATH setting is incorrect. For example, you have two versions of PowerCenter libraries, such as version 7.0 and version 8.0. You are trying to use PowerCenter 8.0, but the library from PowerCenter version 7.0 appears first in the PATH setting.
Action:Check the PATH setting for the specified library. Make sure that library belongs to the PowerCenter version that you want to use.

Above are list of Informatica Error Messages or Warnings received while performing certain operation against Informatica related products.

What are Informatica Error Messages?

Informatica error codes are a set of error codes for use by all Informatica products. Every Informatica error message returned by Informatica, is self explanatory and contains the object name in cases where required.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Informatica Error Code Messages or Warning Messages on Windows and Linux Operating Systems.

 

Troubleshooting Informatica Error Messages and Resolution – Part 433

SQLServerF1

WSC_33030Cannot retrieve NT Domain value for authentication.
Cause:You might not have specified a value for the domain connection attribute in the Web Service application connection.
Action:Enter a value for the domain connection attribute in the Web Service application connection.
WSC_33031Cannot retrieve SSL parameters for authentication.
Cause:You might have specified invalid SSL parameters in the Web Service application connection, or you might not have specified the SSL parameters.
Action:Enter valid SSL parameters in the Web Service application connection.

WSC_33032Failed to set trust certificates file <trust certificates file name>.
Cause:You might have specified an invalid trust certificates file name in the Web Service application connection, or you might not have specified the absolute path to the file.
Action:Enter a valid trust certificates file name in the Web Service application connection, and specify the absolute path to the file.
WSC_33033Failed to set client certificate file: <certificate file name>.
Cause:You might have specified an invalid certificate file name, certificate file password, or certificate file type in the Web Service application connection. Or, you might not have specified the absolute path to the file.
Action:Enter a valid certificate file name, certificate password, and certificate file type in the Web Service application connection, and specify the absolute path to the file.
WSC_38001Cannot find any SQ instances in mapping.
Cause:Internal error.
Action:Contact Informatica Technical Support.
WSC_38002Cannot find connection reference.
Cause:Internal error.
Action:Contact Informatica Technical Support.
WSC_38003Cannot find connection.
Cause:Internal error.
Action:Contact Informatica Technical Support.

WSC_42008Cannot create Java VM <JVM code number>.
Cause:The JDK version is incorrect.
Action:Check the version of the installed JDK.
or
Cause:The PATH setting is incorrect.
Action:Make sure the PATH settings are correct.
or
Cause:The CLASSPATH setting is incorrect.
Action:Make sure the CLASSPATH settings are correct.

Above are list of Informatica Error Messages or Warnings received while performing certain operation against Informatica related products.

What are Informatica Error Messages?

Informatica error codes are a set of error codes for use by all Informatica products. Every Informatica error message returned by Informatica, is self explanatory and contains the object name in cases where required.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Informatica Error Code Messages or Warning Messages on Windows and Linux Operating Systems.

 

Troubleshooting Informatica Error Messages and Resolution – Part 432

WSC_33021Web Service connection <application connection name> cannot have a negative timeout value <timeout value>.
Cause:The value for the Timeout parameter in the Web Service application connection is a negative number.
Action:Set the Timeout value in the Web Service application connection equal to zero or higher.

WSC_33023Encountered a problem during SOAP request conversion (DOC to RPC): <error details>.
Cause:The SOAP request for a web service source contains invalid or incomplete data. See the error details for more information.
Action:Modify the SOAP request in the Edit Tables dialog box.
WSC_33024Error encountered in getting Operation Name for the table <operation name>.
Cause:You might not have registered the PowerCenter Connect for Web Services plug-in.
Action:Register the pmwsconsumer.xml plug-in.
WSC_33026 Cannot retrieve HTTP proxy port number.
Cause:You might not have entered a value for the HTTP proxy port number when you configured the Integration Service.
Action:On Windows, configure the Integration Service in the Informatica Server Setup. On the HTTP Proxy tab, enter a value for the server port.
or
Action:On UNIX, run the pmconfig utility and open pmserver.cfg. Provide a port number for HttpProxyPort.

WSC_33028Cannot retrieve HTTP proxy password.
Cause:You might not have entered a value for the password for the HTTP proxy settings when you configured the Integration Service.
Action:On Windows, configure the Integration Service in the Informatica Server Setup. On the HTTP Proxy tab, enter a password.
or
Action:On UNIX, run the pmconfig utility and open pmserver.cfg. Provide a value for HttpProxyPassword.

Above are list of Informatica Error Messages or Warnings received while performing certain operation against Informatica related products.

What are Informatica Error Messages?

Informatica error codes are a set of error codes for use by all Informatica products. Every Informatica error message returned by Informatica, is self explanatory and contains the object name in cases where required.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Informatica Error Code Messages or Warning Messages on Windows and Linux Operating Systems.

 

Troubleshooting Informatica Error Messages and Resolution – Part 431

SQLServerF1

WRT_8372Row rejected since a rollback was issued due to a failed commit.
Cause:The Integration Service failed to commit a transaction and the session is configured to roll back on failed commit.
Action:Read other messages in the session log to find the cause of the failed commit.
WRT_8398Error opening session output file <file name>. Error: <error text>.
Cause:The Integration Service could not open the target output file for the session. This error can occur if the target output file does not exist, the path to the file is invalid, sufficient permissions do not exist to open the file, or another process is using the file. As a result, the session failed.
Action:Verify that the target output file exists, that the Integration Service has sufficient permissions to open the file, and that the file is not currently in use by another process. If the session is enabled for recovery, recover the session. Otherwise, run the session again.

WRT_8399 Error closing target output file <file name>. Error: <error text>.
Cause:The Integration Service could not close the target output file. This error can occur if there is not sufficient disk space available to close the file. As a result, the session failed.
Action:Verify that there is sufficient disk space for the target output file. If the session is enabled for recovery, recover the session. Otherwise, run the session again.
WRT_8414High availability license is absent. Retry period specified for Integration Service connection to target is ignored.
Cause:The connection object properties are configured, but you do not have the high availability option. The connection retry period is ignored.
Action:None.

WRT_8419Flat file target <target name> FileName port is not supported with connection or merge option.
Cause:The Integration Service failed the session because the FileName port is not supported with the target type or connection. You cannot configure a FileName port with an FTP target, merge file, or file list.
Action:Remove the FileName port from the target.

WRT_8424The Integration Service cannot read the control file template .
Cause:The Integration Service was unable to find the control file template.
Action:Verify that the directory and file name for the control file template are entered correctly in the session properties. Verify that the file exists in the specified directory.
WRT_8425ERROR: Writer execution failed.
Cause:The session failed to write to the target.
Action:Check preceding error messages to see the cause for the error.
WRT_8426ERROR: Writer preparation failed.
Cause:The session failed while the Integration Service was preparing to write to the target. The target might not exist, or the Integration Service encountered other errors.
Action:Check preceding error messages to see the cause for the error.
WRT_31215Valid PowerCenter Connect for Salesforce.com license key is not found.
Cause:The license key does not have the PowerCenter Connect for Salesforce.com option.
Action:Contact your Informatica sales representative to get a license. If you do not know who your sales representative is, contact Informatica Technical Support to log a service request.

Above are list of Informatica Error Messages or Warnings received while performing certain operation against Informatica related products.

What are Informatica Error Messages?

Informatica error codes are a set of error codes for use by all Informatica products. Every Informatica error message returned by Informatica, is self explanatory and contains the object name in cases where required.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Informatica Error Code Messages or Warning Messages on Windows and Linux Operating Systems.

 

Troubleshooting Informatica Error Messages and Resolution – Part 430

WRT_8313External loader error. Upsert is not valid for target instance <target instance name> since update is not valid for the target.
Cause:The MultiLoad or TPump external loader cannot run in upsert mode for one of the following reasons:
−You did not define a primary key for the target.
−You did not define any non-key columns for the target.
Action:Run the external loader in a different mode, define a primary key for the target, or add a non-key column to the target.

WRT_8315The user-defined commit session is not supported for this type of mapping (no targets in commit groups).
Cause:Internal error.
Action:Contact Informatica Technical Support.
WRT_8324Warning: Target Connection Group’s connection doesn’t support transactions. Targets <target names> may not be loaded according to specified transaction boundary rules!
Cause:You are running a source-based commit or user-defined commit session, and the named targets may not recognize transaction boundaries. This might happen with flat file targets or with bulk loading.
Action:This is an informational message for flat file targets, as flat files are commit-neutral. If you run the session in bulk mode, and you want to ensure that the targets load according to transaction boundaries, you can edit the session and run the session in normal mode.
WRT_8329Warning. Ignoring external loader control file directory <directory> since it is all whitespace.
Cause:You configured the Integration Service LoaderControlFileDirectory option to use a directory separate from the Integration Service installation directory to create and store external loader control files, but you did not specify a directory name.
Action:Specify a directory name for LoaderControlFileDirectory.

WRT_8343 Error: Target filename <filename> exceeded maximum allowable length <bytes>.
Cause:The target file name length exceeds the system limit (260 on Windows, 255 on UNIX).
Action:Reduce the length of the file name.
WRT_8371Row rejected since a rollback was issued due to errors in the transaction.
Cause:The Integration Service encountered an error in the transaction and the session is configured to roll back on error.
Action:Read other messages in the log file to find the row that caused the error.
or
Cause:The transaction control expression in a Transaction Control transformation evaluated to roll back the transaction. The Integration Service rolled back all rows in the transaction, including this row.
Action:Read other messages in the log file to find the row that caused the transaction control expression that evaluated to roll back.

Above are list of Informatica Error Messages or Warnings received while performing certain operation against Informatica related products.

What are Informatica Error Messages?

Informatica error codes are a set of error codes for use by all Informatica products. Every Informatica error message returned by Informatica, is self explanatory and contains the object name in cases where required.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Informatica Error Code Messages or Warning Messages on Windows and Linux Operating Systems.

 
1 2 3 4 5 46