Sharepoint 2016 - high trace log load after october updates
Hi experts.
Are you administering Sharepoint 2016 on premises? And you have already installed the Sharepoint updates for october 2020? Then please do me a favor and verify whether your sharepoint tracing service (wsstracing.exe) is consuming a whole CPU core for you as well.
We run Sharepoint 2016 on two systems and haven't changed anything but those updates and ever since, that service is running wild. Anything else works as expected, all tests that we run came back normal.
If you have general advice about sharepoint, please hold it since I am only interested in confirmation.
For a test, I have reduced the log level to errors and critical message and immediately, the load went back to normal.
Are you administering Sharepoint 2016 on premises? And you have already installed the Sharepoint updates for october 2020? Then please do me a favor and verify whether your sharepoint tracing service (wsstracing.exe) is consuming a whole CPU core for you as well.
We run Sharepoint 2016 on two systems and haven't changed anything but those updates and ever since, that service is running wild. Anything else works as expected, all tests that we run came back normal.
If you have general advice about sharepoint, please hold it since I am only interested in confirmation.
For a test, I have reduced the log level to errors and critical message and immediately, the load went back to normal.
Since you use on-premise, any issues using 'Open with Windows' explorer since the October update? It quit working for us after the update.
Danke
Danke
ASKER
Hi.
No issues with "open in explorer" here on these two servers.
May I ask how is the CPU load for that process for you? For us, it equals a whole core. And, more importantly, is your logging setting still at defaults?
Thank you
No issues with "open in explorer" here on these two servers.
May I ask how is the CPU load for that process for you? For us, it equals a whole core. And, more importantly, is your logging setting still at defaults?
Thank you
ASKER
Walter, maybe you missed my response and follow-up question?
Sorry, been swamped. Here is what I have:
APP01 wsstracing.exe PID:2120 Threads:9 CPU:0 AverageCPU:0
APP01 wsstracing.exe PID:20840 Threads:9 CPU:0 AverageCPU:0
WEB01 wsstracing.exe PID:2145 Threads:9 CPU:0 AverageCPU:0
WEB02 wsstracing.exe PID:4164 Threads:9 CPU:0 AverageCPU:0
Logging is set to default.
Hope that helps...
APP01 wsstracing.exe PID:2120 Threads:9 CPU:0 AverageCPU:0
APP01 wsstracing.exe PID:20840 Threads:9 CPU:0 AverageCPU:0
WEB01 wsstracing.exe PID:2145 Threads:9 CPU:0 AverageCPU:0
WEB02 wsstracing.exe PID:4164 Threads:9 CPU:0 AverageCPU:0
Logging is set to default.
Hope that helps...
ASKER
Interesting, thank you. So we will take a closer look at what's being logged now.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You're welcome. Wish I could have helped more.
Hope that helps...