Event ID 302 — RD Gateway Server Connections

Event ID 302 — RD Gateway Server Connections

Published: January 8, 2010

Applies To: Windows Server 2008 R2

For remote clients to successfully connect to internal network resources (computers) through a Remote Desktop Gateway (RD Gateway) server, clients must meet the conditions specified in at least one Remote Desktop connection authorization policy (RD CAP) and Remote Desktop resource authorization policy (RD RAP). RD CAPs specify who can connect to an RD Gateway server and the authentication method that must be used. RD RAPs specify the computers that clients can connect to through an RD Gateway server.

Note: A limit can be set on the RD Gateway server to restrict the maximum number of simultaneous client connections.

Event Details

Product: Windows Operating System
ID: 302
Source: Microsoft-Windows-TerminalServices-Gateway
Version: 6.1
Symbolic Name: AAG_EVENT_CHANNEL_CONNECTED
Message: The user “%1”, on client computer “%2”, connected to resource “%4”.

Resolve

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

Related Management Information

RD Gateway Server Connections

Remote Desktop Services

Related:

Event ID 302 — TS Gateway Server Connections

Event ID 302 — TS Gateway Server Connections

Updated: January 5, 2012

Applies To: Windows Server 2008

For remote clients to successfully connect to internal network resources (computers) through a Terminal Services Gateway (TS Gateway) server, clients must meet the conditions specified in at least one Terminal Services connection authorization policy (TS CAP) and Terminal Services resource authorization policy (TS RAP). TS CAPs specify who can connect to a TS Gateway server and the authentication method that must be used. TS RAPs specify the computers that clients can connect to through a TS Gateway server. Note that a limit can be set on the TS Gateway server to restrict the maximum number of simultaneous client connections.

Event Details

Product: Windows Operating System
ID: 302
Source: Microsoft-Windows-TerminalServices-Gateway
Version: 6.0
Symbolic Name: AAG_EVENT_CHANNEL_CONNECTED
Message: The user “%1”, on client computer “%2”, connected to resource “%4”.

Resolve

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

Related Management Information

TS Gateway Server Connections

Terminal Services

Related:

() The database engine has successfully completed recovery steps.

Details
Product: Exchange
Event ID: 302
Source: ESE
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine
Message: <process name> (<process id>) <number>The database engine has successfully completed recovery steps.
   
Explanation

The Exchange store database engine successfully completed recovery steps.

   
User Action

No user action is required.

Related:

Unable to quarantine message because the spam quarantine mailbox is invalid. Please configure the quarantine mailbox.

Details
Product: Exchange
Event ID: 302
Source: MSExchange Antispam
Version: 8.0
Symbolic Name: ContentFilterQuarantineMailboxIsInvalid
Message: Unable to quarantine message because the spam quarantine mailbox is invalid. Please configure the quarantine mailbox.
   
Explanation

This Warning event indicates that the Content Filter quarantine mailbox is not configured.

   
User Action

To resolve this error, follow one or more of these steps:

  • Log on to the Edge Transport server and configure the quarantine mailbox using the following Exchange Management Shell command: Set-ContentFilterConfig -QuarantineMailbox <SmtpAddress>

    For information about how to configure content filtering and the quarantine mailbox, see the following topics:

  • If you experience mail flow interruptions or other problems in your Exchange environment after you try to resolve this issue, contact Microsoft Customer Support. For information about how to contact support, visit Microsoft Help and Support.

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 has successfully completed recovery steps.

Details
Product: Windows Operating System
Event ID: 302
Source: ESENT
Version: 5.2
Symbolic Name: STOP_REDO_ID
Message: %1 (%2) %3The database engine has successfully completed recovery steps.
   
Explanation

The Exchange store database engine successfully completed recovery steps. Event ID 302 can be associated with System Event ID 4224 or Event ID 7023. You may also see ESENT Event ID 100, 300, or 301 in the Application log file.

   
User Action

No user action is required.

Related: