We have a network with the following servers:
1- Windows Server 2003 Domain controller with the following servers on it: -SQL Server 2005, WSUS 3.0.
2-Windows Server 2003 with Sharepoint Services 3.0 on it.
3- Windows Server 2003 with ISA Server 2006 on it.
4- Windows Server 2003 with Exchange server 2007 on it.
This morning we found out that there was 0 bytes left on the C drive of server 1 the domain controller and low diskspace on server 2 the sharepoint server.
I opened the the event viewer on the domain controller and i find a lot of errors coming from the sql server that saying that the transaction log for the SharePoint_Config database is full.
I did a search on the server and i found that the Sharepoint_Config_log.LDF is the largest file on the server with a size larger that 6GB!!
I also did a search on the sharepoint server and i found about five log files that were larger than 4GB under the following path:
c:\Program Files\Common Files\ Microsoft Shared\Web Server Extentions\12\LOGS
What is the problem and how do i fix it?
Thanks
That set up doesn't look, to me very much like a "home or personal" system.
This forum is focussed on the needs of folks who have problems with home or personal set ups rather than business requirements.
please check out the forums "Terms of Use" particularly:
We offer free computer help and tech support for home and personal use. We are not here to support others that work for profit, or to support/replace your company's IT department.
If I have misinterpreted the situation please post back with details.
Regards
paws
Hi,
Honestly it's not for home or personal use but it isn't for profit either i work at a charity foundation… so if that qualifies then great if not then i'm sorry and it won't happen again.
I would like to believe that Charity would apply… but maybe forum mods differ in opinons there.
Regardless it looks your log files need clean-up a bit
It is, usualy, possible to clear them w/o a too much fuzz and also setup them that way they limit their size to certain value. My logs do not ever exceed 64k - the lowest Win2k settings, but Win2003 might differ a bit. Ragardless - 6G log file? Too much.
Second to that, I would take a look what caused this in the first place. Or if that was just gradual increase of the log size, till it hit the drive capacity limits - you can usualy easily determine that from the events in the log - eg. if the oldest event are like year old and there is like 1000 events per day, then it is okay. If most of the events in that log (like 20, 30 or even more %) are from the last day - then something way deeper went wrong.
Or perhaps someone code is acting up?
✨ Ask AI
AI can make mistakes. Check the cited posts. Archived advice can be out-of-date
Don't include personal information. Questions and selected public posts go to OpenAI. About Ask AI