SharePoint 2013 Audit Log Trimming Timer Job Stuck

Question

Hi All,

I have noticed that the SharePoint content db size increasing quite quickly and I checked the disk usage by table and found out the AuditData table is having 280gb+ over in size.

I investigate on the table and noticed that most of the data is from May to current. Audit Log Trimming is enable in site collection settings but seems like it is not doing it's job. I have also check the job in Central Admin and it is stuck at pausing status (5%) for 2 servers in the farm.

Anyone have idea on what is the issue here?

Answer 1

@Kok Wei
Agree with trevor, you could open a ticket with Microsoft to solve this issue.

Here’s an another reference:
Trim audit log to Improve Performance in SharePoint

---

If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

This is likely because there is too much data to perform the trim and the SQL query is failing or timing out. This often happens when you have View auditing enabled and frequent site usage.

I would recommend opening a case with Microsoft. They can provide guidance and more importantly, leave you in a supported state while manually trimming the table via SQL queries. If you trim the SQL table yourself, your farm will enter an unsupported state.

https://support.microsoft.com/help/841057/