Microsoft is now offering SharePoint Designer 2007 for free!
Jan 262009
I am willing to bet that not too many people run into this issue, but it is still good to know. On, my client’s web server began to stall due to a full C: drive. Their server is an economy model and the C: drive is only 16GB. After some quick investigation, I found that 3.5GB were being used in the C:Program FilesCommon FilesMicrosoft Sharedweb server extensions12LOGS folder. This is the default location for the trace log. The path must exist on all servers in the farm, too. I decided to turn down the logging, at least temporarily, to get the server running again. To complete this task, I took the following steps:
- Navigate to SharePoint Central Administration
- Click Operations
- Click Diagnostic Logging
- Scroll to the bottom of the page to the Trace Log section
- Change Number of log files to 1
- Change Number of minutes to use a log file to 5
My client’s server is back up and running again, and I should not have to worry about the Trace Log getting out of control again.
The downside is that my Trace Log only goes back to the last 5 minutes of work on the server. I am researching my options here. It may not be important enough though.
Nov 212008
While I am in the blogging mood today, I thought I would share a very helpful link. I was trying to figure out the proper way to retrieve the latest recurring events based on the current month. I Googled around for a bit before stumbling upon this:
The key point is the query used:
SPQuery query = new SPQuery();
query.ExpandRecurrence = true;
query.Query =
"<Where>" +
"<DateRangesOverlap>" +
"<FieldRef Name='EventDate' />" +
"<FieldRef Name='EndDate' />" +
"<FieldRef Name='RecurrenceID' />" +
"<Value Type='DateTime'><Month /></Value>" +
"</DateRangesOverlap>" +
"</Where>";
// Look forward from the beginning of the current month
query.CalendarDate = new DateTime(DateTime.Now.Year, DateTime.Now.Month, 1);
Preface
My current day job is developing SharePoint-based web applications. On Thursday, September 11 (coincidence), the SharePoint site became unresponsive. It was not storing any new data, but viewing existing data was still possible. This was important as I have end-users that rely on reports stored in Document Libraries. The daily reports would not save onto the website.
I’m sure that this article is SQL Server Administration 101 for most folks. For those diving into SharePoint with no DBA, this could be a lifesaver.
Table of Contents
Chapter 1: Transaction Log Deletion – what happens when I lost the WSS_Content transaction log
Chapter 2: The Recovery – the steps to recovering the corrupt MDF file
Chapter 3: Prevention – best practices for database and transaction log backup and truncation