A transport-level error has occurred when receiving results from S

I am setting up a replication of a database which has 364 tables. The size of
this database is close to 150 GB.
I have one server as publisher.
I have another server which i am using for distributor as well as
subscriber. Both servers are seperate physical servers.
I tried replicating 2 tables, I don;' see any issue. They replicate with no
issue. However, when I try to replicate all tables I get this error on
snapshot agent.
Please advise if any one has already seen this problem. My both servers are
on SQL 2005 SP2.
Error messages:
Message: A transport-level error has occurred when receiving results from
the server. (provider: TCP Provider, error: 0 - The specified network name is
no longer available.)
Command Text:
set nocount on
declare @.source_object_id int
declare @.sync_object_id int
set @.source_object_id = object_id(quotename(@.source_object_schema) + N'.' +
quotename(@.source_object_name))
set @.sync_object_id = object_id(quotename(@.sync_object_schema) + N'.' +
quotename(@.sync_object_name))
declare @.partitioning_column sysname
declare @.partitioning_column_type sysname
declare @.qualified_source_object_name nvarchar(600)
declare @.partitioning_column_collation sysname
declare @.partitioning_index_name sysname
set @.qualified_source_object_name = quotename(@.source_object_schema) + N'.'
+ quotename(@.source_object_name)
set @.partitioning_column = null
set @.partitioning_column_type = null
set @.partitioning_index_name = null
select @.partitioning_column = sc.name,
@.partitioning_column_type = st.name,
@.partitioning_column_collation = sc.collation,
@.partitioning_index_name = si.name
from sysindexes si
inner join syscolumns sc
on index_col(@.qualified_source_object_name, si.indid, 1) = sc.name
inner join systypes st
on sc.xtype = st.xusertype
where si.id = @.source_object_id
and sc.id = @.sync_object_id
and si.indid = 1
and st.name in (N'uniqueidentifier', N'bit', N'tinyint', N'smallint',
N'int', N'smalldatetime', N'real', N'money', N'datetime', N'float', N'bit',
N'decimal', N'numeric', N'smallmoney', N'bigint', N'varbinary', N'varchar',
N'binary', N'char', N'timestamp', N'nvarchar', N'nchar')
and (@.use_primary_key_only = 0 or si.status & 2048 = 2048)
if @.partitioning_column is not null
begin
select @.partitioning_index_name, @.partitioning_column,
@.partitioning_column_type, @.partitioning_column_collation
dbcc show_statistics(@.qualified_source_object_name,
@.partitioning_index_name)
end
Parameters: @.source_object_name = E_QRTZ_TRIGGER_LISTENERS
@.source_object_schema = dbo
@.sync_object_name = syncobj_0x3238314643373630
@.sync_object_schema = dbo
@.use_primary_key_only = 1
Stack: at
Microsoft.SqlServer.Replication.AgentCore.ReMapSql Exception(SqlException e,
SqlCommand command)
at
Microsoft.SqlServer.Replication.AgentCore.AgentExe cuteReader(SqlCommand
command, Int32 queryTimeout, CommandBehavior commandBehavior)
at
Microsoft.SqlServer.Replication.AgentCore.ExecuteW ithOptionalResults(CommandSetupDelegate
commandSetupDelegate, ProcessResultsDelegate processResultsDelegate, Int32
queryTimeout, CommandBehavior commandBehavior)
at
Microsoft.SqlServer.Replication.AgentCore.ExecuteW ithOptionalResults(CommandSetupDelegate
commandSetupDelegate, ProcessResultsDelegate processResultsDelegate)
at
Microsoft.SqlServer.Replication.Snapshot.SqlServer .ArticleBcpPartitioningResolver.GatherBaseTableSta tistics()
at
Microsoft.SqlServer.Replication.Snapshot.SqlServer .ArticleBcpPartitioningResolver.ResolveArticleBcpP artitioningUsingKeyDistributionHistogram(BaseArtic leWrapper article, Boolean usePrimaryKeyOnly)
at
Microsoft.SqlServer.Replication.Snapshot.SqlServer .ArticleBcpPartitioningResolver.ResolveArticleBcpP artitioning(BaseArticleWrapper
article, Boolean usePrimaryKeyOnly)
at
Microsoft.SqlServer.Replication.Snapshot.SqlServer .BcpLoadHintAndPartitioningResolutionWorkerThreadP rovider.DoWork(WorkItem workItem)
at
Microsoft.SqlServer.Replication.WorkerThread.NonEx ceptionBasedAgentThreadProc()
at Microsoft.SqlServer.Replication.WorkerThread.Agent ThreadProc()
at
Microsoft.SqlServer.Replication.AgentCore.BaseAgen tThread.AgentThreadProcWrapper() (Source: MSSQLServer, Error number: 64)
Get help: http://help/64
Server NTFWEPSQLT1, Level 20, State 0, Line 0
A transport-level error has occurred when receiving results from the server.
(provider: TCP Provider, error: 0 - The specified network name is no longer
available.) (Source: MSSQLServer, Error number: 64)
Get help: http://help/64
Sr DBA
Pier 1 Imports
mabbas@.Pier1.com
You had a network failure in the middle of your snapshot distribution. This
should clear the next time it runs. You might want to run ping -t to watch
to see how lossy your link is.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Moh" <mabbas@.Pier1.com> wrote in message
news:B877BD9F-EE3C-456E-87A7-64BB17FC5C11@.microsoft.com...
>I am setting up a replication of a database which has 364 tables. The size
>of
> this database is close to 150 GB.
> I have one server as publisher.
> I have another server which i am using for distributor as well as
> subscriber. Both servers are seperate physical servers.
> I tried replicating 2 tables, I don;' see any issue. They replicate with
> no
> issue. However, when I try to replicate all tables I get this error on
> snapshot agent.
> Please advise if any one has already seen this problem. My both servers
> are
> on SQL 2005 SP2.
> --
> Error messages:
> Message: A transport-level error has occurred when receiving results from
> the server. (provider: TCP Provider, error: 0 - The specified network name
> is
> no longer available.)
> Command Text:
> set nocount on
> declare @.source_object_id int
> declare @.sync_object_id int
> set @.source_object_id = object_id(quotename(@.source_object_schema) + N'.'
> +
> quotename(@.source_object_name))
> set @.sync_object_id = object_id(quotename(@.sync_object_schema) + N'.' +
> quotename(@.sync_object_name))
> declare @.partitioning_column sysname
> declare @.partitioning_column_type sysname
> declare @.qualified_source_object_name nvarchar(600)
> declare @.partitioning_column_collation sysname
> declare @.partitioning_index_name sysname
> set @.qualified_source_object_name = quotename(@.source_object_schema) +
> N'.'
> + quotename(@.source_object_name)
> set @.partitioning_column = null
> set @.partitioning_column_type = null
> set @.partitioning_index_name = null
> select @.partitioning_column = sc.name,
> @.partitioning_column_type = st.name,
> @.partitioning_column_collation = sc.collation,
> @.partitioning_index_name = si.name
> from sysindexes si
> inner join syscolumns sc
> on index_col(@.qualified_source_object_name, si.indid, 1) = sc.name
> inner join systypes st
> on sc.xtype = st.xusertype
> where si.id = @.source_object_id
> and sc.id = @.sync_object_id
> and si.indid = 1
> and st.name in (N'uniqueidentifier', N'bit', N'tinyint',
> N'smallint',
> N'int', N'smalldatetime', N'real', N'money', N'datetime', N'float',
> N'bit',
> N'decimal', N'numeric', N'smallmoney', N'bigint', N'varbinary',
> N'varchar',
> N'binary', N'char', N'timestamp', N'nvarchar', N'nchar')
> and (@.use_primary_key_only = 0 or si.status & 2048 = 2048)
> if @.partitioning_column is not null
> begin
> select @.partitioning_index_name, @.partitioning_column,
> @.partitioning_column_type, @.partitioning_column_collation
> dbcc show_statistics(@.qualified_source_object_name,
> @.partitioning_index_name)
> end
> Parameters: @.source_object_name = E_QRTZ_TRIGGER_LISTENERS
> @.source_object_schema = dbo
> @.sync_object_name = syncobj_0x3238314643373630
> @.sync_object_schema = dbo
> @.use_primary_key_only = 1
> Stack: at
> Microsoft.SqlServer.Replication.AgentCore.ReMapSql Exception(SqlException
> e,
> SqlCommand command)
> at
> Microsoft.SqlServer.Replication.AgentCore.AgentExe cuteReader(SqlCommand
> command, Int32 queryTimeout, CommandBehavior commandBehavior)
> at
> Microsoft.SqlServer.Replication.AgentCore.ExecuteW ithOptionalResults(CommandSetupDelegate
> commandSetupDelegate, ProcessResultsDelegate processResultsDelegate, Int32
> queryTimeout, CommandBehavior commandBehavior)
> at
> Microsoft.SqlServer.Replication.AgentCore.ExecuteW ithOptionalResults(CommandSetupDelegate
> commandSetupDelegate, ProcessResultsDelegate processResultsDelegate)
> at
> Microsoft.SqlServer.Replication.Snapshot.SqlServer .ArticleBcpPartitioningResolver.GatherBaseTableSta tistics()
> at
> Microsoft.SqlServer.Replication.Snapshot.SqlServer .ArticleBcpPartitioningResolver.ResolveArticleBcpP artitioningUsingKeyDistributionHistogram(BaseArtic leWrapper
> article, Boolean usePrimaryKeyOnly)
> at
> Microsoft.SqlServer.Replication.Snapshot.SqlServer .ArticleBcpPartitioningResolver.ResolveArticleBcpP artitioning(BaseArticleWrapper
> article, Boolean usePrimaryKeyOnly)
> at
> Microsoft.SqlServer.Replication.Snapshot.SqlServer .BcpLoadHintAndPartitioningResolutionWorkerThreadP rovider.DoWork(WorkItem
> workItem)
> at
> Microsoft.SqlServer.Replication.WorkerThread.NonEx ceptionBasedAgentThreadProc()
> at Microsoft.SqlServer.Replication.WorkerThread.Agent ThreadProc()
> at
> Microsoft.SqlServer.Replication.AgentCore.BaseAgen tThread.AgentThreadProcWrapper()
> (Source: MSSQLServer, Error number: 64)
> Get help: http://help/64
> Server NTFWEPSQLT1, Level 20, State 0, Line 0
> A transport-level error has occurred when receiving results from the
> server.
> (provider: TCP Provider, error: 0 - The specified network name is no
> longer
> available.) (Source: MSSQLServer, Error number: 64)
> Get help: http://help/64
> --
> Sr DBA
> Pier 1 Imports
> mabbas@.Pier1.com
|||Hilary - Why then it always works when I replicate any small database or same
data base with few articles. I see no time outs when ping during replication.
Sr DBA
Pier 1 Imports
mabbas@.Pier1.com
"Hilary Cotter" wrote:

> You had a network failure in the middle of your snapshot distribution. This
> should clear the next time it runs. You might want to run ping -t to watch
> to see how lossy your link is.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Moh" <mabbas@.Pier1.com> wrote in message
> news:B877BD9F-EE3C-456E-87A7-64BB17FC5C11@.microsoft.com...
>
>
|||It really looks like a network failure somewhere. The ping-t command should
reveal network hiccups occurring during the snapshot application.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Moh" <mabbas@.Pier1.com> wrote in message
news:C3B863FA-723D-4781-9A99-99FCA2DDB364@.microsoft.com...[vbcol=seagreen]
> Hilary - Why then it always works when I replicate any small database or
> same
> data base with few articles. I see no time outs when ping during
> replication.
> --
> Sr DBA
> Pier 1 Imports
> mabbas@.Pier1.com
>
> "Hilary Cotter" wrote:
|||Actually, the SQL Server could think it's under a DOS attack and start
killing off connections.
Check out section 5.1 of
http://download.microsoft.com/download/f/1/0/f10c4f60-630e-4153-bd53-c3010e4c513b/ReadmeSQLEXP2005.htm#sse_dbengine
for more information.
On Mar 19, 1:02 pm, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:
> It really looks like a network failure somewhere. The ping-t command should
> reveal network hiccups occurring during the snapshot application.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTShttp://www.indexserverfaq.com
> "Moh" <mab...@.Pier1.com> wrote in message
> news:C3B863FA-723D-4781-9A99-99FCA2DDB364@.microsoft.com...
>
>
>
>
>
>
>
>
>
> - Show quoted text -