Problems if the Cryptography Subsystem Is Damaged (306964)

The information in this article applies to:

Microsoft Windows 2000 Server
Microsoft Windows 2000 Advanced Server
Microsoft Windows 2000 Datacenter Server

This article was previously published under Q306964

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

When you connect from a Terminal Services client to a Windows 2000-based server that is running Terminal Services, the Windows 2000-based server may record either of the following Event IDs:Event Type: Error
Event Source: TermService
Event Category: None
Event ID: 1014
Date: date
Time: time
User: N/A
Computer: COMPUTER

Description: Cannot load illegal module: C:\WINNT\System32\rdpwsx.DLL.Description: The new task has been created, but may not run because the account information could not be set.
The specific error is: 0x80090016: Keyset does not exist

CAUSE

This problem may occur if the Cryptography subsystem is damaged.

RESOLUTION

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. To resolve this problem, repair the Cryptography subsystem:

Start Registry Editor.
Locate the following registry key:
HKEY_USERS\.Default\Software\Microsoft\Cryptography\Providers\Type 001
Click the Providers registry key, and then click Export Registry File on the Registry menu. Select a folder in which to save this file, and then save this file.
After you export the registry key in step 3, delete the Type 001 registry key.
Restart the server.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Modification Type:	Minor	Last Reviewed:	4/28/2003
Keywords:	kbenv kberrmsg kbprb KB306964