InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSat, 18 May 2013 09:15:05 GMT20http://www.sqlservercentral.com/Forums/Topic1047579-1550-1.aspxIt is the [b]space issue[/b], 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..:-)Sun, 05 Feb 2012 05:20:49 GMTSurendra Patlehttp://www.sqlservercentral.com/Forums/Topic1047579-1550-1.aspx[quote][b]David Benoit (1/13/2011)[/b][hr]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? [/quote]Yeah, here is the message: [b]Message: There is not enough space on the disk.[/b]Fri, 14 Jan 2011 13:08:49 GMTWildcathttp://www.sqlservercentral.com/Forums/Topic1047579-1550-1.aspxYeah, 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.Thu, 13 Jan 2011 15:54:45 GMTHenry Treftzhttp://www.sqlservercentral.com/Forums/Topic1047579-1550-1.aspxIt 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? Thu, 13 Jan 2011 15:46:37 GMTDavid Benoithttp://www.sqlservercentral.com/Forums/Topic1047579-1550-1.aspxtry running SQL Profiler with the error message options turned on, it is likely trying to insert and existing record or something like that.Thu, 13 Jan 2011 15:23:42 GMTHenry Treftzhttp://www.sqlservercentral.com/Forums/Topic1047579-1550-1.aspxWe are seeing some issue with publicationWhen 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: TransactionalThanksAnitaThu, 13 Jan 2011 14:14:21 GMTanitadba2010