IIS 1068 dependent service or group failed to start the workaround

You are experiencing problems with IIS 1068 dependent services or groups that cannot be started today. Search a press to solve the problem

The original text is as follows
------------------------

Once site access failed and the IIS service failed to start, my solution was this:

Open Administrative tools --> service First and discover world  The wide web publishing service stopped. Then try to start the service, the results of the error, the same situation as you. The

then looks at the service (dependencies) that world wide web publishing services needs to rely on and sees the Iis admin  service. Further found that Iis admin service also can not start, and then check iis admin service dependencies, the results of the investigation is protected  Storage and RPC (Remote procedure call), start RPC, then start iis admin service smoothly, then start world wide  web publishing services, so IIS is back to normal.

Reviews:

(1) View the status of the service and the status of the other services it depends on, which is very basic, but many people get used to the problem of reloading, in fact, or should learn to rational analysis. According to my experience I think the reason for the landlord is probably the same as mine, so in this case, reloading IIS will not have a good result.

(2) Under what circumstances will the RPC stop. In addition to the artificial stop, only in two cases: A, the system is severely damaged, B, some software may affect the RPC service. Please pay particular attention to do not install a personal version of the firewall on the server, because the personal version of the firewall and the server version of the firewall security policy, I have found that the personal version of the firewall initiative to terminate the user's RPC service, because for the individual users of the PRC service is basically harmful and useless, but for the server, RPC is almost a service that can not be opened, only by actually improving the overall security of the system to offset the hidden dangers of RPC. However, the reasons why RPC and some system services are stopped are sometimes not very well judged in practice, and are analyzed by more efficient means such as analyzing the system log.