Lars Nielsen's Discoveries

September 17, 2011

SQL Transaction Logs filling up

Filed under: SharePoint,Troubleshooting — Lars Nielsen @ 7:31 pm

This issue started with someone telling me that they couldn’t update a document in their team site – they got an error saying that they might be a problem with the library or the server might be busy.

I then tried uploading a file to the document library and got an error:

Unable to complete this operation. Please contact your administrator. at Microsoft.SharePoint.Library.SPRequestInternalClass.PutFile(String bstrUrl, String bstrWebRelativeUrl, Object varFile, PutFileOpt PutFileOpt, String bstrCreatedBy, String bstrModifiedBy, Int32 iCreatedByID, Int32 iModifiedByID, Object varTimeCreated, Object varTimeLastModified, Object varProperties, String bstrCheckinComment, UInt32& pdwVirusCheckStatus, String& pVirusCheckMessage) at Microsoft.SharePoint.Library.SPRequest.PutFile(String bstrUrl, String bstrWebRelativeUrl

I then tried updating a list item on the site and got an error:

Exception from HRESULT: 0x80040E14

This was happening not just on this site but on all the parent sites as well, right up to the root of the site collection. Basically it was impossible to do updates on the site collection. I found this page l and found plenty of errors in the SQL Server Database server. There was a low space warning on the drive related to transaction logs, and errors in the event log related to the SQL Transaction logs being full. Indeed the LDF files for the content databases were huge because they weren’t being cleared out properly during the backup.  Shrinking down the log files solved the problem. The best way to do this is to is to use DBCC in Server Management Studio – remember to back up the log file first See http://support.microsoft.com/kb/907511. Note that you should not use AutoShrink with SharePoint databases. The moral is: always keep an wary eye on your SharePoint database server…

Advertisements

Leave a Comment »

No comments yet.

RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Create a free website or blog at WordPress.com.

%d bloggers like this: