Problem when starting agent exec

Hi,

I have a Content Server Active/Passive Cluster running on Windows Server 2003. For a couple of days after installing Content Server everything seemed to work fine but then, suddenly the agent exec process is unable to start in one of the nodes of the Cluster. When the repository service is started on node A the following error appears in the repository log:

[ERROR] [AGENTEXEC 6696] Detected during program initialization: Command Failed: connect,ren_sgd_prod.ren_sgd_prod,sgd_p_dmadmin,'',,,try_native_first, status: 0, with error message [DM_SESSION_E_CLIENT_AUTHENTICATION_FAILURE]error: "Failed to authenticate client. Please check server log for more detail."

This error seems to have started around the time the Active Directory was upgraded from MS AD 2000 to MS AD 2003

When I move the cluster resource group to the Node B, the repository and agent exec start without any problems.

I also used process explorer to find out the command line that was being used to start the dm_agent_exec process and then used that same command line to start the dm_agent_exec process mannualy and it started without any error.

I tried to look through the documentum logs and through the system event viewer to try to find what was causing this problem but I have been unable to discover what the problem is.

Has anyone experienced a similar issue or is able to give me some information on how to find out what the problem is?

Regards,

Pedro Ventura

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

All comments

AnithaSeshadri

This could occur if dfc.keystore file is corrupted.
Please see the below support solution for this issue.

http://solutions.emc.com/emcsolutionview.asp?id=esg100662

This could also occur if there is a hostname and ip address change. This can be specific to any one of the customer environment and need not occur. There may be some incorrect entries in the problematic server which are not there in the other server.

Using the tool which is mentioned in the support solution will only re-register the content server with the new hostname and ip address. We have already recommended this to various customers.

http://solutions.emc.com/emcsolutionview.asp?id=esg92607

Thanks,

Anitha

Pedro Ventura

There was no IP address or hostname change but the dfc.keystore appeared to be corrupted. I copied the dfc.keystore from the working node to the node having problems and the problem appears to have been solved.

Thanks for the help.

Panvivek

Hi OT,
Do we have new links for above shared urls:
http://solutions.emc.com/emcsolutionview.asp?id=esg100662

http://solutions.emc.com/emcsolutionview.asp?id=esg92607

These urls arent hosted anymore. Kindly help