SharePoint_Config_Log file size is 78GB

Been doing a routine check of my servers, and noticed that our SharePoint server was lacking some free space. A little unusual, given our SharePoint installation is quite small. And although this server also acts as a Streaming Media server using Windows Media Services, I didn’t think that we had that much streaming media.

Turns out that the SharePoint_Config_Log file size was 78gb. This is around 80% of the drive that it is stored on. This meant that we had only 6gb remaining.

In this situation a full backup was not possible to truncate the logs. Symantec Backup Exec was still backing up the databases every night though. To cure this problem, a quick little fix:

  1. Open up Microsoft SQL Server Management Studio
  2. New Query
  3. Type in the following and press execute.

Database size magically down from 78gb to 10mb.

Server is now happy, and running better.

19 people found this post useful.

21 thoughts on “SharePoint_Config_Log file size is 78GB

  1. I troubleshot this issue off and on for about 7 hours… and I know how to use Google, I WISH I had found your site first…this fixed it right away. Mad props to you…genius.


  2. SharePoint Config database log file too big. Solve it

    USE SharePoint_Config
    DBCC SHRINKFILE(N’SharePoint_Config_log’, 1)

  3. With SharePoint services enabled the log file grows by about 75 – 80GB a day. Event Viewer – Application revealed an error relating to SharePoint but Googling it revealed it to be very generic and was not much help. Clearing the application log I found out fills with around 33,000 error logs in about 4 seconds with every entry being identical.
    I went on to plan B and followed the procedure to shrink the log file, then proceeded to disable all SharePoint services. That was a week ago and success, No more errors in the event log and the log file remains at 504KB. Although it has fixed the issue I never did get the bottom of the cause of the issue.

  4. Just though I would give an update!!!

    I have managed to shrink it down to 504KB. For whatever reason after multiple detach and attachment of the database suddenly I was able to go into areas I couldn’t before and the shrink command gave me more options. But the big question is, will this be likely to be an ongoing issue?

    1. I have never had to do it again – but I did add it in to my weekly checklist. I have no idea why it would suddenly allow you to shrink it though. Glad you got sorted.

  5. I have tried restarting the server with all other servers and workstations off. Then trying the shrink command again. It managed to free up another couple of MB’s. This file is starting to get dangerously close to filling ALL of C Drive. Have also attempted a repair of .NET4 and WSS with no success. Just noticed it has suddently grown another 60GB within the last hour.

  6. Wish this method worked better for me. The server is 3 weeks old and have nearly finished configuring it when this morning noticed the SharePoint Config LDF is approaching 1TB (yes, terabyte). This company doesn’t even use SharePoint. They are nearly out of space on their server. Running the above command and shrinking the log file recovered 0.19MB of free space.

    1. Wow. Thats the largest I’ve heard of. Have you tried restarting the database instance and then running the command. That should release any locks on the database.

    1. loool, same here dude

      my heart fall down, my database reduced from 322GB to 540KB i thought i lost all my data :D

      wonderful solution, thanks

  7. Something’s not right… Isn’t there something in SQL management about regularly shrinking the logs? Failing that, MAINTENANCE TASK!

  8. Go to SQL2008, shrink the log, change the recovery mode to simple like Capita recommends for SIMS. Won’t ever grow!!

    You should really back it up regularly, then it’ll shrink the log file!!

    1. That’s the annoying thing – I have been!!

      Symantec doing full backup nightly, and to prove that I could even do the test restore to a new server. It just wasn’t shrinking.

      Seems to be shrinking fine now though. Maybe just required this to be run to kick start it?

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.