Event ID 412 — Task Scheduler Service Status

Event ID 412 — Task Scheduler Service Status

Updated: December 6, 2007

Applies To: Windows Server 2008

The Task Scheduler service enables you to perform automated tasks on a local or remote computer. With this service, you can schedule any program to run at any time or when a specific event occurs.

The Task Scheduler service is automatically started by Service Control Manager (SCM). The Task Scheduler service cannot be stopped or disabled by administrators using the Services Microsoft Management Console (MMC) snap-in user interface, unless special permissions are added to the administrator token. The Task Scheduler service uses the Component Object Model (COM) service, the Windows Event Log service, and the Remote Procedure Call (RPC) service; all of these services must be started for the Task Scheduler service to run correctly.

Event Details

Product: Windows Operating System
ID: 412
Source: Microsoft-Windows-TaskScheduler
Version: 6.0
Symbolic Name: SCHEDULE_SERVICE_RUN_BOOT_JOBS_FAILED
Message: Task Scheduler service failed to launch tasks triggered by computer startup. The error value is: %1. Restart the Task Scheduler service.

Resolve
Restart the Task Scheduler service
To perform this procedure, you must have membership in the Administrators group, or you must have been delegated the appropriate authority.

To restart the Task Scheduler service:

1. Click the Start button and type Services in the Start Search box.

2. Select the Services program to start the Services console.

3. Select Task Scheduler from the services list.

4. Click Restart.

Verify

Verify that the Task Scheduler service is running, by opening the Services MMC snap-in, finding the Task Scheduler service, and then verifying that the state is set to Automatic.

To verify that the Task Scheduler state is set to Automatic:

1. Click Start and type Services in the Start Search box.

2. Select the Services program to start the Services console.

3. Verify that the Task Scheduler service Startup Type is not Disabled.

Related Management Information

Task Scheduler Service Status

Management Infrastructure

Related:

{process name} ({process id}) Unable to read the header of logfile {file name}. Error {error code}.

Details
Product: Exchange
Event ID: 412
Source: ESE98
Version: 6.0
Component: Extensible Store Engine
Symbolic Name: LOG_HEADER_READ_ERROR_ID
Message: {process name} ({process id}) Unable to read the header of logfile {file name}. Error {error code}.
   
Explanation
The logfile named in the message is corrupt.
   
User Action
Contact Microsoft Product Support Services.

Related:

() Unable to read the header of logfile . Error .

Details
Product: Exchange
Event ID: 412
Source: ESE
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine
Message: <process name> (<process id>) <storage group name>Unable to read the header of logfile <file name>. Error <error code>.
   
Explanation

Unable to read the header of the log file named in the Event ID 412 message. This may be due to a mismatching log signature, a corrupt log file, or a corrupt log header.

The cause depends on the Jet (ESE) Error code in the Description section of the event. The most common causes are listed below.

  • Error -530 = JET_errBadLogSignature= Bad signature for a log file. A signature for log files is used only to ensure that we are replaying the “right” set of log files. For example, if Log 45 from another storage group ended up in the set of log files of another storage group, then ESE will detect a signature mismatch and not replay this log file. A portion of each database header includes the signature of the current log file generation; if they do not match, then we error out indicating a mismatch.
  • Error -501 = JET_errLogFileCorrupt = Log file corrupt. Error-1022 is returned from corrupting the header of a log file. Corrupting other areas of the log file returns -501 JET_errLogFileCorrupt.
  • Error -1022 = JET_errDiskIO = Disk IO error. The -1022 error is a generic error that appears whenever a disk input/output (I/O) problem prevents Exchange from gaining access to a requested page in the database or to a transaction log. The most common reason for a -1022 error is a database file that was severely damaged or truncated. If this issue occurs, Exchange requests a page number that is larger than the number of pages in the database file, and a -1022 error results. This issue can occur because of issues in the file system or because of improper transaction log replay. In the case of a log file, Error-1022 is returned from corrupting the header of a log file.
   
User Action
  • Restore from online backup.
  • If there is no valid backup, repair the database by running the eseutil /p command, and then run the isinteg -fix command on the affected store repeatedly until you receive 0 fixes or the same result for fixes twice. CAUTION: After you repair the database by using the eseutil /p switch and isinteg -fix, the database may not be stable and reliable. Because the repair process deletes database pages, data loss is likely. NOTE: If you have to run a hard repair on your production database, Microsoft recommends that you move the data out of the repaired database to a new database or rebuild the database using Move Mailbox or ExMerge.

Related:

The DNS server is bound to a large number of IP addresses. Each of these server IP addresses consumes additional system resources and can add a slight increase in performance overhead for DNS query reception. In most cases, you can remove secondary IP addresses that are not required to support server networking hardware. For more information, see “Configuring multihomed servers” in the online Help.

Details
Product: Windows Operating System
Event ID: 412
Source: DNS
Version: 5.0
Symbolic Name: DNS_EVENT_MANY_IP_INTERFACES
Message: The DNS server is bound to a large number of IP addresses. Each of these server IP addresses consumes additional system resources and can add a slight increase in performance overhead for DNS query reception. In most cases, you can remove secondary IP addresses that are not required to support server networking hardware. For more information, see “Configuring multihomed servers” in the online Help.
   
User Action

To verify and reset the IP addresses on which the DNS server should listen:

1. In DNS Manager, right-click the DNS server in the server list.
2. Click Properties.
3. On the Interface tab, use Add and Remove to edit the list of IP addresses. Use Move Up and Move Down to prioritize the list of IP addresses.
4. When you are finished, click OK.

Related:

process name (process id) file nameUnable to read the header of logfile error code. Error %5.

Details
Product: Exchange
Event ID: 412
Source: ESE
Version: 6.5.0000.0
Message: process name (process id) file nameUnable to read the header of logfile error code. Error %5.
   
Explanation

Unable to read the header of the log file named in the Event ID 412

message. This may be due to a mismatching log signature, a corrupt log

file, or a corrupt log header.

The cause depends on the Jet (ESE) Error code in the Description section of

the event. The most common causes are listed below.

  • Error -530 =

    JET_errBadLogSignature= Bad signature for a log file. A signature for

    log files is used only to ensure that we are replaying the “right” set of log

    files. For example, if Log 45 from another storage group ended up in the set of log files of another storage group, then ESE will detect a signature

    mismatch and not replay this log file. A portion of each database header

    includes the signature of the current log file generation; if they do not

    match, then we error out indicating a mismatch.

  • Error -501 =

    JET_errLogFileCorrupt = Log file corrupt. Error-1022 is

    returned from corrupting the header of a log file. Corrupting other areas of

    the log file returns -501 JET_errLogFileCorrupt.

  • Error -1022 = JET_errDiskIO =

    Disk IO error. The -1022 error is a generic error that appears whenever

    a disk input/output (I/O) problem prevents Exchange from gaining access to a

    requested page in the database or to a transaction log. The most common reason for a -1022 error is a

    database file that was severely damaged or truncated. If this issue occurs,
    Exchange requests a page number that is larger than the number of pages in the

    database file, and a -1022 error results. This issue can occur because of

    issues in the file system or because of improper transaction log replay. In

    the case of a log file, Error-1022 is returned from corrupting the header of a

    log file.

   
User Action
  • Restore from online backup.
  • If there is no valid backup,

    repair the database by running the eseutil /p command,

    and then run the isinteg -fix command on the affected store repeatedly until

    you receive 0 fixes or the same result for fixes twice. CAUTION: After you

    repair the database by using the eseutil /p switch and isinteg -fix,

    the database may not be stable and reliable. Because the repair process

    deletes database pages, data loss is likely. NOTE: If you have to run a hard

    repair on your production database, Microsoft recommends that you move the

    data out of the repaired database to a new database or rebuild the database

    using Move Mailbox or ExMerge.

Related:

%1 (%2) %3Unable to read the header of logfile %4. Error %5.

Details
Product: Exchange
Event ID: 412
Source: ESE
Version: 8.0
Symbolic Name: LOG_HEADER_READ_ERROR_ID
Message: %1 (%2) %3Unable to read the header of logfile %4. Error %5.
   
Explanation

This Warning event indicates that the database engine is unable to read the log file header specified in the event description. This may be because of a mismatching log signature, a corrupted log file, or a corrupted log header.

The cause depends on the ESE error code in the Description section of the event. The most common causes are in the following list.

  • Error 530 = Jet_errBadLogSignature = Bad signature for a log file. A signature for log files is used only to make sure that we are replaying the “right” set of log files. For example, if Log 45 from another storage group ended up in the set of log files of another storage group, then ESE will detect a signature mismatch and not replay this log file. A part of each database header includes the signature of the current log file generation; if they do not match, then we error out indicating a mismatch.

  • Error 501 = Jet_errLog fileCorrupt = Log file corrupt. Error 1022 is returned from corrupting the header of a log file. Corrupting other areas of the log file returns 501 Jet_errLog fileCorrupt errors.

  • Error 1022 = Jet_errDiskIO = disk I/O error. The 1022 error is a generic error that appears whenever a disk I/O problem prevents Exchange from gaining access to a requested page in the database or to a transaction log. The most common reason for a 1022 error is a database file that was severely damaged or truncated. If this issue occurs, Exchange requests a page number that is larger than the number of pages in the database file, and a 1022 error results. This issue can occur because of issues in the file system or because of incorrect transaction log replay. In a log file, error 1022 is returned from corrupting the header of a log file.

   
User Action

To resolve the warning, use one of the following procedures:

  • Restore data from online backup.

  • If there is no valid backup, repair the database by running the Eseutil /p command, and then run the isinteg -fix command on the affected store repeatedly until you receive 0 fixes or the same result for fixes two times. After you repair the database by using the Eseutil /p command and isinteg -fix, the database may not be stable and reliable. Because the repair process deletes database pages, data loss is likely. If you have to run a hard repair on your production database, we recommend that you move the data out of the repaired database to a new database or rebuild the database using the Move Mailbox command.

For information about ESE error codes other than the ones explained in this topic, see the following Microsoft Knowledge Base articles:

For more information about ESE error 1022, see 314917, Understanding and Analyzing -1018, -1019, and -1022 Exchange database errors.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related: