Toolset_BusinessLayerPlugin_tracelog.svclog

Found this log file taking up around 8GB of disk space! Couldn't delete it, couldn't clear it, couldn't rename it, the usual symptoms of a file lock. I couldn't stop SW services without a change/outage etc, but I found out which service was locking it: SolarWinds Orion Module Engine. When I stopped that I was able to clear it. Then before starting that service again, you want to make sure that the config file for the toolset logger is set to False otherwise that file will just continue to grow. Keep in mind that "logadjuster" (the one without the space) doesn't seem to work for this.

Steps to disable logging for C:\temp\Toolset_BusinessLayerPlugin_tracelog.svclog for good:

stop the solarwinds orion module engine service

open a notepad as admin

open "C:\Program Files (x86)\SolarWinds\Orion\Toolset\SolarWinds.Toolset.BusinessLayer.dll.config"

Find the "<system.diagnostics>" stanza such as the example below

Ensure the two "switchValue" fields are set "Off"

save the config file and close notepad

open a powershell prompt and run "clear-content "C:\Program Files (x86)\SolarWinds\Orion\Toolset\SolarWinds.Toolset.BusinessLayer.dll.config"" which should zero out the file

start the solarwinds orion module engine service and that log should stay at 0KB

<system.diagnostics>    <sources>      <source name="System.ServiceModel" switchValue="Off">        <listeners>          <add type="System.Diagnostics.DefaultTraceListener" name="Default">            <filter type="" />          </add>          <add name="ServiceModelTraceListener">            <filter type="" />          </add>        </listeners>      </source>      <source name="System.ServiceModel.MessageLogging" switchValue="Off">        <listeners>          <add type="System.Diagnostics.DefaultTraceListener" name="Default">            <filter type="" />          </add>          <add name="ServiceModelMessageLoggingListener">            <filter type="" />          </add>        </listeners>

Find more posts tagged with

log files

Accepted answers

All comments

jagordon

Thank you for this - it goes even a step further than the official support document on this topic - which did not help me, due to it apparently being incomplete. (Located here) C:/temp contains a large file that increases - Toolset_BusinessLayerPlugin_tracelog.svclog - SolarWinds Worldwide, LLC. …

Just to note, I had an additional circumstance that took an additional step. I noticed the PowerShell command outlined above did not work in my environment. No error message was given when I tried, it just didn't zero out the log file as I expected. With the SolarWinds Orion Module Engine stopped again, I was able to manually delete the log file. When I restarted the service, the log file was recreated, and started climbing in size again after a bit. I remembered that due to a different issue, a few weeks prior, Solarwinds Support had been poking around the server with the Solarwinds LogAdjuster tool. (C:\Program Files (x86)\SolarWinds\Orion) I opened that up, scrolled down to the Toolset section, and "Business Layer" was set to TRACE. So I dropped that down to WARN, hit Apply, and it appears that the log has stopped growing.

govitallen

Oops, I copied and pasted your powershell command:

ryan.davis26 wrote:
open a powershell prompt and run "clear-content "C:\Program Files (x86)\SolarWinds\Orion\Toolset\SolarWinds.Toolset.BusinessLayer.dll.config""

I think that should have been

"clear-content "C:\temp\Toolset_BusinessLayerPlugin_tracelog.svclog"" !

Well, I must admit that stopped the log file from growing and I was able to delete it.

stevenstadel

Thanks ryan.davis26 for your work with this issue! Solved my issue.

Can you please edit your instructions to backup the C:\Program Files (x86)\SolarWinds\Orion\Toolset\SolarWinds.Toolset.BusinessLayer.dll.config file before changing?

Also please change

open a powershell prompt and run "clear-content "C:\Program Files (x86)\SolarWinds\Orion\Toolset\SolarWinds.Toolset.BusinessLayer.dll.config"

open a powershell prompt and run "clear-content "C:\temp\Toolset_BusinessLayerPlugin_tracelog.svclog"

Doing the former will zero out the config file that was just changed and when you restart the service there will be issues. (Editing a user on the website will throw an error for instance)

Thanks

Steve