Event ID 1147 — Remote Desktop Session Host Listener Availability

Event ID 1147 — Remote Desktop Session Host Listener Availability

Published: January 8, 2010

Applies To: Windows Server 2008 R2

The listener component runs on the RD Session Host server and is responsible for listening for and accepting new Remote Desktop Protocol (RDP) client connections, thereby allowing users to establish new remote sessions on the RD Session Host server. There is a listener for each Remote Desktop Services connection that exists on the RD Session Host server. Connections can be created and configured by using the Remote Desktop Session Host Configuration tool.

Event Details

Product: Windows Operating System
ID: 1147
Source: Microsoft-Windows-TerminalServices-RemoteConnectionManager
Version: 6.1
Symbolic Name: EVENT_TS_SHADOW_SUCCEEDED
Message: Remote Desktop Services: Remote control session connection succeeded:%1 initiated a remote control session:User: %2Domain: %3

Resolve

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

Related Management Information

Remote Desktop Session Host Listener Availability

Remote Desktop Services

Related:

Error %3 while disabling rule on public folder with rule ID %2. The folder ID of the public folder is in the data section of this event.

Details
Product: Exchange
Event ID: 1147
Source: MSExchangeIS
Version: 8.0
Symbolic Name: msgidErrorDisablingRule
Message: Error %3 while disabling rule on public folder with rule ID %2. The folder ID of the public folder is in the data section of this event.
   
Explanation

This Error event indicates that there was a problem running a rule on a public folder. Public folders can have rules associated with them. One of the most common public folder rules is a rule that designates that all incoming message items that are sent to a public folder are forwarded to a specific mailbox. In this scenario, this event is logged if the mailbox to which this public folder’s mail is being forwarded to has exceeded its configured limits. If this is the case, MSExchangeIS event ID 8528 is logged and that event indicates that the mailbox has exceeded its limits.

   
User Action

To resolve this error, check the public folder’s rules. If any of the rules involve forwarding message items to other mailboxes, verify that the mailboxes that are configured to receive message items have not reached any limits. You should also verify that the mailboxes can receive messages.

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:

Error while disabling rule on public folder with rule ID . The folder ID of the public folder is in the data section of this event.

Details
Product: Exchange
Event ID: 1147
Source: MSExchangeIS
Version: 6.5.6940.0
Component: Microsoft Exchange Information Store
Message: Error <error code> while disabling rule on public folder with rule ID <rule id>. The folder ID of the public folder is in the data section of this event.
   
Explanation

This event indicates that there was a problem executing a rule on a public folder. Public Folders can have rules associated with them by using the Folder Assistant option in the properties of the Public Folder. For example, a Public Folder can have a rule where all incoming mail to that Public Folder is forwarded to a mailbox.

This error can be caused if there is a problem executing the rule. Typically, this will occur if the mailbox to which this Public Folders mail is being forwarded has some limits set on it. You may observe an event 8528 that indicates that the mailbox in question has exceeded its limits.

   
User Action

Check the rules of the Public Folders rules. If the rules are forwarding mails to other mailboxes, check these other mailboxes and ensure that they have not reached any limits.

Related:

An interoperability error occurred with entity {object name}. A reliable transport service element (RTSE) error occurred. Session protocol data unit (SPDU) decode failure occurred. Server error code {error code} was detected at offset {value}. Node label {name}. Control block index {index name}. [{value}{value}{value}{value}] (14)

Details
Product: Exchange
Event ID: 1147
Source: MSExchangeMTA
Version: 6.0
Component: Message Transfer Agent
Symbolic Name: MTA01147
Message: An interoperability error occurred with entity {object name}. A reliable transport service element (RTSE) error occurred. Session protocol data unit (SPDU) decode failure occurred. Server error code {error code} was detected at offset {value}. Node label {name}. Control block index {index name}. [{value}{value}{value}{value}] (14)
   
Explanation
The diagnostics logging levels of the message transfer agent (MTA) Interface and Interoperability categories should be increased to create interoperability logs.These logs are text logs that consist of the binary contents of communication among MTAs in different sites and between MTA and client applications within a site. They are stored in the \Exchsrvr\Mtadata directory. The current log is always named Bf0.log. Prior logs are named Bfx.log, where x increases as the age of the log increases.
   
User Action
To help Microsoft Product Support Services track down the problem, create log files. See Knowledge Base articles Q163032 and Q168906 for more information. To create Ap*.log files, in the Diagnostics Logging tab of the Server Properties dialog box, select MSExchangeMTA and set the logging level of the Interoperability and Interface categories to Maximum. To create Bf*.log files, set the logging level of the APDU and X.400 Service categories to Maximum.Save all MTA log files (mtadata\*.log), Event Viewer output, and database files. Contact Microsoft Product Support Services.You can enable text event log files (Ev*.log) by modifying the Registry. Contact Microsoft Product Support Services for assistance.

Related: