Сегодня на забугорном языке!
When you perform a clean installation of Exchange 2000 or you upgrade to Exchange 2000 from Exchange Server 5.5, the installation fails, and you receive the following error message:
Setup failed while installing the subcomponent: Microsoft Exchange Server level objects with the error code 0x80090020 (Please consult the installation logs for a detailed description)
Setup failed while creating Active Directory objects for Microsoft Exchange Server level objects (Error: 0x80090020. An internal error occurred)
In addition, the following entries are logged in the Exchange Server Setup Progress.log file:
[16:47:37] ScInitPasskeys failed with sc = 80090020, dwStatus = 4
[16:47:37] ScMaintainServerKeys (N:\admin\src\libs\exsetup\dsmisc.cxx:32
85) Error code 0X80090020 (32): An internal error occurred.
[16:47:37] Leaving ScMaintainServerKeys
[16:47:37] CAtomServer::ScAddDSObjects (N:\admin\src\udog\exsetdata\components\s
erver\a_server.cxx:392) Error code 0X80090020 (32): An internal error occurred.
[16:47:37] Leaving CAtomServer::ScAddDSObjects
[16:47:37] CBaseAtom::ScAdd (N:\admin\src\udog\setupbase\basecomp\ba
seatom.cxx:867) Error code 0X80090020 (32): An internal error occurred.
[16:47:37] Service = '' CBaseServiceAtom::ScAdd (N:\admin\src\udog\setupbase\basecomp\ba
sesvcatom.cxx:196) Error code 0X80090020 (32): An internal error occurred.
[16:47:37] CAtomServer::ScAdd (N:\admin\src\udog\exsetdata\components\s
erver\a_server.cxx:148) Error code 0X80090020 (32): An internal error occurred.
[16:47:37] mode = 'Install' (61953) CBaseAtom::ScSetup (N:\admin\src\udog\setupbase\basecomp\ba
seatom.cxx:782) Error code 0X80090020 (32): An internal error occurred.
[16:47:49] Setup encountered an error during Microsoft Exchange Messaging and Collaboration Services of Install component task. CBaseComponent::ScSetup (N:\admin\src\udog\setupbase\basecomp\ba
secomp.cxx:1041) Error code 0X80090020 (32): An internal error occurred.
When the error messages occur, Setup cannot continue. If you remove Exchange 2000 completely, remove Internet Information Services (IIS) 5.0, and then reinstall it, Setup does not continue. If you remove these programs, and then reinstall them, you may experience the following symptoms:
Errors occur when you install IIS 5.0.
Encryption of files or folders fails, and the following error messages are displayed:
Error Applying Attributes
An error occurred applying attributes to the file:
[folder or file location]
Keyset does not exist
You may be unable to schedule any tasks or modify the account credentials of an existing task. When you try to create a new scheduled task, you may receive the following error message:
The new task has been created, but may not run because the account information has not been set. Keyset does not exist.
If you try to modify the Account credentials of an existing task, you may receive the following error message:
General Page initialization failed The specific error is: 0x80090016 Keyset does not exist.
When you try to renew a certificate request in IIS to Windows 2000 Certificate server you may receive the following error messages:
Failed to generate the certificate request. An internal error occurred.
You can test this by opening up Certificate manager and selecting New Certificate. You receive the following message:
Windows cannot find a certification authority that can process the request.
Terminal Server licensing service may not start and you may receive the following error messages:
An Error Event occurred. EventID: 0x00000027 (Event ID 39) Event String: Can't generate new public/private keys because of error 'Cannot acquire Crypt Context, error 80090016.'.
An Error Event occurred. EventID: 0x00000025 (Event ID 37) Event String: Can't start Terminal Services Licensing because of error 'Can't initialize Cryptographic - error code 80090016.'
An Error Event occurred. EventID: 0xC0001B70 (Event ID 7024) Event String: The Terminal Services Licensing service terminated with service-specific error 3221291009.
This issue can occur if a registry key exists which modifies the default behavior of the Cryptography APIs. In this case, the Cryptography APIs cannot create the public and private encryption keysets that are necessary to continue the installation.
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 issue:
Click Start, click Run, and then type regedit to open the standard Registry Editor.
Locate and click the following registry key:
Click the Providers key, click Export Registry File on the Registry menu, and then type the location where you want to save this file. Save this file to a location where you can easily access it at a later time if necessary.
Press DELETE, and then click Yes to confirm that you want to delete this registry key.
Restart the server. You are able to perform any of the tasks which were formerly not possible because of the Cryptography APIs issue. These tasks include (but are not limited to):
Encrypting files and folders
Installing IIS 5.0 without any errors
Installing Exchange 2000