Troubleshooting Steps when running into the error above:
- Check if it is a problem with using a Native Account
An easy test for this is to create a new Native account within the Informatica security domain and ensure that this new account is added to the same native security group as the login that is currently having issues. Then test with a new connection object with this dummy Native user within the same group. This way, we know that the problem isn't with the Informatica group if we have no issues.
- Ensure that the Native user has all necessary permissions
Insufficient permissions can always be a problem; double check that the user has all the necessary permissions for the repository.
- Check the Native Account's credentials
Check that the account's credentials are correct by manually logging into the domain or the Informatica client applications such as repository manager or designer. If it works, then make sure that these credentials are the same as in the connection object.
- Test the getworkflow log command manually
The RA Informatica connection object runs this command and may have trouble doing so. Manually test the getworkflog log command to ensure that Informatica security isn't the cause:
$INFA_HOME/server/bin/infacmd.sh getWorkflowLog -dn <Domain Name> -rs <Repository Name> -is <Integration> -ru <username> -rp '<Password>' -fn <Folder Name> -wf <Workflow Name> -fm TEXT
- See if the Informatica connection object is corrupted
The RA Informatica Object may be corrupted which is why the getworkflow log command is not running. To test this, try deleting the old connection object and making a new connection object with the same credentials.
- Delete the Agent cache
Stop the Agent and in the cache folder delete INFORMATICAAGENT. Be very careful when doing this step! Don't do this with root and check where your path is located before deleting anything. This comes from the actual Agent so it will be rebuilt after being deleted.
-The issue still persists?
While a possible Informatica solution is to recreate the entire domain, this is obviously a very impactful action. When running into this error it is a good idea to check these steps first. When making a ticket with support, please note which steps have already been tried so that it will be easier to narrow down the issue.