Source

Level

Description

The <service name 1> service depends on the <service name 2> service which failed to start because of the following error: <error message>

Comments

 

It indicates the failure of a service startup due to the fact that one of the depedency did not start. This event can occur for potentially any service or application. Before any other troubleshooting attempt, please verify that the service listed as dependency is started. If it is not, first take care of that problem - there may be other events related to that service.

See ME274814 and ME285173 for more details.

Service 2:  Microsoft Forefront TMG Control - See ME2659700.

Service 1: World Wide Web Publishing Service, service 2: HTTP SSL, error: "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it." - Enable ( change to manual/automatic) required service in dependencies and start it.

- Service 2: Info Sentinel, error message: "The dependency service or group failed to start" - See "Business Objects Support Article ID: c2006555".
- Service 2: NetBIOS over TCP/IP, error message: "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it" - See WITP76126.
- Service 2: CIO Array Management Service, error message: "After starting, the service hung in the start-pending state" - See "Adaptec Support Answer ID: 5227".
- Service 2: WINS Client (TCP/IP), error message: "A device attached to the system is not functioning" - See ME183901.
- Service 2: Trend ServerProtect Filter, error message: "The dependency service or group failed to start" - See "Trend Micro Support Solution ID: 20348".
- Service 2: Protected Storage, error message: "The system cannot find the path specified" - See ME189649 and ME249023.
- Service 2: NetBEUI protocol, error message: "The system cannot find the file specified" - See ME193840 and WITP72137.
- Service 2: IIS Admin Service, error message: "The system cannot find the file specified" - See ME332103.
- Service 2: IIS Admin Service, error message: "The dependency service or group failed to start" - See ME189649 and ME249023.
- Service 2: IIS Admin Service, error message: "The executable program that this service is configured to run in does not implement the service" - See ME922729.
- Service 2: RAS Connection Manager - See ME248639.
- Service 2: Microsoft Exchange System Attendant, error message: "Access is denied" - See ME312417.
- Service 2: Microsoft ISA Server Control, error message: "The service did not respond to the start or control request in a timely fashion" - See ME838857.
- Service 2: RIP for Nwlink IPX, error message: "The parameter is incorrect" - See ME165941.
- Service 2: Server, error message: "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it" - See ME312945 and the link to "Symantec Knowledge Base Document ID: 2003040408054454".
- Service 2: Server, error message: "After starting, the service hung in a start-pending state" - See ME319127.

- Service 2: SYMTDI - Symtdi.sys, a Symantec related file, registers itself as a dependency of DHCP. If it fails, it will cause DHCP and other services to fail. This problem may occur after uninstalling Norton Antivirus. A manual edit of the registy may be necessary to fix this problem. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DHCP\DependOnService and remove only the SYMTDI section. Reboot when finished.

- Service 2: WINS Client(TCP/IP), error message: "A device attached to the system is not functioning" - See ME250262.
- Service 2: NetBIOS, error message: "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it" - See ME278658.
- Service 2: Microsoft Exchange System Attendant, error message: "%%0" - See ME274447, ME290542, and ME316710.
- Service 2: Microsoft Exchange Directory, error message: "The dependency service or group failed to start" - See ME260698.
- Service 2: Microsoft Exchange Information Store, error message: "The dependency service or group failed to start" - See ME316710.
- Service 2: <snalink>, error message: " The dependency service or group failed to start" - See ME110582.
- Service 2: MUP, error message: "An instance of the service is already running" - See ME136934.
- Service 2: IBMSYNC, error message: "A device attached to the system is not functioning" - See ME149706.
- Service 2: server, error message: "Not enough server storage is available to process this command" - See ME151427 and ME180140.
- Service 2: server, error message: "A device attached to the system is not functioning" - See ME231604 and ME234636.
- Service 2: Workstation, error message: "A duplicate name exists on the network" - See ME317140.
- Service 2: Workstation - See ME887416.
- Service 2: SAP Agent, error message: "The specified service could not start" - See ME157363.
- Service 2: Netlogon, error message: " The service has returned a service-specific error code" - See ME164130.
- Service 2: Workstation, error message: " A duplicate name exists on the network" - See ME166184 and ME317140.
- Service 2: Remote Access Connection Manager, error message: "The service has returned a service specific error code" - See ME168683.
- Service 2: Server, error message: "More data is available" - See ME175529.
- Service 2: IIS Admin Service, error message: "The dependency service does not exist or has been marked for deletion" - See ME189649, ME218458, ME249023.
- Service 2: Microsoft Exchange Information Store, error message: "The dependency service or group failed to start" - See ME260698.
- Service 2: Microsoft Exchange Directory, error message: "The dependency service or group failed to start" - See ME260698.
- Service 2: Microsoft Exchange System Attendant, error message: "The dependency service or group failed to start" - See ME260698.
- Service 2: MUP, error message: "An instance of the service is already running" - See ME266208.
- Service 2: TCP/IP Service, error message: "The specified service is disabled and cannot be started" - See ME167093.
- Service 2: MSSQL$BKUPEXEC, error message: "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it" - See "Veritas Support Document ID: 256189" and "Veritas Support Document ID: 257064".
- Service 2: Backup Exec Device & Media Service - See "Veritas Support Document ID: 242522" and "Veritas Support Document ID: 271405".
- Service 2: ISA Server Network Address Translation (NAT) Driver - See ME888854.
- Service 2: MSSQLServer - See ME188685.
See MSW2KDB for additional information on this error.

- Service 2: ISA Server Packet Filter Extension Driver, error message: "This driver has been blocked from loading" - This event is seen along with Event ID 876 & Event ID 7000. When you install ISA 2000 on Windows Server 2003, it automatically blocks this driver from loading. To resolve this, install ISA SP# 2 along with "ISA Server 2000: Required Updates for Windows Server 2003". See ME555428 for more details.

I had the problem and found out that the exchange server could not see the Schema master. To fix the problem check that the FSMO roles are correct and viewable from all domain controllers.

Service 1: Sentinel, Service 2: Parport - See HP document EM020214_CW01.

Service 1: "Remote Access Connection Manager", Service 2: "Telephony", error message: "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it." - The event occurred after disabling the Telephone service. Re-enable the service to avoid the error.