Code Coverage - Error
Hi! Can you help me make the Code coverage tab work?
I edited the registry and rebooted my server in accordance with the error, but it did not resolve this issue.
I have the following message on the Code coverage tab:
System.IO.FileNotFoundException: Could not
load file or assembly 'Microsoft.SqlServer.TransactSql.ScriptDom,
Version=15.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of
its dependencies. The system cannot find the file specified. File name:
'Microsoft.SqlServer.TransactSql.ScriptDom, Version=15.0.0.0, Culture=neutral,
PublicKeyToken=89845dcd8080cc91' at
SQLCover.Parsers.StatementParser.GetChildStatements(String script, Boolean
quotedIdentifier) at SQLCover.Source.DatabaseSourceGateway.GetBatches(List`1
objectFilter) at SQLCover.CodeCoverage.GenerateResults(List`1 filter, List`1
xml) at SQLCover.CodeCoverage.Stop() at
RedGate.SQLTest.tSQLt.Cover.SqlCoverTracker.Stop() WRN: Assembly binding logging
is turned OFF. To enable assembly bind failure logging, set the registry value
[HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some
performance penalty associated with assembly bind failure logging. To turn this
feature off, remove the registry value
[HKLM\Software\Microsoft\Fusion!EnableLog].
Thank you!
Tagged:
Answers
@terrybuda
Thank you for reaching out on the Redgate forums and sorry to hear about your SQL Test error.
Are you able to confirm your SQL Test & SSMS installed versions.
Has this been a recent occurrence when opening the Code Coverage tab, since updating SQL Test to a newer version?
Can you confirm if this happens on any database that you try to run it on? Or is it just on this one in particular?
Are you able to try conducting an un-install/re-install of SQL Test to see if it resolves this issue.
Latest two versions of SQL Test can be accessed here
https://download.red-gate.com/checkforupdates/SQLTest/SQLTest_4.1.3.1995.exe
https://download.red-gate.com/checkforupdates/SQLTest/SQLTest_4.1.2.1837.exe
Providing both in the event this has been caused by the latest version and you can downgrade to a previously working instance.
- Our Windows 2016 servers run:
Microsoft SQL Server Management Studio 13.0.16106.4Microsoft Data Access Components (MDAC) 10.0.14393.0
Microsoft MSXML 3.0 6.0
Microsoft .NET Framework 4.0.30319.42000
Operating System 6.3.14393
Thanks in advance for any help you can provide!
Hi @terrybuda
Thanks for your patience with this as I've heard from the developers.
They've confirmed that a fix for this should have been released in the latest version.
Can you try upgrading and let me know if that helps you out?
Download Link: https://download.red-gate.com/checkforupdates/SQLTest/SQLTest_4.1.4.2200.exe