Replication error --> General Network Error with 11 & 08S01 errors

HI ,
I found that the replication keeps failing and have logged the replication -
-> scalaDB_MLD (not the Snapshot or logreader agent of that publication) and
got the followings details :
++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++
Adding alert to msdb..sysreplicationalerts: ErrorId = 48,
Transaction Seqno = 000005ff00005ce7000400000001, Command ID = 5
Message: Replication-Replication Distribution Subsystem: agent MLDDC1-
scalaDB_MLD-SQL1-24 scheduled for retry. General network error. Check your
network documentation.[11/24/2005 3:52:08 PM]MLDDC1.distribution: {call
sp_MSadd_repl_alert(3, 24, 48, 14152, ?, 5, N'MLDDC1', N'scalaDB_MLD',
N'SQL1', N'scalaDB_MLD', ?)}
ErrorId = 48, SourceTypeId = 1
ErrorCode = ''
ErrorText = 'SET ARITHABORT ON SET NUMERIC_ROUNDABORT OFF SET
CONCAT_NULL_YIELDS_NULL ON SET QUOTED_IDENTIFIER ON SET ANSI_NULLS ON SET
ANSI_PADDING ON SET ANSI_WARNINGS ON '
[11/24/2005 3:52:08 PM]MLDDC1.distribution: {call sp_MSadd_repl_error(48, 0,
1, ?, N'', ?)}
Category:COMMAND
Source: Failed Command
Number:
Message: SET ARITHABORT ON SET NUMERIC_ROUNDABORT OFF SET
CONCAT_NULL_YIELDS_NULL ON SET QUOTED_IDENTIFIER ON SET ANSI_NULLS ON SET
ANSI_PADDING ON SET ANSI_WARNINGS ON
ErrorId = 48, SourceTypeId = 5
ErrorCode = '11'
ErrorText = 'General network error. Check your network documentation.'
[11/24/2005 3:52:08 PM]MLDDC1.distribution: {call sp_MSadd_repl_error(48, 0,
5, ?, N'11', ?)}
Category:SQLSERVER
Source: SQL1
Number: 11
Message: General network error. Check your network documentation.
ErrorId = 48, SourceTypeId = 4
ErrorCode = '08S01'
ErrorText = 'Communication link failure'
[11/24/2005 3:52:08 PM]MLDDC1.distribution: {call sp_MSadd_repl_error(48, 0,
4, ?, N'08S01', ?)}
Category:ODBC
Source: ODBC SQL Server Driver
Number: 08S01
Message: Communication link failure
ErrorId = 48, SourceTypeId = 4
ErrorCode = '08S01'
ErrorText = 'Communication link failure'
[11/24/2005 3:52:08 PM]MLDDC1.distribution: {call sp_MSadd_repl_error(48, 0,
4, ?, N'08S01', ?)}
Category:ODBC
Source: ODBC SQL Server Driver
Number: 08S01
Message: Communication link failure
[11/24/2005 3:52:08 PM]SQL1.scalaDB_MLD: exec dbo.sp_MSupdatelastsyncinfo
N'MLDDC1',N'scalaDB_MLD', N'', 0, 5, N'General network error. Check your
network documentation.'
Disconnecting from Subscriber 'SQL1'
Disconnecting from Distributor 'MLDDC1'
Disconnecting from Distributor History 'MLDDC1'
The agent failed with a 'Retry' status. Try to run the agent at a later time.
++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++
i could see there is ODBC SQL Server Driver that caused the communication
link failure, so i have manually created a SQL SERVER odbc link from the data
sources and it seems that i could connect
i have checked the event viewer but could not see any particular details
where it can show connectivity issue
in fact the error happens intermittenly , but previously there's no change of
the settings and it could work
Wherelse can i check to be able to resolve this error once & for all ?
I am using SQL Server 2000 , SP3a , TCP/IP protocol using the default port#
1433
appreciate ur advise
tks & rdgs
Message posted via http://www.droptable.com
Hi,
Refering to the same issue below : i could see the agent profile details
(default) as below
BcpBatchSize - 100000
CommitBatchSize - 100
CommmitBatchThreshold - 1000
Are those in bytes and shld any of the values be decreased/increased ?
tks & rdgs
maxzsim wrote:
>HI ,
> I found that the replication keeps failing and have logged the replication -
>-> scalaDB_MLD (not the Snapshot or logreader agent of that publication) and
>got the followings details :
>+++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++
> Adding alert to msdb..sysreplicationalerts: ErrorId = 48,
>Transaction Seqno = 000005ff00005ce7000400000001, Command ID = 5
>Message: Replication-Replication Distribution Subsystem: agent MLDDC1-
>scalaDB_MLD-SQL1-24 scheduled for retry. General network error. Check your
>network documentation.[11/24/2005 3:52:08 PM]MLDDC1.distribution: {call
>sp_MSadd_repl_alert(3, 24, 48, 14152, ?, 5, N'MLDDC1', N'scalaDB_MLD',
>N'SQL1', N'scalaDB_MLD', ?)}
>ErrorId = 48, SourceTypeId = 1
>ErrorCode = ''
>ErrorText = 'SET ARITHABORT ON SET NUMERIC_ROUNDABORT OFF SET
>CONCAT_NULL_YIELDS_NULL ON SET QUOTED_IDENTIFIER ON SET ANSI_NULLS ON SET
>ANSI_PADDING ON SET ANSI_WARNINGS ON '
>[11/24/2005 3:52:08 PM]MLDDC1.distribution: {call sp_MSadd_repl_error(48, 0,
>1, ?, N'', ?)}
>Category:COMMAND
>Source: Failed Command
>Number:
>Message: SET ARITHABORT ON SET NUMERIC_ROUNDABORT OFF SET
>CONCAT_NULL_YIELDS_NULL ON SET QUOTED_IDENTIFIER ON SET ANSI_NULLS ON SET
>ANSI_PADDING ON SET ANSI_WARNINGS ON
>ErrorId = 48, SourceTypeId = 5
>ErrorCode = '11'
>ErrorText = 'General network error. Check your network documentation.'
>[11/24/2005 3:52:08 PM]MLDDC1.distribution: {call sp_MSadd_repl_error(48, 0,
>5, ?, N'11', ?)}
>Category:SQLSERVER
>Source: SQL1
>Number: 11
>Message: General network error. Check your network documentation.
>ErrorId = 48, SourceTypeId = 4
>ErrorCode = '08S01'
>ErrorText = 'Communication link failure'
>[11/24/2005 3:52:08 PM]MLDDC1.distribution: {call sp_MSadd_repl_error(48, 0,
>4, ?, N'08S01', ?)}
>Category:ODBC
>Source: ODBC SQL Server Driver
>Number: 08S01
>Message: Communication link failure
>ErrorId = 48, SourceTypeId = 4
>ErrorCode = '08S01'
>ErrorText = 'Communication link failure'
>[11/24/2005 3:52:08 PM]MLDDC1.distribution: {call sp_MSadd_repl_error(48, 0,
>4, ?, N'08S01', ?)}
>Category:ODBC
>Source: ODBC SQL Server Driver
>Number: 08S01
>Message: Communication link failure
>[11/24/2005 3:52:08 PM]SQL1.scalaDB_MLD: exec dbo.sp_MSupdatelastsyncinfo
>N'MLDDC1',N'scalaDB_MLD', N'', 0, 5, N'General network error. Check your
>network documentation.'
>Disconnecting from Subscriber 'SQL1'
>Disconnecting from Distributor 'MLDDC1'
>Disconnecting from Distributor History 'MLDDC1'
>The agent failed with a 'Retry' status. Try to run the agent at a later time.
>+++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++
>i could see there is ODBC SQL Server Driver that caused the communication
>link failure, so i have manually created a SQL SERVER odbc link from the data
>sources and it seems that i could connect
>i have checked the event viewer but could not see any particular details
>where it can show connectivity issue
>in fact the error happens intermittenly , but previously there's no change of
>the settings and it could work
>Wherelse can i check to be able to resolve this error once & for all ?
>I am using SQL Server 2000 , SP3a , TCP/IP protocol using the default port#
>1433
>appreciate ur advise
>tks & rdgs
Message posted via http://www.droptable.com
|||Hi ,
Futher info is the script in that agent : -Subscriber [SQL1] -SubscriberDB
[scalaDB_MLD] -Publisher [MLDDC1] -Distributor [MLDDC1] -
DistributorSecurityMode 1 -PublisherDB [scalaDB_MLD] -Continuous
appreciate any advise
tks & rdgs
maxzsim wrote:[vbcol=seagreen]
>Hi,
> Refering to the same issue below : i could see the agent profile details
>(default) as below
> BcpBatchSize - 100000
> CommitBatchSize - 100
> CommmitBatchThreshold - 1000
> Are those in bytes and shld any of the values be decreased/increased ?
>tks & rdgs
>[quoted text clipped - 80 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...ation/200511/1
|||Hi ,
I have checked thru the error details , it was able to applied some of
the schema files xxx.sch before getting the general network error msg
The last command was :
++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++
SET ARITHABORT ON SET NUMERIC_ROUNDABORT OFF SET CONCAT_NULL_YIELDS_NULL ON
SET QUOTED_IDENTIFIER ON SET ANSI_NULLS ON SET ANSI_PADDING ON SET
ANSI_WARNINGS ON
Transaction sequence number and command ID of last execution batch are
0x000005FF00005CE7000400000001 and 20.
++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++
does this mean anything ?
appreciate if anyone could point out where it might have gone wrong
tks & rdgs
maxzsim wrote:[vbcol=seagreen]
>Hi ,
>Futher info is the script in that agent : -Subscriber [SQL1] -SubscriberDB
>[scalaDB_MLD] -Publisher [MLDDC1] -Distributor [MLDDC1] -
>DistributorSecurityMode 1 -PublisherDB [scalaDB_MLD] -Continuous
>appreciate any advise
>tks & rdgs
>[quoted text clipped - 13 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...ation/200511/1

replication error - agent is suspect

Hi,
I have set up a replication and it was doing the bulk copy from SrvA to
SrvB when it says "The agent is suspect as there's no response for the last
10 mins" or something like that ?
what could be the problem here ?
however, after i refresh it , it keeps running though but i am unsure if the
data has been successfully replicated over as the processing's running
appreciate any advise
tks & rdgs
Hi,
See the previous posts:-
http://groups.google.co.in/group/mic...36c788aeacadb7
Thanks
Hari
SQL Server MVP
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:13D1D8DF-E095-4F6C-9CAB-06D63015A95D@.microsoft.com...
> Hi,
> I have set up a replication and it was doing the bulk copy from SrvA to
> SrvB when it says "The agent is suspect as there's no response for the
> last
> 10 mins" or something like that ?
> what could be the problem here ?
> however, after i refresh it , it keeps running though but i am unsure if
> the
> data has been successfully replicated over as the processing's running
> appreciate any advise
> tks & rdgs
|||Hi ,
I have managed to resolve this issue by increasing the default 10 mins of
agent inactivity
tks & rdgs
"maxzsim" wrote:

> Hi,
> I have set up a replication and it was doing the bulk copy from SrvA to
> SrvB when it says "The agent is suspect as there's no response for the last
> 10 mins" or something like that ?
> what could be the problem here ?
> however, after i refresh it , it keeps running though but i am unsure if the
> data has been successfully replicated over as the processing's running
> appreciate any advise
> tks & rdgs

replication error - agent is suspect

Hi,
I have set up a replication and it was doing the bulk copy from SrvA to
SrvB when it says "The agent is suspect as there's no response for the last
10 mins" or something like that ?
what could be the problem here ?
however, after i refresh it , it keeps running though but i am unsure if the
data has been successfully replicated over as the processing's running
appreciate any advise
tks & rdgsHi,
See the previous posts:-
http://groups.google.co.in/group/mi...936c788aeacadb7
Thanks
Hari
SQL Server MVP
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:13D1D8DF-E095-4F6C-9CAB-06D63015A95D@.microsoft.com...
> Hi,
> I have set up a replication and it was doing the bulk copy from SrvA to
> SrvB when it says "The agent is suspect as there's no response for the
> last
> 10 mins" or something like that ?
> what could be the problem here ?
> however, after i refresh it , it keeps running though but i am unsure if
> the
> data has been successfully replicated over as the processing's running
> appreciate any advise
> tks & rdgs|||Hi ,
I have managed to resolve this issue by increasing the default 10 mins of
agent inactivity
tks & rdgs
"maxzsim" wrote:

> Hi,
> I have set up a replication and it was doing the bulk copy from SrvA to
> SrvB when it says "The agent is suspect as there's no response for the las
t
> 10 mins" or something like that ?
> what could be the problem here ?
> however, after i refresh it , it keeps running though but i am unsure if t
he
> data has been successfully replicated over as the processing's running
> appreciate any advise
> tks & rdgs

replication error - agent is suspect

Hi,
I have set up a replication and it was doing the bulk copy from SrvA to
SrvB when it says "The agent is suspect as there's no response for the last
10 mins" or something like that ?
what could be the problem here ?
however, after i refresh it , it keeps running though but i am unsure if the
data has been successfully replicated over as the processing's running
appreciate any advise
tks & rdgsHi,
See the previous posts:-
http://groups.google.co.in/group/microsoft.public.sqlserver.replication/browse_thread/thread/45cba0e7e1543879/7936c788aeacadb7?q=replication+agent+is+suspect&rnum=2&hl=en#7936c788aeacadb7
Thanks
Hari
SQL Server MVP
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:13D1D8DF-E095-4F6C-9CAB-06D63015A95D@.microsoft.com...
> Hi,
> I have set up a replication and it was doing the bulk copy from SrvA to
> SrvB when it says "The agent is suspect as there's no response for the
> last
> 10 mins" or something like that ?
> what could be the problem here ?
> however, after i refresh it , it keeps running though but i am unsure if
> the
> data has been successfully replicated over as the processing's running
> appreciate any advise
> tks & rdgs|||Hi ,
I have managed to resolve this issue by increasing the default 10 mins of
agent inactivity
tks & rdgs
"maxzsim" wrote:
> Hi,
> I have set up a replication and it was doing the bulk copy from SrvA to
> SrvB when it says "The agent is suspect as there's no response for the last
> 10 mins" or something like that ?
> what could be the problem here ?
> however, after i refresh it , it keeps running though but i am unsure if the
> data has been successfully replicated over as the processing's running
> appreciate any advise
> tks & rdgs

replication error

i have a problem

when i select distributor and click next

"SQL server agent on 'PC-...' currently uses the system account, which causes replication between servers to fail. In te following dialog box, specify another account for the Service startup account"

and

"SQL server enterprise manager couldn not configure 'PC-...' as the distributor for 'PC-...'

Error 18483: Could not connect to server 'PC-...' because 'distributor admin' is not defined as a remote login at the server."

what can i do?I would start by setting up the sql server agent to use a domain user account. I am no replication expert. Not yet anyways. That project is coming soon.|||My suggestions are:

1. Create a domain user specifically for SQL replication, and no other purpose
2. Before you get a new machine involved with replication, make that domain user a local administrator on the new machine.
3. Start the SQL Agent on the machine that is the distributor using the domain accout from step 1.

Depending on how far you got with the replication installation, you may want to reinstall Replication. I know that I would!

-PatP

Replication Error

Hi all,
Please help me with issue. I have the following error accured always when
i
run the merge agent. I have 3 database makes replication, 2 are running
and
is giving this error:
LAST COMMAND : {call sp_MSenumchanges(?,?,?,?,?,?,?,?)}
The process could not enumerate changes at the 'Subscriber'.
(Source: Merge Replication Provider (Agent); Error number: -2147200999)
--
The merge process timed out while executing a query. Reconfigure the
QueryTimeout parameter and retry the operation.
(Source: SERV-COMPAQ (Data source); Error number: 0)
--
The process was successfully stopped.
(Source: Merge Replication Provider (Agent); Error number: -2147200999)
--
any help is realy appreciated.
thanks all.
Samir R. Ibrahim
I have did that on both servers. with the same result.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:372e01c4a553$224b3800$a301280a@.phx.gbl...
> Samir,
> try setting the QueryTimeout to 0 in the merge agent's
> job.
> HTH,
> Paul IBison
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Samir,
you could try running the merge agent again, but before
that, enable logging http://support.microsoft.com/?
id=312292
Rgds,
Paul Ibison
|||Thank you Paul for your help. i will give that a try.
Samir R. Ibrahim
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:2b2101c4a55a$a221cba0$a501280a@.phx.gbl...
> Samir,
> you could try running the merge agent again, but before
> that, enable logging http://support.microsoft.com/?
> id=312292
> Rgds,
> Paul Ibison
>

Replication Distribution Agent Does Not Start

Hi,
For some magical reason, my database replication has suddenly stopped
working. I modified the publication but the Distribution agent will
not run; the snapshot does not get applied to the subscriber, and
changes made at the publisher do not get replicated.
My configuration is: Transactional Replication with a
‘Pull’ Subscription. The Subscriber is Updateable with
Immediate Updates Only. All created via the SQL Server Enterprise
Manager. Both the Publisher and Subscriber are on the same server.
I’m running SQL Server 2000 (8.00.760 SP3), on Windows 2000
Server (5.0 (2195)).
I manually run the snapshop agent. It runs fine with the status
‘Succeeded’ and the Last Action is ‘A Snapshot of X
article(s) was generated’.
When I look at the distribution agent, things start to get a bit
confusing in ( <SERVERNAME>/Replication Monitor/ Publishers/
<SERVERNAME?>/ Publication/ Subscription), the status stays
constantly at ‘Never Started’. All other columns are
either blank or 0. When I right click over the subscription, both
Start Synchronising and Stop Synchronising are NOT greyed out. If I
click on either Start Synchronising or Stop Synchronising (absolutely)
nothing happens (except the mouse turns ‘busy’ for a
fraction of a second). There are no error messages.
I added -output c:\sqlout.txt -outputverboselevel 3 to the
distribution agent command. C:\sqlout.txt did not get created.
It worked fine up to a couple of days ago. I’m not sure exactly
what caused the problem, as I made a few changes at the same time. The
changes included: adding a new transactional publication, adding more
articles to an existing transaction publication, and adding a merge
publication. I’ve tried to go back to the set up before I made
the changes, even disabling replication and starting again from
scratch. Still the problem persists.
The owner of the distribution agent has dbo permissions in both the
publishing and subscribing database. Under ‘Publisher and
Distributor Properties’ I’ve set the ‘Replication
Agent Connection to Publisher’ and ‘Agent Connection to
the Subscriber’ both to Use SQL Server Authentication, both with
the same account that has dbo permissions in both publishing and
subscribing database.
Has anybody come across anything like this before? Can anybody make
any suggestions? Thanks in advance for your help.
Regards
Damian Helme
IS Manager
INTEC Engineering (UK) Ltd.
are you using an ActiveX control or Windows Synchronization Manager to
manage this subscription? If so you will not be able to manage your
distribution agent in EM.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Damian H" <damianhelme@.hotmail.com> wrote in message
news:2b893e38.0407220153.32af854e@.posting.google.c om...
> Hi,
> For some magical reason, my database replication has suddenly stopped
> working. I modified the publication but the Distribution agent will
> not run; the snapshot does not get applied to the subscriber, and
> changes made at the publisher do not get replicated.
> My configuration is: Transactional Replication with a
> ‘Pull’ Subscription. The Subscriber is Updateable with
> Immediate Updates Only. All created via the SQL Server Enterprise
> Manager. Both the Publisher and Subscriber are on the same server.
> I’m running SQL Server 2000 (8.00.760 SP3), on Windows 2000
> Server (5.0 (2195)).
> I manually run the snapshop agent. It runs fine with the status
> ‘Succeeded’ and the Last Action is ‘A Snapshot of X
> article(s) was generated’.
> When I look at the distribution agent, things start to get a bit
> confusing in ( <SERVERNAME>/Replication Monitor/ Publishers/
> <SERVERNAME?>/ Publication/ Subscription), the status stays
> constantly at ‘Never Started’. All other columns are
> either blank or 0. When I right click over the subscription, both
> Start Synchronising and Stop Synchronising are NOT greyed out. If I
> click on either Start Synchronising or Stop Synchronising (absolutely)
> nothing happens (except the mouse turns ‘busy’ for a
> fraction of a second). There are no error messages.
> I added -output c:\sqlout.txt -outputverboselevel 3 to the
> distribution agent command. C:\sqlout.txt did not get created.
> It worked fine up to a couple of days ago. I’m not sure exactly
> what caused the problem, as I made a few changes at the same time. The
> changes included: adding a new transactional publication, adding more
> articles to an existing transaction publication, and adding a merge
> publication. I’ve tried to go back to the set up before I made
> the changes, even disabling replication and starting again from
> scratch. Still the problem persists.
> The owner of the distribution agent has dbo permissions in both the
> publishing and subscribing database. Under ‘Publisher and
> Distributor Properties’ I’ve set the ‘Replication
> Agent Connection to Publisher’ and ‘Agent Connection to
> the Subscriber’ both to Use SQL Server Authentication, both with
> the same account that has dbo permissions in both publishing and
> subscribing database.
> Has anybody come across anything like this before? Can anybody make
> any suggestions? Thanks in advance for your help.
> Regards
> Damian Helme
> IS Manager
> INTEC Engineering (UK) Ltd.
|||Hillary
Thanks for your reply. No I am not using an ActiveX control or Windows
Synchronization Manager. It is all done through EM.
Here's the post again, but this time free of the garbled control
characters:
================================================== =============================
Hi,
For some magical reason, my database replication has suddenly stopped
working. I modified the publication but the Distribution agent will
not run; the snapshot does not get applied to the subscriber, and
changes made at the publisher do not get replicated.
My configuration is: Transactional Replication with a 'Pull'
Subscription. The Subscriber is Updateable with Immediate Updates
Only. All created via the SQL Server Enterprise Manager. Both the
Publisher and Subscriber are on the same server. I'm running SQL
Server 2000 (8.00.760 SP3), on Windows 2000 Server (5.0 (2195)).
I manually run the snapshop agent. It runs fine with the status
'Succeeded' and the Last Action is 'A Snapshot of X article(s) was
generated'.
When I look at the distribution agent, things start to get a bit
confusing in ( <SERVERNAME>/Replication Monitor/ Publishers/
<SERVERNAME?>/ Publication/ Subscription), the status stays
constantly at 'Never Started'. All other columns are either blank or
0. When I right click over the subscription, both Start Synchronising
and Stop Synchronising are NOT greyed out. If I click on either Start
Synchronising or Stop Synchronising (absolutely) nothing happens
(except the mouse turns 'busy' for a fraction of a second). There are
no error messages.
I added -output c:\sqlout.txt -outputverboselevel 3 to the
distribution agent command. C:\sqlout.txt did not get created.
It worked fine up to a couple of days ago. I'm not sure exactly what
caused the problem, as I made a few changes at the same time. The
changes included: adding a new transactional publication, adding more
articles to an existing transaction publication, and adding a merge
publication. I've tried to go back to the set up before I made the
changes, even disabling replication and starting again from scratch.
Still the problem persists.
The owner of the distribution agent has dbo permissions in both the
publishing and subscribing database. Under 'Publisher and Distributor
Properties' I've set the 'Replication Agent Connection to Publisher'
and 'Agent Connection to the Subscriber' both to Use SQL Server
Authentication, both with the same account that has dbo permissions in
both publishing and subscribing database.
Has anybody come across this problem before? Can anybody make any
suggestions? Thanks in advance for your help.
Regards
Damian Helme
IS Manager
INTEC Engineering (UK) Ltd.
|||I've encountered this error before and its driving me crazy trying to recall
exactly what is causing it. IIRC its something pretty simple.
Can you right click on your distribution agent, select agent properties
select steps, click on Run Agent, and click edit.
Then copy everything in the commands text box.
Open a command window and go to c:\program files\microsoft sql server\80\com
and then type
distrib and paste your commands here. To do this, go to the c:\ thingy in
the upper left hand corner of your command window and select edit - paste.
Make sure there is a space between distrib and the commands.
Then hit enter. You should get an error message this time.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Damian H" <damianhelme@.hotmail.com> wrote in message
news:2b893e38.0407222334.bc69d37@.posting.google.co m...
> Hillary
> Thanks for your reply. No I am not using an ActiveX control or Windows
> Synchronization Manager. It is all done through EM.
> Here's the post again, but this time free of the garbled control
> characters:
>
>
================================================== ==========================
===
> Hi,
> For some magical reason, my database replication has suddenly stopped
> working. I modified the publication but the Distribution agent will
> not run; the snapshot does not get applied to the subscriber, and
> changes made at the publisher do not get replicated.
>
> My configuration is: Transactional Replication with a 'Pull'
> Subscription. The Subscriber is Updateable with Immediate Updates
> Only. All created via the SQL Server Enterprise Manager. Both the
> Publisher and Subscriber are on the same server. I'm running SQL
> Server 2000 (8.00.760 SP3), on Windows 2000 Server (5.0 (2195)).
> I manually run the snapshop agent. It runs fine with the status
> 'Succeeded' and the Last Action is 'A Snapshot of X article(s) was
> generated'.
> When I look at the distribution agent, things start to get a bit
> confusing in ( <SERVERNAME>/Replication Monitor/ Publishers/
> <SERVERNAME?>/ Publication/ Subscription), the status stays
> constantly at 'Never Started'. All other columns are either blank or
> 0. When I right click over the subscription, both Start Synchronising
> and Stop Synchronising are NOT greyed out. If I click on either Start
> Synchronising or Stop Synchronising (absolutely) nothing happens
> (except the mouse turns 'busy' for a fraction of a second). There are
> no error messages.
> I added -output c:\sqlout.txt -outputverboselevel 3 to the
> distribution agent command. C:\sqlout.txt did not get created.
> It worked fine up to a couple of days ago. I'm not sure exactly what
> caused the problem, as I made a few changes at the same time. The
> changes included: adding a new transactional publication, adding more
> articles to an existing transaction publication, and adding a merge
> publication. I've tried to go back to the set up before I made the
> changes, even disabling replication and starting again from scratch.
> Still the problem persists.
> The owner of the distribution agent has dbo permissions in both the
> publishing and subscribing database. Under 'Publisher and Distributor
> Properties' I've set the 'Replication Agent Connection to Publisher'
> and 'Agent Connection to the Subscriber' both to Use SQL Server
> Authentication, both with the same account that has dbo permissions in
> both publishing and subscribing database.
> Has anybody come across this problem before? Can anybody make any
> suggestions? Thanks in advance for your help.
> Regards
> Damian Helme
> IS Manager
> INTEC Engineering (UK) Ltd.
|||Thanks for the suggestion, I didn't get chance to try your suggestion
as I had already reinstalled SQL Server, which solved the problem.
I'll keep a note of your suggestion for future use.
Thanks again.
Damian.

Replication Distribution Agent Does Not Start

Hi,

For some magical reason, my database replication has suddenly stopped
working. I modified the publication but the Distribution agent will
not run; the snapshot does not get applied to the subscriber, and
changes made at the publisher do not get replicated.

My configuration is: Transactional Replication with a 'Pull'
Subscription. The Subscriber is Updateable with Immediate Updates
Only. All created via the SQL Server Enterprise Manager. Both the
Publisher and Subscriber are on the same server. I'm running SQL
Server 2000 (8.00.760 SP3), on Windows 2000 Server (5.0 (2195)).

I manually run the snapshop agent. It runs fine with the status
'Succeeded' and the Last Action is 'A Snapshot of X article(s) was
generated'.

When I look at the distribution agent, things start to get a bit
confusing in ( <SERVERNAME>/Replication Monitor/ Publishers/
<SERVERNAME?>/ Publication/ Subscription), the status stays
constantly at 'Never Started'. All other columns are either blank or
0. When I right click over the subscription, both Start Synchronising
and Stop Synchronising are NOT greyed out. If I click on either Start
Synchronising or Stop Synchronising (absolutely) nothing happens
(except the mouse turns 'busy' for a fraction of a second). There are
no error messages.

I added -output c:\sqlout.txt -outputverboselevel 3 to the
distribution agent command. C:\sqlout.txt did not get created.

It worked fine up to a couple of days ago. I'm not sure exactly what
caused the problem, as I made a few changes at the same time. The
changes included: adding a new transactional publication, adding more
articles to an existing transaction publication, and adding a merge
publication. I've tried to go back to the set up before I made the
changes, even disabling replication and starting again from scratch.
Still the problem persists.

The owner of the distribution agent has dbo permissions in both the
publishing and subscribing database. Under 'Publisher and Distributor
Properties' I've set the 'Replication Agent Connection to Publisher'
and 'Agent Connection to the Subscriber' both to Use SQL Server
Authentication, both with the same account that has dbo permissions in
both publishing and subscribing database.

Has anybody come across this problem before? Can anybody make any
suggestions? Thanks in advance for your help.

Regards

Damian Helme
IS Manager
INTEC Engineering (UK) Ltd."Damian H" <damianhelme@.hotmail.com> wrote in message
news:2b893e38.0407222337.542a5fd1@.posting.google.c om...
> Hi,
> For some magical reason, my database replication has suddenly stopped
> working. I modified the publication but the Distribution agent will
> not run; the snapshot does not get applied to the subscriber, and
> changes made at the publisher do not get replicated.
>
> My configuration is: Transactional Replication with a 'Pull'
> Subscription. The Subscriber is Updateable with Immediate Updates
> Only. All created via the SQL Server Enterprise Manager. Both the
> Publisher and Subscriber are on the same server. I'm running SQL
> Server 2000 (8.00.760 SP3), on Windows 2000 Server (5.0 (2195)).
> I manually run the snapshop agent. It runs fine with the status
> 'Succeeded' and the Last Action is 'A Snapshot of X article(s) was
> generated'.
> When I look at the distribution agent, things start to get a bit
> confusing in ( <SERVERNAME>/Replication Monitor/ Publishers/
> <SERVERNAME?>/ Publication/ Subscription), the status stays
> constantly at 'Never Started'. All other columns are either blank or
> 0. When I right click over the subscription, both Start Synchronising
> and Stop Synchronising are NOT greyed out. If I click on either Start
> Synchronising or Stop Synchronising (absolutely) nothing happens
> (except the mouse turns 'busy' for a fraction of a second). There are
> no error messages.
> I added -output c:\sqlout.txt -outputverboselevel 3 to the
> distribution agent command. C:\sqlout.txt did not get created.
> It worked fine up to a couple of days ago. I'm not sure exactly what
> caused the problem, as I made a few changes at the same time. The
> changes included: adding a new transactional publication, adding more
> articles to an existing transaction publication, and adding a merge
> publication. I've tried to go back to the set up before I made the
> changes, even disabling replication and starting again from scratch.
> Still the problem persists.
> The owner of the distribution agent has dbo permissions in both the
> publishing and subscribing database. Under 'Publisher and Distributor
> Properties' I've set the 'Replication Agent Connection to Publisher'
> and 'Agent Connection to the Subscriber' both to Use SQL Server
> Authentication, both with the same account that has dbo permissions in
> both publishing and subscribing database.
> Has anybody come across this problem before? Can anybody make any
> suggestions? Thanks in advance for your help.
> Regards
> Damian Helme
> IS Manager
> INTEC Engineering (UK) Ltd.

You might want to post this in microsoft.public.sqlserver.replication, as
you may get a better answer over there.

Simon

Replication Distribution Agent cpu continues to grow

We have transactional replication set up. The agent is running on the
subscriber. However the CPU continues to grow on the subscriber. Yesterday
morning the cpu was about ten thousand and this afternoon it reached over a
million cpu and continued to grow until I stopped and restarted the the pull
subscription agent on the distribution server. Then it went down to about a
hundred cpu. As I'm writing this article its already up to three thousand cpu.
Is there a profile setting that I'm missing?
Thanks all in advance!!
Message posted via http://www.droptable.com
On Mar 1, 1:39 pm, "fnadal via droptable.com" <u10790@.uwe> wrote:
> We have transactional replication set up. The agent is running on the
> subscriber. However the CPU continues to grow on the subscriber. Yesterday
> morning the cpu was about ten thousand and this afternoon it reached over a
> million cpu and continued to grow until I stopped and restarted the the pull
> subscription agent on the distribution server. Then it went down to about a
> hundred cpu. As I'm writing this article its already up to three thousand cpu.
> Is there a profile setting that I'm missing?
> Thanks all in advance!!
> --
> Message posted viahttp://www.droptable.com
Can you explain a little more clearly? Exactly what statistic are you
looking at? What value is growing?
|||The cpu usage. When I do a select spid,loginame,program_name, cpu from master.
sysprocesses where kpid > 0, I see Replication Distribution Agent cpu at
3000. Earlier this afternoon the cpu from sysprocesses was over a million for
that agent.
Tracy McKibben wrote:
>[quoted text clipped - 9 lines]
>Can you explain a little more clearly? Exactly what statistic are you
>looking at? What value is growing?
Message posted via http://www.droptable.com
|||That is a cumulative value since the connection started, not an immediate
usage value.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"fnadal via droptable.com" <u10790@.uwe> wrote in message
news:6e8b921a334f3@.uwe...
> The cpu usage. When I do a select spid,loginame,program_name, cpu from
> master.
> sysprocesses where kpid > 0, I see Replication Distribution Agent cpu at
> 3000. Earlier this afternoon the cpu from sysprocesses was over a million
> for
> that agent.
> Tracy McKibben wrote:
> --
> Message posted via http://www.droptable.com
>
|||How would I obtain an immediate usage value?
Geoff N. Hiten wrote:[vbcol=seagreen]
>That is a cumulative value since the connection started, not an immediate
>usage value.
>[quoted text clipped - 12 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server/200703/1

Replication Distribution Agent cpu continues to grow

We have transactional replication set up. The agent is running on the
subscriber. However the CPU continues to grow on the subscriber. Yesterday
morning the cpu was about ten thousand and this afternoon it reached over a
million cpu and continued to grow until I stopped and restarted the the pull
subscription agent on the distribution server. Then it went down to about a
hundred cpu. As I'm writing this article its already up to three thousand cp
u.
Is there a profile setting that I'm missing?
Thanks all in advance!!
Message posted via http://www.droptable.comOn Mar 1, 1:39 pm, "fnadal via droptable.com" <u10790@.uwe> wrote:
> We have transactional replication set up. The agent is running on the
> subscriber. However the CPU continues to grow on the subscriber. Yesterday
> morning the cpu was about ten thousand and this afternoon it reached over
a
> million cpu and continued to grow until I stopped and restarted the the pu
ll
> subscription agent on the distribution server. Then it went down to about
a
> hundred cpu. As I'm writing this article its already up to three thousand
cpu.
> Is there a profile setting that I'm missing?
> Thanks all in advance!!
> --
> Message posted viahttp://www.droptable.com
Can you explain a little more clearly? Exactly what statistic are you
looking at? What value is growing?|||The cpu usage. When I do a select spid,loginame,program_name, cpu from maste
r.
sysprocesses where kpid > 0, I see Replication Distribution Agent cpu at
3000. Earlier this afternoon the cpu from sysprocesses was over a million fo
r
that agent.
Tracy McKibben wrote:
>[quoted text clipped - 9 lines]
>Can you explain a little more clearly? Exactly what statistic are you
>looking at? What value is growing?
Message posted via http://www.droptable.com|||That is a cumulative value since the connection started, not an immediate
usage value.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"fnadal via droptable.com" <u10790@.uwe> wrote in message
news:6e8b921a334f3@.uwe...
> The cpu usage. When I do a select spid,loginame,program_name, cpu from
> master.
> sysprocesses where kpid > 0, I see Replication Distribution Agent cpu at
> 3000. Earlier this afternoon the cpu from sysprocesses was over a million
> for
> that agent.
> Tracy McKibben wrote:
> --
> Message posted via http://www.droptable.com
>|||How would I obtain an immediate usage value?
Geoff N. Hiten wrote:[vbcol=seagreen]
>That is a cumulative value since the connection started, not an immediate
>usage value.
>
>[quoted text clipped - 12 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200703/1sql

Replication Distribution Agent cpu continues to grow

We have transactional replication set up. The agent is running on the
subscriber. However the CPU continues to grow on the subscriber. Yesterday
morning the cpu was about ten thousand and this afternoon it reached over a
million cpu and continued to grow until I stopped and restarted the the pull
subscription agent on the distribution server. Then it went down to about a
hundred cpu. As I'm writing this article its already up to three thousand cpu.
Is there a profile setting that I'm missing?
Thanks all in advance!!
--
Message posted via http://www.sqlmonster.comOn Mar 1, 1:39 pm, "fnadal via SQLMonster.com" <u10790@.uwe> wrote:
> We have transactional replication set up. The agent is running on the
> subscriber. However the CPU continues to grow on the subscriber. Yesterday
> morning the cpu was about ten thousand and this afternoon it reached over a
> million cpu and continued to grow until I stopped and restarted the the pull
> subscription agent on the distribution server. Then it went down to about a
> hundred cpu. As I'm writing this article its already up to three thousand cpu.
> Is there a profile setting that I'm missing?
> Thanks all in advance!!
> --
> Message posted viahttp://www.sqlmonster.com
Can you explain a little more clearly? Exactly what statistic are you
looking at? What value is growing?|||The cpu usage. When I do a select spid,loginame,program_name, cpu from master.
sysprocesses where kpid > 0, I see Replication Distribution Agent cpu at
3000. Earlier this afternoon the cpu from sysprocesses was over a million for
that agent.
Tracy McKibben wrote:
>> We have transactional replication set up. The agent is running on the
>> subscriber. However the CPU continues to grow on the subscriber. Yesterday
>[quoted text clipped - 9 lines]
>> --
>> Message posted viahttp://www.sqlmonster.com
>Can you explain a little more clearly? Exactly what statistic are you
>looking at? What value is growing?
--
Message posted via http://www.sqlmonster.com|||That is a cumulative value since the connection started, not an immediate
usage value.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"fnadal via SQLMonster.com" <u10790@.uwe> wrote in message
news:6e8b921a334f3@.uwe...
> The cpu usage. When I do a select spid,loginame,program_name, cpu from
> master.
> sysprocesses where kpid > 0, I see Replication Distribution Agent cpu at
> 3000. Earlier this afternoon the cpu from sysprocesses was over a million
> for
> that agent.
> Tracy McKibben wrote:
>> We have transactional replication set up. The agent is running on the
>> subscriber. However the CPU continues to grow on the subscriber.
>> Yesterday
>>[quoted text clipped - 9 lines]
>> --
>> Message posted viahttp://www.sqlmonster.com
>>Can you explain a little more clearly? Exactly what statistic are you
>>looking at? What value is growing?
> --
> Message posted via http://www.sqlmonster.com
>|||How would I obtain an immediate usage value?
Geoff N. Hiten wrote:
>That is a cumulative value since the connection started, not an immediate
>usage value.
>> The cpu usage. When I do a select spid,loginame,program_name, cpu from
>> master.
>[quoted text clipped - 12 lines]
>>Can you explain a little more clearly? Exactly what statistic are you
>>looking at? What value is growing?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200703/1

Replication Deadlocks

Hello,
I am running multiple replication publication on a SQL 2k database, with
a separate server as distribution agent, then finally push subscriptions
to multiple databases across 5 servers.
All publications use row and column filtering in them.
My question is, can I use locking hints on the selection criteria for
the row filtering?
ie. Can I specify WITH (NOLOCK) on the row filtering so that it
eliminates the majority of the blocking / deadlocks?
Thanks
Dave
*** Sent via Developersdex http://www.codecomments.com ***
You could if it was a subquery. Do you have indexes on the join
condition/filter key in your filter?
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
"Dave" <Anonymous@.devdex.com> wrote in message
news:eqm8zv1THHA.5060@.TK2MSFTNGP02.phx.gbl...
>
> Hello,
> I am running multiple replication publication on a SQL 2k database, with
> a separate server as distribution agent, then finally push subscriptions
> to multiple databases across 5 servers.
> All publications use row and column filtering in them.
> My question is, can I use locking hints on the selection criteria for
> the row filtering?
> ie. Can I specify WITH (NOLOCK) on the row filtering so that it
> eliminates the majority of the blocking / deadlocks?
> Thanks
> Dave
> *** Sent via Developersdex http://www.codecomments.com ***
|||There is an index on the originating table/column, but the deadlocking
appears to be happening on the distribution database.
David
*** Sent via Developersdex http://www.codecomments.com ***

replication and 'syntax error near E'

I use SQL2005 with bunch of stored procedures. All worked fine. Then I set u
p
push transactional replication with sqlexpress so all agent were running on
publisher. Replication ran without errors and replicated articles. After som
e
time (about 1 hour) few stored procedures failed with 'Incorrect syntax near
E' error.
When I remove replication same stored procedures work without any error.
Every time when replication is set up error occurs on same procedures.
Stored procedures work with cursor, create and update temporary tables using
EXEC statement with dinamicaly build query.
When I remove replication same stored procedures work without any error, so
I guess it's not SQL.
I havent found nothing on this on Technet, MSDN or on internet.
Thank you for any hint.Enable logging to see exactly what is causing this error. Refer to this kb
article for more info on how to enable logging.
http://support.microsoft.com/kb/312292/en-us
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"janez" <janez@.discussions.microsoft.com> wrote in message
news:18698F9A-84F2-446F-9175-0B753EA01A99@.microsoft.com...
>I use SQL2005 with bunch of stored procedures. All worked fine. Then I set
>up
> push transactional replication with sqlexpress so all agent were running
> on
> publisher. Replication ran without errors and replicated articles. After
> some
> time (about 1 hour) few stored procedures failed with 'Incorrect syntax
> near
> E' error.
> When I remove replication same stored procedures work without any error.
> Every time when replication is set up error occurs on same procedures.
> Stored procedures work with cursor, create and update temporary tables
> using
> EXEC statement with dinamicaly build query.
> When I remove replication same stored procedures work without any error,
> so
> I guess it's not SQL.
> I havent found nothing on this on Technet, MSDN or on internet.
> Thank you for any hint.|||Thanks for advice. It will be usefuul in further analysis of the cause.
By trying I found setting scheduled snapshot to cause error. Transactional
replication with only initial snapshot works without any problem.
"Hilary Cotter" wrote:

> Enable logging to see exactly what is causing this error. Refer to this kb
> article for more info on how to enable logging.
> http://support.microsoft.com/kb/312292/en-us
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> 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
>
> "janez" <janez@.discussions.microsoft.com> wrote in message
> news:18698F9A-84F2-446F-9175-0B753EA01A99@.microsoft.com...
>
>

Replication and large transactions

Hello,
Is it true that merge agent is not replicating at all when a transaction is
going on?
In my system I use merge replication and I have set the merge agents on
continuous replication to make sure that all changes are replicated to all
databases as soon as possible. Now I notice that when a large transaction is
going on (about 10 minutes) the merge agent is not replicating at all. So if
concurrently a small transaction took place and was committed, these changes
are replicated after the large transaction was finished.
I guess this behaviour is caused by the merge agent that waits for the large
transaction to finish before it has access to the
msmerge_contents/msmerge_tombstone tables.
Is there any way to prevent this blocking?
Can I set the Isolation Level of the transaction of the merge agent?
thanks in advance,
Marco Broenink
Yes, the way it works is that triggers fire on the tables which are
published to and subscriber to for merge replication.
If you have a large transaction which commits at the end of the transaction,
the triggers will not fire until the commit happens.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Marco Broenink" <MarcoBroenink@.discussions.microsoft.com> wrote in message
news:D0D14388-1660-49DC-9555-DAFD9B8E0C66@.microsoft.com...
> Hello,
> Is it true that merge agent is not replicating at all when a transaction
is
> going on?
> In my system I use merge replication and I have set the merge agents on
> continuous replication to make sure that all changes are replicated to all
> databases as soon as possible. Now I notice that when a large transaction
is
> going on (about 10 minutes) the merge agent is not replicating at all. So
if
> concurrently a small transaction took place and was committed, these
changes
> are replicated after the large transaction was finished.
> I guess this behaviour is caused by the merge agent that waits for the
large
> transaction to finish before it has access to the
> msmerge_contents/msmerge_tombstone tables.
> Is there any way to prevent this blocking?
> Can I set the Isolation Level of the transaction of the merge agent?
> thanks in advance,
> Marco Broenink

Replication - SQLServer Agent uses System Account

When I attempt to set up replication on my local box, I receive the error -'SQLServer Agent uses the Systems Account, which causes replication betweem servers to fail'.
Why does this happen? And can I overcome this?
Thanks :)
BiancaStart SQLServerAgent service using a domain account. This account must have the appropriate rights on teh Publisher, Distributor and Subscriber computers (depending on the replication type)

Originally posted by Bianca_J
When I attempt to set up replication on my local box, I receive the error -'SQLServer Agent uses the Systems Account, which causes replication betweem servers to fail'.

Why does this happen? And can I overcome this?

Thanks :)

Bianca|||Thank you for your post :)

What is a Domain Account?

Is this set up in Windows 2000? And if I set up a Domain Account in my local Windows 2000 box - how do I have right over a remore server?

Thanks

Bianca

replication - agent is suspect

I setup a client with merge replication, the following error was
returned after working successfully for a day "The agent is suspect.
No response within the last 10 minutes". Most research I found on
the newsgroup is this error does not stop merge replication from
working, but in my case it did stop replication from working. I was
able to get to working again by running the following command.
sp_replication_agent_checkup @.heartbeat_interval = 6000
Can anybody explain why replication stopped working altogether with the
agent is suspect message, and what can I do to avoid this message to
begin with?
Thank you,
Pauly C
Suspect means that the agent hasn't communicated with the job subsystem in
the interval defined in the heartbeat_interval.
The job will be failed after the heartbeat_interval has passed, but I am not
exactly sure when.
The agent could be busy, dead, or trying to connect. Run profiler on the
subscriber to try to figure out what is going on. Profiler might not reveal
anything. There is a condition when the publisher or subscriber has
exhausted buffers and hangs on initialization. You can clear this by
rebooting.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"paulysc" <paulysc@.optonline.net> wrote in message
news:1141228700.833217.245870@.t39g2000cwt.googlegr oups.com...
>I setup a client with merge replication, the following error was
> returned after working successfully for a day "The agent is suspect.
> No response within the last 10 minutes". Most research I found on
> the newsgroup is this error does not stop merge replication from
> working, but in my case it did stop replication from working. I was
> able to get to working again by running the following command.
> sp_replication_agent_checkup @.heartbeat_interval = 6000
> Can anybody explain why replication stopped working altogether with the
> agent is suspect message, and what can I do to avoid this message to
> begin with?
> Thank you,
> Pauly C
>
|||I saw this error message if the job runs against a wrong database. In my
case, the Queue Reader was running against the master database, not the
distribution, which resulted to the same error message as yours.
hope it helps,
FJY
"paulysc" wrote:

> I setup a client with merge replication, the following error was
> returned after working successfully for a day "The agent is suspect.
> No response within the last 10 minutes". Most research I found on
> the newsgroup is this error does not stop merge replication from
> working, but in my case it did stop replication from working. I was
> able to get to working again by running the following command.
> sp_replication_agent_checkup @.heartbeat_interval = 6000
> Can anybody explain why replication stopped working altogether with the
> agent is suspect message, and what can I do to avoid this message to
> begin with?
> Thank you,
> Pauly C
>

Replicating Stored Procedure

Hi:
I made a change to the stored proc in the publisher database but the change
did not get replicated. I should not have to run the snapshot agent again to
do that. Please let me know how can this be easily done.
Thanks
Mike,
this is better handled in SQL 2005, but in 2000 we can use sp_addscriptexec,
linked servers or manual addition of the new code. For this reason I
generally add the code parts of my publications (sps, views, functions) to a
separate publication, so if I decide to use replication to send them over, it
doesn't disturb my main publication.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Use sp_addscriptexec to send the commands if your subscribers were deployed
through UNC(file copies). If there were deployed through ftp you will have
to connect to them individual and run the commands individually.
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
"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:15028C08-3FA7-4647-9C23-7A2698AF8C41@.microsoft.com...
> Hi:
> I made a change to the stored proc in the publisher database but the
> change
> did not get replicated. I should not have to run the snapshot agent again
> to
> do that. Please let me know how can this be easily done.
> Thanks
>