My main file server has been happily chugging along for two years, it's a VM Windows Server 2008 R2-Enterprise machine. We do use the File Server Resource manager function to prevent executables from being saved in the data volumes, but I do not do quotas, reports, etc. on the server at all.
All of a sudden, yesterday, the File Server Storage Reports manager has begun to eat every available byte of RAM and put pressure on the dynamic memory of the machine to hit the wall on memory. It usually sits at around 6GB running, and this process alone has consumed 9GB making the server hit its max demand at 12GB. It's slowed to a crawl for everything, even bringing up the services MMC took 4 minutes to launch! The server is as plain as it gets, files, printers and logon. I've killed the service, but is it actually necessary for File Screening to function, or is it just for reporting? I could care less about reporting and so could disable this service, but if I need it for screening I'd need to fix whatever it is that's causing it to go haywire. Even as we speak it's climbed back to 1GB RAM and going up fast, stopping the service frees up the memory, but it fires right back up and starts eating memory again.
Does anyone know what could cause this, and better yet how to make it stop? If it's not needed I can disable it, but I hate that that would be 'the fix' (not elegant :-) ).
Curt Kessler - FLC