LM Messages

Explanation:	A service process could not determine the storage directory used for failover and recovery.
User Response:	Verify that $PMStorageDir is configured properly in the Integration Service process properties.

LM_36129 Cannot open log file <name>.

Explanation:	The Integration Service cannot open the named log file.
User Response:	Verify that the log file exists in the directory you specified in the session or workflow properties. Also, verify that the user attempting to access the log file has read permission for the file.

LM_36133 Fail in reading log file <name>.

Explanation:	The Integration Service was able to open the named log file, but cannot read it. An administrator could have deleted the log file while you were attempting to access it.
User Response:	Verify that the log file exists in the directory you specified in the session or workflow properties. Then try to access the file again.

LM_36134 Session is initializing. Session log file is temporarily unavailable.

Explanation:	You are trying to access a session log file while the session is still initializing.
User Response:	Wait and open the file when the session has finished initializing.

LM_36136 Task instance <task ID> with workflow <workflow ID> <run ID> did not run on this Integration Service.

Explanation:	The specified task instance did not run.
User Response:	Review the workflow log to view detailed information about why the task instance did not run.

LM_36138 Cannot find workflow log name.

Explanation:	You did not specify a workflow log name in the workflow properties.
User Response:	Enter a workflow log name in the workflow properties.

LM_36210 Get worklet instance name from repository failed.

Explanation:	You may have deleted the worklet from the repository.
User Response:	Verify that the worklet exists.
Explanation:	The database server or the Repository Service may have failed.
User Response:	Verify that the database server and Repository Service are running.
Explanation:	The repository may contain inconsistencies.
User Response:	Contact Informatica Global Customer Support.

LM_36220 Log file <name> contains no data.

Explanation:	The log file is empty, most likely because someone deleted its contents.
User Response:	If you need to see the log file data, rerun the session or workflow to generate the log file again.

LM_36225 The session log file was not created for session instance [ID = <number> in folder [ID = <number>, workflow [ID = <number> [run ID = <number>, worklet [ID = <number> (possibly because the session failed during initialization).

Explanation:	The Integration Service failed to create the named session log file because the session failed during initialization.
User Response:	Check the workflow or server log file to see why the session failed.

LM_36229 Request failed because the connection was broken or the client is too slow in processing replies, client <name>, connection <name>, request ID <number>.

Explanation:	The Integration Service tried to retrieve a session or workflow log file over a network connection, but the connection was broken or timed out.
User Response:	Check the network connection and try to open the log file again.

LM_36269 Connection request was made from client <PowerCenter Client> on host <host machine> for connection to service type <service type>, service name <service>, and service process name <node>. The connection request failed because the service process <node> is not the intended service process.

Explanation:	A client application attempted a connection to a service process that is not the master service process. With pmcmd, this error occurs if you use the host name and port number options rather than the pmcmd options -d <domain> and -sv <service>.
User Response:	Verify that the node is available and attempt the connection again. If you use pmcmd, use the options -d <domain> and -sv <service>.

LM_36271 Connection request was made from client <client> on host <node> for connection to service type <type>, domain name <domain>, service name <service>, and service process name <node>. The connection request failed because the lookup for the service failed.

Explanation:	The Service Manager could not find the Integration Service in the domain.
User Response:	Verify that the Integration Service is running in the domain. Use the pmcmd options -d <domain> and -sv <service>, rather than the host name and port number options.

LM_36272 Failed to get gateway information from URI <universal resource identifier>.

Explanation:	The Integration Service could not identify the master gateway.
User Response:	Verify that Informatica Services is running on the gateway node. Start Informatica Services on the gateway node.

LM_36273 Failed to look up service in domain <domain>, service <service>, service process <node> from name service lookup using the URI <universal resource identifier>.

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

LM_36274 Failed to look up service in domain <domain>, service <service>, service process <service process> from name service lookup using this URI <service process> with fault code <code>, fault message <message text>.

Explanation:	The Service Manager failed to provide the connectivity information for the Integration Service for the specified reason.
User Response:	Verify that the domain and the Integration Service are running. Verify that you used the correct uniform resource identifier (URI).

LM_36275 Connection request was made from client <PowerCenter Client> on host <host machine> for connection to service type <service type>, domain name <domain>, service name <service>, and service process name <node>. The connection request failed because the service is not configured to redirect connections.

Explanation:	The Integration Service is configured so that connections are not redirected.
User Response:	In the Integration Service properties, set the custom flag EnableConnectionRedirection to Yes, which is the default value.

LM_36310 Workflow <name>: Cannot open log file <name>.

Explanation:	The Integration Service could not open the named log file during execution of the named workflow. The workflow failed.
User Response:	Verify that the workflow log file directory specified in the workflow properties exists and that the user attempting to access the log file has write permission for the file.

LM_36311 Workflow <name>: Failed to expand workflow log file name <name>.

Explanation:	The log file name for the named workflow is invalid.
User Response:	Check the workflow log file name in the workflow properties. If you entered the file path directly or used service process variables to represent the file path in the Workflow Log File Name field, verify that the file path is correct and that the service process variables are spelled correctly.

LM_36312 Workflow <name>: Log path exceeds limit of <number> characters: <path>.

Explanation:	The workflow log file path you specified in the workflow properties is too long.
User Response:	Shorten the file path so that it is less than or equal to the displayed character limit.

LM36320 <Workflow or task name>: Execution failed.

Explanation:	Execution of workflow or task failed.
User Response:	Review other messages in the workflow and session log to find the cause for failure, fix the problem, and then run the workflow again.

LM_36338 Workflow <name> Could not start execution of this workflow because the current run on this Integration Service has not completed yet.

Explanation:	You may be running the specified workflow.
User Response:	Wait until the workflow completes to restart it.
Explanation:	You may have attempted to restart a workflow that is suspended but not stopped.
User Response:	To restart a suspended workflow, choose resume to complete the workflow.
Explanation:	You made a change to a workflow that is set to run continuously.
User Response:	Stop or unschedule the workflow, save the workflow, and then restart or reschedule the workflow.

LM_36348 <Workflow, worklet, or session instance name>: Parameter file <name> not found.

Explanation:	The Integration Service cannot locate the parameter file for the named workflow, worklet, or session.
User Response:	Check the workflow or session properties to make sure the named parameter file exists in the specified directory. Also, check to make sure the user accessing the file has read permission for the file.

LM_36349 <Workflow or worklet name>: Failure to create variable manager.

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

LM_36350 Error in binding the pre-defined variable <name>.

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

LM_36351 <Workflow name>: Error in persisting variable values.

Explanation:	Internal error. The Integration Service failed to write the persistent variable value to the repository.
User Response:	Contact Informatica Global Customer Support.

LM_36362 Workflow <name>: The workflow log count in the repository is negative <number>.

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

LM_36363 Workflow <name>: Cannot rename workflow log file <file name> to <file name>.

Explanation:	You saved the workflow logs for the named workflow by number of runs. The Integration Service encountered an error when it tried to rename an existing log file. The disk on which the log files are located might be out of space.
User Response:	Check the disk and directory where the log file is located. Make sure the disk is not out of space.

LM_36364 Workflow <name>: Failed to increment the log file number in the repository.

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

LM_36366 <Worklet name>: Failed to set the passed value for variable <name>.

Explanation:	Internal error. The Integration Service failed to pass the initial value of the named variable to the named worklet.
User Response:	Contact Informatica Global Customer Support.

LM_36367 <Task instance name and path>: Suspension email has an empty user name.

Explanation:	You configured the workflow to send a suspension email, but the email address for the suspension email is missing.
User Response:	Enter an email address in the Email User Name field for the suspension Email task.

LM_36368 <Task instance name and path>: Failed to send suspension email.

Explanation:	You configured the workflow to send a suspension email, but the Integration Service failed to send the suspension email. This might occur if you did not specify an email profile on the machine hosting the Integration Service, or if the machine does not have an email client.
User Response:	Verify you specified an email profile on the machine hosting the Integration Service, and that the machine has the correct email client.

LM_36369 <Session task instance> <task instance path> Encountered task instance <task instance name> of unknown type.

Explanation:	The Integration Service has encountered a task type that it cannot recognize because the version of the Integration Service and repository are inconsistent. You have upgraded the repository but not the Integration Service.
User Response:	Upgrade the Integration Service.

LM_36381 <Worklet name>: Failed to set the passed value for variable <name>. Cannot find a user-defined variable with this name.

Explanation:	The Integration Service attempted to override the initial value of the named variable in the named worklet, but it could not locate the named worklet variable.
User Response:	Make sure you defined the named variable in the worklet.

LM_36382 <Worklet name>: Failed to set the passed value for variable <name>. The variable <name> cannot be found at the parent <workflow or worklet name>.

Explanation:	The Integration Service attempted to override the initial value of the named variable in the named worklet. It could not do this because it could not locate the named parent workflow or worklet variable.
User Response:	Make sure you defined the named variable in the parent workflow or worklet.

LM_36383 Error in expanding variable parameter.

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

LM_36385 Workflow <name>: Could not acquire the execute lock for Workflow <name>.

Explanation:	You started the specified workflow, but the Load Manager could not lock the workflow before running it. This message occurs when you or another user is currently running the workflow.
User Response:	Make sure that the workflow has finished running before running it again.

LM_36401 <Session task instance> <task instance path> Execution terminated unexpectedly.

Explanation:	The DTM process did not stop, abort, or fail properly.
User Response:	Contact Informatica Global Customer Support.

LM_36440 <Task type> task instance <task instance path>: Error in fetching persistent variable values for <workflow or worklet> <workflow or worklet name>.

Explanation:	The Integration Service failed to get a persistent variable value for the workflow or worklet.
User Response:	Check the Integration Service log and Repository Agent log for more information.

LM_36441 Error: Both parameter list and parameter file are specified.

Explanation:	A third party application tried to start a workflow and specified both a parameter list and a parameter file. The Integration Service needs one or the other to run a workflow, not both.
User Response:	In the third party application, verify you only specify a parameter list or a parameter file.

LM_36471 <Workflow name>: Failover of workflow schedule failed because the information in storage is inconsistent or incomplete.

Explanation:	Trace message. If you have the high availability option, workflow schedule information is written to a storage file in the storage directory, $PMStorageDir. The Integration Service could not retrieve the information required to start up the scheduled workflow on another node.
User Response:	Explicitly schedule the workflow again to run it.

LM_36476 <Workflow name>: Failover of workflow execution failed because the workflow cannot be internally scheduled in recovery mode.

Explanation:	After the Integration Service failed over the workflow to another node, an internal limit was exceeded.
User Response:	Try to recover the workflow manually. Also, verify the availability of the node where the service process started the workflow.

LM_36477 <Workflow name>: Failed to save workflow information for failover.

Explanation:	The Integration Service was unable to write the workflow data to a storage file to enable failover.
User Response:	Verify that the Integration Service can access the storage directory $PMStorageDir. To access the storage directory, the directory must be properly mapped or mounted, and the Integration Service must have the necessary security permissions. If the directory does not exist or cannot be written to, the requests cannot be stored for persistence. Verify that the directory is not full.

LM_36527 <Task instance name and path>: Failed to fetch session to send post session email for this session instance.

Explanation:	The repository containing the session object is not running.
User Response:	Start the repository.
Explanation:	Internal error.
User Response:	Contact Informatica Global Customer Support.

LM_36528 <Task instance name and path>: Failed to expand E-mail user name <user name> for this session instance.

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

LM_36529 <Task instance name and path>: The e-mail user name in the post session failure e-mail component for this session instance is empty.

Explanation:	You selected the On Failure Email option for the session, but the email address for the post-session email is missing.
User Response:	Enter an email address in the Email User Name field for the post-session Email task.

LM_36530 <Task instance name and path>: Failed to send post session failure e-mail for this session instance.

Explanation:	You selected the On Failure Email option for the session, but the Integration Service failed to send the post-session email. This might occur if you did not specify an email profile on the machine hosting the Integration Service, or if the machine does not have an email client.
User Response:	Verify you specify an email profile on the machine hosting the Integration Service, and that the machine has the correct email client.

LM_36538 <Session instance path>: Unable to write to temporary parameter file <parameter file name> with error <error number> <cause of error>.

Explanation:

The workflow is configured to run on a grid. The master service process distributed a session that uses a parameter file to a worker service process. The worker service process needs to create a temporary parameter file in its $PMTempDir directory using parameter file information received from the master service process. However, the worker service process failed to create the temporary parameter file because the Informatica Services account or the operating system user in the operating system profile does not have write permission on $PMTempDir, or because the directory contains a file with the same name.

User Response:

Grant read and write permissions on $PMTempDir to the Informatica Services account or the operating system user in the operating system profile on the worker node, and then run the workflow again. Or, if $PMTempDir contains a file with the same name as the temporary parameter file, delete it and run the workflow again.

LM_36539 <Session instance path>: Unable to unlink temporary parameter file <parameter file name> with error <error number> <cause of error>.

Explanation:	The workflow was configured to run on a grid. The master service process distributed the session to a worker service process. The worker service process created a temporary parameter file in $PMTempDir, but it failed to delete the file.
User Response:	On the worker node, grant permissions to delete a file in $PMTempDir for the Informatica Services account or the operating system user in the operating system profile, and verify that there is enough disk space. Or, manually delete the temporary parameter file from the $PMTempDir directory.

LM_36543 <Task name> condition expression eval error < expression >.

Explanation:	The expression you entered may have invalid characters or cannot be evaluated.
User Response:	Verify that the expression is valid in the Workflow Manager.

LM_36544 <Task name>: condition expression <expression> will not evaluate to a numeric value.

Explanation:	You may have entered the wrong datatype in the expression.
User Response:	Review the expression in the Workflow Manager to ensure that it uses Numeric datatypes.

LM_36564 <Task name>: Invalid datatype conversion for variable <name>, expression datatype <datatype>, variable datatype <datatype>.

Explanation:	In the Workflow Manager, you assigned a value to a variable using the Assignment task. The Integration Service cannot convert the datatype of the expression to the datatype of the variable.
User Response:	Either fix the expression in the Assignment task or change the datatype of the variable.

LM_36565 <Task name>: Variable <name>: data conversion exception <value>.

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

LM_36566 <Task name>: Unable to resolve the left-hand side variable <name> as a user-defined workflow/worklet variable.

Explanation:	In the Workflow Manager, you assigned a value to a variable using the Assignment task. The Integration Service does not recognize the variable as a user-defined workflow or worklet variable.
User Response:	Check the variable declaration in the Assignment task and make sure it matches the name of a user-defined workflow or worklet variable.

LM_36567 Unable to rollback the assignment for variable <name>.

Explanation:	Internal error. An error occurred during the assignment of a variable. The Integration Service updated the value of the variable and could not rollback the change.
User Response:	Contact Informatica Global Customer Support.

LM_36580 <Task instance name and path>. Email Username not specified.

Explanation:	The email address for the Email task is missing.
User Response:	Enter a valid email address in the Email User Name field for the Email task.

LM_36581 <Task instance name and path>. Failed to send email.

Explanation:	The Integration Service failed to send the email specified in the Email task. This might occur if you did not specify an email profile on the machine hosting the Integration Service, or if the machine does not have an email client.
User Response:	Verify you specify an email profile on the machine hosting the Integration Service, and that the machine has the correct email client.

LM_36601 <Timer name> Unable to schedule timer with the timer task manager.

Explanation:	The time specified is invalid. The range must be between 00:00:00 January 1, 1970 UTC, and 3:14:07 January 19, 2038 UTC.
User Response:	Specify a time within the valid range.

LM_36602 <Variable name> Wait for absolute time specified by variable <variable type>. The variable does not exist.

Explanation:	The variable is not specified in the workflow.
User Response:	Specify the variable in the workflow properties.

LM_36603 <Variable name> Wait for absolute time specified by variable <variable type>. The variable is not of type date/time.

Explanation:	The variable type entered was not the Date/Time datatype.
User Response:	Change the datatype to Date/Time.

LM_36604 <Variable name> Wait for absolute time specified by variable <variable type>. The variable value is null.

Explanation:	The value of the variable was null.
User Response:	Specify a value that is not null.

LM_36648 <Event-Wait task>: watch file <indicator file name> was detected, but encountered an error deleting the file. Error code [errno = <error number>, error message <error message>.

Explanation:	An Event-Wait task was configured to delete the file watch indicator file when the Integration Service detected the file. The Integration Service detected the file but failed to delete it.
User Response:	Grant permission to delete the file for the Informatica Services account or the operating system user in the operating system profile.

LM_36823 Workflow <workflow ID> <session> not unscheduled because it is not scheduled.

Explanation:	You tried to remove from schedule a workflow that you have not yet scheduled.
User Response:	Verify that you selected the correct workflow to remove from schedule.

LM_44122 Errors encountered in initializing storage in directory <directory name>.

Explanation:

See previous error message in log for information.

LM_44124 Integration Service is missing workflow manager storage.

Explanation:	Internal Error. The Integration Service could not find the state of operations.
User Response:	Contact Informatica Global Customer Support.

LM_44125 Workflow manager storage is not ready for Integration Service.

Explanation:	Internal Error. The Integration Service is missing the storage file that it uses to write information about services running during failover.
User Response:	Contact Informatica Global Customer Support.

LM_44127 Failed to prepare the task <name>.

Explanation:	The Integration Service was unable to prepare the task due to an internal error.
User Response:	Contact Informatica Global Customer Support.

LM_44136 Failed to release remaining execution locks as failover.

Explanation:	A network or database issue prevented locks from being released. Resilience mechanisms could not recover from a connection problem between the Integration Service and the Repository Service or between the Repository Service and the repository database.
User Response:	Verify that the Integration Service and Repository Service are running and that Repository Service can connect to the repository database.

LM_44180 The number of asynchronous threads for repository connections specified <number of threads> is too low, using default of <number of threads>.

Explanation:	By default, the Integration Service creates one asynchronous thread for every 10 repository connections. The number of threads specified by the LMRepoConnAsyncThreads custom Integration Service property is less than 10. The specified number of threads is not sufficient for the number of repository connections.
User Response:	To use the default number of threads, remove the LMRepoConnAsyncThreads custom Integration property. Alternatively, you can increase the LMRepoConnAsyncThreads value.

LM_44181 Workflow <workflow name> is impacted. The Integration Service is not configured to run sessions impacted by dependency updates.

User Response:

In the Administrator tool, configure the Integration Service advanced property to run sessions impacted by dependency updates.

LM_44183 Scheduling workflow is not allowed because the Integration Service is running in safe mode.

Explanation:	The Integration Service assigned to the workflow is running in safe mode. You cannot schedule workflows when the Integration Service runs in safe mode.
User Response:	If you have the required privilege, you can manually start the workflow. You can also change the operating mode for the Integration Service to normal.

LM_44184 Scheduled workflow <workflow name> was not rescheduled because the Integration Service is running in safe mode.

Explanation:	The workflow runs on a schedule. However, the Integration Service does not run scheduled workflows in safe mode.
User Response:	If you have the required privilege, you can manually start the workflow. You can also change the operating mode for the Integration Service to normal.When you change the operating mode to normal, all scheduled workflows will begin running.

LM_44185 User <user name> does not have sufficient privilege to log on while the Integration Service is running in safe mode.

Explanation:	You do not have the required privilege to connect to an Integration Service running in safe mode.
User Response:	Use a user account with the required privilege or wait until the Integration Service is no longer in safe mode.

LM_44188 <Task name>: Failed to expand email user <name> for this email task.

Explanation:	The Integration Service cannot expand a parameter or variable in the email user name.
User Response:	Verify that the parameter or variable is defined properly in the parameter file and that its value in the parameter file matches the parameter or variable datatype. For example, you cannot set an integer workflow variable to a text string in the parameter file.
Explanation:	The Integration Service cannot expand the parameter or variable in the email user name due to an internal error.
User Response:	Contact Informatica Global Customer Support.

LM_44189 <Workflow name>: Failed to expand email user <name> for this suspension email.

Explanation:	The Integration Service cannot expand a parameter or variable in the email user name.
User Response:	Verify that the parameter or variable is defined properly in the parameter file and that its value in the parameter file matches the parameter or variable datatype. For example, you cannot set an integer workflow variable to a text string in the parameter file.
Explanation:	The Integration Service cannot expand the parameter or variable in the email user name due to an internal error.
User Response:	Contact Informatica Global Customer Support.

LM_44190 <Command task name>: Failed to expand command <command name>, with command value <command text>.

Explanation:	The Integration Service cannot expand a parameter or variable in the command text.
User Response:	Verify that the parameter or variable is defined properly in the parameter file and that its value in the parameter file matches the parameter or variable datatype. For example, you cannot set an integer workflow variable to a text string in the parameter file.
Explanation:	The Integration Service cannot expand a parameter or variable in the command text due to an internal error.
User Response:	Contact Informatica Global Customer Support.

LM_44193 Integration Service <name> will not perform workflow and schedule failover or recovery when running in safe mode.

Explanation:	The workflow is assigned to an Integration Service running in safe mode. The Integration Service will perform workflow and schedule failover and workflow recovery when you change the Integration Service operating mode to normal.
User Response:	Change the Integration Service operating mode to normal.

LM_44205 Error using operating system profiles to run task <task name>: <error message>.

Explanation:	The Integration Service could not use the operating system profile assigned to the workflow.
User Response:	See additional error message for more information.

LM_44207 Cannot stop or abort workflow <ID = run ID> or a task within the workflow. The specified run ID is not found on the Integration Service.

Explanation:	The Integration Service could not stop or abort the workflow because the stopworkflow or abortworkflow pmcmd has an incorrect run ID parameter.
User Response:	Verify that you entered the correct run ID for the workflow. You can find the workflow run ID number in the Workflow Monitor by opening the workflow log or the workflow properties panel.

LM_44208 Cannot stop or abort workflow <ID = run ID> or a task within the workflow. There is more than one instance of this workflow running on the Integration Service. Specify the run ID to stop or abort.

Explanation:	The Integration Service could not stop or abort the workflow because two or more instances of the same workflow are running.
User Response:	When you enter the abortworkflow or stopworkflow pmcmd, enter the run ID option. The run ID is unique for each workflow instance. You can find the workflow run ID number in the Workflow Monitor by opening the workflow log or the workflow properties panel of the workflow you want to stop.

LM_44210 Cannot wait for workflow <ID = run ID> or a task within the workflow. The run ID is not found on the Integration Service.

Explanation:	You entered the pmcmd waitworkflow with an invalid run ID argument.
User Response:	Verify that you entered the correct run ID for the workflow. You can find the workflow run ID number in the Workflow Monitor by opening the workflow log or the workflow properties panel.

LM_44211 Cannot wait for workflow or a task within the workflow. The Integration Service is running more than one instance of the workflow. Specify the workflow run ID to wait for.

Explanation:	You entered the pmcmd waitworkflow with a workflow name, but the Integration Service is running more than one instance of the workflow.
User Response:	Enter pmcmd waitworkflow with a run ID argument. The run ID is unique for each workflow instance. You can find the workflow run ID number in the Workflow Monitor by opening the workflow log or the workflow properties panel.

LM_44220 <Workflow or worklet name>: Failed to set the variable assignment value for variable <name>.

Explanation:	The Integration Service cannot assign a value to the variable in a post-session variable assignment.
User Response:	Verify that the variable exists and that the name is spelled correctly in the assignment statement. Verify that the datatypes of both variables in the assignment statement match.

LM_44222 Request to recover workflow <workflow name> run ID <run ID> does not match the current workflow run ID.

Explanation:	You entered the pmcmd recoverworkflow with a workflow run ID argument that does not match a run ID for a recoverable workflow.
User Response:	Verify that you entered the correct run ID for the workflow. You can find the workflow run ID number in the Workflow Monitor by opening the workflow log or the workflow properties panel of the workflow you want to stop.

LM_44223 The workflow <name> failed because an operating system profile was not specified and the Integration Service uses operating system profiles.

Explanation:	The Integration Service uses operating system profiles.
User Response:	Specify an operating system profile for the workflow in the folder properties or when you manually start a workflow.

LM_44224 The workflow <name> failed because the Integration Service is not enabled to use operating system profiles and an operating system profile was specified.

Explanation:	An operating system profile was assigned to the workflow and the Integration Service does not use operating system profiles.
User Response:	Remove the assignment of an operating system profile. Configure the Integration Service to use operating system profiles.

LM_44225 The Integration Service failed to read parameter file <file name> using the operating system profile.

Explanation:	The Integration Service could not open the parameter file specified for the session.
User Response:	Verify that the operating system user specified in the operating system profile has read permissions on the parameter file.

LM_44226 The maximum number of allowed concurrent runs has been exceeded.

Explanation:	The Integration Service could not start a new workflow instance because the number of workflow instances is at the configured limit.
User Response:	Start the workflow instance after one of the instances completes running.

LM_44227 The workflow contains persisted variables.

Explanation:	The workflow failed because it has the same persisted variables as another workflow instance that is running concurrently.
User Response:	To persist variables for concurrent workflows, configure different workflow instance names and parameters.

LM_44228 A workflow with the same instance name is already running.

Explanation:	The workflow failed to start because a workflow with the same instance name is already running.
User Response:	Verify that the workflow is enabled to run concurrently. Configure unique instance names for each workflow run, or enable the workflow to run concurrently without unique instance names.

LM_44254 Concurrent workflow [folder [ID = <number>], workflow [ID = <number>]] runs with the same instance name. Specify the workflow run ID for recovery.

Explanation:	You tried to recover a concurrent workflow with the same instance name without specifying the workflow run ID.
User Response:	Specify the run ID to identify which workflow instance to recover.

LM_44255 Failed to fetch workflow [Folder ID = <folder ID>, Workflow ID = <workflow ID>] from the repository.

Explanation:	The workflow has been removed from the repository.
User Response:	Specify a valid workflow.
Explanation:	The repository contains inconsistent data.
User Response:	Contact Informatica Global Customer Support.

Explanation:	You have modified the data movement mode in the Administrator tool.
User Response:	Change the data movement mode to ASCII or Unicode by modifying the Administrator tool.

Explanation:	You attempted to run a workflow instance for a workflow that is not enabled for concurrent execution.
User Response:	Do not provide an instance name when running the workflow.

Explanation:	There are no Web Services Hub services in the domain configured to run the web service workflow.
User Response:	Configure the web service workflow to run on a Web Services Hub.

LM Messages

LM_36053 The server mode <current server mode> is invalid. Default server mode <default server mode> will be used.

LM_36072 Cannot get $PMStorageDir from configuration.

LM_36129 Cannot open log file <name>.

LM_36133 Fail in reading log file <name>.

LM_36134 Session is initializing. Session log file is temporarily unavailable.

LM_36136 Task instance <task ID> with workflow <workflow ID> <run ID> did not run on this Integration Service.

LM_36138 Cannot find workflow log name.

LM_36210 Get worklet instance name from repository failed.

LM_36220 Log file <name> contains no data.

LM_36225 The session log file was not created for session instance [ID = <number> in folder [ID = <number>, workflow [ID = <number> [run ID = <number>, worklet [ID = <number> (possibly because the session failed during initialization).

LM_36229 Request failed because the connection was broken or the client is too slow in processing replies, client <name>, connection <name>, request ID <number>.

LM_36269 Connection request was made from client <PowerCenter Client> on host <host machine> for connection to service type <service type>, service name <service>, and service process name <node>. The connection request failed because the service process <node> is not the intended service process.

LM_36271 Connection request was made from client <client> on host <node> for connection to service type <type>, domain name <domain>, service name <service>, and service process name <node>. The connection request failed because the lookup for the service failed.

LM_36272 Failed to get gateway information from URI <universal resource identifier>.

LM_36273 Failed to look up service in domain <domain>, service <service>, service process <node> from name service lookup using the URI <universal resource identifier>.

LM_36274 Failed to look up service in domain <domain>, service <service>, service process <service process> from name service lookup using this URI <service process> with fault code <code>, fault message <message text>.

LM_36310 Workflow <name>: Cannot open log file <name>.

LM_36311 Workflow <name>: Failed to expand workflow log file name <name>.

LM_36312 Workflow <name>: Log path exceeds limit of <number> characters: <path>.

LM36320 <Workflow or task name>: Execution failed.

LM_36338 Workflow <name> Could not start execution of this workflow because the current run on this Integration Service has not completed yet.

LM_36348 <Workflow, worklet, or session instance name>: Parameter file <name> not found.

LM_36349 <Workflow or worklet name>: Failure to create variable manager.

LM_36350 Error in binding the pre-defined variable <name>.

LM_36351 <Workflow name>: Error in persisting variable values.

LM_36362 Workflow <name>: The workflow log count in the repository is negative <number>.

LM_36363 Workflow <name>: Cannot rename workflow log file <file name> to <file name>.

LM_36364 Workflow <name>: Failed to increment the log file number in the repository.

LM_36366 <Worklet name>: Failed to set the passed value for variable <name>.

LM_36367 <Task instance name and path>: Suspension email has an empty user name.

LM_36368 <Task instance name and path>: Failed to send suspension email.

LM_36369 <Session task instance> <task instance path> Encountered task instance <task instance name> of unknown type.

LM_36381 <Worklet name>: Failed to set the passed value for variable <name>. Cannot find a user-defined variable with this name.

LM_36382 <Worklet name>: Failed to set the passed value for variable <name>. The variable <name> cannot be found at the parent <workflow or worklet name>.

LM_36383 Error in expanding variable parameter.

LM_36385 Workflow <name>: Could not acquire the execute lock for Workflow <name>.

LM_36401 <Session task instance> <task instance path> Execution terminated unexpectedly.

LM_36440 <Task type> task instance <task instance path>: Error in fetching persistent variable values for <workflow or worklet> <workflow or worklet name>.

LM_36441 Error: Both parameter list and parameter file are specified.

LM_36471 <Workflow name>: Failover of workflow schedule failed because the information in storage is inconsistent or incomplete.

LM_36476 <Workflow name>: Failover of workflow execution failed because the workflow cannot be internally scheduled in recovery mode.

LM_36477 <Workflow name>: Failed to save workflow information for failover.

LM_36527 <Task instance name and path>: Failed to fetch session to send post session email for this session instance.

LM_36528 <Task instance name and path>: Failed to expand E-mail user name <user name> for this session instance.

LM_36529 <Task instance name and path>: The e-mail user name in the post session failure e-mail component for this session instance is empty.

LM_36530 <Task instance name and path>: Failed to send post session failure e-mail for this session instance.

LM_36538 <Session instance path>: Unable to write to temporary parameter file <parameter file name> with error <error number> <cause of error>.

LM_36539 <Session instance path>: Unable to unlink temporary parameter file <parameter file name> with error <error number> <cause of error>.

LM_36543 <Task name> condition expression eval error < expression >.

LM_36544 <Task name>: condition expression <expression> will not evaluate to a numeric value.

LM_36564 <Task name>: Invalid datatype conversion for variable <name>, expression datatype <datatype>, variable datatype <datatype>.

LM_36565 <Task name>: Variable <name>: data conversion exception <value>.

LM_36566 <Task name>: Unable to resolve the left-hand side variable <name> as a user-defined workflow/worklet variable.

LM_36567 Unable to rollback the assignment for variable <name>.

LM_36580 <Task instance name and path>. Email Username not specified.

LM_36581 <Task instance name and path>. Failed to send email.

LM_36601 <Timer name> Unable to schedule timer with the timer task manager.

LM_36602 <Variable name> Wait for absolute time specified by variable <variable type>. The variable does not exist.

LM_36603 <Variable name> Wait for absolute time specified by variable <variable type>. The variable is not of type date/time.

LM_36604 <Variable name> Wait for absolute time specified by variable <variable type>. The variable value is null.

LM_36648 <Event-Wait task>: watch file <indicator file name> was detected, but encountered an error deleting the file. Error code [errno = <error number>, error message <error message>.

LM_36823 Workflow <workflow ID> <session> not unscheduled because it is not scheduled.

LM_44122 Errors encountered in initializing storage in directory <directory name>.

LM_44124 Integration Service is missing workflow manager storage.

LM_44125 Workflow manager storage is not ready for Integration Service.

LM_44127 Failed to prepare the task <name>.

LM_44136 Failed to release remaining execution locks as failover.

LM_44180 The number of asynchronous threads for repository connections specified <number of threads> is too low, using default of <number of threads>.

LM_44181 Workflow <workflow name> is impacted. The Integration Service is not configured to run sessions impacted by dependency updates.

LM_44183 Scheduling workflow is not allowed because the Integration Service is running in safe mode.

LM_44184 Scheduled workflow <workflow name> was not rescheduled because the Integration Service is running in safe mode.

LM_44185 User <user name> does not have sufficient privilege to log on while the Integration Service is running in safe mode.

LM_44188 <Task name>: Failed to expand email user <name> for this email task.

LM_44189 <Workflow name>: Failed to expand email user <name> for this suspension email.

LM_44190 <Command task name>: Failed to expand command <command name>, with command value <command text>.

LM_44193 Integration Service <name> will not perform workflow and schedule failover or recovery when running in safe mode.

LM_44205 Error using operating system profiles to run task <task name>: <error message>.

LM_44207 Cannot stop or abort workflow <ID = run ID> or a task within the workflow. The specified run ID is not found on the Integration Service.

LM_44208 Cannot stop or abort workflow <ID = run ID> or a task within the workflow. There is more than one instance of this workflow running on the Integration Service. Specify the run ID to stop or abort.