IBM Support

3rd-party Database Monitoring Software causes ContentQueue table updates to fail

Troubleshooting


Problem

Content cannot be moved from inbound folder to staging area.

Symptom

Rows in ContentQueue table cannot process successfully and would always end up in transaction rollback.

The Content Engine (CE) trace and error logs will show the following types of errors and warnings:

  • WARN the number of rows selected doesn't match the number updated 0 vs -1
  • ERROR Can't access or update server/object store assignments in GCD, transaction failed\ncom.filenet.api.exception.EngineRuntimeException: E_INVALID_ARGUMENT: Invalid argument Return from update/insert FNGCD_CESERVERS did not have count of 1

[{"Product":{"code":"SSNVNV","label":"FileNet Content Manager"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Content Engine","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"4.5.0;4.5.1;5.0;5.1.0","Edition":"All Editions","Line of Business":{"code":"LOB76","label":"Data Platform"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
28 April 2025

UID

swg21615178