当前位置：文江博客话题详情

代理消息代码 20084。进程无法连接到订阅服务器

发布于 2024-08-19 22:52:21 字数 1890 浏览 7 评论 0原文

所有运行 SQL 2005

SQL Server (NOLA) 的服务器都会复制到 35 个远程位置 (StoreXX)。

本周早些时候，一份出版物开始出现连接问题到 35 个远程位置中的 30 个，错误为：

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

日期 2/4 /2010 10:00:01 AM

日志作业历史记录（NOLA-Closing_Balance-CB 默认为 Stores-R99S-

Store1-2790）

步骤 ID 2

服务器 NOLA

作业名称 NOLA-Closing_Balance-CB 默认为 Stores-R99S-Store1-2790

步骤名称运行代理。

持续时间 00:31:47

Sql 严重性 0

Sql 消息 ID 0

操作员通过电子邮件发送

操作员网络发送

操作员

尝试分页重试 0

消息

2010-02-04 16:31:48.081 从代理配置文件获取的参数值：

                    -bcpbatchsize 2147473647 

                    -commitbatchsize 100 

                    -commitbatchthreshold 1000 

                    -historyverboselevel 2 

                    -keepalivemessageinterval 300 

                    -logintimeout 15 

                    -maxbcpthreads 1 

                    -maxdeliveredtransactions 0 

                    -pollinginterval 5000 

                    -querytimeout 1800 

                    -skiperrors 

                    -transactionsperhistory 100

2010-02-04 16:31： 48.081 连接到订阅服务器“R99S-Store1”

2010-02-04 16:31:48.440 代理消息代码 20084。进程无法

连接到订阅服务器“R99S-Store1”。

2010-02-04 16:31:48.472 类别：NULL

来源：Microsoft SQL Native Client

编号：10054

消息：TCP 提供程序：现有连接被强行关闭远程主机。 2010-02-04 16:31:48.472 类别：NULL

来源：Microsoft SQL 本机客户端

编号：10054

消息：通信链接失败

2010-02-04 16:31:48.472 代理失败，状态为“重试”。尝试稍后运行代理。

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 问题仅在于这一篇出版物&不是所有订阅。我已删除有问题的订阅&已读，同样的问题。

我创建了另一个出版物（相同的 dB）&订阅（相同& 新订阅者）具有相同的结果（上面的错误）。

现在事情变得奇怪了……

我在两个出版商上使用不同的 dB 创建了一个新出版物 &订户和一切正常。

我已经让网络人员检查了他们需要检查的内容以及有谷歌搜索直到我脸色发青。

谁能给我对这个问题的任何见解。

阿希亚，拉里……

原文

All servers running SQL 2005

SQL server (NOLA) replicates to 35 remote locations (StoreXX).

Earlier this week, one publication started having problems connecting
to 30 of the 35 remote locations, with an error of:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Date 2/4/2010 10:00:01 AM

Log Job History (NOLA-Closing_Balance-CB Defaults to Stores-R99S-

Store1-2790)

Step ID 2

Server NOLA

Job Name NOLA-Closing_Balance-CB Defaults to Stores-R99S-Store1-2790

Step Name Run agent.

Duration 00:31:47

Sql Severity 0

Sql Message ID 0

Operator Emailed

Operator Net sent

Operator Paged

Retries Attempted 0

Message

2010-02-04 16:31:48.081 Parameter values obtained from agent profile:

                    -bcpbatchsize 2147473647 

                    -commitbatchsize 100 

                    -commitbatchthreshold 1000 

                    -historyverboselevel 2 

                    -keepalivemessageinterval 300 

                    -logintimeout 15 

                    -maxbcpthreads 1 

                    -maxdeliveredtransactions 0 

                    -pollinginterval 5000 

                    -querytimeout 1800 

                    -skiperrors 

                    -transactionsperhistory 100

2010-02-04 16:31:48.081 Connecting to Subscriber 'R99S-Store1'

2010-02-04 16:31:48.440 Agent message code 20084. The process could

not connect to Subscriber 'R99S-Store1'.

2010-02-04 16:31:48.472 Category:NULL

Source: Microsoft SQL Native Client

Number: 10054

Message: TCP Provider: An existing connection was forcibly closed by
the remote host.
2010-02-04 16:31:48.472 Category:NULL

Source: Microsoft SQL Native Client

Number: 10054

Message: Communication link failure

2010-02-04 16:31:48.472 The agent failed with a 'Retry' status. Try to
run the agent at a later time.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The problem is only this one publication & not all subscriptions. I
have deleted a problem subscription & readded, same problem.

I have created another publication (same dB) & subscription (same &
new subscribers) with the same results (error above).

Now is where it gets weird…..

I created a new publication using a different dB on both the publisher
& subscriber & everything works fine.

I have had the network folks check what they need to check & have
googled until I am blue in the face.

Can anyone give me any insight into this issue.

AHIA,
Larry….

分享到QQ

分享到微博