Event ID 101 — RD Gateway Server Availability

Event ID 101 — RD Gateway Server Availability

Published: January 8, 2010

Applies To: Windows Server 2008 R2

The Remote Desktop Gateway (RD Gateway) server must be available on the network, and the appropriate services must be running on the RD Gateway server. The Remote Desktop connection authorization policy (RD CAP) and the Remote Desktop resource authorization policy (RD RAP) stores must also be available, so that these policies can be evaluated to determine whether remote clients meet policy requirements. RD CAPs specify who can connect to an RD Gateway server. RD RAPs specify the internal network resources (computers) that clients can connect to through an RD Gateway server. If RD CAPs and RD RAPs are not available, the RD Gateway server will not be available for client connections.

Event Details

Product: Windows Operating System
ID: 101
Source: Microsoft-Windows-TerminalServices-Gateway
Version: 6.1
Symbolic Name: AAG_EVENT_SERVICE_STARTED
Message: The RD Gateway service has started.

Resolve

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

Related Management Information

RD Gateway Server Availability

Remote Desktop Services

Related:

Event ID 101 — Task Properties

Event ID 101 — 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: 101
Source: Microsoft-Windows-TaskScheduler
Version: 6.0
Symbolic Name: JOB_START_FAILED
Message: Task Scheduler failed to start the “%1” task for user “%2”. The error value is: %3.

Resolve
Use error code to diagnose launch failure

Use the error code provided in the launch failure event to further diagnose reasons for a task failing to start. To find a description of the error code provided in the event, convert the error code into decimal form and then find the error code in the list of system error codes on http://go.microsoft.com/fwlink/?LinkId=102313.

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:

No providers are found in the folder “%1”. The Autodiscover service is unable to process any valid requests. Check Autodiscover service configuration.

Details
Product: Exchange
Event ID: 101
Source: MSExchange Autodiscover
Version: 8.0
Symbolic Name: ErrCoreNoProvidersFound
Message: No providers are found in the folder “%1”. The Autodiscover service is unable to process any valid requests. Check Autodiscover service configuration.
   
Explanation

This Error event indicates that the Microsoft Exchange Autodiscover service is unable to process requests from the Outlook or mobile clients because the Outlook or mobile provider file was unavailable in the Autodiscover virtual directory configuration. Therefore, Outlook or mobile clients will be unable to access Exchange services such as the Availability service. This event may be caused because the Autodiscover service is not configured correctly on the Microsoft Exchange Client Access server.

   
User Action

To resolve this error, do the following on the Exchange Client Access Server.

  • Check to see whether Autodiscover service is configured correctly.

  • Install or reinstall the provider file, Microsoft.Exchange.Autodiscover.dll in this path: D:\Program Files\Microsoft\Exchange Server\ClientAccess\Autodiscover\bin.

  • If these options 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.

For more information about the Autodiscover service, see Managing Autodiscover.

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:

Resource “%1” for storage group “%2” on clustered mailbox server %3 was not brought online because of data loss. The known log information is: LatestInspectorTime=%4, LatestCopyNotificationTime=%5, InspectorGenerationNumber=%6, LatestLogGenerationNumber=%7.

Details
Product: Exchange
Event ID: 101
Source: MSExchangeRepl
Version: 8.0
Symbolic Name: DataLoss
Message: Resource “%1” for storage group “%2” on clustered mailbox server %3 was not brought online because of data loss. The known log information is:
LatestInspectorTime=%4, LatestCopyNotificationTime=%5, InspectorGenerationNumber=%6, LatestLogGenerationNumber=%7.
   
Explanation

This Error event indicates that database %1 in storage group %2 on clustered mailbox server %3 was not brought online because of data loss. This is an extremely abnormal condition and requires advanced diagnostics or debugging to determine the cause of the failure.

The known log information is:

LatestInspectorTime=%4

LatestCopyNotificationTime=%5

InspectorGenerationNumber=%6

LatestLogGenerationNumber=%7.

   
User Action

To resolve this error, do the following:

  • Review the System and Application event logs for related events. For example, events that occur immediately before and after this event may provide more information about the root cause of this error.

  • Contact Microsoft Product Support Services. For information about contacting support, visit 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) %3The database engine stopped.

Details
Product: Windows Operating System
Event ID: 101
Source: ESENT
Version: 5.2
Symbolic Name: STOP_ID
Message: %1 (%2) %3The database engine stopped.
   
Explanation

The extensible storage engine database engine stopped.

Possible causes include:

  • An online restoration failed. There may be missing log files on the computer or in an online restoration, or there may be old log files that are out of sequence with the log that is mentioned in the Restore.env file.
  • A database could not be loaded. The directory where the database or logs exist might not have the correct permissions assigned to it in order to load the store.
  • An information store was unloaded.
  • There might be file-level virus-scanning software running against the log file directory.
   
User Action

To troubleshoot the problem, check the Application log and the System log to determine the exact sequence of related events leading up to this event.

For more information about this event, see article Q274321 in the Microsoft Knowledge Base.

Related:

process name (process id) %3The database engine stopped.

Details
Product: Exchange
Event ID: 101
Source: ESE
Version: 6.5.0000.0
Message: process name (process id) %3The database engine stopped.
   
Explanation

ESE Event ID 100 indicates that the database engine started.

ESE Event ID 101 indicates that the database engine stopped.

ESE Event ID 100 is usually followed by a series of other ESE Events

describing an online restore, or mounting of information store databases. 

If an online restore fails to complete, or a database fails to mount, you may

receive an Event ID 101, indicating that the database engine has stopped. 

You may also receive this event when an information store dismounts for any

reason.  If you try to mount the store again and the store fails to mount, you may receive Event ID 100 indicating the database engine started, and then

again receive Event ID 101, indicating the database engine failed to start. 

In Exchange System Manager, if the arrow points down and is red, which displays

on the Exchange System Manager icon, this indicates that the stores are

dismounted.

In summary, receiving ESE Event ID 100 simply means that the database engine

started.  It does not mean the information store will mount, since it may be

followed by an ESE Event ID 101, which means the database engine stopped. 

In this case, the store failed to mount.  The reasons for ESE Event ID 101

are many and varied.  These events by themselves are generic for restoring

and for mounting of the information store databases.

For examples of causes, there may not be enough permissions on the
directory where the database or logs exist to mount the store.  There may

be missing log files on the production, or in an online restore, there may be

old log files that are out of sequence with the log that is mentioned in

Restore.env file.  There may be file level virus scanning software running

against the log file directory.

   
User Action

In normal operations, if you receive ESE Event ID 100 or ESE Event 101, and

Exchange is functioning normally,  no user action is required.

However, if an online aware restore of Exchange fails or an information

store database fails to mount as expected, then ESE Event ID 101 indicates that there may be a problem with the database or its logs.  Check the Application

log and the System log for related events to determine the exact sequence of

events leading up to ESE Event ID 101.

Related: