SYMPTOM:
Users may observe multiple errors of the form "Object with ID `XXX` and type 34 (User) is not found in metadata" when accessing or executing an application object such as a report or document, or a folder in the Strategy metadata. The errors can be seen every time the action that triggers these is repeated.
CAUSE:
There are multiple causes for the error "Object with ID 'XXX' and type 34 (User) is not found in the metadata. It may have been deleted'. This error is seen in the specific case where users or groups have specific access control lists (ACLs) controlling access to an object, and these users or groups are subsequently deleted from the metadata.
Every time an object is accessed on or executed, the Intelligence Server will attempt to load the ACLs for that object and the error described above will be displayed if the user or groups who previously had ACLs applied are missing in the metadata.
ACTION:
In Strategy 9.4.x, users can use the MDDoctor utility to check and correct ACLs for users and groups missing in the metadata. This information is documented in the technical note: KB8529 "What checks are performed by MDDoctor and how should the results be interpreted?".
Note: MD Doctor is currently not supported to be used against Strategy 10.x metadatas. This is documented in the following technical note:
KB303391: Is MD Doctor 6 supported with Strategy 10.x metadata?
WORKAROUND:
The error messages can simply be ignored. However, if users desire to avoid these messages from being included in the Intelligence Server DSSErrors log, a new log destination may be created in the Strategy Diagnostics tool, and the Object Server -> Trace dispatcher may be redirected to this new log destination for the CastorServer Instance.
