We just upgraded a standalone ArcGIS Server instance from 11.3 to 11.5 and it started raising hundreds of warnings "Error in checking static data for service: xyzxyzx - Service not found." In some cases it's raising 15 warnings every minute, but in all it's flushing out our logs and consuming memory resources. Typically it will spend ~ 1 hour logging these messages and simply stop. The thing is, these are all old services that have been deleted. I've verified that none of the server directories have orphaned entries. Preceding many of these incidents, Server will log a message "checking for expired items in D:\arcgisserver\directories\arcgisoutput" or "checking for expired items in D:\arcgisserver\directories\arcgissystem\arcgisuploads."
This behavior first arose following an in-place upgrade from 11.3 to 11.5 and we noticed this before I applied any Server security patches (but subsequent application has not improved that behavior). The machine is running in Windows Server 2022 Datacenter, IIS Web Adaptor, and alongside a PostgreSQL 16.8 EGDB. This instance of Server is not federated with any Portal. A similar upgrade to a dev ArcGIS Server instance has not raised the same warnings.
I commented in this thread that these issues seem similar, but ours arose prior to applying the Security 2026 Update 2 patch: https://community.esri.com/t5/arcgis-enterprise-questions/portal-for-arcgis-security-2026-update-2-p...
Did you checked the following directory to confirm if the old service folders still exists or not
D:\arcgisserver\directories\arcgisoutput
D:\arcgisserver\directories\arcgissystem\arcgisuploads
Additionally, Check for Orphaned Configuration Files in D:\arcgisserver\config-store\services, ensure there are no leftover .json files for deleted services.
If you find any, back them up and then remove them.
As I mentioned in my post we did verify that there are no folders for these old services anywhere in D:\arcgisserver\... . My assumption is that there is internal content elsewhere triggering these warnings, but whether it's readable/editable as plaintext I don't know. I also verified that a robots.txt is in place at the IIS root to dissuade web crawlers from hitting endpoints for old services.