Fatal Network Error 4014 when writing big BLOB chunks

Using the SqlClient provider I'm trying to write big datachunks of maybe 20 MB each to SQL server to store in BLOBs using blobColumn.Write(...) using .NET 2.0 dbcommand object calling a Stored procedure

CREATE PROCEDURE [dbo].[putBlobByPK]

(

@.id dKey

, @.value VARBINARY(MAX)

, @.offset bigint

, @.length bigint

, @.ModDttm dModDttm OUT

, @.ModUser dModUser OUT

, @.ModClient dModClient OUT

, @.ModAppl dModAppl OUT

)

....

When doing this I can do this exactly 3 times than the application hangs (for ever).

When looking in the SQL Server log, I find the following to errors:

Error: 4014, Severity: 20, Status: 2.

A fatal error occurred while reading the input stream from the network. The session will be terminated.

I don't get this error on the client! OK, the session died.

What may be the problem?

I write big chunks like this to avoid many writes as the data shall be replicated later using peer to peer replication. And the more writes used for writing the total BLOB the more huge becomes the transaction log of the subscriber database.

TIA

Hannoman

After rebooting all machines (client and server) this didn't happen any more. And the client has a problem with a deferred installation - when starting the test application MSI installer tries to install something but isn't successfull. It seems, that this causes the hanging of the client machine.sql

Fake "Broken connection" error

I get the following error when running a particular query, although I know
for sure the server and network are working properly:
"[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken"
Is this a hint that something else might be wrong with my sql server?
Any funky characters in the query? If memory servers correctly thats the
message I got when I had a } one time.
"Ken Abe" <KenAbe@.discussions.microsoft.com> wrote in message
news:42E86DB8-21EE-4D35-854A-0D73B416BF9B@.microsoft.com...
>I get the following error when running a particular query, although I know
> for sure the server and network are working properly:
>
> "[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken"
>
> Is this a hint that something else might be wrong with my sql server?
>
>
|||Hi Chris,
Thank you very much for your reply. No, the query contains no funky
characters such as '{'. If it did that should return a different kind of
error, shouldn't it?
"ChrisR" wrote:

> Any funky characters in the query? If memory servers correctly thats the
> message I got when I had a } one time.
>
> "Ken Abe" <KenAbe@.discussions.microsoft.com> wrote in message
> news:42E86DB8-21EE-4D35-854A-0D73B416BF9B@.microsoft.com...
>
>
|||Not sure as it's been a while...
"Ken Abe" <KenAbe@.discussions.microsoft.com> wrote in message
news:14502176-0C71-4B79-941C-8EF965238B15@.microsoft.com...[vbcol=seagreen]
> Hi Chris,
> Thank you very much for your reply. No, the query contains no funky
> characters such as '{'. If it did that should return a different kind of
> error, shouldn't it?
> "ChrisR" wrote:

Fake "Broken connection" error

I get the following error when running a particular query, although I know
for sure the server and network are working properly:
"[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckFor
Data
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken"
Is this a hint that something else might be wrong with my sql server?Any funky characters in the query? If memory servers correctly thats the
message I got when I had a } one time.
"Ken Abe" <KenAbe@.discussions.microsoft.com> wrote in message
news:42E86DB8-21EE-4D35-854A-0D73B416BF9B@.microsoft.com...
>I get the following error when running a particular query, although I know
> for sure the server and network are working properly:
>
> "[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckF
orData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken"
>
> Is this a hint that something else might be wrong with my sql server?
>
>|||Hi Chris,
Thank you very much for your reply. No, the query contains no funky
characters such as '{'. If it did that should return a different kind o
f
error, shouldn't it?
"ChrisR" wrote:

> Any funky characters in the query? If memory servers correctly thats the
> message I got when I had a } one time.
>
> "Ken Abe" <KenAbe@.discussions.microsoft.com> wrote in message
> news:42E86DB8-21EE-4D35-854A-0D73B416BF9B@.microsoft.com...
>
>|||Not sure as it's been a while...
"Ken Abe" <KenAbe@.discussions.microsoft.com> wrote in message
news:14502176-0C71-4B79-941C-8EF965238B15@.microsoft.com...[vbcol=seagreen]
> Hi Chris,
> Thank you very much for your reply. No, the query contains no funky
> characters such as '{'. If it did that should return a different kind
of
> error, shouldn't it?
> "ChrisR" wrote:
>

Fake "Broken connection" error

I get the following error when running a particular query, although I know
for sure the server and network are working properly:
"[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken"
Is this a hint that something else might be wrong with my sql server?Any funky characters in the query? If memory servers correctly thats the
message I got when I had a } one time.
"Ken Abe" <KenAbe@.discussions.microsoft.com> wrote in message
news:42E86DB8-21EE-4D35-854A-0D73B416BF9B@.microsoft.com...
>I get the following error when running a particular query, although I know
> for sure the server and network are working properly:
>
> "[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken"
>
> Is this a hint that something else might be wrong with my sql server?
>
>|||Hi Chris,
Thank you very much for your reply. No, the query contains no funky
characters such as '{'. If it did that should return a different kind of
error, shouldn't it?
"ChrisR" wrote:
> Any funky characters in the query? If memory servers correctly thats the
> message I got when I had a } one time.
>
> "Ken Abe" <KenAbe@.discussions.microsoft.com> wrote in message
> news:42E86DB8-21EE-4D35-854A-0D73B416BF9B@.microsoft.com...
> >I get the following error when running a particular query, although I know
> > for sure the server and network are working properly:
> >
> >
> > "[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
> > (CheckforData()).
> > Server: Msg 11, Level 16, State 1, Line 0
> > General network error. Check your network documentation.
> >
> > Connection Broken"
> >
> >
> > Is this a hint that something else might be wrong with my sql server?
> >
> >
> >
>
>|||Not sure as it's been a while...
"Ken Abe" <KenAbe@.discussions.microsoft.com> wrote in message
news:14502176-0C71-4B79-941C-8EF965238B15@.microsoft.com...
> Hi Chris,
> Thank you very much for your reply. No, the query contains no funky
> characters such as '{'. If it did that should return a different kind of
> error, shouldn't it?
> "ChrisR" wrote:
>> Any funky characters in the query? If memory servers correctly thats the
>> message I got when I had a } one time.
>>
>> "Ken Abe" <KenAbe@.discussions.microsoft.com> wrote in message
>> news:42E86DB8-21EE-4D35-854A-0D73B416BF9B@.microsoft.com...
>> >I get the following error when running a particular query, although I
>> >know
>> > for sure the server and network are working properly:
>> >
>> >
>> > "[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
>> > (CheckforData()).
>> > Server: Msg 11, Level 16, State 1, Line 0
>> > General network error. Check your network documentation.
>> >
>> > Connection Broken"
>> >
>> >
>> > Is this a hint that something else might be wrong with my sql server?
>> >
>> >
>> >
>>