Skip to main content

Disable logging in WSS 3.0

After a server failure I discovered that Windows Sharepoint Services was creating gigabytes of log files where after our server died with a ‘no more disk space’ error.

WSS V3 out of the box has extensive logging activity, Logs can be usually found in this directory  C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS

If you are running WSS V3, you can disable logging activity by doing the following:

  • Go to WSS V3 Central Administration -> Operations -> Logging and Reporting

  • Click on Diagnostic Logging

    1. Customer Experience Improvement Program: select No, I don't wish to participate

    2. Error Reports: select Ignore errors and don't collect information.

    3. Trace log: clear the entire Path.

    4. Click OK

  • Click on Usage Analysis Processing

    1. Uncheck Enable logging

    2. Click OK

  • Click on Information Management Policy Usage Reports

    1. Uncheck Enable recurring policy usage reports

Please remember that once you have disabled logging it will be impossible to troubleshoot any WSS errors.

    Popular posts from this blog

    Azure DevOps/ GitHub emoji

    I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

    Podman– Command execution failed with exit code 125

    After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

    Cleaner switch expressions with pattern matching in C#

    Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...