SF Messages

Explanation:	The Integration Service could not connect to Salesforce using the configured proxy.
User Response:	Correct the error and run the session again.

SF_31233 Could not set up cURL to connect to the Salesforce Bulk API. Using the standard Salesforce API.

Explanation:	The Integration Service cannot connect to the Salesforce Bulk API. Instead, it connects using the standard Salesforce API.
User Response:	Run the session again. If the same error occurs, contact Informatica Global Customer Support.

SF_31234 Bulk API error received from Salesforce. Exception code <code>. Exception message <message>.

Explanation:	An internal error occurred with the Salesforce Bulk API.
User Response:	Run the session again. If the same error occurs, contact Salesforce for additional information.

SF_31235 Bulk API cURL error received. Error message <message>.

Explanation:	An error occurred with the Salesforce Bulk API.
User Response:	Run the session again. If the same error occurs, contact Informatica Global Customer Support.

SF_31242 Bulk API job ID <job ID> failed.

Explanation:	A Salesforce Bulk API job failed.
User Response:	Check the activity log for related errors. Correct the error and run the session again.

SF_31253 Attempt to connect to Salesforce through proxy <proxy ID> failed because of the following error: <error message>.

Explanation:	The Integration Service could not connect to Salesforce using the configured proxy.
User Response:	Correct the error and run the session again.

SF_31255 Salesforce could not process batch <batch ID> of job ID <job ID> because of the following error: <message>.

Explanation:	Salesforce could not process a batch in the Salesforce Bulk API session.
User Response:	Correct the error and run the session again.

SF_31259 ZLib compression returned the following error: <message>.

Explanation:	An error occurred when compressing data for a Salesforce Bulk API session.
User Response:	Run the session again. If the same error occurs, contact Informatica Global Customer Support.

SF_31324 Attempt to connect to Salesforce through proxy <proxy ID> failed because of the following error: <error message>.

Explanation:	The Integration Service could not connect to Salesforce using the configured proxy.
User Response:	Correct the error and run the session again.

SF_31426 Attempt to connect to Salesforce through proxy <proxy ID> failed because of the following error: <error message>.

Explanation:	The Integration Service could not connect to Salesforce using the configured proxy.
User Response:	Correct the error and run the session again.

SF_31523 Attempt to connect to Salesforce through proxy <proxy ID> failed because of the following error: <error message>.

Explanation:	The Integration Service could not connect to Salesforce using the configured proxy.
User Response:	Correct the error and run the session again.

SF_34030 Client application <application>, connection <connection ID>: recv failed. System returns error code <error number>, error message <error message>.

Explanation:	The client application failed to establish a connection.
User Response:	See the additional error message for more information. Also, disable and enable the Integration Service.

SF_34032 Closing client application <application>’s connection dues to PROTOCOL ERROR. Please contact Informatica Global Customer Support.

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

SF_34033 PROTOCOL ERROR: Received object of unexpected type <type> from client application <application> on connection <connection ID>.

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

SF_34034 PROTOCOL ERROR: Received object of unexpected type <type> from client application <application> on connection <connection ID>.

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

SF_34035 PROTOCOL ERROR: Got request ID <request ID> while expecting request ID <request ID> from client application <application> on connection <connection ID>.

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

SF_34036 PROTOCOL ERROR: Got request key <key> while expecting request key <key> from client application <application> on connection <connection ID>.

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

SF_34037 PROTOCOL ERROR: Got request type <request type> while in state <state> from client application <application> on connection <connection ID>.

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

SF_34062 Cannot open service control manager.

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

SF_34063 Cannot close service control manager.

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

SF_34064 Cannot lock service database.

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

SF_34065 Cannot unlock service database.

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

SF_34066 Cannot open service.

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

SF_34067 Cannot close service.

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

SF_34068 Cannot query service.

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

SF_34069 Cannot control service.

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

SF_34070 Cannot stop service.

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

SF_34071 Cannot delete service.

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

SF_34072 Cannot create service.

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

SF_34094 Caught a fatal signal. Will abort this server process shortly.

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

SF_34095 Aborting this process due to a fatal signal.

Explanation:	Internal error. This message is preceded by SF_34094.
User Response:	Contact Informatica Global Customer Support.

SF_34096 Caught SIGFPE signal. Aborting this server process.

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

SF_34098 Failed to allocate memory. Out of virtual memory.

Explanation:	The Integration Service requires more memory.
User Response:	Increase the amount of available virtual memory on the Integration Service system.

SF_34105 Failed to redirect standard error (stderr) messages to the file <file name>. System error is <system error number> <system error message>.

Explanation:	You enabled the Integration Service custom property, ConsoleOutputFilename, to redirect standard output and standard error messages to a file. The Integration Service could not redirect standard error messages and failed to initialize. This could be due to insufficient resources, such as file descriptors or memory.
User Response:	Review the system error and contact the system administrator.

SF_34106 Failed to redirect standard output (stdout) messages to the file <file name>. System error is <system error number> <system error message>.

Explanation:	You enabled the Integration Service custom property, ConsoleOutputFilename, to redirect standard output and standard error messages to a file. The Integration Service could not redirect standard output messages and failed to initialize. This could be due to insufficient resources, such as file descriptors or memory.
User Response:	Review the system error and contact the system administrator.

SF_34109 Failed to open file <file name> for redirecting console output (stdout/stderr) messages System error is <system error number> <system error message>.

Explanation:	You enabled the Integration Service custom property, ConsoleOutputFilename, to redirect standard output and standard error messages to a file. The Integration Service failed to open the file to write messages.
User Response:	Verify that the user starting the Integration Service has write permission on the file directory. Review the system error and contact the system administrator.

SF_34120 Cannot persist request GUID <GUID>, made by client application <client name> on host <host name> through connection <connection name>. Request might not be executed following a service process failure.

Explanation:	During a transient failure, the Integration Service could not access the $PMStorageDir to store the request for recovery.
User Response:	Verify that the Integration Service can access $PMStorageDir. If the directory does not exist or cannot be written to, the request cannot be persisted.

SF_34130 Cannot get the storage files in directory <directory name>.

Explanation:	The storage directory does not exist or there are no storage files in this directory.
User Response:	Make sure the $PMStorageDir directory path is set to directory that exists, and you have proper write permissions to the directory.

SF_34132 Errors encountered while reading from storage files.

Explanation:	You do not have write permission, or the disk is full.
User Response:	Make sure you have write permission, and the disk has enough room for the storage file.

SF_34134 Error in writing to storage file <file name>.

Explanation:	You do not have write permission, or the disk is full.
User Response:	Make sure you have write permission, and the disk has enough room for the storage file.

SF_34135 Errors encountered while writing to storage files.

Explanation:	The Integration Service does not have write permission on the directory to write the state of operations.
User Response:	Verify that the user configured to start Informatica Services has write permission, and the disk has enough room for the storage file.

SF_34136 Error in removing storage file <file name>.

Explanation:	The storage file is in use, or you do not have write permissions on the storage file.
User Response:	Make sure you have write permission, and the disk has enough room for the storage file.

SF_34155 Child process <process ID> terminated due to spurious abort errno <error number>.

Explanation:	The Session or Command task exited unexpectedly and the machine running the Integration Service process generated an error.
User Response:	Use the error number to determine the cause of the error. If it indicates an out-of-memory error, increase the swap space or reduce the maximum processes threshold. You define the maximum processes threshold on the Properties tab for the node in the Administrator tool. Review the core file of the process for the Command task.

SF_34160 High availability has been disabled. Contact Informatica Global Customer Support.

Explanation:	A custom property for the Integration Service is configured to disable high availability.
User Response:	Contact Informatica Global Customer Support.