Nishant Rana's Weblog


Home | Pages | Archives


Unexpected error (SQL Timeout error) while trying to delete Audit Log

November 30, 2018 6:17 PM


Unexpected error (SQL Timeout error) while trying to delete Audit Log

We had around 200 GB of Audit Log data in our Production Environment (Online), but while trying to delete it through Audit Log Management resulted into unexpected error.

The only option is to raise the support ticket with Microsoft. We also raised the same but it unfortunately resulted in our Production Server being down for brief period of time because of time out issue while performing the operation in Audit Base.

So, in short if we are facing issue while deleting log ourselves, we need to raise the support ticket and also the plan the same during downtime or weekends when users are not using the system.

Hope it helps..


Discover more from Nishant Rana's Weblog

Subscribe to get the latest posts sent to your email.

Posted by Nishant Rana

Categories: Dynamics 365, Microsoft Dynamics 365

Tags: , ,

5 Responses to “Unexpected error (SQL Timeout error) while trying to delete Audit Log”

  1. […] The only option is to raise the support ticket with Microsoft. We also raised the same but … Continue reading "Unexpected error (SQL Timeout error) while trying to delete Audit Log&qu… Read Complete Post and […]

    Like

    By Unexpected error (SQL Timeout error) while trying to delete Audit Log - Microsoft Dynamics CRM Community on November 30, 2018 at 6:32 PM

  2. Was this online or on-premise?

    Liked by 1 person

    By Harj on November 30, 2018 at 6:37 PM

    1. Online Harj. Thanks for pointing that out, I have updated the post.

      Liked by 1 person

      By Nishant Rana on November 30, 2018 at 6:40 PM

  3. We get timeouts at a customer’s as well, although we only have 31 GB audit files. Looks like some not performant SQL script running into the 2 minute timout.

    Liked by 1 person

    By Jan Nebendahl on December 17, 2018 at 5:39 PM

    1. thanks Jan for sharing your experience with this error. Yes if it is giving the same error with 31 GB then the problem lies in the script itself, only the size cannot be blamed.

      Like

      By Nishant Rana on December 17, 2018 at 10:57 PM

Leave a Reply



Mobile Site | Full Site


Get a free blog at WordPress.com Theme: WordPress Mobile Edition by Alex King.