PerthRM8 Outstanding Contributor.
Outstanding Contributor.

Logs to find out when user used higher TRIM version to access PROD

Hi all,

HPE RM8.3 Patch 2 , Win 10, MS Office 2016, SQL 2012-R2 (Could be 2016)

Testing Micro Focus Content Manager


OK, we really must find out when the user/tester with CM9.3 Client installed, instead of pointing to TEST environment of 9.3 actually pointed towards the PRODUCTION HPE RM8.3 TRIM Database and done some changes (so, logs for history events/ausit logs, Online ones) .... is there any metadata anywhere that say that user used the CM9.3 instead of RM8.3 ...

The idea is to compile the saved search for all logs/events (changes) coming from higher TRIM this case we want to isolate events which are BTW not written in the Prod 8.3 TRIM Database anywhere.... So, if the user edit document using CM 9.3, pointing to a lower TRIM version database and change the dollar value in a contract document , that is not written in the normal logs, e.g. right click security - evnt audits ....then the troubles starts.

The only good news that these events are written in the Offline Logs as TALF extension text documents .... but once again, there is no distinction between these logs, e.g. cannot figure it out which line of log are done using CM9.3 Client and which one are made using normal matching version HPE RM8.3

The only difference i spot was the different assett number of the PC machine, but that is not reliable..

Anyone worried about these sort of things or ...?

Any comments appreciated.



2 Replies
Outstanding Contributor.. Sten28 Outstanding Contributor..
Outstanding Contributor..

Re: Logs to find out when user used higher TRIM version to access PROD

In my experience, the CM back-end does not note the version in use via the logs. You may find PC asset number as you had mentioned, but not much more than that. 

Rather than tackle it via CM, you could consider going through your desktop team, i.e. identify which PC assets have had the new client deployed for testing purposes. That may help you narrow down machines/unique users.

PerthRM8 Outstanding Contributor.
Outstanding Contributor.

Re: Logs to find out when user used higher TRIM version to access PROD

Thanks Sten28,

I intend to ask MicroFocus for the enhancement to fix this as we often find our selfs in the situation where we have a higher TRIM Client than the database version and that audit trail (History events logs) are not complete, they are compromised as users are doing changes on the document and that is not recorded in the TRIM database simply because the user is using higher TRIM Client.

I was hoping that someone here will come up with some SQL code/statement or SQL Report run against the PROD database 8.3 whic will clearly identify the user and events who have done some changes to the TRIM documents in PROD... Anything, differences between server date/times, process ID's, event ID, object ID, connection / Client IP Address , some folder path, anything (and anywhere - online or offline logs) that will say, that "this user has accessed the PROD with higher version of TRIM, changed the document (metadata or electronic document) and that is not recorded in the PROD TRIM Online logs " ... Must be distinctive in the Offline logs BTW.

TRIM Document's Store perhaps, are there any logs there to say that metadata of this new document's revision is a bit strange? ...


Anyone else?




The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.