Event 40966: "A program fault has raised an exception" - Archiving and Provisioning Tasks stop running
Article ID: 100034071
Updated On:
Description
Error Message
Event ID 40966:A program fault has raised an exception. Exception: A connection was successfully established with the server, but then an error occurred during the pre-login handshake, (provider: SSL Provider, error: 0- the client and server cannot communicate, because they do not possess a common algorithm.)
Either of the following solutions can be used to work around this scenario:
- Leave TLS 1.0 enabled on the server.
Set the following registry key: HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\ClientEnabled = 1
- If TLS 1.0, SSL, and all earlier protocols are disabled on the server, the security option System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing must be enabled on the server.
Note: More information about this security option may be found in the following Microsoft article: https://technet.microsoft.com/en-us/library/jj852197(v=ws.11).aspx
Cause
As part of best practice, secure environments typically disable TLS (Transport Layer Security) 1.0 and newer protocols are used to secure communications between production servers.
However, Enterprise Vault uses the Microsoft OLE DB Provider for SQL Server for communication with the Enterprise Vault SQL databases. When TLS 1.0, SSL, and earlier security protocols are disabled on the server, any connection to a SQL database using the Microsoft OLE DB Provider for SQL Server fails. This scenario also applies for any connection attempts to any SQL database using Microsoft OLE DB Provider for SQL Server, not just for connections by Enterprise Vault.
Issue/Introduction
Both the Archiving and Provisioning Tasks stop and do not process items. When checking the Enterprise Vault, Event Viewer Event 40966 is displayed.
Was this article helpful?
Yes
No
Powered by
