Windows Event ID 7001 – Service Control Manager: Service Dependency Failure

Start by examining the service dependencies through the Windows Services console to identify the failed dependency chain.

1. Press Windows + R, type services.msc, and press Enter
2. Locate the service mentioned in the Event ID 7001 error message
3. Right-click the service and select Properties
4. Click the Dependencies tab to view required services
5. Check each dependent service listed under This service depends on the following system components
6. For each dependency, verify its status in the main Services window
7. Look for services with status Stopped or Disabled
8. Right-click any stopped dependent service and select Start
9. If a service is disabled, right-click, select Properties, change Startup type to Automatic, and click Start

Use PowerShell to get detailed service dependency information and automate the investigation process.

1. Open PowerShell as Administrator
2. Get the service details from the event log:

   Get-WinEvent -FilterHashtable @{LogName='System'; Id=7001} -MaxEvents 5 | Format-List TimeCreated, Id, LevelDisplayName, Message

3. Identify the failing service name from the event message
4. Check service dependencies:

   $serviceName = "YourServiceName"
   Get-Service -Name $serviceName -DependentServices
   Get-Service -Name $serviceName -RequiredServices

5. Check the status of all required services:

   $requiredServices = Get-Service -Name $serviceName -RequiredServices
   $requiredServices | Select-Object Name, Status, StartType

6. Start any stopped required services:

   $requiredServices | Where-Object {$_.Status -eq 'Stopped'} | Start-Service -Verbose

7. Verify the main service can now start:

   Start-Service -Name $serviceName -Verbose

Investigate service dependency configuration in the Windows Registry to identify and fix dependency issues.

1. Press Windows + R, type regedit, and press Enter
2. Navigate to HKLM\SYSTEM\CurrentControlSet\Services
3. Find the subfolder matching your service name
4. Check the DependOnService value (REG_MULTI_SZ) for the list of required services
5. Verify each listed service exists in the Services registry location
6. Check for circular dependencies by examining the DependOnService values of dependent services
7. Use PowerShell to validate registry service dependencies:

   $serviceName = "YourServiceName"
   $regPath = "HKLM:\SYSTEM\CurrentControlSet\Services\$serviceName"
   $dependencies = Get-ItemProperty -Path $regPath -Name "DependOnService" -ErrorAction SilentlyContinue
   if ($dependencies) {
       $dependencies.DependOnService | ForEach-Object {
           $depService = Get-Service -Name $_ -ErrorAction SilentlyContinue
           if ($depService) {
               Write-Output "$_ : $($depService.Status)"
           } else {
               Write-Output "$_ : SERVICE NOT FOUND"
           }
       }
   }

8. If invalid dependencies are found, backup the registry key and remove invalid entries
9. Restart the service after making registry changes

Utilize the Service Control (SC) command-line tool for detailed service dependency analysis and configuration.

1. Open Command Prompt as Administrator
2. Query service configuration:

   sc qc "ServiceName"

3. Check service dependencies:

   sc enumdepend "ServiceName"

4. Query service status and detailed information:

   sc query "ServiceName"
   sc queryex "ServiceName"

5. Check if dependent services are running:

   for /f "tokens=2" %i in ('sc enumdepend "ServiceName" ^| findstr "SERVICE_NAME"') do sc query %i

6. Attempt to start the service with verbose output:

   sc start "ServiceName"

7. If the service has configurable dependencies, modify them:

   sc config "ServiceName" depend= "Dependency1/Dependency2"

8. Use PowerShell to create a comprehensive dependency report:

   $services = Get-Service
   $dependencyReport = @()
   foreach ($service in $services) {
       $required = Get-Service -Name $service.Name -RequiredServices -ErrorAction SilentlyContinue
       if ($required) {
           $dependencyReport += [PSCustomObject]@{
               ServiceName = $service.Name
               Status = $service.Status
               RequiredServices = ($required.Name -join ", ")
               RequiredServicesStatus = ($required.Status -join ", ")
           }
       }
   }
   $dependencyReport | Where-Object {$_.RequiredServicesStatus -like "*Stopped*"} | Format-Table -AutoSize

Implement comprehensive service dependency resolution including automatic recovery configuration and system-level troubleshooting.

1. Create a PowerShell script for automated dependency resolution:

   function Resolve-ServiceDependencies {
       param([string]$ServiceName)
       
       $service = Get-Service -Name $ServiceName -ErrorAction SilentlyContinue
       if (-not $service) {
           Write-Error "Service $ServiceName not found"
           return
       }
       
       $requiredServices = Get-Service -Name $ServiceName -RequiredServices
       
       foreach ($reqService in $requiredServices) {
           if ($reqService.Status -ne 'Running') {
               Write-Output "Starting required service: $($reqService.Name)"
               try {
                   Start-Service -Name $reqService.Name -ErrorAction Stop
                   Start-Sleep -Seconds 2
               } catch {
                   Write-Error "Failed to start $($reqService.Name): $($_.Exception.Message)"
               }
           }
       }
       
       # Attempt to start the main service
       try {
           Start-Service -Name $ServiceName -ErrorAction Stop
           Write-Output "Successfully started $ServiceName"
       } catch {
           Write-Error "Failed to start $ServiceName after resolving dependencies: $($_.Exception.Message)"
       }
   }

2. Configure service recovery options:

   sc failure "ServiceName" reset= 86400 actions= restart/5000/restart/5000/restart/5000

3. Check Windows Event Log for additional error details:

   Get-WinEvent -FilterHashtable @{LogName='System'; Id=7000,7001,7009,7011,7023,7024} -MaxEvents 20 | Where-Object {$_.Message -like "*ServiceName*"} | Format-List TimeCreated, Id, LevelDisplayName, Message

4. Analyze service startup performance:

   Get-WinEvent -FilterHashtable @{LogName='System'; Id=7036} -MaxEvents 50 | Where-Object {$_.Message -like "*entered the running state*"} | Select-Object TimeCreated, @{Name='ServiceName';Expression={($_.Message -split ' ')[0]}} | Sort-Object TimeCreated -Descending

5. Create a scheduled task for automatic service monitoring:

   $action = New-ScheduledTaskAction -Execute "PowerShell.exe" -Argument "-File C:\Scripts\ServiceMonitor.ps1"
   $trigger = New-ScheduledTaskTrigger -AtStartup
   $principal = New-ScheduledTaskPrincipal -UserId "SYSTEM" -LogonType ServiceAccount
   Register-ScheduledTask -TaskName "ServiceDependencyMonitor" -Action $action -Trigger $trigger -Principal $principal

6. Implement comprehensive logging for future troubleshooting:

   Start-Transcript -Path "C:\Logs\ServiceDependency-$(Get-Date -Format 'yyyyMMdd-HHmmss').log"
   Resolve-ServiceDependencies -ServiceName "YourServiceName"
   Stop-Transcript