Failed to load cryptographic provider '%.*ls' due to an invalid Authenticode signature or invalid file path. Check previous messages for other failures.
SQL Server was unable to load the cryptographic provider listed in the error message. There are several Win API failures which might cause this error. The ring buffer contains the name of the failed API and the Windows error code returned by the API. To get more information, query the sys.dm_os_ring_buffers view using the following query.
To investigate the problem, search for the Windows error code in MSDN (http://msdn.microsoft.com/). Resolve the error, or contact Microsoft CSS for more information. If you need to contact CSS, collect the following information for our support staff.
The error log showing the failed to load cryptographic provider error.
The output from the following statement:
Try to collect the ring buffer information promptly as ring buffer information can be lost during a restart.