Many friends often ask IIS's problems, such as refusing service, 500 errors, etc., there are also many friends who are enthusiastic to answer these questions: "Restart the server; reload IIS; reload system ....".
So how do you solve the key to the IIS problem?
According to I summarize, there are 5 points:
1. View log events, most errors will have records, and you can find the root of events through the log. 2, good use of tools, such as Filemon, can detect most of the permissions. IISSTATE, used to debug IIS. 3. For the problem of the site, you can use Performance Monitor to monitor, performance Monitor provides relevant counters for ASP / ASP.NET, you can check the memory leaks, CPU bottlenecks, etc. 4, good use of KB, this is not to say more, most questions can be found, but you have to look at your E text. 5, update the patch. Another point is not a problem, it is not resolved, but we didn't find a solution, I think it is not good for the IIS designer complaint. In fact, most IIS issues are caused by improper use of users themselves.
