Computers and inventory data classes no longer replicate from a child SMP to a parent.

Products

• IT Management Suite

Issue/Introduction

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.

Environment

ITMS 8.x

Cause

The parent had recently had one or more pointfixes 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.

Resolution

Verify that the version and HF level of all servers in the hierarchy match exactly.  

Additional Information

215121 CUMULATIVE POST ITMS 8.6 RTM (GA) POINT FIXES

221269 CUMULATIVE POST ITMS 8.6 RU1 POINT FIXES

235538 CUMULATIVE POST ITMS 8.6 RU2 POINT FIXES

249427 CUMULATIVE POST ITMS 8.6 RU3 POINT FIXES

261271 CUMULATIVE POST ITMS 8.7 RTM POINT FIXES

273903 CUMULATIVE POST ITMS 8.7.1 POINT FIXES

366939 CUMULATIVE POST ITMS 8.7.2 POINT FIXES

382575  CUMULATIVE POST ITMS 8.7.3 POINT FIXES