Hi Rick,
I was poking around at my app logging on my 2 production app servers today and also took a peek at wcerrors. To my surprise, on one server the file was over 6GB. On the other, it was 500k. I took that first server out of rotation, rebooted, and as soon as I put it back in rotation, wcerrors started growing rapidly again. It's up to 5.5MB in the hour or so since I restarted. Nothing in the log appears to be an error. Here are a few lines:
2026-01-29 10:58:35.799 - 1115799723132_13 - Starting Request - /login.usm - usr: rfcadmin / - iis: /LM/W3SVC/2/ROOT
2026-01-29 10:58:35.799 - 1115799723132_13 - Retrieving Server Instance - /login.usm - usr: rfcadmin / - iis: /LM/W3SVC/2/ROOT
2026-01-29 10:58:35.799 - 1115799723132_13 - GetServer() entered - /login.usm - usr: rfcadmin / - iis: /LM/W3SVC/2/ROOT
2026-01-29 10:58:35.799 - 1115799723132_13 - Server COM Instance retrieved: #1 - /login.usm - usr: rfcadmin / - iis: /LM/W3SVC/2/ROOT
2026-01-29 10:58:35.799 - 1115799723132_13 - Com Server ProcessHit Start - /login.usm - usr: rfcadmin / - iis: /LM/W3SVC/2/ROOT
I checked the INIs and both servers are configured identically as far as logging level is concerned. As best I can tell, my app is perfectly happy but seeing this logging on what appears to be practically every hit is making me a little queasy.
Thoughts?
I found it. LogDetail in web.config was set to true on that server. Not sure how that got that way but in the immortal words of Emily Litella, "Never mind."
Yup - Log Detailed Errors is a debugging feature and it generates a lot of data. It can be useful if you're trying to track down problems, but actually has a negative performance impact due to the frequent log writing and blocking while trying to access the log file.
So yeah - turn off in production unless you're trying to debug a problem...
+++ Rick ---