Event ID 104 — Private Channel Configuration

Event ID 104 — Private Channel Configuration

Updated: August 5, 2011

Applies To: Windows Server 2008 R2

Each event channel has configuration settings, such as the maximum size of the log and the custom security descriptor specified by the administrator for the log. The events that refer to the maximum size of the log serve as indicators for how the service dealt with the log when it reached its maximum size. The operation of the service is not affected, but an event can indicate to the administrator the configuration setting that might require a change.

Events that report problems with an event log security descriptor are more significant. They can indicate that the desired security settings are not be set correctly and the channel is more or less accessible than intended by the administrator.

Event Details

Product: Windows Operating System
ID: 104
Source: Microsoft-Windows-Eventlog
Version: 6.1
Symbolic Name: EVENT_LOG_CLEARED
Message: The %3 log file was cleared.

Resolve

This is a normal condition. No further action is required.

Related Management Information

Private Channel Configuration

Management Infrastructure

Related:

Event ID 104 — Task Properties

Event ID 104 — Task Properties

Updated: December 6, 2007

Applies To: Windows Server 2008

Task properties define the settings and conditions for running a task. A task will run if all of its conditions are met after the task is triggered to start. Conditions are divided into three categories: idle conditions, power conditions, and network conditions. The conditions for a task care displayed on the Conditions tab of the Task Properties or the Create Task dialog box in Task Scheduler.

Task settings specify how a task is run, stopped, or deleted. The settings for a task are displayed on the Settings tab of the Task Properties or the Create Task dialog box in Task Scheduler.

Event Details

Product: Windows Operating System
ID: 104
Source: Microsoft-Windows-TaskScheduler
Version: 6.0
Symbolic Name: LOGON_FAILURE
Message: Task Scheduler failed to log on “%1”. The failure occurred in “%2”. Ensure the credentials for the task are correctly specified. The error value is: %3.

Resolve
Fix task credentials

To change the credentials for the task:

1. Click the Start button and type Task Scheduler in the Start Search box.

2. Select the Task Scheduler program to start Task Scheduler.

3. Locate the task in the task folder hierarchy. 

4. Right-click the task and select Properties.

5. Update the user credentials for running the task under the Security options on the General tab.

6. Click OK.

Verify

To verify that the task runs correctly:

1. Click the Start button and type Task Scheduler in the Start Search box.

2. Select the Task Scheduler program to start Task Scheduler.

3. Select the task that you want to run by locating the task in the task folder hierarchy.

4. On the Actions menu click Run. You can also click Run in the Actions pane.

5. Click the History tab to view task events and verify the selected task started successfully.

6. Similarly, verify that the task starts as expected when its defined trigger fires.

Related Management Information

Task Properties

Management Infrastructure

Related:

%1 (%2) %3The database engine stopped the instance (%4) with error (%5).

Details
Product: Exchange
Event ID: 104
Source: ESE
Version: 8.0
Symbolic Name: STOP_INSTANCE_ID_WITH_ERROR
Message: %1 (%2) %3The database engine stopped the instance (%4) with error (%5).
   
Explanation

This Error event first occurs when there are no log file names remaining. The affected storage group will not start until you resolve the problem.

The maximum number of transaction log files that can be generated in a single sequence is 2,147,486,647 (0x7FFFFFFF). Typically, it will take dozens to hundreds of years of operation before this many log files will be generated.

The transaction log file names resemble E0100012345.log, E01000ABCDE.log, E01000FFF00.log. The last eight characters of each log file name is the number of the log in the sequence. ESE has reached the last usable log generation number (0x7FFFFFEC), which is 16 logs before the maximum (0x7FFFFFFF) and all databases in the storage group have stopped with the error Jet_errLogSequenceEnd. Stopping this error before the end of the sequence enables more than enough additional logs for the database to be returned to a Clean Shutdown state.

   
User Action

To recover from this problem, you must reset the log file sequence. To do this requires removing all existing transaction logs. After you do this, a new sequence of log files, starting with 0x00000001 will be generated.

Before removing transaction logs, you must verify that all databases in the storage group are in a Clean Shutdown state.

For more information about how to reset the log file sequence, follow the steps under WORKAROUND in Microsoft Knowledge Base article 830408, Store databases are dismounted without warning or users cannot log on to their mailboxes in Exchange Server 2003 or in Exchange 2000 Server.

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:

Unable to initialize bytes of memory. Reboot the computer. If that does not work, call Microsoft Technical Support. [ ] (16)

Details
Product: Exchange
Event ID: 104
Source: MSExchangeMTA
Version: 6.5.6940.0
Component: Microsoft Exchange Message Transfer Agent
Message: Unable to initialize <value> bytes of memory. Reboot the computer. If that does not work, call Microsoft Technical Support. [<value> <value> <value> <value>] (16)
   
Explanation

The message transfer agent (MTA) has failed to allocate and reserve memory from the operating system.

   
User Action

Use Performance Monitor to determine if a particular item is taking up too much memory. To allocate more memory, close any nonessential applications. You may also increase your system’s physical or virtual memory. Verify that there is enough disk space for the paging file to grow.

Related:

Cannot request exclusive semaphores at interrupt time.

Details
Product: Windows Operating System
Event ID: 104
Source: Kernel
Version: 5.0
Component: System Resources
Symbolic Name: ERROR_INVALID_AT_INTERRUPT_TIME
Message: Cannot request exclusive semaphores at interrupt time.
   
Explanation

Exclusive system semaphores are owned by a task. The system checks to make sure that only the owner modifies the semaphore. It is impossible to determine the requester at interrupt time, so exclusive semaphores might not be modified then.

   
User Action

End your requested operation, wait awhile, and retry. If you still get this message, contact the supplier of the running application.

Related:

Unable to initialize value bytes of memory. Reboot the computer. If that does not work, call Microsoft Technical Support. [valuevaluevaluevalue] (16)

Details
Product: Exchange
Event ID: 104
Source: MSExchangeMTA
Version: 6.5.0000.0
Message: Unable to initialize value bytes of memory. Reboot the computer. If that does not work, call Microsoft Technical Support. [valuevaluevaluevalue] (16)
   
Explanation
The message transfer agent (MTA) has failed to allocate and reserve memory from the operating system.
   
User Action
Use Performance Monitor to determine if a particular item is taking up too much memory. To allocate more memory, close any nonessential applications. You may also increase your system’s physical or virtual memory. Verify that there is enough disk space for the paging file to grow.

Related:

Machine Check Event reported is a corrected error reported to CPU %1.

Details
Product: Windows Operating System
Event ID: 104
Source: WMIxWDM
Version: 5.2
Symbolic Name: MCA_WARNING_UNKNOWN
Message: Machine Check Event reported is a corrected error reported to CPU %1.
   
Explanation

A hardware error was resolved by your system. The type of error cannot be determined because the error record returned by the firmware is not in the required format. For detailed information about the hardware that caused the problem, refer to the event log.

   
User Action

If the problem continues, contact your hardware support provider.

Related:

Exchange Search Indexer failed to enable the Mailbox Database %1 (GUID = %2) after %3 tries. The last failure was: %4. It will retry after %5 minutes.

Details
Product: Exchange
Event ID: 104
Source: MSExchange Search Indexer
Version: 8.0
Symbolic Name: FailedToEnableMDB
Message: Exchange Search Indexer failed to enable the Mailbox Database %1 (GUID = %2) after %3 tries. The last failure was: %4. It will retry after %5 minutes.
   
Explanation

This Error event indicates that the Microsoft Exchange Search service did not enable indexing for the specified mailbox database after a specified number of tries. To enable indexing means to create and mount the search catalog for the mailbox database. This error can occur because the disk is full.

   
User Action

To resolve this error, do one or more of the following:

  • View the Application event log for a detailed event description.

  • Do nothing. The Exchange Search service will try again to enable indexing for the mailbox database.

  • Restart the Microsoft Exchange Search service from the Services snap-in.

  • Get additional help by posting the issue at Newsgroups: Exchange Server and Outlook.

  • If the options here do not help in resolving the issue, contact Microsoft Product Support Services. For more information, visit the Contact Us page of the Microsoft Help and Support Web site.

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:

%1 (%2) %3 The database engine stopped the instance (%4) with error (%5).

Details
Product: Exchange
Event ID: 104
Source: ESE
Version: 6.5.7596.0
Message: %1 (%2) %3 The database engine stopped the instance (%4) with error (%5).
   
Explanation

Event ID 104 frequently occurs with other related events. The following describes these three events.

  • ESE event 102   The database engine started a new instance (Instance #).

  • ESE event 103   The database engine stopped the instance (Instance #).

  • ESE event 104   The database engine stopped an instance (Instance #) with error (Error #).

There is only one Jet database engine, Ese.dll, per server. However, there can be one instance of Jet running per storage group. Event 102 signifies that an instance of Jet has started and indicates which instance has started. Event 103 indicates which instance has stopped. These events can occur in the ordinary operation of a Microsoft® Exchange Server environment, or they may be associated with errors. An error is never mentioned in the description section of event 103. Event 104 definitely indicates that there is a problem and that the named instance of Jet has stopped with a definite error associated with it. The error is named in the description section of Event 104.

Event ID 104 has many potential causes. Use the following explanations of common error codes to help you understand the root cause ESE event 104:

  • Error -1090 = 0xfffffbbe = JET_errInstanceUnavailable = This instance cannot be used because it encountered a fatal error.

    If ESE encounters this error, ESE will not be able to roll back any transactions and will dismount the databases in the Storage Group for that instance of Jet.

  • Error -1022 = 0xfffffc02 = 4294966274 = JET_errDiskIO = Disk IO error.

    A disk or controller failure has occurred. Access to the whole drive has been lost, sometimes temporarily. Examine the System log for I/O or drive errors near the time of the 439 Event. In this case, you may see Error -1022 in the description of Event ID 104.

    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. Permissions have been removed from the folder where the file resides. The file has been marked read-only. The folder that contains the file has been renamed or deleted. Error -1022 can occur when Exchange cannot write to the hard disk and generates an error message: Either software that has been installed has prevented the write operation or the hard disk itself is corrupted. Error -1022 is frequently associated with Error 1022.

    Error 1022 indicates that there is a disk input/output (I/O) error. For example, it may mean that the hard disk has been corrupted. Error 1022 is generated by Exchange whenever Exchange cannot write to the hard disk. Although though you may suspect that there is a problem with a corrupted hard disk, Error 1022 may also occur when any software that is incompatible with Exchange is stopping Exchange from correctly writing to the hard disk. This issue can also occur because of incorrect permissions on the Exchsrvr folder structure.

  • Error -510 = 0xfffffe02 = 4294966786 = JET_errLogWriteFail = Failure when writing to log file.

    This error has both been seen in the description of event 104 and has been more typically associated with a different ESE event. Error -510 can be caused by permissions issues, space issues, and other issues affecting reads or writes to the disks.

   
User Action

To resolve ESE Event ID 104

  1. Run chkdsk /f /r.

  2. If Chkdsk does not resolve the issue, examine the permissions on the Exchsrvr folder structure.

  3. If you still cannot mount the databases, troubleshoot any Microsoft Windows NT® file-level antivirus software running on the Exchange server.

For more information about related ESE event 103, search for information about that event in the Errors and Events Message Center.

Related: