000018022 - Agent host cannot be updated when Auto registration client is installed

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000018022
Applies ToAuthentication Manager 6.1.1
Microsoft Windows 2003 Server
IssueAgent host cannot be updated when Auto registration client is installed
Error "acesync error 3820" messages in RSA server log monitor.

Windows Application log errors: Cannot Update(Create) Agent On Replica 381 (10.201.1.165) SYSTEM Progress Run-Time Error 0. [perelt.c.6700.36]SQL Message: ** SDCLIENT already exists with chNetAddress "10.201.5.137" iProtocol 2. (132) Agent Host record is locked and cannot be updated. Will attempt to update at next replication pass. gqbl931.us.interlink-intranet.net (10.201.1.165) SYSTEM Progress Run-Time Error 0. [climerge.c.681.35].

Unable to transfer Agents from Replica (10.201.1.165) SYSTEM 3010 0. [mloop.c.728.33]


Database compression and re-creating the replica package resolves the issue temporarily, but then the issue comes back.
CauseReplica rejects the agent host's record modification when the Client machine name is changed to the same name as the name which already exists as agent host.
ResolutionThis has been identified as a defect 53104 and resolved in cumulative hot fix 83 for the Authentication Agent and cumulative hot fix 110 for RSA Authentication Manager. Please contact RSA Technical Support to obtain the cumulative hot fixes for server and the Agent. The hot fix consists syncsrvc.exe and it has to be replaced on Primary and Replica servers as well.
Legacy Article IDa34542

Attachments

    Outcomes