none
pull replication error

    Question

  • hi,

    one of my coworker setup a bunch of pull transactional replication.  The snaps for this publication is compressed and is stored on the publisher+distributor.  There are 30GBs of disk space atm. all the publication are working fine except for one.  I keep getting the following error

    Replication-Replication Distribution Subsystem: agent ABCDE39-pubname-subscribername-104 failed. The process encountered operating system error '՝'.

    When i look at the replication, I see:

    Command attempted:

    if @@trancount > 0 rollback tran (Transaction sequence number: 0x0001A1AD000337A201D700000000, Command ID: 3275)

    Error messages:

    • The process encountered operating system error 'ؓ'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20034) Get help: http://help/MSSQL_REPL20034
    • There is not enough disk space on the disk.  (Source: MSSQL_REPL, Error number: MSSQL_REPL112) Get help: http://help/MSSQL_REPL112
    • The process encountered operating system error 'ؓ'. (Source: MSSQL_REPL, Error number: MSSQL_REPL1779) Get help: http://help/MSSQL_REPL1779

    at first I thought that the compressed cab file would be stored in the temp directory on the subscriber and that doesn't have a lot of space so I changed the system environment variable from c:\windows\temp to v:\temp.  This shut it up for a while but then the message started to show up again.

    I have been monitoring the drive where repldata is stored but i don't see it reducing in size.  Does replication not even bother with using the disk space if the size isn't big enough, like the restore function?

    if this has to do with the amount of free space where repldata reside, if I change its location, do i need to stop replication first or will it pick up that info automatically?

    any help would be greatly appreciated.

    thx

    • Moved by Naomi N Thursday, March 28, 2013 10:07 PM Better answer can be here
    Thursday, March 28, 2013 9:55 PM

All replies

  • Thanks for the move Naomi.

    Update: I went ahead and changed the location of the repldata to another drive, setup the share w/ all the necessary permission and still got the above error.

    • Edited by Red8Rain Thursday, March 28, 2013 10:38 PM
    Thursday, March 28, 2013 10:17 PM
  • Hi RedRain,

    Thank you for your question. 
    I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated. 
    Thank you for your understanding and support.


    Maggie Luo
    TechNet Community Support

    Wednesday, April 03, 2013 9:02 AM
  • Is there enough space on the v drive? The error is clearly related to space issues. Also are you doing compression? The files might end up being compresses in %temp% which by default is on the c drive.

    looking for a book on SQL Server 2008 Administration? http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search? http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

    Wednesday, April 03, 2013 2:40 PM
  • Hi Hilary,

    there are over 150GB of free space on the V: drive and 25GB of free space on the C:\ drive on the subscriber.

    I did a bit more digging and the table in question is only 1.5GB so either the C: or V: drive has more than enough disk space.

    Additionally, it might be that the error message is generic.  When looking at the snapshot that's being delivered to the subscriber, it always get stuck at table XYZ.  I removed table XYZ from the snapshot, took another one and send it over.  It went find until it hit another table, ABC, and failed w/ similar error

    Replication-Replication Distribution Subsystem: agent ABCDE39-pubname-subscribername-104 failed. The process encountered operating system error '՝'.

    both table XYZ and ABC total 4GB.

    Only thing I haven't done is delete the publication and recreate it but I don't think that will do much.

    Wednesday, April 03, 2013 3:03 PM
  • How about space on the subscriber?

    Can you replicate these tables individually?

    What is the error number you are getting - to me they are showing up as non-ASCII characters.


    looking for a book on SQL Server 2008 Administration? http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search? http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

    Wednesday, April 03, 2013 3:32 PM
  • Hilary,

    that's the free space on the subscriber.  the publisher has about the same.

    here's a screenshot of the error

    I have asked my dev to look at the table to see if the data is messed up but they haven't responded yet.  The thing is that we have 18 other databases with the same exact schema and this one is the only one that is giving me problem.

    all other tables were able to replicate except for ABC and XYZ.

    Wednesday, April 03, 2013 4:40 PM
  • 1. What is the error number you see after "The process encountered operating system error" ?

    2. Can you enable verbose logging for distribution agent and share the output?


    Thank you,

    Karthick P.K |My blogs|My Scribbles|Twitter|My Facebook Group|

    www.Mssqlwiki.com

    Please click the Mark as answer button and vote as helpful if this reply solves your problem

    Monday, May 20, 2013 6:15 AM