A Windows Rights Management Services (RMS) server may not service all requests (832954)



The information in this article applies to:

  • Microsoft Windows Rights Management Services (RMS) for Windows Server 2003

Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

SYMPTOMS

A Microsoft Windows Rights Management Services (RMS) server may not service certification requests or licensing requests. Additionally, you may notice the following errors in the Windows event log:
Connection was closed
Unspecified error

CAUSE

This behavior may occur if the RMS server uses the Windows integrated authentication scheme. A server that uses this scheme does not reuse a Transmission Control Protocol (TCP) connection unless the connection is closed and the corresponding port is not used for four minutes. If the server receives many requests in a short time, all TCP ports may be used, and the server may not service all requests. As a result, you receive the errors that are mentioned in the "Symptoms" section.

RESOLUTION

To resolve this problem, set the wait delay period for the RMS server to the minimum value. If you do this, the server can service more requests by reusing previously-used ports more rapidly.

To set the wait delay period for the RMS server, follow these steps:

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
  1. Use Registry Editor to create the following REG_DWORD registry entry:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\TcpTimedWaitDelay
  2. Set the corresponding registry value to 0x1e ( 30 in decimal notation).

    Note This value corresponds to the minimum wait delay period of 30 seconds.

Modification Type:MinorLast Reviewed:12/18/2003
Keywords:kbRegistry kbAuthentication kbService kbServer kberrmsg kbprb KB832954 kbAudDeveloper