Client Support
Showing results for 
Search instead for 
Do you mean 

HP RM8.1 Audit Logs blocked by Error - every morning

Valued Contributor

HP RM8.1 Audit Logs blocked by Error - every morning

[ Edited ]
Hi, HP RM8.1..1.7760 Win 7, SQL 2012 Every morning HP RM ES shows that Audit Log events are blocked by error and not processing, just accumulating. Resume events does not help, only the restart or whatever IT does. The error on the WGS is just this one below for the last 3-4 days, and the URI number mentioned in the WGS logs is I believe just a normal document opening normally, checking out and in without issues, no workflow actions etc.. Any ideas why is this happening? Thanks ======== Log opened on Server.something.com.au at Tuesday, 28 July 2015 at 12:53:34 AM GMT (Tuesday, 28 July 2015 at 8:53:34 AM) 00:53:34:860 1 MR TRIMEvent starting. 00:53:34:876 0 MR EventsInBatch=1000 00:53:34:876 0 MR EventPollingInterval=60 00:53:34:876 0 MR LockTimeout=600 18:14:28:326 0 MR Error : MR User: Server - Function request () for HP Records Manager Workgroup Server 'Server.something.com.au' failed. Error executing SQL statement: Query timeout expired Details: Extended SQL Error Information: Number = 0x80040e31 Source = Microsoft OLE DB Provider for SQL Server Description = Query timeout expired SQLState = HYT00 NativeError = 0 SQL command: SELECT recordId FROM TSRECORD WITH (NOLOCK) WHERE (uri = 2604228) AND ( NOT EXISTS ( SELECT aexObjectUri FROM TSaccessEx WITH (NOLOCK) WHERE aexObjectUri IN (TSRECORD.rcMatterRecord, TSRECORD.uri) AND aexObject = 6 AND (aexLocUri IN (0,343665) )) ) ====================== Log opened on Server.something.com.au at Thursday, 30 July 2015 at 1:18:13 AM GMT (Thursday, 30 July 2015 at 9:18:13 AM) 01:18:13:364 0 MR TRIMEvent starting. 01:18:13:364 0 MR EventsInBatch=1000 01:18:13:364 0 MR EventPollingInterval=60 01:18:13:364 0 MR LockTimeout=600 Log opened on Server.something.com.au at Thursday, 30 July 2015 at 1:18:24 AM GMT (Thursday, 30 July 2015 at 9:18:24 AM) 01:18:24:054 0 MR TRIMEvent starting. 01:18:24:070 0 MR EventsInBatch=1000 01:18:24:070 0 MR EventPollingInterval=60 01:18:24:070 0 MR LockTimeout=600 18:13:43:756 0 MR Error : MR User: Server - Function request () for HP Records Manager Workgroup Server 'Server.something.com.au' failed. Error executing SQL statement: Query timeout expired Details: Extended SQL Error Information: Number = 0x80040e31 Source = Microsoft OLE DB Provider for SQL Server Description = Query timeout expired SQLState = HYT00 NativeError = 0 SQL command: SELECT recordId FROM TSRECORD WITH (NOLOCK) WHERE (uri = 2604228) AND ( NOT EXISTS ( SELECT aexObjectUri FROM TSaccessEx WITH (NOLOCK) WHERE aexObjectUri IN (TSRECORD.rcMatterRecord, TSRECORD.uri) AND aexObject = 6 AND (aexLocUri IN (0,343665) )) ) ====== Log opened on Server.something.com.au at Thursday, 30 July 2015 at 6:13:43 PM GMT (Friday, 31 July 2015 at 2:13:43 AM) 18:13:43:160 1 MR Error : MR User: Server - Error executing SQL statement: Query timeout expired Details: Extended SQL Error Information: Number = 0x80040e31 Source = Microsoft OLE DB Provider for SQL Server Description = Query timeout expired SQLState = HYT00 NativeError = 0 SQL command: SELECT recordId FROM TSRECORD WITH (NOLOCK) WHERE (uri = 2604228) AND ( NOT EXISTS ( SELECT aexObjectUri FROM TSaccessEx WITH (NOLOCK) WHERE aexObjectUri IN (TSRECORD.rcMatterRecord, TSRECORD.uri) AND aexObject = 6 AND (aexLocUri IN (0,343665) )) )
3 REPLIES
HPE Expert

Re: HP RM8.1 Audit Logs blocked by Error - every morning

Hey mate,

 

Best if this come through as a support case, we will need to examine the log files and you might not want to post them up here.

**Any opinions expressed in this forum are my own personal opinion and should not be interpreted as an official statement on behalf of Hewlett Packard Enterprise**
Advisor

Re: HP RM8.1 Audit Logs blocked by Error - every morning

PerthRM8 from your logs listed it is showing that a SQL Query Timeout is happening and for the same Record URI. This could happen for more then one reason with several ways to discover the cause.

 

  1. Within TMS verify your Connection Timeout setting from the connection tab of the properties of your Dataset. Default is -1 for 30 seconds and 0 means no timeout is set (numbers without the dash are per second as 60 =  60 seconds).
  2. Review the Application Events on the WGS and SQL Servers to verify if any other Events were recorded just prior to the Query Timeout. 
  3. Verify that no SQL jobs or SQL Backups are running at the time of the Error.
  4. Verify that you have a SQL Maintenance Job that includes Dropping or Rebuilding  the Idexes and Updating the Statistics.
  5. Since it is the same Record URI that is in the Errors that you provided try running the  SQL Select Clause SQL Management Studio SELECT recordId FROM TSRECORD WITH (NOLOCK) WHERE (uri = 2604228) AND ( NOT EXISTS ( SELECT aexObjectUri FROM TSaccessEx WITH (NOLOCK) WHERE aexObjectUri IN (TSRECORD.rcMatterRecord, TSRECORD.uri) AND aexObject = 6 AND (aexLocUri IN (0,343665) )) ) to verify a result.
  6. Then from the Query Tab in the SQL Management Studio select Display Estimated Execution Plan This will show you the details of how your Query will be Executed Graphically take notice of Nested conditions and or the use of Lazy Spools If you have Lazy Spools then your issue is with how the Statistics are being update.
**Any opinions expressed in this forum are my own personal opinion and should not be interpreted as an official statement on behalf of Hewlett Packard** .
Valued Contributor

Re: HP RM8.1 Audit Logs blocked by Error - every morning

Thanks Cirilo & Methody, I will instruct IT to try this, Much appreciated. Regards