SAP Knowledge Base Article - Preview

1902985 - Replication Jobs remain in a Pending state

Symptom

  • A Replication Job is in a Pending state and never goes to running even though nothing obvious is blocking it.
  • When you look at the instance details, you notice the Next Run Time is 30 minutes after the time you originally set.
  • In the AJS logs from the ReplicationSchedulingService child process, the below errors may be seen:
    Another replication job is replicating content from the same origin site. This job will be attempted again later. (FWM 14009)

  • In specific circumstances, the below error may also be seen
    The property SI_CUID of info object with id number x is not unique. Table = 'CMS_InfoObjects7'. Column = 'SI_CUID' 
     <CUID> Replication lock for <SERVER>  Folder


Read more...

Environment

  • SAP BusinessObjects Business Intelligence (BI) Platform 4.x / 2025
  • Windows
  • Linux / Unix 

Product

SAP BusinessObjects Business Intelligence platform 2025 ; SAP BusinessObjects Business Intelligence platform 4.3

Keywords

Un autre travail de réplication réplique le contenu du même site d'origine. Une nouvelle tentative sera effectuée sur ce travail ultérieurement. (FWM 14009)
WARN  2026-03-05T10:07:33.746Z  La propriété SI_CUID de l'objet info portant l'ID <ID> n'est pas unique. Table = dbo.CMS_InfoObjects7. Colonne = SI_CUID.
  <CUID> Replication lock for <SERVER>  Dossier , KBA , BI-BIP-DEP , Webapp Deployment, Networking, Vulnerabilities, Webservices , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.