The transaction log for database 'SharePoint_Config' is full

Question

_{Tuesday, January 10, 2012 10:44 PM}

Hi all ,

I am very new to sharepoint. when i tried to remove a wsp file from central administration i got the message like

The transaction log for database 'SharePoint_Config' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases.

Can anybody help me to solve this please. I saw one solution in net like this but i don't know how to do this. Can anybody help me how to do these steps please.

1.        Take the configuration database offline and detach it

2.        Copy the current MDF to a new location (to be used as a way of recovering the database if needed)

3.        Put the database back on-line, reattach it and then put it within simple mode (from full), with an aim of this stopping the database from increasing in size

4.        Shrink the database and recover log space

5.        Should the shrinking fail, we'd look at detaching the database, making a sideways copy of the log file to another database

6.        We would then reattach the database, which should generate a new log file

Thank you 

All replies (10)

_{Wednesday, January 11, 2012 12:57 AM ✅Answered | 8 votes}

On your SQL Server, open the SQL Server Management Studio.  Connect to the local SQL Server.  Right click SharePoint_Config -> Properties -> Options.  Change Recover Model from Full to Simple.  Click OK.  Right click SharePoint_Config, go to Tasks -> Shrink -> Shrink Files.  Select a File type of Log, then Shrink.http://sharepoint.nauplius.net

_{Tuesday, January 10, 2012 11:05 PM}

Hi,

Do you have any DBA resource where you are working at? He should be able to do this for you. Or is it a lab environment that you built for yourself?

Thanks, Soumya | MCITP, SharePoint 2010

_{Tuesday, January 10, 2012 11:15 PM}

Change the Recovery Model of the SharePoint_Config database from Full to Simple (if not using replication).

Shrink LDF.

http://sharepoint.nauplius.net

_{Wednesday, January 11, 2012 12:10 AM}

Hi Soumya,

I don't have any dba resource. And it is not a lab environment. It's Corporate environment.

Thanks alot for ur quick reply.

_{Wednesday, January 11, 2012 12:11 AM}

Hi Trevor,

I am sorry to ask u this questions but really i don't know.

How to open sharepoint_config file. Where it will be located.

How can i do Replication.

Thank you verymuch for ur  valuable reply

_{Wednesday, January 11, 2012 1:29 AM}

Thanks alot Trevor.

Thank you very much

_{Friday, February 20, 2015 7:17 PM}

Change the Recovery Model of the SharePoint_Config database from Full to Simple (if not using replication).

Shrink LDF.

http://sharepoint.nauplius.net

Why? Replication works in simple recovery model.

My blog: SQL Soldier
Twitter: @SQLSoldier
Microsoft Certified Master: SQL Server 2008
My book: Pro SQL Server 2008 Mirroring

_{Friday, February 20, 2015 7:29 PM}

Hi Soumya,

I don't have any dba resource. And it is not a lab environment. It's Corporate environment.

Thanks alot for ur quick reply.

I normally don't just come onto the threads and tell people that they need a consultant, but you might want to look at getting a consultant to help make sure that your SharePoint environment is health and can be restored in the event of a server failure.  Based on the problem that you have described it might not be recoverable, or at least it might not be as recoverable as you want it to be.

At the very least you'll want to watch this video of my session at TechEd 2014 which talks about backups and how to set them up. http://channel9.msdn.com/events/TechEd/NorthAmerica/2014/DBI-B214#fbid=

Thank You,

Denny Cherry

_{Tuesday, July 5, 2016 12:46 AM | 2 votes}

Hi,

This error occurs because the transaction log becomes full due to LOG_BACKUP. Therefore, you can’t perform any action on this database, and In this case, the SQL Server Database Engine will raise a 9002 error.

To solve this issue you should do the following

• Take a Full database backup.
• Shrink the log file to reduce the physical file size.
• Create a LOG_BACKUP
• Create  Maintenance Plan to take backup logs frequently.

All details are mentioned at  The transaction log for database ‘SharePoint_Config’ is full due to LOG_BACKUP to do the above steps

Hope this help you

_{Saturday, January 7, 2017 11:11 AM}

Amazing. This solved my problem on SharePoint_Config Shrink.