Timeline for Changing Diagnostic Logging Level Works Incorrectly
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 2, 2016 at 21:20 | comment | added | Denis Molodtsov | I've tried it today. It seemed to work at first. I did not see any log entries lower than medium level when playing in central administration website. However, when I've accessed the main site collection it just exploded with Verbose and VerboseEx messages. I had to stop the SharePoint Tracing service | |
| Feb 1, 2016 at 5:10 | comment | added | user6024 | Have you tried clearing the config cache (and then validating SPTimerV4 and the SharePoint Admin service are running)? | |
| Feb 1, 2016 at 3:20 | comment | added | Denis Molodtsov | I was forced to turn Tracing Service off. Otherwise SharePoint logs eat up 2-4 GB every 20 minutes. Still thinking what to do. It seems like something is wrong with the entire farm. Maybe someone changed something in the registry or something like that. | |
| Feb 1, 2016 at 3:03 | comment | added | Denis Molodtsov | Thank you, Trevor. Unfortunately even all-powerful PowerShell can't help me with this. nothing seems to work | |
| Feb 1, 2016 at 2:56 | history | answered | user6024 | CC BY-SA 3.0 |