Data class changes and new data classes were reported to not be replicating from a child SMP up to the parent. It had previously been working fine.
Upon running the following query (against the database of the child) it showed that each computer to be replicated resulted in StatusCode "-2147418113", but the StatusText box had no information to explain what it meant.
select vc.Guid, vc.Name, r._eventTime, r.StatusCode, r.StatusText, vs.Name as Destination from Evt_NS_Object_Replication_Status r join vComputer vc on vc.Guid = r.LocalGuid join vSource vs on vs.Guid = r.RemoteNS order by r._eventTime desc
Because the computer objects failed to replicate the data class information that was supposed to go with them also failed to be sent.
Management Platform 7.6, 8.0
The parent had recently had one or more post 7.6 HF7 cumulative pointfix relases (INFO3459) installed on it; or some other update which was not present on the child. Any version mismatch could be problematic.
Replication, especially in a hierarchy is very sensitive to version mismatches between source and destination servers, and will usually fail to perform replication functions. Most of the time it (version mismatch) will be reflected to the SMP logs, but in some cases it does not.
Verify that the version and HF level of all servers in the hierarchy match exactly.
Subscribing will provide email updates when this Article is updated. Login is required.