#Windows server 2008 security authorization manager driver
If you look back at the figure above, you will notice that there is a plus sign to the left of the listings for the Base Filtering Engine service and the Windows Firewall Authorization Driver service. One thing that is important to keep in mind as you troubleshoot service dependencies is that sometimes the dependencies can form a multilevel hierarchy. You can also see that there are no services that directly depend on the Windows Firewall service.įigure A: Sometimes the failure of a dependency service may prevent a service from starting.
In this particular screen capture you can see that the Windows Firewall service cannot start unless the Base Filtering Engine and the Windows Firewall Authorization Driver have started. The bottom portion of the tab lists services that cannot be started until the selected service is running. The top portion lists the services that must be running in order for the service that you have selected to start. The Dependencies tab is divided into two sections. When you do, Windows will display the service’s properties sheet.Īs you can see in Figure A, this properties sheet contains a Dependencies tab. To check service dependencies, open the Service Control Manager, right click on the service that you are having trouble starting, and select the Properties command from the resulting shortcut menu. In the old days it was really tough to track down problems with dependency services, but most of the newer versions of Windows make it easy. Granted, not all services have dependencies associated with them, but dependency services are common enough that they certainly warrant a look if you are having trouble starting a service. Services can sometimes form a hierarchical architecture in which other services must be running in order for a service to start.
Sometimes a service may fail to start due to a problem with a dependency.
0 kommentar(er)
