Event ID 7033 — Basic Service Control Manager Operations

Event ID 7033 — Basic Service Control Manager Operations

Updated: December 11, 2007

Applies To: Windows Server 2008

The basic operations that Service Control Manager (SCM) performs include managing the services and driver services that allow the operating system to start successfully, and reporting when one of these services or driver services fail during system startup. These operations are not associated with any particular service.

Event Details

Product: Windows Operating System
ID: 7033
Source: Service Control Manager
Version: 6.0
Symbolic Name: EVENT_SERVICE_SCESRV_FAILED
Message: The Service Control Manager did not initialize successfully. The security configuration server (scesrv.dll) failed to initialize with error %1. The system is restarting…

Resolve
Perform a system backup and restart the computer

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To resolve this issue:

  1. Make a backup of your data, if needed. For more information, see Windows Server 2008 Backup and Recovery Step-by-Step Guide (http://go.microsoft.com/fwlink/?LinkID=87597).
  2. Restart the computer.

Verify

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that the Service Control Manager (SCM) is successfully sending commands to services:

  1. Open the Services snap-in by clicking the Start button, Control Panel,  and Administrative Tools, then double-clicking Services.

    Note: For Windows Vista, use the Classic View display option in Control Panel to see the Administration Tools.

  2. Right-click on a stopped service that is not a system service and select Start. If the SCM was successful in starting the service, the Status field for that service will display Started.

 To verify that the Service Control Manager is logging service events correctly:

  1. Open Event Viewer by clicking the Start button, Control Panel, and Administration Tools, then double-clicking Event Viewer.

    Note: For Windows Vista, use the Classic View display option in Control Panel to see the Administration Tools.

  2. Click Event Viewer (Local), then Windows Logs and System.
  3. In the details pane, click on the Source column to view the events sorted by the entity that logged that event. For events logged by the SCM, the source is the Service Control Manager Eventlog Provider.
  4. Review the events and confirm that event ID 7036 was logged for the action taken by the SCM in step 1 of the To verify that the Service Control Manager is successsfully sending commands to services procedure above.

Related Management Information

Basic Service Control Manager Operations

Core Operating System

Related:

Event ID 7027 — Basic Service Control Manager Operations

Event ID 7027 — Basic Service Control Manager Operations

Updated: January 6, 2009

Applies To: Windows Server 2008 R2

The basic operations that Service Control Manager (SCM) performs include managing the services and driver services that allow the operating system to start successfully, and reporting when one of these services or driver services fail during system startup. These operations are not associated with any particular service.

Event Details

Product: Windows Operating System
ID: 7027
Source: Service Control Manager
Version: 6.1
Symbolic Name: EVENT_RUNNING_LASTKNOWNGOOD
Message: Windows could not be started as configured. A previous working configuration was used instead.

Resolve
Review the event log messages

To resolve this issue, review the Event logs and note if any other events have been logged by the Service Control Manager (SCM) Eventlog Provider. The event log message and related events logged by the SCM should help you to further troubleshoot and resolve the issue. Some examples are provided below.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

  1. If event ID 7011 is also logged for a service, then extending the service timeout period to resolve event ID 7011 would also resolve this error.
  2. If event ID 7034 is also logged for a service, then restoring the service default settings to resolve event ID 7034 would also resolve this error.

If the issue remains unresolved, contact Microsoft support and provide the error information. For information about how to contact Microsoft support, see Support Options from Microsoft Services (http://go.microsoft.com/fwlink/?LinkId=89446).

To review the events logged by the SCM:

  1. Open Event Viewer by clicking the Start button, Control Panel, and Administration Tools, then double-clicking Event Viewer.

    Note: For Windows Vista, use the Classic View display option in Control Panel to see the Administration Tools.

  2. Click Event Viewer (Local), then Windows Logs and System.
  3. In the details pane, click on the Source column to view the events sorted by the entity that logged that event. For events logged by the SCM, the source is the Service Control Manager Eventlog Provider.

Verify

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that the Service Control Manager (SCM) is successfully sending commands to services:

  1. Open the Services snap-in by clicking the Start button, Control Panel,  and Administrative Tools, then double-clicking Services.

    Note: For Windows Vista, use the Classic View display option in Control Panel to see the Administration Tools.

  2. Right-click on a stopped service that is not a system service and select Start. If the SCM was successful in starting the service, the Status field for that service will display Started.

 To verify that the Service Control Manager is logging service events correctly:

  1. Open Event Viewer by clicking the Start button, Control Panel, and Administration Tools, then double-clicking Event Viewer.

    Note: For Windows Vista, use the Classic View display option in Control Panel to see the Administration Tools.

  2. Click Event Viewer (Local), then Windows Logs and System.
  3. In the details pane, click on the Source column to view the events sorted by the entity that logged that event. For events logged by the SCM, the source is the Service Control Manager Eventlog Provider.
  4. Review the events and confirm that event ID 7036 was logged for the action taken by the SCM in step 1 of the To verify that the Service Control Manager is successsfully sending commands to services procedure above.

Related Management Information

Basic Service Control Manager Operations

Core Operating System

Related:

Event ID 7025 — Basic Service Control Manager Operations

Event ID 7025 — Basic Service Control Manager Operations

Updated: January 6, 2009

Applies To: Windows Server 2008 R2

The basic operations that Service Control Manager (SCM) performs include managing the services and driver services that allow the operating system to start successfully, and reporting when one of these services or driver services fail during system startup. These operations are not associated with any particular service.

Event Details

Product: Windows Operating System
ID: 7025
Source: Service Control Manager
Version: 6.1
Symbolic Name: EVENT_SERVICE_START_AT_BOOT_FAILED
Message: At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details.

Resolve
Review the event log messages

To resolve this issue, review the Event logs and note if any other events have been logged by the Service Control Manager (SCM) Eventlog Provider. The event log message and related events logged by the SCM should help you to further troubleshoot and resolve the issue. Some examples are provided below.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

  1. If event ID 7011 is also logged for a service, then extending the service timeout period to resolve event ID 7011 would also resolve this error.
  2. If event ID 7034 is also logged for a service, then restoring the service default settings to resolve event ID 7034 would also resolve this error.

If the issue remains unresolved, contact Microsoft support and provide the error information. For information about how to contact Microsoft support, see Support Options from Microsoft Services (http://go.microsoft.com/fwlink/?LinkId=89446).

To review the events logged by the SCM:

  1. Open Event Viewer by clicking the Start button, Control Panel, and Administration Tools, then double-clicking Event Viewer.

    Note: For Windows Vista, use the Classic View display option in Control Panel to see the Administration Tools.

  2. Click Event Viewer (Local), then Windows Logs and System.
  3. In the details pane, click on the Source column to view the events sorted by the entity that logged that event. For events logged by the SCM, the source is the Service Control Manager Eventlog Provider.

Verify

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that the Service Control Manager (SCM) is successfully sending commands to services:

  1. Open the Services snap-in by clicking the Start button, Control Panel,  and Administrative Tools, then double-clicking Services.

    Note: For Windows Vista, use the Classic View display option in Control Panel to see the Administration Tools.

  2. Right-click on a stopped service that is not a system service and select Start. If the SCM was successful in starting the service, the Status field for that service will display Started.

 To verify that the Service Control Manager is logging service events correctly:

  1. Open Event Viewer by clicking the Start button, Control Panel, and Administration Tools, then double-clicking Event Viewer.

    Note: For Windows Vista, use the Classic View display option in Control Panel to see the Administration Tools.

  2. Click Event Viewer (Local), then Windows Logs and System.
  3. In the details pane, click on the Source column to view the events sorted by the entity that logged that event. For events logged by the SCM, the source is the Service Control Manager Eventlog Provider.
  4. Review the events and confirm that event ID 7036 was logged for the action taken by the SCM in step 1 of the To verify that the Service Control Manager is successsfully sending commands to services procedure above.

Related Management Information

Basic Service Control Manager Operations

Core Operating System

Related:

Event ID 7043 — Service Stop Operations

Event ID 7043 — Service Stop Operations

Updated: January 6, 2009

Applies To: Windows Server 2008 R2

Service Control Manager (SCM) stops services and driver services. It also reports when services terminate unexpectedly or fail to restart after it takes corrective action.

Event Details

Product: Windows Operating System
ID: 7043
Source: Service Control Manager
Version: 6.1
Symbolic Name: EVENT_SERVICE_SHUTDOWN_FAILED
Message: The %1 service did not shutdown properly after receiving a preshutdown control.

Resolve
Stop the service manually

To resolve this issue, stop the service manually.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To stop a service:

  1. Open the Services snap-in by clicking the Start button, Control Panel, and Administrative Tools, then double-clicking Services.

    Note: For Windows Vista, use the Classic View display option in Control Panel to see the Administration Tools.

  2. In the details pane of the Services snap-in, right-click on the name of the service you want to stop and select Stop.

Verify

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that a service has stopped:

  1. Open the Services snap-in by clicking the Start button, Control Panel, and Administrative Tools, then double-clicking Services.

    Note: For Windows Vista, use the Classic View display option in Control Panel to see the Administration Tools.

  2. In the details pane of the Services snap-in, locate the name of the service and verify that the Status column shows a blank status.

Related Management Information

Service Stop Operations

Core Operating System

Related:

Event ID 7022 — Service Start Operations

Event ID 7022 — Service Start Operations

Updated: January 6, 2009

Applies To: Windows Server 2008 R2

Service Control Manager (SCM) starts services and driver services. It also reports when services fail to start or hang while starting.

Event Details

Product: Windows Operating System
ID: 7022
Source: Service Control Manager
Version: 6.1
Symbolic Name: EVENT_SERVICE_START_HUNG
Message: The %1 service hung on starting.

Resolve
Start the service manually

To resolve this issue, try starting the service manually.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To start a service:

  1. Open the Services snap-in by clicking the Start button, Control Panel, and Administrative Tools, then double-clicking Services.

    Note: For Windows Vista, use the Classic View display option in Control Panel to see the Administration Tools.

  2. In the details pane of the Services snap-in, right-click on the name of the service you want to start and select Start.

Verify

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that a service has started:

  1. Open the Services snap-in by clicking the Start button, Control Panel,  and Administrative Tools, then double-clicking Services.

    Note: For Windows Vista, use the Classic View display option in Control Panel to see the Administration Tools.

  2. In the details pane of the Services snap-in, locate the name of the service and verify that the Status column shows a status of Started.

Related Management Information

Service Start Operations

Core Operating System

Related:

Event ID 7020 — Service Start Operations

Event ID 7020 — Service Start Operations

Updated: December 11, 2007

Applies To: Windows Server 2008

Service Control Manager (SCM) starts services and driver services. It also reports when services fail to start or hang while starting.

Event Details

Product: Windows Operating System
ID: 7020
Source: Service Control Manager
Version: 6.0
Symbolic Name: EVENT_DEPEND_ON_LATER_GROUP
Message: Circular dependency: The %1 service depends on a group which starts later.

Resolve
Remove the circular dependency

This issue occurs because the  manually started services have a circular dependency chain, for example, service A depends on service B which depends on service C which depends on service A. To resolve this issue, remove the circular dependency.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To list the dependent services or service groups for a service and remove the circular dependencies:

  1. At a command prompt, type sc qc service_name to view the other services and service groups on which service_name is dependent.
  2. Type sc config service_name depend= service_name/+group_name (where service_name is the name of any noncircular dependent service and group_name is the name of any noncircular dependent service group) to remove dependencies on individual circular services or service groups.

Note: If the service has no dependent services or service groups, enter a null value for the depend parameter.

For more information about the sc command, see SC Command Reference Help (http://go.microsoft.com/fwlink/?LinkID=84961).

Verify

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that a service has started:

  1. Open the Services snap-in by clicking the Start button, Control Panel,  and Administrative Tools, then double-clicking Services.

    Note: For Windows Vista, use the Classic View display option in Control Panel to see the Administration Tools.

  2. In the details pane of the Services snap-in, locate the name of the service and verify that the Status column shows a status of Started.

Related Management Information

Service Start Operations

Core Operating System

Related:

Event ID 7030 — Basic Service Operations

Event ID 7030 — Basic Service Operations

Updated: December 11, 2007

Applies To: Windows Server 2008

Service Control Manager transmits control requests to running services and driver services. It also maintains status information about those services, and reports configuration changes and state changes.

Event Details

Product: Windows Operating System
ID: 7030
Source: Service Control Manager
Version: 6.0
Symbolic Name: EVENT_SERVICE_NOT_INTERACTIVE
Message: The %1 service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly.

Resolve
Change the interact with desktop setting

This error occurs if the service has been configured to allow the service to interact with the desktop. Interactive services can display a user interface and receive user input. If you allow the service to interact with the desktop, any information that the service displays on the desktop will also be displayed on an interactive user’s desktop. A malicious user could then take control of the service or attack it from the interactive desktop. In Windows Vista and Windows Server 2008, support for interactive services has been removed to mitigate this security risk; therefore, this error will be generated by any service configured as an interactive service. To resolve this issue, change the interact with desktop setting for the service. 

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To change the interact with desktop setting:

  1. Open the Services snap-in by clicking the Start button, Control Panel, and Administrative Tools, then double-clicking Services.

    Note: For Windows Vista, use the Classic View display option in Control Panel to see the Administration Tools.

  2. In the details pane of the Services snap-in, right-click on the name of the service you want to start and select Properties.
  3. Click the Log On tab and clear the Allow service to interact with desktop checkbox.
  4. Click OK.

Verify

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify the state in which a service is operating:

  1. Click the Start button, Run, then type cmd to open a command prompt.
  2. Type sc interrogate service_name (where service_name is the name of the service) at the command prompt to update the status of that service in Service Control Manager.
  3. Type sc qc service_name at the command prompt to display the configuration status of the service.
  4. Type sc queryex service_name at the command prompt to display the extended status of the service. This command will provide the following information about a service: SERVICE_NAME (the service’s registry subkey name), TYPE (the type of service, for example, shared process, interactive), STATE (for example, running, paused, and the states that are not available), WIN32_EXIT_CODE (the Windows exit error code), SERVICE_EXIT_CODE (the service exit code), CHECKPOINT, WAIT_HINT (the time period the SCM waits before reporting a service failure), PID (ID of the process running the service), and FLAGS. If the service was started successfully, the WIN32_EXIT_CODE field should contain a zero (0). If the service failed to start when an attempt was made, this field should contain an exit code provided by the service when it could not start.
  5. Type net helpmsg exit_code (where exit_code is the 4 digit number of the error code) at the command prompt to display the meaning of the exit code.

For more information about the sc command, see SC Command Reference Help (http://go.microsoft.com/fwlink/?LinkID=84961). For more information about the net helpmsg command, see http://go.microsoft.com/fwlink/?LinkId=105087.

Related Management Information

Basic Service Operations

Core Operating System

Related:

Event ID 7037 — Basic Service Operations

Event ID 7037 — Basic Service Operations

Updated: December 11, 2007

Applies To: Windows Server 2008

Service Control Manager transmits control requests to running services and driver services. It also maintains status information about those services, and reports configuration changes and state changes.

Event Details

Product: Windows Operating System
ID: 7037
Source: Service Control Manager
Version: 6.0
Symbolic Name: EVENT_SERVICE_CONFIG_BACKOUT_FAILED
Message: The Service Control Manager encountered an error undoing a configuration change to the %1 service. The service’s %2 is currently in an unpredictable state. If you do not correct this configuration, you may not be able to restart the %1 service or may encounter other errors. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC).

Resolve
Restore the default settings

If there were changes in the service settings (for example, the start up type was changed from Automatic to Manual), the service may be unable to start. To resolve this issue, first restore the default settings of the service and then start the service.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

Restore the default settings of the service

To restore the default settings of the service:

  1. Open the Services snap-in by clicking the Start button, Control Panel, and Administrative Tools, then double-clicking Services.

    Note: For Windows Vista, use the Classic View display option in Control Panel to see the Administration Tools.

  2. In the details pane of the Services snap-in, right-click on the name of the service you want to start and select Properties.
  3. Click the Log On tab and note the account listed under Log On As.
  4. Restore the default settings, if necessary. For a list of the default settings for system services, see http://go.microsoft.com/fwlink/?LinkId=105223. For non-system settings, see the documentation for that product.

Start the service

To start a service:

  1. Open the Services snap-in by clicking the Start button, Control Panel, and Administrative Tools, then double-clicking Services.

    Note: For Windows Vista, use the Classic View display option in Control Panel to see the Administration Tools.

  2. In the details pane of the Services snap-in, right-click on the name of the service you want to start and select Start.

Verify

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify the state in which a service is operating:

  1. Click the Start button, Run, then type cmd to open a command prompt.
  2. Type sc interrogate service_name (where service_name is the name of the service) at the command prompt to update the status of that service in Service Control Manager.
  3. Type sc qc service_name at the command prompt to display the configuration status of the service.
  4. Type sc queryex service_name at the command prompt to display the extended status of the service. This command will provide the following information about a service: SERVICE_NAME (the service’s registry subkey name), TYPE (the type of service, for example, shared process, interactive), STATE (for example, running, paused, and the states that are not available), WIN32_EXIT_CODE (the Windows exit error code), SERVICE_EXIT_CODE (the service exit code), CHECKPOINT, WAIT_HINT (the time period the SCM waits before reporting a service failure), PID (ID of the process running the service), and FLAGS. If the service was started successfully, the WIN32_EXIT_CODE field should contain a zero (0). If the service failed to start when an attempt was made, this field should contain an exit code provided by the service when it could not start.
  5. Type net helpmsg exit_code (where exit_code is the 4 digit number of the error code) at the command prompt to display the meaning of the exit code.

For more information about the sc command, see SC Command Reference Help (http://go.microsoft.com/fwlink/?LinkID=84961). For more information about the net helpmsg command, see http://go.microsoft.com/fwlink/?LinkId=105087.

Related Management Information

Basic Service Operations

Core Operating System

Related:

Event ID 7019 — Service Start Operations

Event ID 7019 — Service Start Operations

Updated: December 11, 2007

Applies To: Windows Server 2008

Service Control Manager (SCM) starts services and driver services. It also reports when services fail to start or hang while starting.

Event Details

Product: Windows Operating System
ID: 7019
Source: Service Control Manager
Version: 6.0
Symbolic Name: EVENT_DEPEND_ON_LATER_SERVICE
Message: Circular dependency: The %1 service depends on a service in a group which starts later.

Resolve
Remove the circular dependency

This issue occurs because the  manually started services have a circular dependency chain, for example, service A depends on service B which depends on service C which depends on service A. To resolve this issue, remove the circular dependency.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To list the dependent services or service groups for a service and remove the circular dependencies:

  1. At a command prompt, type sc qc service_name to view the other services and service groups on which service_name is dependent.
  2. Type sc config service_name depend= service_name/+group_name (where service_name is the name of any noncircular dependent service and group_name is the name of any noncircular dependent service group) to remove dependencies on individual circular services or service groups.

Note: If the service has no dependent services or service groups, enter a null value for the depend parameter.

For more information about the sc command, see SC Command Reference Help (http://go.microsoft.com/fwlink/?LinkID=84961).

Verify

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that a service has started:

  1. Open the Services snap-in by clicking the Start button, Control Panel,  and Administrative Tools, then double-clicking Services.

    Note: For Windows Vista, use the Classic View display option in Control Panel to see the Administration Tools.

  2. In the details pane of the Services snap-in, locate the name of the service and verify that the Status column shows a status of Started.

Related Management Information

Service Start Operations

Core Operating System

Related:

Event ID 7028 — Basic Service Control Manager Operations

Event ID 7028 — Basic Service Control Manager Operations

Updated: January 6, 2009

Applies To: Windows Server 2008 R2

The basic operations that Service Control Manager (SCM) performs include managing the services and driver services that allow the operating system to start successfully, and reporting when one of these services or driver services fail during system startup. These operations are not associated with any particular service.

Event Details

Product: Windows Operating System
ID: 7028
Source: Service Control Manager
Version: 6.1
Symbolic Name: EVENT_TAKE_OWNERSHIP
Message: The %1 Registry key denied access to SYSTEM account programs so the Service Control Manager took ownership of the Registry key.

Resolve
Review the event log messages

To resolve this issue, review the Event logs and note if any other events have been logged by the Service Control Manager (SCM) Eventlog Provider. The event log message and related events logged by the SCM should help you to further troubleshoot and resolve the issue. Some examples are provided below.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

  1. If event ID 7011 is also logged for a service, then extending the service timeout period to resolve event ID 7011 would also resolve this error.
  2. If event ID 7034 is also logged for a service, then restoring the service default settings to resolve event ID 7034 would also resolve this error.

If the issue remains unresolved, contact Microsoft support and provide the error information. For information about how to contact Microsoft support, see Support Options from Microsoft Services (http://go.microsoft.com/fwlink/?LinkId=89446).

To review the events logged by the SCM:

  1. Open Event Viewer by clicking the Start button, Control Panel, and Administration Tools, then double-clicking Event Viewer.

    Note: For Windows Vista, use the Classic View display option in Control Panel to see the Administration Tools.

  2. Click Event Viewer (Local), then Windows Logs and System.
  3. In the details pane, click on the Source column to view the events sorted by the entity that logged that event. For events logged by the SCM, the source is the Service Control Manager Eventlog Provider.

Verify

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that the Service Control Manager (SCM) is successfully sending commands to services:

  1. Open the Services snap-in by clicking the Start button, Control Panel,  and Administrative Tools, then double-clicking Services.

    Note: For Windows Vista, use the Classic View display option in Control Panel to see the Administration Tools.

  2. Right-click on a stopped service that is not a system service and select Start. If the SCM was successful in starting the service, the Status field for that service will display Started.

 To verify that the Service Control Manager is logging service events correctly:

  1. Open Event Viewer by clicking the Start button, Control Panel, and Administration Tools, then double-clicking Event Viewer.

    Note: For Windows Vista, use the Classic View display option in Control Panel to see the Administration Tools.

  2. Click Event Viewer (Local), then Windows Logs and System.
  3. In the details pane, click on the Source column to view the events sorted by the entity that logged that event. For events logged by the SCM, the source is the Service Control Manager Eventlog Provider.
  4. Review the events and confirm that event ID 7036 was logged for the action taken by the SCM in step 1 of the To verify that the Service Control Manager is successsfully sending commands to services procedure above.

Related Management Information

Basic Service Control Manager Operations

Core Operating System

Related: