locked
snapshot agent having the error message : The specified network name is no longer available RRS feed

  • Question

  • hi folks:

     Our snapshot replication is on a cluster server. Recently, I start to see errors from snapshot agent

    Error message below:

    Error messages:

    Message: The specified network name is no longer available.
    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)
    Get help: http://help/0

    Does that mean the drive snapshot files sits on has some issue? how to confirm it? 

     Thanks

     Hui


    --Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

    Saturday, September 3, 2016 6:12 AM

Answers

  • Thanks Martin. Seem it might be related to disk being filled up. The System Admin has increased disk space and after that, I do not see these type of errors again...

    --Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

    Monday, September 12, 2016 4:37 PM

All replies

  • it stopped around 82%

    picture below


    --Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

    Saturday, September 3, 2016 6:17 AM
  • Check your cluster logs and see if there was a failover at the same time.

    The disk will go offline for a short time while the resource fails over from one node to the other and I don;t believe that the snapshot agent has any great retry logic built in to cover this event.

    If there was a failover then investigate the cause of that - if it wasn't a failed disk then you should be OK to restart the snapshot agent


    Martin Cairney SQL Server MVP

    Saturday, September 3, 2016 7:50 AM
  • Thansk Martin. I checked the cluster logs, nothing suspicious during the time when the error "the specific network name no longer available "  pops up or around... no fail over occurred either.

    --Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

    Saturday, September 3, 2016 8:05 AM
  • H Cat_Ca,

    The BCP which is performing looks like its quite massive and dont know about inside of configuration from where to where & locations/what files..etc.. that is trying to perform the operations..according to the message- incase if any very minor n/w Glitch(n/w packets drops) also can contribute here & its quite very difficult to trace it out. hence we might need to change the way that we trying to execute ..like break it an lower chunk & schedule during non business hours .

    Also below links helps further --- please check if those helps..

    Snapshot Considerations
    https://technet.microsoft.com/en-us/library/ms151791.aspx

    Reduce Transactional Replication Synchronization Time By Applying Snapshots Manually
    http://www.kendalvandyke.com/2008/10/reduce-transactional-replication.html

    Compressed Snapshots
    https://technet.microsoft.com/en-us/library/ms151773.aspx

    Alternate Snapshot Folder Locations
    https://technet.microsoft.com/en-us/library/ms151327.aspx

    Frequently Asked Questions for Replication Administrators
    https://msdn.microsoft.com/en-us/library/ms151740.aspx


    Regards, S_NO "_"

    Sunday, September 4, 2016 5:00 AM
  • Have a look in the Windows logs on each cluster node as well.   Are you saving the snapshot locally on the cluster? If not then it may have been an issue on the server you are exporting to.

    Also - could the disk have filled up?

    The snapshot and bcp process should be fine and can handle large volumes - the message certainly suggests something at the infrastructure level that has had an issue - I don't know what your infrastructure is like so can't suggest other places to look for now.


    Martin Cairney SQL Server MVP

    Sunday, September 11, 2016 11:32 PM
  • This is occuring during the snapshot generation process. The network name error means that the publisher can't connect to the distirbutor.

    This looks like a transient network issue. Is it reproducible and does it fail at the same point?


    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

    Monday, September 12, 2016 1:40 PM
    Answerer
  • Thanks Martin. Seem it might be related to disk being filled up. The System Admin has increased disk space and after that, I do not see these type of errors again...

    --Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

    Monday, September 12, 2016 4:37 PM