Internal tracing functions are being called when tracing is turned off. This creates unnecessary processing and overhead, which can lead to slow performance. 

All

The workaround for this issue is to change the Reporting Server trace settings, disabling all trace components. 

To implement the workaround, go to the Reporting Server Console. 

Go to "Workspace", expand "Logs and Traces" in the left pane, then right-click "Traces" and click "Configure".

Then in the center pane, click the drop down for "Choose the trace components to activate" and click "Custom Components"

To disable all trace components, Click the check box to the left of "Category/Title" twice. The first click will enable all componentes, and the second click will disable all components. 

If you are not able to restart the Reporting Server immediately, then click the "Save" button in the lower right corner.

If you are able to restart the Reporting Server immediatley, then click "Save and Restart Server"

Note: If capturing traces is needed to debug an issue with Customer Support, it will be necessary to re-enable Default trace components, reproduce the issue with traces on, capture diagnostics (savediag), and then disable all trace components again. 

Performance on WebFOCUS Reporting Servers, and Data Migrator Servers may be slow compared to previous releases.