Event ID 409 — Task Scheduler Service Status

Event ID 409 — Task Scheduler Service Status

Updated: August 5, 2011

Applies To: Windows Server 2008 R2

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: 409
Source: Microsoft-Windows-TaskScheduler
Version: 6.1
Symbolic Name: SCHEDULE_SERVICE_TIME_CHANGE_INIT_ERROR
Message: The Task Scheduler service failed to initialize a time change notification. System time updates may not be picked by the service and task schedules may not be updated. The error value is: %1.

Resolve
Ensure that there is sufficient free memory
To perform this procedure, you must have membership in the Administrators group, or you must have been delegated the appropriate authority.

Ensure that there is sufficient free memory on the computer and then restart the Task Scheduler service. You can close some applications to free memory. To restart the Task Scheduler service:

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

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

3. Right-click the Task Scheduler service and select 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:

Event ID 409 — DNS Server Configuration

Event ID 409 — DNS Server Configuration

Updated: November 13, 2007

Applies To: Windows Server 2008

The DNS server configuration consists of the settings that determine how the DNS server will function on a network and how those settings are stored and retrieved when they are needed.

 

Event Details

Product: Windows Operating System
ID: 409
Source: Microsoft-Windows-DNS-Server-Service
Version: 6.0
Symbolic Name: DNS_EVENT_UPDATE_LISTEN_ADDRESSES
Message: The DNS server list of restricted interfaces contains IP addresses that are not configured for use at the server computer. Use the DNS manager server properties, interfaces dialog, to verify and reset the IP addresses the DNS server should listen on. For more information, see "To restrict a DNS server to listen only on selected addresses" in the online Help.

Resolve
Correct the network interface problem

On computers with more than one network interface, the DNS server can be configured to respond to Domain Name System (DNS) requests on one or more of the interfaces. If the list of interface addresses is not correct, the DNS server is not able to respond to requests from other computers on the network.

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

To correct the IP addresses that the DNS server is configured to use:

  1. On the DNS server, start Server Manager. To start Server Manager, click Start, click Administrative Tools, and then click Server Manager.
  2. In the console tree, double-click Roles, double-click DNS Server, and then double-click DNS.
  3. Right-click the DNS server, and then click Properties.
  4. On the Interfaces tab, ensure that All IP addresses is selected or determine if any address in the IP addresses list is not valid for the server’s network interfaces.
  5. Clear the check box next to the invalid addresses, and then click OK.
  6. Right-click the DNS server, click All Tasks, and then click Restart.

Verify

To verify that the Domain Name System (DNS) configuration is correct, verify that all configuration settings are correct, check the event log for events that indicate continuing problems, and then verify that DNS client computers are able to resolve names properly.

To verify DNS configuration settings:

  1. On the DNS server, start Server Manager. To start Server Manager, click Start, click Administrative Tools, and then click Server Manager.
  2. In the console tree, double-click Roles, double-click DNS Server, and then double-click DNS.
  3. Right-click the DNS server, and then click Properties.
  4. Review the settings on each tab, and verify that they contain the intended values.
  5. Expand the DNS server.
  6. Expand a zone folder, right-click a zone, and then click Properties.
  7. Review the settings on each tab, and verify that they contain the intended values.
  8. Repeat steps 6 and 7 for each zone.

To verify that DNS client computers can resolve names properly:

  1. On a DNS client computer, open a command prompt. To open a command prompt, click Start, click Run, type cmd, and then click OK.
  2. At the command prompt, type pinghostname (where hostname is the DNS name of a computer with a known IP address), and then press ENTER.

If the client can resolve the name, the ping command responds with the following message:

Pinging
hostname [ip_address]

Note: The name resolution is successful even if the ping command reports that the destination is unreachable.

If the client cannot resolve the name, the ping command responds with the following message:

Ping request could not find host
hostname

Related Management Information

DNS Server Configuration

DNS Infrastructure

Related:

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

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

The log file named in the message is corrupt.

   
User Action

If one or more log files are inaccessible, check the file permissions and attributes. Verify that none of the log files are hidden or read-only. The Local System account should have full access to the log files. Also check the system event log for indications of hardware problems.

Review the disk and log file which you are trying to write to. Use the Error.exe utility to resolve system errors.

For more information about the error code reference specified in the message, go to www.reskit.com.

Related:

The DNS server list of restricted interfaces contains IP addresses that are not configured for use at the server computer. Use the DNS manager server properties, interfaces dialog, to verify and reset the IP addresses the DNS server should listen on. For more information, see “To restrict a DNS server to listen only on selected addresses” in the online Help.

Details
Product: Windows Operating System
Event ID: 409
Source: DNS
Version: 5.0
Symbolic Name: DNS_EVENT_UPDATE_LISTEN_ADDRESSES
Message: The DNS server list of restricted interfaces contains IP addresses that are not configured for use at the server computer. Use the DNS manager server properties, interfaces dialog, to verify and reset the IP addresses the DNS server should listen on. For more information, see “To restrict a DNS server to listen only on selected addresses” in the online Help.
   
Explanation

If you are using database files that have been imported from a non-Microsoft DNS server, you must install these files in the Systemroot\System32\Dns folder. Before importing the files, use a text editor to edit the files so that the directory command identifies the DNS directory.

   
User Action

If the specified file is a boot file that you have imported from another DNS server, stop DNS. Verify that all databases that were imported are located in the Systemroot\System32\Dns folder. If they are, rename the boot file to Boot.bak and restart DNS. The DNS server will now boot from the registry.

Related:

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

Details
Product: Exchange
Event ID: 409
Source: ESE98
Version: 6.0
Component: Extensible Store Engine
Symbolic Name: LOG_HEADER_WRITE_ERROR_ID
Message: {process name} ({process id}) Unable to write to the header of logfile {file name}. Error {error code}.
   
Explanation
The log file named in the message is corrupt.
   
User Action
If one or more log files is inaccessible, check the file permissions and attributes. Verify that none of the log files is hidden or read-only. The Local System account should have full access to the log files. Also check the system event log for indications of hardware problems. Review the disk and log file which you are trying to write to. Use the Error.exe utility to resolve system errors. For more information about the error code reference specified in the message, go to www.reskit.com.

Related: