Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Replication Publication issue Expand / Collapse
Author
Message
Posted Thursday, January 13, 2011 2:14 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, January 31, 2011 1:20 PM
Points: 6, Visits: 34
We are seeing some issue with publication

When i launch replicaiton monitor, i see that status of pulications is 'Retrying failed command'

And when i look under the Agent Tab, and open the job snapshot agent which has a status 'Retrying failed command', the last action message is below. Can anyone guide how to fix this issue?


Message: There is not enough space on the disk.
Stack: at Microsoft.SqlServer.Replication.Snapshot.SqlServer.NativeBcpOutProvider.ThrowNativeBcpOutException(CConnection* pNativeConnectionWrapper)
at Microsoft.SqlServer.Replication.Snapshot.SqlServer.NativeBcpOutProvider.BcpOut(String strBcpObjectName, String strBcpObjectOwner, String strBaseBcpObjectName, Boolean fUnicodeConversion, String strDataFile, String strLoadOrderingHint, String strWhereClause, Boolean useTableLockHint, Int32 bcpFileFormatVersion)
at Microsoft.SqlServer.Replication.Snapshot.SqlServer.BcpOutThreadProvider.DoWork(WorkItem workItem)
at Microsoft.SqlServer.Replication.WorkerThread.NonExceptionBasedAgentThreadProc()
at Microsoft.SqlServer.Replication.AgentCore.BaseAgentThread.AgentThreadProcWrapper() (Source: MSSQLServer, Error number: 0)

Publication Type: Transactional

Thanks
Anita

Post #1047579
Posted Thursday, January 13, 2011 3:23 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, December 1, 2014 12:34 PM
Points: 177, Visits: 362
try running SQL Profiler with the error message options turned on, it is likely trying to insert and existing record or something like that.
Post #1047617
Posted Thursday, January 13, 2011 3:46 PM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: 2 days ago @ 8:02 AM
Points: 2,049, Visits: 3,596
It looks like it is dying on the snapshot. Can you right click on the publication and select "View Snapshot Agent Status". If that looks ok, then it is having a problem with applying the snapshot on the subscriber. Based on the error it also looks like you are out of space for that database. Have you checked that?



David

@SQLTentmaker
SQL Tentmaker
“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
Post #1047635
Posted Thursday, January 13, 2011 3:54 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, December 1, 2014 12:34 PM
Points: 177, Visits: 362
Yeah,

Forget what I said, when the snapshot is being created take a look at how much free space there is on the device where the snapshot is going.

If you have already created your snapshot and this is happening after that, take a look at your subscriber and see if it is having space issues.
Post #1047640
Posted Friday, January 14, 2011 1:08 PM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Friday, November 7, 2014 12:18 PM
Points: 413, Visits: 1,438
David Benoit (1/13/2011)
It looks like it is dying on the snapshot. Can you right click on the publication and select "View Snapshot Agent Status". If that looks ok, then it is having a problem with applying the snapshot on the subscriber. Based on the error it also looks like you are out of space for that database. Have you checked that?



Yeah, here is the message: Message: There is not enough space on the disk.
Post #1048160
Posted Sunday, February 5, 2012 5:20 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, December 15, 2014 1:45 PM
Points: 7, Visits: 121
It is the space issue, Even I encountered the same problem with Transaction Replication and resolved it doing below:-

Cause:- The Snapshot you are taking in any drive, there is not enough space to hold the snapshot of your Publication. Published Articles size are bigger than space available in disk...

Steps:- 1. Check in which Drive your snapshot is getting stored, Right click on concern Publication --> Properties --> Snapshot --> Locations Of Snapshot files, there you will see one of the check box is selected "Put Files in the default folder' and "Put Files in Following Folder' with local or network mapped path.

2. Get the path and go to Drive and see how much disk space available there in that drive, that must be less than your Published Articles in that Publication...

3. Once you verified this and in order to run everything once again fine you need to free/make enough space in that Drive. Or point your Publication Snapshot to stored in other drive where you think enough space present...If changing drive path, change by Un checking 'Default Folder check box' and Checking 'Put files in following folder' Check box.

4. After doing above try taking Snapshot again, it wont throw same error again if you have pointed drive really having enough space.

Plz try this and do let me know if this doesn't work.
Thanks.

SurendraP..
Post #1246983
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse