• State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 27 subscribers
  • Views 8994 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Replication Error: object reference not set to an instance of an object

pkuo
over 5 years ago

I have a server 2008 R2 with version 6.1.3 Rapid Restore installed and it's replicating to an off-site server 2012 R2.

I deleted a 1 replicating server from the off-site server and deleted the restore points, but I keep all other servers.

Now I need to start add the server back to replicate to the off site location. The requests showed up at the remote site server and when I tried to add it back to the repository, it gives me an error message "object reference not set to an instance of an object" 

Detail says "object reference not set to an instance of an object"

I found an article similar to the error: https://support.quest.com/appassure/kb/118352/error-object-reference-not-set-to-an-instance-of-an-object-when-adding-an-agent-to-protection

but the reg key isn't there since it is a replication server, not the main backup server. 

 

more info:

Track Trace shows

Server side:

System.NullReferenceException: Object reference not set to an instance of an object.

   at Replay.Core.Implementation.Agents.SlaveCoreAgent.ChangeAgentReplicatedCoreInfo(RemoteCoreSummaryInfo info)

   at Replay.Core.Implementation.Replication.RemoteMasterCore.ReplaceRemoteReplicatedMasterAgents(RemoteCoreSummaryInfo info)

   at Replay.Core.Implementation.Replication.RemoteMasterCore.AddReplicatedAgentsFromRemoteMasterCore(IRemoteMasterCore sourceRemoteMasterCore)

   at Replay.Core.Implementation.Replication.ReplicationService.RespondToPairingRequest(Guid requestId, PendingReplicationPairingResponse response)

   at Replay.Core.Management.Replication.ReplicationManagement.RespondToPairingRequest(String requestId, PendingReplicationPairingResponse response)

 

 

 

 

 UI side:

   at WCFClientBase.HttpResponseMessageExtensions.Check(HttpResponseMessage message, Uri uri, String method, ILogger logger)

   at WCFClientBase.ClientBase.GetResponse[T](Uri uri, String method, T request, String knownEtag)

   at Replay.Core.Client.ReplicationManagementCoreClient.RespondToPairingRequest(String requestId, PendingReplicationPairingResponse response)

   at Replay.Core.Web.Controllers.ReplicationController.ApproveReplicationRequest(ReviewReplicationRequestModel model)

   at lambda_method(Closure , ControllerBase , Object[] )

   at System.Web.Mvc.ReflectedActionDescriptor.Execute(ControllerContext controllerContext, IDictionary`2 parameters)

   at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethod(ControllerContext controllerContext, ActionDescriptor actionDescriptor, IDictionary`2 parameters)

   at System.Web.Mvc.ControllerActionInvoker.<>c__DisplayClass13.b__10()

   at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethodFilter(IActionFilter filter, ActionExecutingContext preContext, Func`1 continuation)

   at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethodFilter(IActionFilter filter, ActionExecutingContext preContext, Func`1 continuation)

   at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethodFilter(IActionFilter filter, ActionExecutingContext preContext, Func

 

 

Has anyone run into this before?

Parents
  • +1 over 5 years ago
    Hi pkuo:
    The replicated agent information is held in more than just one place and KB#118252 is mentioning only the most common situation. You may want to check the registry subkeys under 'HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\Replication\RemoteCores\Slaves\[GUID]\PairingStatus\Agents' which are named 0, 1, 2 , etc and delete any reference to the agent in question (if present). As always when working with the registry, export the key first so you are able to revert easily should something goes wrong.
Reply
  • +1 over 5 years ago
    Hi pkuo:
    The replicated agent information is held in more than just one place and KB#118252 is mentioning only the most common situation. You may want to check the registry subkeys under 'HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\Replication\RemoteCores\Slaves\[GUID]\PairingStatus\Agents' which are named 0, 1, 2 , etc and delete any reference to the agent in question (if present). As always when working with the registry, export the key first so you are able to revert easily should something goes wrong.
Children
No Data