How can I debug loading test data with Microsoft.VisualStudio.TestTools.WebTesting.DataSource?

Question

For our performance tests we are loading test date from a CSV-File. Up until recently this worked fine. But now we get the following error:

Could not run Web test 'XXXXX' on agent 'XXXXXX': Could not access table 'Test#csv' in data source 'dsTest' of test 'XXXXXX,XXXXXX': The OleDbParameterCollection only accepts non-null OleDbParameter type objects, not SqlParameter objects.

And I have no idea where this is coming from. I was able to pinpoint the problem to the following statement:

c#
    using WebTesting = Microsoft.VisualStudio.TestTools.WebTesting;

    [WebTesting.DataSource (
        dataSourceName: "dsTest",
        providerName: "Microsoft.VisualStudio.TestTools.DataSource.CSV",
        connectionString: "|DataDirectory|\\data\\Test.csv",
        WebTesting.DataBindingAccessMethod.Sequential,
        WebTesting.DataBindingSelectColumns.SelectOnlyBoundColumns,
        tableName: "Test#csv")]

But this is an annotation and now I'm at a loss on how to debug loading the data.

Update 1

I checked reading the CSV manually and that works as expected:

c#
    var dataTable = new Csv.CsvDataTable();

    dataTable.ReadFromFile(
        filename: System.IO.Directory.GetCurrentDirectory() + "\\Test.csv", 
        setheaderfromfirstrow: true, 
        encoding: System.Text.Encoding.UTF8, 
        delimeter: ',',
        quote : '"',  
        emptyLineBehavior: Csv.EmptyLineBehavior.NoColumns);

Update 2

Just to be sure it's not and I18N Problem I replaced the , with ;. Same result. So now I wonder if even the header line is read.

PS: The CSV-file itself contains confidential data — I would have to sanitise it and then it's not the same file any more. I would really prefer if I'm helped along finding the error.

Update 3

Considering it might be an version mismatch after the lates Visual Studio update I updated all nuget packages. That make no difference either.

Update 4

We have one virtual machine on which the performance tests are still working and I have noticed that this virtual machine is using “Windows Server 2016 Datacenter” while all the other virtual machines which don't work any more have been update to “Windows Server 2019 Datacenter”.

This reframes the problem and I might have to ask the question again.

Answer 1

As a workaround pending a fix from Microsoft to this VS2019 issue, the tests work in VS2017.

Answer 2

To anyone who finds this, there is a patch coming:
https://developercommunity.visualstudio.com/t/1610-upgrade-breaks-MSTest-DataSourceAt/1468870