Hi there. This post was actually sleeping in my draft folder for a long that I finally decided to finalize and post it ASAP before it gets completely outdated.
On WSS3/MOSS 207, the SPAdmin Service (Windows SharePoint Services Administration, process WSSADMIN.EXE) is logging its activity out to the file WSS_AdminService.log located under C:Documents and SettingsDefault UserLocal SettingsTemp (Server 2003) or C:UsersDefault UserLocal Settings (Server 2008 and beyond).
Apparently there is no limit to its expansion so don’t be surprised if its size goes well beyond 1 GB over time.
It is solely used for internal tracing and there is no clean nor supported way for controlling it (disabling, limiting its size…) like you would do for Diagnostics or Usage Logs.
There are 2 dirty (although working) ways to prevent SPAdmin service from writing out to disk:
- Setting the read-only attribute on the file: attrib +r “C:Documents and SettingsDefault UserLocal SettingsTempWSS_AdminService.log”
- Denying access to the Local System account:
icacls “C:Documents and SettingsDefault UserLocal SettingsTempWSS_AdminService.log” /deny “NT AUTHORITYSYSTEM”:F
I have seen on some blogs that you could configure a user profile to that service by changing the account that is running it and therefore grant you the flexibility to redirect the profile to another partition. From the informal conversations I had with MS support, this would void supportability since the SPAdmin service is meant to run exclusively under Local System .
If you wish to keep it while managing its size, you can set-up a scheduled task that would delete the file if it goes beyond a certain size, taking care of archiving it as necessary. BTW, the service does not set an exclusive lock on the file permanently so as long as it does not write to it, there is nothing preventing its deletion.
Finally, you can also enable the compression on that file (log files usually shrink well, expect a 5 to 1 ratio): compact /c “C:Documents and SettingsDefault UserLocal SettingsTempWSS_AdminService.log”
I will later post a PoSH script to tidy up the log file and running as schedule task.