Replication Error Messages

The following tables list possible causes for error messages caused by replication issues.

Error Messages on Replica Servers

Table 37 lists possible causes for error messages on replica servers in a replication realm.

Table 37: Error Messages on Replica Servers

Error Type	Error Message	Possible Cause
Post Errors (Errors with Notification from Primary)	CRadManagedServerNotifyPost:: ExecutePost invalid signature!	Mismatched replication secret.
	CRadManagedServerNotifyPost:: ExecutePost invalid sequence number	Two posts have the same sequence number. The clocks on the primary and replica are more than 10 minutes apart.
	CRadManagedServerNotifyPost:: ExecutePost decrypt failed	Shared secret failed to decrypt. Bad Replication Shared secret.
	CRadManagedServerNotifyPost:: ExecutePost invalid <body> missing parameters	Post had an invalid xml request.
Update Errors (Errors with Published package from Primary)	CRadManagedServerUpdate:: DoStart Failed to open 'file_name' for writing	Temp directory does not exist. Temp directory or file have incorrect permissions.
	CRadManagedServerUpdate:: StartUpdates has already started update	Update is already in progress.
	CRadManagedServerUpdate:: DownloadPackage HTTP POST error:errCode Primary ID	Error in transmitting request to Primary (timeout during transmit).
	CRadManagedServerUpdate:: DownloadPackage HTTP headers parsing error	Error in receiving package. Typically caused by a timeout during receive resulting from an invalid package.
	CRadManagedServerUpdate:: DownloadPackage connection `primary IP Addr error: errCode Primary ID`	Replica failed to connect with Primary. Primary not running.
	CRadManagedServerUpdate:: DownloadPackage exceeded iterations limit while communicating with CCM	Update failed after three attempts.
	CRadManagedServerUpdate:: ProcessPackage signature mismatch	Secrets on Replica and Primary do not match.
	CRadManagedServerUpdate:: ProcessPackage CCM error: 'Error String' 'Parameter'	Error parsing downloaded packages.
	CRadManagedServerUpdate:: ProcessPackage Failed to open \'” << file_name << “\' for writing	Temp directory does not exist. Temp directory or file has incorrect permissions.
	CRadManagedServerUpdate:: ProcessPackage thumbprint mismatch	Invalid package. Republish the package.
Proxy Errors (Statistics retrieve errors)	CRadProxyPost:: ExecutePost invalid signature!	Mismatched replication secret.
	CRadProxyPost:: ExecutePost invalid sequence number	Two posts have the same sequence number. The clocks on the primary and replica are more than 10 minutes apart.
	CRadProxyPost:: ExecutePost decrypt failed	Shared secret failed to decrypt. Bad Replication Shared secret.
	CRadProxyPost:: ExecutePost invalid <body> missing parameters	Post had an invalid XML request.

Error Messages on Primary Servers

Table 38 lists possible causes for error messages on primary servers in a replication realm.

Table 38: Error Messages on Primary Servers

Error Type	Error Message	Possible Cause
Notify Target (Both Notify and Publish send a notification)	CRadConfigManagedServerHTTP Notification::NotifyTarget failed to fetch	Replica does not exist in database. This can occur if two administrators are running instances of Web GUI, one administrator deletes a replica, then the other administrator tries to publish to that replica.
	CRadConfigManagedServerHTTP Notification::NotifyTarget failed replicaId	Notify failed to communicate with replica, Replica is not running, or check Replica DCF log for more information.
Publication Provider (requests from GUI to Notify or Publish)	CRadConfigPublicationProvider:: UpdateResource notify invoked when not Primary	Attempted to Notify as a Replica, this is only allowed from a Primary.
	CRadConfigPublicationProvider:: UpdateResource publish invoked when not Primary	Replica attempted to publish; publication is permitted only from a Primary.
Publication Post (parsing of Post from replica to get data)	CRadConfigServerProviderPost:: ExecutePost signature mismatch with server:	Replica and Primary have different replication secrets.
	CRadConfigServerProvider:: GetResource invoked when not Primary	Another Replica is requesting a download from this server which is a replica. Replica that is requesting a download needs to be reconfigured.
Proxy Errors (Statistics retrieve errors)	CRadProxyClient:: Send failed to fetch	Replica does not exist in database. This can occur if two administrators are running instances of Web GUI, one administrator deletes a replica, then the other administrator tries to publish to that replica.
	CRadProxyClient:: SendData HTTP POST error:	Connection error with replica.