Internal Connection Fatal Error

scottnelsonscottnelson Posts: 29
I get this error with SQL Data Compare v5.3.0.68 when I try to compare a large table. It happens right at the very end of the comparison, before it generates any script.

I saw an old post about this which suggested forcing the TCP protocol and an IP address to be used, but that didn't help.

This problem even happens when I try to compare two databases on the same server with SQL Data Compare running locally, on the same box, connecting using tcp:127.0.0.1 as the server name in both cases.

I'm at a loss as to why there is a problem with a local connection, but in any case, I can't actually compare anything with this tool as it fails EVERY SINGLE TIME.

HELP!!!!!!

Comments

  • Brian DonahueBrian Donahue Posts: 6,590 Bronze 1
    Hello,

    Please reference this as a starting point:

    http://support.microsoft.com/kb/328383/

    There is no one solution to fix this problem. It's either because of the SQL Server configuration or the .NET Framework configuration.
  • Brian DonahueBrian Donahue Posts: 6,590 Bronze 1
    Apparently, upgrading to .NET Framework 2.0 fixes this problem.
    If you have Framework 1.1 installed as well as 2.0, you can force Data Compare to use 2.0 by creating a .config file:

    First, create a new text document in the Bundle installation folder (c:\program files\red gate\sql bundle 5). It needs to contain the following:
    <configuration>
    <startup>
    <supportedRuntime version="v2.0.50727"/>
    </startup>
    </configuration>
    Save this as RedGate.SQLDataCompare.UI.exe.config. This will make Data Compare use .NET 2.0, otherwise it will use 1.1 by default.

    Microsoft admit that there could be a problem in ADO .NET 1.1 in the SqlDataReader class. The network protocols change mid-stream when the reader is closed.
  • davebublitzdavebublitz Posts: 12 Bronze 2
    We experienced this exact error today and we have the .NET Framework 2.0 installed on the workstation. We still have a copy of 4.0 and it reported an invalid date problem. We found that somehow we did get an invalid date in row. After removing the one row SQL Data Compare 5 was able to compare and update the tables.

    Perhaps this is the real issue?

    Dave
  • Hi,

    Have you any idea what the contents of that row were? Was the date 'special' in any way?

    Thanks,

    David Atkinson
    Red Gate Software
    David Atkinson
    Product Manager
    Redgate Software
  • davebublitzdavebublitz Posts: 12 Bronze 2
    David,

    Here is what was in one of the date columns:

    -29762-12-16 499:03:07.627

    I would say it is "special"! This happened on a development server so we don't know how this data was created.

    Dave
Sign In or Register to comment.