Jan 08
Troubleshooting SharePoint Diagnostics Logging
Sebastian Atar
I'm in my second year with C/D/H and look forward to using my 10+ years of IT experience, along with my MBA background in finance and lean operations to solve business problems.
Most recently, this has involved using Microsoft Office SharePoint Server to enable collaboration and sharing of information, as well as Novell Identity Manager to simplify management of user accounts.
When not working, I enjoy spending time with my wife and son. We love visiting family in Seattle and New York. When not traveling, we pass time reading, gardening and BBQ-ing with family.
More about Sebastian
Articles by Sebastian Atar
One of my clients called the other day with a SharePoint logging problem. Her server(s) were creating blank log files, 0KB in size without any errors or apparent issue.
I started with some basics:
1) Is there adequate disk space on the server(s)?
2) Is the “Windows SharePoint Timer Service” running?
I then restarted the timer service to ensure that the credentials were still valid. But that didn’t help.
Next, I wanted to validate what my logging levels were set to, so I ran the following STSADM command:
stsadm -o listlogginglevels
This revealed that everything was set to “None” from the original defaults.
I next ran the following command to reset values to defaults:
stsadm -o setlogginglevel -default
That did it!