Return
-
Title
Rollup jobs are not able to run -
Description
When forcing rollup on an agent, the task never gets created and appears rollup wasn't working or you get the following error:"The remote slave core with the id 'c9e2335a-db33-4833-ae33-0cb27bd20c33' was not found."Alternatively, jobs may get created but ends almost immediately, without processing any data. Comparing a list of recovery point with retention policy may show discrepancies. -
Cause
Looking at the logs you see the following errors:Microsoft.Http.HttpStageProcessingException ---> System.Net.WebException ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 192.168.1.100:8006at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)Replay.Core.Contracts.Replication.RemoteSlaveCoreNotFoundException depth 0: The remote slave core with the id 'c9e2335a-db33-4833-ae33-0cb27bd20c33' was not found. (0x80131500) ---> System.Collections.Generic.KeyNotFoundException depth 1: The given key was not present in the dictionary. (0x80131577) -
Resolution
There is a replication target for the Core that is unreachable.
Please review Replication Targets and delete any servers that appear as grey or red before forcing rollup.
Once replication core has been removed, rollups will work going forward.