Event ID 1009 — RemoteApp and Desktop Connection Configuration

Event ID 1009 — RemoteApp and Desktop Connection Configuration

Published: January 8, 2010

Applies To: Windows Server 2008 R2

RemoteApp and Desktop Connection is configured by using the Control Panel.

Event Details

Product: Windows Operating System
ID: 1009
Source: Microsoft-Windows-RemoteApp and Desktop Connections
Version: 6.1
Symbolic Name: TSWORKSPACE_UPDATE_INCOMPLETE_WARNING
Message: Some available resources could not be downloaded. Resources available: %5 Resources downloaded: %6 Resources not downloaded: %7
Contact your workplace administrator for assistance.Connection name: %1Connection URL: %2Error code: %3, %4

Resolve
Locate related events

This issue happens when a file did not download correctly. To troubleshoot this issue further, look for other events in the event log that provide more information. For more information, see Event 1017 or Event 1018 in the Microsoft-Windows-RemoteApp and Desktop Connections event source.

Verify

To verify that RemoteApp and Desktop Connection is configured correctly, you should start a RemoteApp program that is published by using RemoteApp and Desktop Connection.

To start a RemoteApp program that is published by using RemoteApp and Desktop Connection:

  1. On a client computer, click Start, point to All Programs, point to RemoteApp and Desktop Connections, point to Enterprise Remote Access, and then click a RemoteApp program.
  2. Verify that the RemoteApp program opens successfully.

Related Management Information

RemoteApp and Desktop Connection Configuration

Remote Desktop Services

Related:

Receive connector %1 rejected an incoming connection. The maximum number of connections (%2) for this connector has been reached.

Details
Product: Exchange
Event ID: 1009
Source: MSExchangeTransport
Version: 8.0
Symbolic Name: SmtpReceiveMaxConnectionReached
Message: Receive connector %1 rejected an incoming connection. The maximum number of connections (%2) for this connector has been reached.
   
Explanation

This Warning event indicates that a Receive connector has reached the maximum permitted number of simultaneous incoming connections. This value is specified by the MaxInboundConnection parameter on the Receive connector. The default value is 5000.

   
User Action

To resolve this warning, increase the value of the MaxInboundConnection parameter on the Receive connector by using the Set-ReceiveConnector cmdlet in the Exchange Management Shell. The valid input range for this parameter is 1 to 2147483647. To disable the inbound connection limit on a Receive connector, enter a value of unlimited.

For more information, see Set-ReceiveConnector.

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:

Failed to access the metabase, error code is .

Details
Product: Exchange
Event ID: 1009
Source: MSExchangeMU
Version: 6.5.6940.0
Component: Microsoft Exchange Metabase Update
Message: Failed to access the metabase, error code is <error code>.
   
Explanation

The metabase update agent cannot access the Internet Information Services (IIS) metabase. You will receive the following phrase in the Event Description: Failed to access the metabase, error code is [Error code number] (Error text.).

One possible cause is that IIS Admin Service is not started or is disabled. There could also be a problem with IIS, such as a corrupted metabase.bin file. Commonly, this event indicates that the metabase has become corrupt.

Root causes for MSExchangeMU Event ID 1009 are many and are associated with specific error codes. The most common error codes are listed as follows:

  • Cause 1 – Failed to access the metabase, error code is 80004002 (Invalid Signature.).
  • Cause 2 – Failed to access the metabase, error code is 80090006 (Invalid Signature.).
  • Cause 3 – Failed to access the metabase, error code is 80040154 (Class not registered.).
  • Cause 4 – Failed to access the metabase, error code is 8009000f (Object already exists.).
  • Cause 5 – Failed to access the metabase, error code is 80070422 (The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.).
   
User Action

Verify that the IIS Admin Service is running correctly. Specific resolutions associated with the listed causes are as follows:

  • Resolution 1 – Remove the existing installation of the IIS computer that runs Exchange Server. Make sure that the metabase.bin file is gone. If it is not, manually remove it. Reinstall IIS on the computer. Reinstall the same operating system service pack and any operating system hotfixes. Reinstall Exchange Server over its existing installation. (Do NOT uninstall Exchange Server — simply perform a reinstall.) Reinstall any Exchange service packs and hotfixes. Another alternative is to restore the metabase.
  • Resolution 2 – Same as Resolution 1.
  • Resolution 3 – Restore from the metabase from last good online backup. If you do not have a backup, perform the steps in Resolution 1. If you still get the same error, you may need to reinstall the operating system and Exchange server.
  • Resolution 4 – Remove IIS and delete all the files in the MachineKeys directory except the newest one (and not the backups). Restart the computer. Install IIS (by using Add/Remove Programs in Control Panel). For further information, see Microsoft Knowledge Base article PRB: Error Message “0x8009000F = Object Already Exists” 271865.KB.EN-US.
  • Resolution 5 – This error rarely occurs. If you receive this error, follow the steps in Resolution 1.

Related:

Failed to access the metabase, error code is error code.

Details
Product: Exchange
Event ID: 1009
Source: MSExchangeMU
Version: 6.5.0000.0
Message: Failed to access the metabase, error code is error code.
   
Explanation
The Metabase Update Agent cannot access the IIS metabase.

You will receive the following phrase in the Event Description:  Failed to

access the metabase, error code is [Error code number] (Error text.).

One possible cause is that IISAdmin is not started or is disabled. There may

also be some other problem with Internet Information Services (IIS), such as a

corrupted metabase.bin file. Commonly, this event indicates that the metabase has become corrupt.

Root causes for MSExchangeMU Event ID 1009 are many and are associated with

specific error codes. The most common error codes are listed below:

  • Cause 1 – Failed to access the metabase, error code is 80004002 (Invalid

    Signature.).

  • Cause 2 – Failed to access the metabase, error code is 80090006 (Invalid

    Signature.).

  • Cause 3 – Failed to access the metabase, error code is 80040154 (Class not

    registered.).

  • Cause 4 – Failed to access the metabase, error code is 8009000f (Object already exists.).
  • Cause 5 – Failed to access the metabase, error code is 80070422 (The service cannot be started,either because it is disabled or because it has no enabled

    devices associated

    with it.).

   
User Action

Verify that the IIS Admin Service is running properly. Specific
resolutions associated with the listed causes are as follows:

  • Resolution 1 – Remove the existing installation of the Internet

    Information Services (IIS) computer that runs Exchange Server. Make sure that the metabase.bin file is gone. If it is not, manually remove it. Reinstall IIS on the computer.

    Reinstall the same operating system service pack and any operating system

    hotfixes. Reinstall Exchange Server over its

    existing installation. (Do NOT uninstall Exchange Server — simply perform a

    reinstall.) Reinstall any Exchange service

    packs and hotfixes. Another alternative is to restore the metabase.

  • Resolution 2 – Same as Resolution 1.
  • Resolution 3 – Restore from the metabase from last good online backup. If you do

    not have a backup, perform the steps in

    Resolution 1. If you still get the same error, you may need to reinstall the

    operating system and Exchange server.

  • Resolution 4 – Remove IIS and delete all the files in the MachineKeys directory

    except the newest one (and not the backups).

    Restart the computer. Install IIS (by using Add/Remove Programs in Control

    Panel). For further information, see Knowledge Base

    article PRB: Error Message “0x8009000F = Object Already Exists” 271865.KB.EN-US.

  • Resolution 5 – This error has been found to be rarely seen. If you receive this

    error, follow the steps in Resolution 1.

Related:

The timeout period elapsed prior to the completion of a Transact-SQL statement.

Details
Product: SQL Server Notification Services
Event ID: 1009
Source: NotificationServices
Version: 2.0.9999.9
Message: The timeout period elapsed prior to the completion of a Transact-SQL statement.
   
Explanation
This error occurs when an executing query or stored procedure does not complete within the specified timeout. It typically indicates that SQL Server is too busy. (A different error message is returned if the execution of an event rule or a subscription rule exceeds the timeout specified in the ActionTimeout parameter.)

The event log entry for this error includes the description of the actual error that caused it.

   
User Action
Examine the event log entry for additional information on the action that timed out.

If vacuuming was the cause of the failure then it may be necessary to manually vacuum expired events and notifications by running the NSVacuum stored procedure.

Notification Services uses a timeout value of 30 seconds for many operations. If possible, reduce the processing of the affected action such that it can complete within 30 seconds.

Related:

The Microsoft Exchange Mail Submission Service is currently unable to contact any Hub Transport servers in the local Active Directory site. The servers may be too busy to accept new connections at this time.

Details
Product: Exchange
Event ID: 1009
Source: MSExchangeMailSubmission
Version: 8.0
Symbolic Name: NoActiveBridgeheadServer
Message: The Microsoft Exchange Mail Submission Service is currently unable to contact any Hub Transport servers in the local Active Directory site. The servers may be too busy to accept new connections at this time.
   
Explanation

This Warning event indicates that the computer that is running the Mailbox server role cannot submit messages to a computer that is running the Microsoft® Exchange Server 2007 Hub Transport server role. Additionally, there are Hub Transport servers in the same Active Directory® directory service site as the Mailbox server that can respond to the request. This event may occur if any of the following conditions is true:

  • The Microsoft Exchange Transport service is not running on a Hub Transport server.

  • The MAPI RPC connection is blocked between the Mailbox server and Hub Transport server.

  • The Hub Transport server has reached the maximum number of submission threads that the server can have open at the same time to send messages from mailboxes. This behavior may occur if the computer that is running the Mailbox server role has multi-processors and the computer that is running the Hub Transport server role is a single-processor. In this configuration, the Mailbox server may submit more e-mail traffic than the Hub Transport server can process.

In Exchange 2007, a new notification service called the Microsoft Exchange Mail Submission service runs on the mailbox server and notifies an available Hub Transport server in the same Active Directory site in which the service is running that messages are available for retrieval from a sender’s Outbox. The Microsoft Exchange Mail Submission service tries to distribute message submissions equally across all available Hub Transport servers that are available in the same Active Directory site in which the service is running.

The Microsoft Exchange Mail Submission service obtains a list of Hub Transport servers in the same Active Directory site as the mailbox from which a Store driver retrieves messages. A round-robin process determines which bridgehead server is notified. The store driver on the Hub Transport server that is notified retrieves the message and adds the message to the transport pipeline by putting it in the Submission queue on the Hub Transport server that was notified. If no bridgehead servers are available, messages cannot be added to the transport pipeline.

For more information, see Transport Architecture.

   
User Action

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

  • Make sure that the Microsoft Exchange Transport Service is enabled and running on the Hub Transport server.

  • Make sure that no firewalls filter network data or block MAPI remote procedure call (RPC) traffic between the Mailbox server and Hub Transport server.

  • Make sure that the Mailbox server and the Hub Transport server are not deployed in a perimeter network.

  • If this frequently occurs, consider whether you should add more processors on the Hub Transport server. You can also increase the value of MaxConcurrentMailboxSubmissions by using the Set-TransportServer cmdlet. For more information, see Set-TransportServer.

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:

Direct Push has detected that the configuration value for the minimum heartbeat interval is set to a value higher than the maximum heartbeat interval. Therefore, the default minimum heartbeat interval of “%1” seconds and the default maximum heartbeat interval of “%2” seconds will be used until the next time that the computer is restarted. To avoid seeing this message in the future, use Internet Information Services (IIS) Manager to correct these values. Reset the values to the default, or use other acceptable values.

Details
Product: Exchange
Event ID: 1009
Source: MSExchange ActiveSync
Version: 8.0
Symbolic Name: InvalidHbiLimits
Message: Direct Push has detected that the configuration value for the minimum heartbeat interval is set to a value higher than the maximum heartbeat interval. Therefore, the default minimum heartbeat interval of “%1” seconds and the default maximum heartbeat interval of “%2” seconds will be used until the next time that the computer is restarted. To avoid seeing this message in the future, use Internet Information Services (IIS) Manager to correct these values. Reset the values to the default, or use other acceptable values.
   
Explanation

This Warning event indicates that Exchange Direct Push has detected that the configuration value for the minimum heartbeat interval is set to a value higher than the maximum heartbeat interval. This can only be caused if these settings were manually changed. This configuration is not valid. Exchange ActiveSync reverted to the default values for minimum heartbeat interval and maximum heartbeat interval. The default minimum heartbeat interval is 60 seconds (1 minute). The default maximum heartbeat interval is 3,540 seconds (59 minutes). Exchange ActiveSync will use the default settings until the next time that the server that is running Microsoft® Exchange Server is restarted.

We recommend that you only change these values if that has been recommended by Microsoft Product Support Services.

   
User Action

To resolve this warning, manually change the settings to the default settings or other acceptable values:

  1. Start Internet Information Services (IIS) Manager.

  2. In the console tree, click Web Sites, and then click Default Web Site.

  3. Right-click Microsoft-Server-ActiveSync, and then click Properties.

  4. On the ASP.NET tab, click Edit Configuration.

  5. On the General tab, under Application settings, take one of these steps:

    • Configure the MinHeartbeatInterval and MaxHeartbeatInterval settings to match the default values.

    • Configure values that are not default. When you use values that are not default, you must configure the MinHeartbeatInterval to a value lower than the MaxHeartbeatInterval. You must also configure values in the acceptable range. The acceptable range of values for the MinHeartbeatInterval is 1 to 3,540. The acceptable range of values for the MaxHeartbeatInterval is 2 to 3,540.

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: