Publishes are failing with errors such as these messages in the pw/server/tmp/ps_<instance>/pserver.trace (with debug enabled):

ERROR (120006): Instance not found.; OI-416A0A06F8BB4C3AA8A5B13F126A09BC
    at com.bmc.cmdb.api.CMDBProxyJRpcBase.verifyStatus(Unknown Source)

WARN [RequestHandler-1] (PublishFilter.java:313) - Unexpected: No extended slots available. Per the expected oscomm should have already set the ci.

'Unexpected: no base instance of OI-B6F82B54660A46849BF7C2A5950D387D'

If you check the BMC.CORE:BMC_BaseElement form in the Remedy AR Server, you may not find reference to the InstanceId values that are referenced.  Likewise, if you check for those InstanceId values in the BMC.CORE:BMC_BaseRelationship form, you may find no reference to those values in the Source.InstanceId or Destination.InstanceId fields.

However, if you check the previous publish logs in pw/server/log/ps_<instance>, you may find references to those InstanceId's, indicating that they had once been known by the CMDB and were previously published.

 

These symptoms taken together are a sign that the cell that you are publishing to and the CMDB are out of sync.

Running 'pinit -n <cellname>' followed by a regular publish should correct this.