Hi Rick, This problem just cropped up.

I've included a couple of screen shots here: Request Log: Module Log:

My Request Log is showing the request hitting the server, but the module log just shows process is shut down, and doesn't seem to show the request, or be in sync with the request log. The symptom is that nothing happens after the request hits the server, not sure why. I'd greatly appreciate your help. Could a new installation of Bit Defender on the server cause this?

Years ago I installed Bit Defender on my PC and did it ever eat up performance with its constant real-time scanning. I uninstalled it.

I asked Gemini this: 'bit defender on iis server causes problems' and it came back with more than I can paste in here, but here's some of it:

Bitdefender can cause issues on an Internet Information Services (IIS) server, primarily through its real-time scanning, firewall, and network protection modules. These components can interfere with how IIS processes and serves web content, leading to performance degradation, connection failures, or blocked services.

The most common problems and their solutions typically involve configuring exclusions in Bitdefender.

There's no such thing as server is shut down in COM mode - any request will restart the server. The log shows shut downs, but it doesn't show startups unless you enabled the verbose detailed log mode.

If you want to stop requests from going through you'll have to stop the Application Pool, or switch into file based mode and then kill all instances.

In COM mode there's no 'off-switch'.

You can put the server into maintenance mode which disables all but administrator traffic. If this is for admin tasks, you can put the server into single instance mode so you can get EXCLUSIVE access to data so you can do operations like PACK and REINDEX etc. all on the Admin page.

+++ Rick ---

Thanks Rick, I'll get the infrastructure contractors (the server is onsite) to create the exclusions, I've managed to resolve it by adjusting my code. This one was definitely a coding error on my part, all my testing had been on my server and I had neglected to update the live server data with a couple of key field UUIDs, after I did that everything works well. Good tip on Bit Defender, do you have any thoughts on what processes I should get the infrastructure guys to exclude? If not, I can ask them to do some analysis and determine the needed exclusions. As always, greatly appreciate your help!

Thanks, that's good to know.