How to resolve third party log file error?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

How to resolve third party log file error?

L5 Sessionator

We have many linux machines onboarded in our cyberark. Almost all machines gets verified and password changed successfully. There are good numbers of machines which throws below error:

CACPM406E Reconciling Password Safe: xxxx-xxxx-xxxx-xxx-xxxx, Folder: Root, Object: Operating System-xxxx-xxxx-xxx-xxx-xyxdjserlkd-oracle failed (try #0). Code: -532462766, Error: CACPM243W Failed to read from third party log file. Error: The system cannot find the file specified. The CPM is trying to reconcile this password because its status matches the following search criteria: ResetImmediately.

Neither it reconcile too.

Our CPM's .Net framework is 4.8, DEP is applied and TPC engine is in good status. What suggestions and ideas you will be best to resolve this issue permanently?

​

Help will be appreciated.

1 accepted solution

Accepted Solutions

L3 Networker

I have faced the same issue and got resolved. the address hostname was too long. I changed to IP address and its works.

I believe the hostname or username is too long. CPM plugin will not work.

View solution in original post

11 REPLIES 11

L6 Presenter

Hi @sanjay shah​,

 

Is the problem general or only on the indicated server?

 

See if the Article 000005033 can help you.

 

Nino

It's the problem for few servers but do not happen with all linux servers. The counting may be around forty and I don't see any dash issue in our object names

Hi @sanjay sah​,

 

I advise you to activate traces and run some tests (change, verify, reconcile).

This way you can verify the whole chain of commands.

 

Nino

 

It is as you suggesting but no chance to resolve the issue.

L7 Applicator

Object name might be too long. Some CPM plugins have an issue where they fail if the path (absolute path + file name) of the log file is too long. Rename the account to use a shorter name and try again.

L4 Transporter

Hi @sanjay sah​ 

 

As it seems BernhardB provided an answer for your question, could you kindly share if this solution resolved your issue?

If so, could you please mark their answer as "Select as Best" to help other community members?

 

If the issue is still relevant, I would advise raising a ticket with our Support team for further assistance.

 

Thank you,

Niv

I shorted the name but I am getting new error "ImmediateTask. Failure Description: ] Execution error. EXT01::First login - User is not allowed to log in. Error code:8012".

​

Reconciliation happens successfully but verify and change fails with above error

After shorting the name I get this "ImmediateTask. Failure Description: ] Execution error. EXT01::First login - User is not allowed to log in. Error code:8012" error but reconcile is good now, but verify and change fails with this error

Hi @sanjay shah​ Was this issue resolved? Could you share the resolution, please? We are having the same issue on 12.2 self-hosted.

Do you have ideas to play with CPM plugins? There you should have to tweak to make it successful.

L3 Networker

I have faced the same issue and got resolved. the address hostname was too long. I changed to IP address and its works.

I believe the hostname or username is too long. CPM plugin will not work.

  • 1 accepted solution
  • 4367 Views
  • 11 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!