Inconsistent encryption settings between an archiving server and the storage server can cause Enterprise Vault Services to shutdown.
Article ID: 100052997
Updated On:
Description
Error Message
The event logs of the archiving server may show numerous of the following event's:
Event ID: 3433 Could not build a saveset for the message titled [RE: Inflation Worries] in Mailbox [/o=VTAS/ou=Heathrow/cn=Recipients/cn=John Smith], function [IStorageArchiveV80::Store()] failed. |Error: 0x80070057 |Description: The parameter is incorrect. |
Additionally, a dtrace of the ArchiveTask on the archiving server will show the following repeatedly:
CSavesetPersist::ResetStorage Failed to delete file: C:\users\app\local\Temp\~DF44C5C4F627DBBB56.TMP Status:0x80070020
As the archiving task continues to run and items in the temp location build up eventually the drive may run out of space and shut down the EV servers generating an error as follows:
Type : Error
Date : 3/27/2022
Time : 12:46:02 AM
Event : 4141
Source : Enterprise Vault
Category : Admin Service
User : N/A
Computer : evserver1.ev.local
Description:
Insufficient diskspace is available on drive C: for the Enterprise Vault to run
Enterprise Vault will now be shut down; to correct this problem, delete any unwanted files and restart Enterprise Vault
Cause
This issue can be caused by inconsistent encryption settings between the archiving server and the storage server.
For instance: The storage server will have the following encryption settings the local security policy.
Local Policies => Security Options => Network Security: Configure encryption types allowed for Kerberos
Defined with the following:
RC4_HMAC_MD5, AES128_HMAC_SHA1, AES256_HMAC_SHA1, Future encryption types
While the Archiving server may have the following encryption settings in it's local security policy.
Local Policies => Security Options => Network Security: Configure encryption types allowed for Kerberos
Defined with the following:
AES128_HMAC_SHA1, AES256_HMAC_SHA1, Future encryption types
Notice: The archiving server does not have RC4_HMAC_MD5 in it's local security policy.
Resolution
To resolve this issue enable RC4_HMAC_MD5 on the local security policy of the Archiving server to match the encryption settings on the local security policy of the storage server.
Issue/Introduction
