On the first day of work, I heard the test server was hung up. Take a look at the IIS logs, we've been in charge of several applications that have been hanging out for half a month. How can there be such a thing--!
Problem Description:
Run the program while the application pool is open, but the application pool is automatically stopped
Analysis of background reasons:
A new SharePoint project started by the leader to borrow this server to the development team if the server is not available.
From the error point of view, it seems that there is no relationship with SharePoint, that is, someone modified the configuration.
There are many posts on the Internet to resolve this issue, but the cause of the problem is different. Various Balabala. Or a targeted solution to their own problems.
Finally, the workaround is as follows under IIS error ID 2282:
For an IIS application pool that is faulted, set the following: Right-click Advanced, enable 32bit mode->false
But again the problem arises: some programs that need to be compatible with 32-bit systems are reported as abnormal after this setup. The only solution is to be compatible with 32-bit systems.
The ultimate Solution:
This issue has been fixed by modifying applicationhost.config.
The following modification commands are run:
"%systemroot%\system32\inetsrv\appcmd.exe" set config-section: System.webserver/globalmodules/[ Name= ' Spnativerequestmodule '].precondition:integratedmode,bitness64
Problem solved.
IIS7 503 Error Service unavailable