SEVERE errors in Server

Question

My instance of Server 11.2 running on Windows Server 2019 logs these error messages periodically. This is from the "server" log file. Response already committed. Cannot forward to error page. Response already committed. Cannot forward to error page. This exception was thrown after the response was committed. Access to this resource is not allowed RHandler is null, Access to this resource is not allowed Response already committed. Cannot forward to error page. I turned up the log level to INFO from the default of WARNING. Now I can see normal requests coming through too so it's not as dismal (opening a log and seeing it packed with a continuous stream of SEVERE errors is disturbing.) I have looked at the 'code' field, it's described here: https://enterprise.arcgis.com/en/server/latest/administer/windows/core-server-log-codes.htm and it's the same as the text in the log, for example, code 9001 means "Response already committed. Cannot forward to error page." There is no further information. The "INFO" level message shown above is interesting too, it's a code 9000 "Internal Server Error" even though it's only logged as an INFO (information only message) it appears to be an error. Does anyone know what an "RHandler" is?? I spent a few hours trying to correlate the IIS log file with the ArcGIS Server server log file but nothing popped out, I don't think the errors are tied to any particular service, they just "happen" from time to time. I am looking for suggestions on how to chase this down and fix it. Over the years each time we do something like upgrade the OS, move Server to a separate VM, add memory, migrate to a new release, etc etc, nothing has changed, we still get these errors. (I live in hope, ever) Like the "boy who cried wolf", when we see SEVERE messages now, we have learned to shrug them off, "that's normal!" I am always afraid we'll miss something buried in the noise. Happy Wednesday all! --Brian

AnibalMmartinez · Answer

Hola, tengo el mismo problema, sobre ArcGis Server 11.1 , y no encuentro nada sobre

* Defect: ENH-000156901

Lo habrán desestimado?, la verdad que estaría bueno que sume alguna información para orientar a que se debe.

Saludos,

Anibal

NickN · Answer

I also get these errors on an 11.1 deployment. There's also another thread with other severe errors that has been going on since 2021 (i'm sure there are other threads too) that are unaddressed.

The annoying part is how these show up in ArcGIS Monitor under the Failed Requests. All of a sudden you'll have 10 or so failed requests popup on the graph...you go to investigate and see it's this or that error in the other thread. Makes this a "Boy Who Cried Wolf" metric and virtually useless for monitoring for actual severe issues.

Server logs definitely need some kind of overhaul.

AmandaBrown · Answer

We have this issue with one of our servers. We are on 10.9.1 with Windows Server 2022.

We migrated to 10.9.1 a month-ish ago and have had these errors since.  Our environment is brand new and we have also noticed the same error popping up.

We are currently troubleshooting these errors. Performance for all our services seem to be okay. I'm definitely keen to watch any progress on this and will try to add anything I learn here also.