In our case, the issue was caused by the AppPools setting 'Maximum Worker Processes' to 0.
By default, this should be set to 1 to prevent opening new server processes with new sessions based on the current load.