Event ID 201 — BITS Client Connectivity

Event ID 201 — BITS Client Connectivity

Updated: December 13, 2007

Applies To: Windows Server 2008

In order for the BITS client to successfully complete files transfers, the client must be able to connect to a BITS server that is available on the network.

Event Details

Product: Windows Operating System
ID: 201
Source: Microsoft-Windows-Bits-Client
Version: 7.0
Symbolic Name: EVT_PROXY_FAILURE
Message: The BITS job named “%1” was unable to contact any HTTP proxy server in its proxy list. This may indicate a problem with the proxy servers or with the client’s network configuration. An administrator should verify whether the proxy list is correct. BITS will periodically try to transfer the job. The HTTP proxy list is “%6”. The proxy-bypass list is “%7”.

Resolve
Ensure that the HTTP proxy is configured correctly

To resolve this issue, check the proxy settings for the job by using the BITSAdmin tool and correct settings if needed.

BITSAdmin is a command-line tool that you can use to create download or upload jobs and monitor their progress. The \Support\Tools\Support.cab file on the operating system installation CD contains the BITSAdmin tool.

To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

To ensure that the HTTP proxy is configured correctly:

  1. Open an elevated command prompt. To open an elevated command prompt, click Start, right-click Command Prompt, and then click Run as Administrator.
  2. Type:
    • BITSADMIN /GETPROXYUSAGE job
    • BITSADMIN /GETPROXYLIST job
    • BITSADMIN /GETPROXYBYPASSLIST job
  3. Check whether the proxy settings are appropriate for your environment.
  4. If the proxy settings are incorrect, use the BITSAdmin tool to configure the correct proxy settings.
  5. To display usage for BITSAdmin settings, type:
    • BITSADMIN /SETPROXYSETTINGS job usage

The choices for usage are:

  • PRECONFIG: Use the owner’s Internet Explorer defaults.
  • AUTODETECT: Force autodetection of proxy.
  • NO_PROXY: Do not use a proxy server.
  • OVERRIDE: Use an explicit proxy list and bypass list. Must be followed by a proxy list and a proxy bypass list.
  • NULL or “”: May be used for an empty proxy bypass list.

Examples:

  • bitsadmin /setproxysettings MyJob PRECONFIG
  • bitsadmin /setproxysettings MyJob AUTODETECT
  • bitsadmin /setproxysettings MyJob NO_PROXY
  • bitsadmin /setproxysettings MyJob OVERRIDE proxy1:80
  • bitsadmin /setproxysettings MyJob OVERRIDE proxy1,proxy2,proxy3 NULL

Verify

Confirm that the proxy servers support HTTP 1.1 RANGE requests. If RANGE requests are enabled, BITS will automatically retry the job.

 

 

Related Management Information

BITS Client Connectivity

BITS Infrastructure

Related:

Event ID 201 — RD Gateway Server Connections

Event ID 201 — 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: 201
Source: Microsoft-Windows-TerminalServices-Gateway
Version: 6.1
Symbolic Name: AAG_EVENT_NAP_FAILED
Message: The user “%1”, on client computer “%2”, did not meet connection authorization policy requirements and was therefore not authorized to access the RD Gateway server. The following authentication method was attempted: “%3”. The following error occurred: “%5”.

Resolve
Ensure that the client meets the requirements of the RD CAP

To resolve this issue, ensure that the clients meet the requirements of at least one Remote Desktop connection authorization policy (RD CAP).

To determine whether a client meets the requirements of at least one RD CAP, do the following:

  • Check the RD CAP settings on the RD Gateway server. For instructions, see “Check RD CAP settings on the RD Gateway server” later in this topic.
  • Ensure that the local or Active Directory security group specified in the RD CAP exists, and that the user account (and if applicable, the computer account) for the client is a member of the appropriate security group. For instructions for Active Directory security groups, see “Confirm that the Active Directory security group specified in the RD CAP exists, and check account membership for the client in this group.” For instructions for local security groups, see “Confirm that the local security group specified in the RD CAP exists, and check account membership for the client in this group” later in this topic.

Check RD CAP settings on the RD Gateway server

To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

To check RD CAP settings on the RD Gateway server:

  1. Open Remote Desktop Gateway Manager. To open Remote Desktop Gateway Manager, click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Gateway Manager.
  2. In the Remote Desktop Gateway Manager console tree, select the node that represents the local RD Gateway server, which is named for the computer on which the RD Gateway server is running.
  3. In the console tree, expand Policies, and then click Connection Authorization Policies.
  4. In the results pane, in the list of RD CAPs, right-click the RD CAP that you want to check, and then click Properties.
  5. On the Requirements tab, do the following:
    • Under Supported Windows authentication methods, check whether the specified method is compatible with the authentication method used by the client. The user on the client must use the same authentication method (for example, smart card or password) that is specified in the RD CAP.
    • In User group membership (required), note the name of the user group so that you can ensure that the specified user group exists in Active Directory Domain Services or Local Users and Computers. Then, check whether the user account for the client is a member of this group. For instructions for Active Directory security groups, see “Confirm that the Active Directory security group specified in the RD CAP exists, and check account membership for the client in this group.” For instructions for local security groups, see “Confirm that the local security group specified in the RD CAP exists, and check account membership for the client in this group” later in this topic.
    • Under Client computer group membership (optional), check whether a client computer group is specified. If so, note the name of the client computer group so that you can ensure that the specified client computer group exists in Active Directory Domain Services or Local Users and Computers. Then, check whether the computer account for the client is a member of this group.
  6. Click OK.
  7. If the client settings and RD CAP settings are not compatible, do one of the following:
    • Modify the client configuration.
    • Modify the settings of the existing RD CAP.
    • Create a new RD CAP. For information about how to create an RD CAP, see “Create an RD CAP” in the Remote Desktop Gateway Manager Help in the Windows Server 2008 R2 Technical Library (http://go.microsoft.com/fwlink/?LinkId=178452).

After you check RD CAP settings, ensure that the local or Active Directory security group specified in the RD CAP exists, and that the user account (and if applicable, the computer account) for the client is a member of the appropriate security group.

Performing these procedures does not require membership in the local Administrators group. Therefore, as a security best practice, consider performing these tasks as a user without administrative credentials.

Confirm that the Active Directory security group specified in the RD CAP exists, and check account membership for the client in this group

To confirm that the Active Directory security group specified in the RD CAP exists:

  1. On a computer running Active Directory Users and Computers, click Start, click Run, type dsa.msc, and then press ENTER.
  2. In the console tree, expand Active Directory Users and Computers/DomainNode/, where the DomainNode is the domain to which the security group belongs.
  3. Right-click the domain, and then click Find. In the Find Users, Contacts, and Groups dialog box, type the name of the security group that is specified in the RD CAP, and then click Find Now.
  4. If the group exists, it will appear in the search results.
  5. Close the Find Users, Contacts, and Groups dialog box.

To check account membership for the client in this security group:

  1. On a computer running Active Directory Users and Computers, click Start, click Run, type dsa.msc, and then press ENTER.
  2. In the console tree, expand Active Directory Users and Computers/DomainNode/Users, where the DomainNode is the domain to which the user belongs.
  3. In the details pane, right-click the user name, and then click Properties.
  4. On the Member Of tab, confirm that one of the groups listed matches one of the groups that is specified in the RD CAP, and then click OK.
  5. If client computer group membership has also been specified as a requirement in the RD CAP, expand Active Directory Users and Computers/DomainNode/Computers, where the DomainNode is the domain to which the computer belongs.
  6. In the details pane, right-click the computer name, and then click Properties.
  7. On the Member Of tab, confirm that one of the groups listed matches one of the groups that is specified in the RD CAP, and then click OK.

Confirm that the local security group specified in the RD CAP exists, and check account membership for the client in this group

To confirm that the local security group specified in the RD CAP exists, and to check account membership for the client in this group:

  1. On the RD Gateway server, open Computer Management. To open Computer Management, click Start, point to Administrative Tools, and then click Computer Management.
  2. In the console tree, expand Local Users and Groups, and then click Groups.
  3. In the results pane, locate the local security group that has been created to grant members access to the RD Gateway server (the group name or description should indicate whether the group has been created for this purpose).
  4. Right-click the group name, and then click Properties.
  5. On the General tab of the Properties dialog box for the group, confirm that the user account is a member of this group, and that this group is one of the groups that is specified in the RD CAP.
  6. If client computer group membership has also been specified as a requirement in the RD CAP, on the General tab, confirm that the client computer account is also a member of this group, and then click OK.

Verify

To verify that RD Gateway server connectivity is working, examine Event Viewer logs and search for the following event messages.

To perform this procedure, you do not need to have membership in the local Administrators group. Therefore, as a security best practice, consider performing this task as a user without administrative credentials.

To verify that RD Gateway server connectivity is working:

  1. On the RD Gateway server, click Start, point to Administrative Tools, and then click Event Viewer.
  2. In the Event Viewer console tree, navigate to Application and Services Logs\Microsoft\Windows\TerminalServices-Gateway, and then search for the following events:
    • Event ID 101, Source TerminalServices-Gateway: This event indicates that the Remote Desktop Gateway service is running.
    • Event ID 200, Source TerminalServices-Gateway: This event indicates that the client is connected to the RD Gateway server.
    • Event ID 302, Source TerminalServices-Gateway: This event indicates that the client is connected to an internal network resource through the RD Gateway server.

 

Related Management Information

RD Gateway Server Connections

Remote Desktop Services

Related:

Event ID 201 — Task Monitoring and Control

Event ID 201 — Task Monitoring and Control

Updated: December 6, 2007

Applies To: Windows Server 2008

The history of a task is tracked by events. These events can be viewed in Task Scheduler for each task to track when the task was registered, run, and when it completed or failed. The progress of a task can be monitored through its history. A task can be controlled by running or stopping the task manually (on-demand).

Event Details

Product: Windows Operating System
ID: 201
Source: Microsoft-Windows-TaskScheduler
Version: 6.0
Symbolic Name: ACTION_SUCCESS
Message: Task Scheduler successfully completed task “%1” , instance “%3” , and action “%2”.

Resolve

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

Related Management Information

Task Monitoring and Control

Management Infrastructure

Related:

A loop has been detected in the message being transferred in. A non-delivery report was generated with reason code and diagnostic code . [ ] (14)

Details
Product: Exchange
Event ID: 201
Source: MSExchangeMTA
Version: 6.5.6940.0
Component: Microsoft Exchange Message Transfer Agent
Message: A loop has been detected in the message <text> being transferred in. A non-delivery report was generated with reason code <error code> and diagnostic code <error code>. [<value> <value> <value> <value>] (14)
   
Explanation

A loop was detected in the message being transferred in. A non-delivery report (NDR) was generated.

   
User Action

The problem may be the existence of a redundant route located in the Intermediary or Hub Site within the path to the destination site. Examine your routing tables on all of your Exchange servers, particularly those running Exchange 5.5 and older. Use message tracking to help locate the problem.

Related:

%1 (%2) %3The database engine is starting an incremental backup.

Details
Product: Exchange
Event ID: 201
Source: ESE
Version: 8.0
Symbolic Name: START_INCREMENTAL_BACKUP_ID
Message: %1 (%2) %3The database engine is starting an incremental backup.
   
Explanation

This Information event indicates that the database is starting an incremental backup.

   
User Action

No user action is required.

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:

A loop has been detected in the message text being transferred in. A non-delivery report was generated with reason code error code and diagnostic code error code. [valuevaluevaluevalue] (14)

Details
Product: Exchange
Event ID: 201
Source: MSExchangeMTA
Version: 6.5.0000.0
Message: A loop has been detected in the message text being transferred in. A non-delivery report was generated with reason code error code and diagnostic code error code. [valuevaluevaluevalue] (14)
   
Explanation
A loop was detected in the message being transferred in. A non-delivery report (NDR) was generated.
   
User Action
The problem may be the existance of a redundant route located in the

Intermediary or Hub Site within the path to the destination site. Examine your routing tables on all of your Exchange servers, particularly those running Exchange 5.5 and older. Use message tracking to help locate the problem.

Related: