System.Data.SqlClient.SqlException ----A transport-level error has occurred when receiving results from the server

Question

I am getting below issue while performing bulk copy in c#

System.Data.SqlClient.SqlException (0x80131904): A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) ---> System.ComponentModel.Win32Exception (0x80004005): The specified network name is no longer available at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)

using (SqlBulkCopy bulkCopy = new SqlBulkCopy(connectionstr, SqlBulkCopyOptions.KeepIdentity))

        {
            bulkCopy.DestinationTableName = Table;
            bulkCopy.BulkCopyTimeout = 0;

            foreach (DataColumn dccolumn in dccolumns)
            {
                bulkCopy.ColumnMappings.Add(dccolumn.ColumnName, dccolumn.ColumnName);
            }

            // Write from the source to the destination.       


            bulkCopy.WriteToServer(dt);

            bulkCopy.Close();
        }
    }

Please advise.

Answer 1

Hi @prasad k ,

It may not be a statement issue, it could be a network related issue with the service provider, your application is unable to connect the database engine. Check your firewall for any blocked setting and raise it with your service provider.

You also can check your error log first to see if there are any messages which seem to correlate with this error. Try to use DBCC to check if there is any corruption in the database： https://learn.microsoft.com/en-us/sql/t-sql/database-console-commands/dbcc-checkdb-transact-sql?view=sql-server-ver15

Answer 2

Check the SQL Server log to see if there are error messages that correlates in time with these events.

If there is not, I'm inclined to agree with Yufei that it is a network issue.

Answer 3

I've run into this a few times, I work in an environment where my laptop is connecting to several different PC's with the same IP address. Something gets buffered in entityframework or SQL, I'm not sure, but this particular error has always been resolved by restarting both the machine hosting the DB and the machine running the EF commands.