Public Service Announcement Enabling Trace Logging (on User Account) can make things go BOOM

Someone had enabled Trace logging in one of our users probably to capture / troubleshoot an issue a few years ago.

Turns out the Epicor client doesn’t automatically clean those Trace Files. This morning one of our users was getting a weird error in Epicor

After much troubleshooting we remoted into her computer to see her C: drive was 100% full
HardDrive Full:

That’s right she had 172GB worth of Traces in her hard drive :man_facepalming:

Found a few more

SELECT * FROM ice.UserTracing
WHERE DataTrace=1
3 Likes

Do I smell an Epicor Idea? Either a warning message when the user logs in letting them know that Tracing is enabled? And/Or possibly a clean-up process or a file size limit that you can set?

We had something similar happen once too… ARGH! :roll_eyes:

There should be an upper limit of maybe 10GB worth of Logs I would expect. I’ll write it up, though frankly with Kineitc UX it won’t be necessary any more. So never mind , I won’t waste my breath

I thought there was a way to prohibit users from accidently turning tracing on.