Troubleshooting Informatica Error Messages and Resolution – Part 199


LM_36210Get worklet instance name from repository failed.
Cause:You may have deleted the worklet from the repository.
Action:Verify that the worklet exists.
Cause:The database server or the Repository Service may have failed.
Action:Verify that the database server and Repository Service are running.
Cause:The repository may contain inconsistencies.
Action:Contact Informatica Technical Support.
LM_36220Log file [name] contains no data.
Cause:The log file is empty, most likely because someone deleted its contents.
Action:If you need to see the log file data, rerun the session or workflow to generate the log file again.

LM_36225The 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).
Cause:The Integration Service failed to create the named session log file because the session failed during initialization.
Action:Check the workflow or server log file to see why the session failed.
LM_36229Request failed because the connection was broken or the client is too slow in processing replies, client [name], connection [name], request ID [number].
Cause:The Integration Service tried to retrieve a session or workflow log file over a network connection, but the connection was broken or timed out.
Action:Check the network connection and try to open the log file again.

LM_36269Connection 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.
Cause: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>.
Action:Verify that the node is available and attempt the connection again. If you use pmcmd, use the options -d <domain> and -sv <service>.

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.

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


Leave a Reply

Your email address will not be published. Required fields are marked *