Post reply

ConnectionRead (WrapperRead())...General network error

  • August 6, 2004 at 11:33 am

    #161300

    I am getting strange error when I try to backup database from the job and here is the background.
     

    • It is the msdb backup job that runs as domain account and it is backing up to nework drive.
    • This job never had problem until after I apply SP3a
    • All user database have same problem except master database backup job is running without problem.
    • If I take the backup syntax from job and run it under SQL Analyzer, it works.
    • And here is the error message "Executed as user: Domain\ServiceAccount. 11 percent backed up. [SQLSTATE 01000] (Message 3211)  21 percent backed up. [SQLSTATE 01000] (Message 3211)  31 percent backed up. [SQLSTATE 01000] (Message 3211)  41 percent backed up. [SQLSTATE 01000] (Message 3211)  51 percent backed up. [SQLSTATE 01000] (Message 3211)  61 percent backed up. [SQLSTATE 01000] (Message 3211)  70 percent backed up. [SQLSTATE 01000] (Message 3211)  81 percent backed up. [SQLSTATE 01000] (Message 3211)  91 percent backed up. [SQLSTATE 01000] (Message 3211)  Processed 6064 pages for database 'msdb', file 'MSDBData' on file 1. [SQLSTATE 01000] (Message 4035)  100 percent backed up. [SQLSTATE 01000] (Message 3211)  ConnectionRead (WrapperRead()). [SQLSTATE 01000] (Message 258)  General network error. Check your network documentation. [SQLSTATE 08S01] (Error 11)  Processed 4 pages for database 'msdb', file 'MSDBLog' on file 1. [SQLSTATE 01000] (Error 4035).  The step failed."

    I did all different approch like messing arround Shared memeory Protocal, setting up TCP/IP alias from SQL Client Networ Utility, messing around security group policy, etc and all did not work and I realized that master backup job is running and one of the new security changes that SP3a did was "corss-database ownership chanining" and I did enabled it per recommendation so I disabled it and all worked right away. I enabled back to see if that casued the problem is it failed again.

    Anyone has any idea why that can cause above error? Any known KB article?

  • August 9, 2004 at 8:00 am

    This was removed by the editor as SPAM

  • August 12, 2004 at 4:55 am

    #518629

    please check that:

    1-  you have a Space on your Hard Drive

    2- the log file of DB is not huge in size

    3- do u have SP3a installed ? it solve many problems with SQL Server

     also install MDAC 2.7 SP1 on all clients and cerver machines

    I hope this help u.

     


    Alamir Mohamed
    Alamir_mohamed@yahoo.com

  • August 12, 2004 at 8:05 am

    #518672

    Hi Alamir,

    Answer to your question

    1. yes, there are planty of HDD space

    2. nop, less then 100MB

    3. yes, this is caused by SP3a and I will check and try SP1 on server since there is no client involved.

    Thank you for your input..

  • August 30, 2004 at 12:05 am

    #521016

    Have you checked to see what your CPU load is?  I had the same problem when trying to load a huge amount of data and CPU was hitting 100%.

    I ended up removing the "Boost SQL Server Priority on Windows" setting and it fixed it.

    Angela

  • August 30, 2004 at 9:31 am

    #521078

    Hi Angela,

    I suspected that as well but the CPU load is always under 20%.. this box is dedicated to replication distribution box so there isn't much things going on..

    After I changed to cross database ownership, the job worked for a couple of days and starting to fail again so I did all different combination for backup query..

    And I found one interesting thing. I changed the backup job not to run directly from job schedule but made DTS package and scheduled it and now backup is working again and it's been 3 days so far.

    Any idea? Why backup job doesn't work from direct sql job schedule but work from DTS and schedule it.

     

  • August 30, 2004 at 7:23 pm

    #521148

    Sounds like it is definately a network problem.  Have you monitored whats happening on the network and the NIC/s on the SQL box when you're running the backup?

    Do you get the same problem backing up the databases to local disk?  I suspect you won't.

    I think its probably just coincedence that it's running ok at the moment as a DTS package.

  • August 31, 2004 at 11:10 am

    #521264

    I tried Local Drive but it failed every other times as well.. I set to try every 1 minitues and tested on Local drive..

    I also tested DTS package to run every minitues but that succeed.

  • October 8, 2004 at 2:50 pm

    #526027

    Microsoft has released a hotfix that may address this. If you are running Windows Server 2003, try the following hotfix (827452):

    http://support.microsoft.com/default.aspx?scid=kb;en-us;827452

    Hope this helps,

    Jeff

  • October 11, 2004 at 7:39 am

    #526146

    Thank you and I already know about that bug. And it is not Windows Server 2003. :-/

  • December 8, 2004 at 5:51 am

    #533015

    Please check http://www.sql-server.org/WrapperRead_Error____Fixed-4356163-3717-a.html

    Regards,

    Bart Michiels.

  • December 8, 2004 at 6:26 am

    #533019

    Thank you so much Bart,.. this does sounds like the solution.

  • February 19, 2005 at 11:05 am

    #543221

    We are experiencing the same issue, but when I tried to use the link suggested by Bart:

    http://www.sql-server.org/WrapperRead_Error_Fixed-4356163-3717-a.html

    it did not bring me anywhere.

    Is there a typo in the link or is there a different link?

    Can you correct the link or just send me the information in attachment form. My email is

    vkomarovsky@donlen.com

     

  • February 21, 2005 at 4:23 am

    #543294

    Apperantly the page doens't exist anymore. I have included in this post the most important information but more import the fix you will have to buy from Microsoft is http://support.microsoft.com/default.aspx?scid=kb;en-us;827452

    After I 've installed this (MDAC 2.8) hotfix my are problems were solved....

    Bart.

    Some extract of the HTML page to which I referred in the past:

    Title: FIX: General Network Error When You Try to Back up or Restore a SQL
    Server Database on a Computer That Is Running Windows Server 2003
     ---------------------------
     Don't let the title fool you.
    We where getting desperate.  We have 46 servers, running on NT4 (SP6) with
    SQL7 (SP4).
    Our development systems started to have wrapperread errors very often, and
    in fact, we could not complete our backups, unless we did them via QA and
    TCP/IP connections.
     
    I found the above KB article, and called to get the hotfix.
    They would not give it to us right away, as it specifically stated that it
    was a Windows 2003 and SQL2000 issue.
     
    But after an hour of talking on the phone with multiple support people, it
    was determined that the .dll listed in the article was specific to MDAC 2.8
    and not SQL or Windows versions.
     
    So they sent us the HotFix...
    I am happy to say that it has fixed our WrapperRead errors.  Both for
    Queries from remote terminals, and Internal Server Processes.
     
    If you are having this error, I HIGHLY recommend that you installed MDAC 2.8
    and obtain this Hotfix from MS.
    According to the rep, he is submitting a request to have the KB altered to
    reflect that this error could also occur on other combinations, or
    specifically MDAC 2.8 and named pipes.

  • February 21, 2005 at 7:53 am

    #543323

    Thanks a lot!

Viewing 15 posts - 1 through 15 (of 17 total)

You must be logged in to reply to this topic. Login to reply