Hello, I got this error message. The server is experiencing issue of service broker suddenly stopping, so we are ruling out all errors at this point. Server is setup with HADR.
Win Server 2008 R2 Ent SP1
SQL 2012 11.0.3349 EntLog Name: Application
Date: 4/18/2013 7:17:26 AM
Event ID: 33081
Task Category: Server
Failed to verify Authenticode signature on DLL 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQL01\MSSQL\Binn\msxmlsql.dll'.
<Provider Name="MSSQL$SQL01" />
<TimeCreated SystemTime="2013-04-18T11:17:26.000000000Z" />
<Data>C:\Program Files\Microsoft SQL Server\MSSQL11.SQL01\MSSQL\Binn\msxmlsql.dll</Data>
- Moved by Maggie LuoMicrosoft community contributor, Moderator Monday, April 22, 2013 7:05 AM
Please click the Mark as answer button and vote as helpful if this reply solves your problem
- Edited by Saurabh Sinha DBAMicrosoft community contributor Friday, April 19, 2013 2:10 AM
Have you found C:\Program Files\Microsoft SQL Server\MSSQL11.SQL01\MSSQL\Binn\msxmlsql.dll? I think msxmlsql.dll is in the C:\Program Files\Microsoft SQL Server\110\Shared. Please check it. You could try to Copying msxmlsql.dll to the Binn folder to see if it would be OK.
Or you could try to repair the SQL Server through SQL Server Installation Center.
TechNet Community Support
I had the Failed to verify Authenticode signature on DLL 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn\odsole70.dll' error when a ETL job was attempting to run. There are .Net/IE STIG hardending restrictions that alter software certificate validation/lookup behavior of the ‘state’ user registry key located @ HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing\. To get around errors referencing Authenticode signatures / generic trust failures log into the server and delete the ‘state’ registry key and then perform the software install, etc. If the failure is happening within an application which runs as a specific user, log into the server as the service account user and then delete the key. The key will automatically be recreated during Group Policy refresh but usually you just need to perform this to get past a certain point with installs/upgrades.