QUEUE READER FAILS! Help...

Hi,
We are using transactional replication with queued updating between
SQL2000 Servers (Win 2003).
1) The queue reader has failed with the error message "Queue Reader
aborting. The step failed."
The error details stack shows (from last to first):
Queue Reader aborting. The step failed
Processed 53 queued trans, 105 cmds, 1 conflicts
Failed while applying queued message to publisher
CQueueRdrRowChange: ApplyCommand: Failed to create instance of
pMessage->pParams(ProcParams)
What's causing this? How can I restart the Queue Reader Agent after the
failure?
thanks,
Fabio
I take it that the error repeats next time you run the queue reader. To
restart it after failure I would put it on a schedule of every 5 minutes.
You can have it return to job step 1 on failure.
How many subscribers do you have? Also queued is designed for less than 10
subscribers and where the majority of the DML occurs on the publisher - does
your topology fit into this case?
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
<fabio.pliger@.gmail.com> wrote in message
news:1164187151.581038.182820@.j44g2000cwa.googlegr oups.com...
> Hi,
> We are using transactional replication with queued updating between
> SQL2000 Servers (Win 2003).
> 1) The queue reader has failed with the error message "Queue Reader
> aborting. The step failed."
> The error details stack shows (from last to first):
> Queue Reader aborting. The step failed
> Processed 53 queued trans, 105 cmds, 1 conflicts
> Failed while applying queued message to publisher
> CQueueRdrRowChange: ApplyCommand: Failed to create instance of
> pMessage->pParams(ProcParams)
> What's causing this? How can I restart the Queue Reader Agent after the
> failure?
> thanks,
> Fabio
>
|||Yes, the error repeates everytime i re-run the queue reader.. and it
always returns me those actions:
- Queue reader aborting...
- Processing ## queued trans, ## cmds, ## conflicts
- Failed whiale applying queued message to publisher
- CQueuedRdrRowChange::ApplyCommand: Failed.... bla bla...
- Queue Reader Agent blabla Started
- Starting agent
I do have 5 subscribers. 4 of those have a filter by column on only one
table.
Much DML occurs also at the subscribers...
I see that after the agentes fails... data from 2 of the subscribers is
sent to the publisher (and their Ms_replication_queue table il empty,
but no data from the others subscribers is sent to the publisher and
their replication queue table is unchanged... Can help if i delete all
the records in those tables at the subscribers?
What kind of error is that? Any hint on what i can look at to solve it?
thanks,
Fabio
Hilary Cotter ha scritto:
[vbcol=seagreen]
> I take it that the error repeats next time you run the queue reader. To
> restart it after failure I would put it on a schedule of every 5 minutes.
> You can have it return to job step 1 on failure.
> How many subscribers do you have? Also queued is designed for less than 10
> subscribers and where the majority of the DML occurs on the publisher - does
> your topology fit into this case?
> --
> 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
>
> <fabio.pliger@.gmail.com> wrote in message
> news:1164187151.581038.182820@.j44g2000cwa.googlegr oups.com...
|||Can you enable logging? Follow these steps
http://support.microsoft.com/default.aspx?scid=kb;en-us;312292&sd=tech
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
<fabio.pliger@.gmail.com> wrote in message
news:1164207423.995497.310220@.h48g2000cwc.googlegr oups.com...
> Yes, the error repeates everytime i re-run the queue reader.. and it
> always returns me those actions:
> - Queue reader aborting...
> - Processing ## queued trans, ## cmds, ## conflicts
> - Failed whiale applying queued message to publisher
> - CQueuedRdrRowChange::ApplyCommand: Failed.... bla bla...
> - Queue Reader Agent blabla Started
> - Starting agent
> I do have 5 subscribers. 4 of those have a filter by column on only one
> table.
> Much DML occurs also at the subscribers...
> I see that after the agentes fails... data from 2 of the subscribers is
> sent to the publisher (and their Ms_replication_queue table il empty,
> but no data from the others subscribers is sent to the publisher and
> their replication queue table is unchanged... Can help if i delete all
> the records in those tables at the subscribers?
> What kind of error is that? Any hint on what i can look at to solve it?
> thanks,
> Fabio
>
> Hilary Cotter ha scritto:
>
|||Here's what i get:
Connecting to QueueReader 'WN055.distribution'
Queue Reader Agent [WN055].8 (Id = 5) started
[11/22/2006 4:32:11 PM]WN055.distribution: execute
dbo.sp_MShelp_profile 5, 9, N''
Connecting to WN046 'WN046.FDF'
[11/22/2006 4:32:11 PM]WN055.distribution: exec
dbo.sp_helpdistpublisher @.publisher = N'WN055'
Connecting to WN055 'WN055.FDF'
SQL Command : <exec [dbo].[sp_MSsync_ins_Aut_LogBatch_3] N'WN046',
N'FDF', 250008816, 250000361, N'AUTO', '2006-11-22 16:19:32.000',
N'34B4', '5992D20D-A9E7-40AF-AB71-43F650E4E8AC', 1>
Disconnecting from WN055 'WN055'
Disconnecting from WN046 'WN046'
Connecting to WN030 'WN030.FDF'
[11/22/2006 4:32:26 PM]WN055.distribution: exec
dbo.sp_helpdistpublisher @.publisher = N'WN055'
Connecting to WN055 'WN055.FDF'
CQueueRdrRowChange::ApplyCommand:Failed to create instance of
pMessage->pParams(ProcParams)
Failed while applying queued message to publisher
Disconnecting from WN055 'WN055'
Worker Thread 540 : Task Failed
Disconnecting from WN030 'WN030'
Processed 29 queued trans, 57 cmds, 0 conflicts
Queue Reader aborting
It seem's like the subscriber WN030has some problems comunicating with
publisher-... right? Any hint?
Fabio
Hilary Cotter ha scritto:
[vbcol=seagreen]
> Can you enable logging? Follow these steps
> http://support.microsoft.com/default.aspx?scid=kb;en-us;312292&sd=tech
> --
> 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
>
> <fabio.pliger@.gmail.com> wrote in message
> news:1164207423.995497.310220@.h48g2000cwc.googlegr oups.com...
|||I've shutedown the sqlserveragent at the subscriber WN030 (the one
generating the error...) and the queue reader agent don't fails
anymore... So.. bypassing this subscriber the agent is able to run..
but my goal is to solve the problem and reconnect the subscriber...
Deleting the MS_replicationqueue at tje subscriber can help? I would
prefer to don't loose those transactions... but if it's the only way i
can delete it...
thanks,
Fabio
fabio.pliger@.gmail.com ha scritto:
[vbcol=seagreen]
> Here's what i get:
> Connecting to QueueReader 'WN055.distribution'
> Queue Reader Agent [WN055].8 (Id = 5) started
> [11/22/2006 4:32:11 PM]WN055.distribution: execute
> dbo.sp_MShelp_profile 5, 9, N''
> Connecting to WN046 'WN046.FDF'
> [11/22/2006 4:32:11 PM]WN055.distribution: exec
> dbo.sp_helpdistpublisher @.publisher = N'WN055'
> Connecting to WN055 'WN055.FDF'
> SQL Command : <exec [dbo].[sp_MSsync_ins_Aut_LogBatch_3] N'WN046',
> N'FDF', 250008816, 250000361, N'AUTO', '2006-11-22 16:19:32.000',
> N'34B4', '5992D20D-A9E7-40AF-AB71-43F650E4E8AC', 1>
> Disconnecting from WN055 'WN05
> Disconnecting from WN046 'WN046'
> Connecting to WN030 'WN030.FDF'
> [11/22/2006 4:32:26 PM]WN055.distribution: exec
> dbo.sp_helpdistpublisher @.publisher = N'WN055'
> Connecting to WN055 'WN055.FDF'
> CQueueRdrRowChange::ApplyCommand:Failed to create instance of
> pMessage->pParams(ProcParams)
> Failed while applying queued message to publisher
> Disconnecting from WN055 'WN055'
> Worker Thread 540 : Task Failed
> Disconnecting from WN030 'WN030'
> Processed 29 queued trans, 57 cmds, 0 conflicts
> Queue Reader aborting
>
> It seem's like the subscriber WN030has some problems comunicating with
> publisher-... right? Any hint?
> Fabio
>
>
> Hilary Cotter ha scritto:
|||No, it looks like it is crashing on a single command. Almost like there is a
command in the queue causing it to crash.
Deleting the contents of the queue will cause you to lose work. I would stop
all users working on the subscriber database and try to flush the queue and
see if there is a command stuck in there.
keep logging, and run the queue until one command remains and then I would
consider deleting that one command.
Something is very wrong here. I think you should open a support incident
with Microsoft on this one. Where is Raymond when you really want him?
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
<fabio.pliger@.gmail.com> wrote in message
news:1164210515.241841.233780@.f16g2000cwb.googlegr oups.com...
> Here's what i get:
> Connecting to QueueReader 'WN055.distribution'
> Queue Reader Agent [WN055].8 (Id = 5) started
> [11/22/2006 4:32:11 PM]WN055.distribution: execute
> dbo.sp_MShelp_profile 5, 9, N''
> Connecting to WN046 'WN046.FDF'
> [11/22/2006 4:32:11 PM]WN055.distribution: exec
> dbo.sp_helpdistpublisher @.publisher = N'WN055'
> Connecting to WN055 'WN055.FDF'
> SQL Command : <exec [dbo].[sp_MSsync_ins_Aut_LogBatch_3] N'WN046',
> N'FDF', 250008816, 250000361, N'AUTO', '2006-11-22 16:19:32.000',
> N'34B4', '5992D20D-A9E7-40AF-AB71-43F650E4E8AC', 1>
> Disconnecting from WN055 'WN055'
> Disconnecting from WN046 'WN046'
> Connecting to WN030 'WN030.FDF'
> [11/22/2006 4:32:26 PM]WN055.distribution: exec
> dbo.sp_helpdistpublisher @.publisher = N'WN055'
> Connecting to WN055 'WN055.FDF'
> CQueueRdrRowChange::ApplyCommand:Failed to create instance of
> pMessage->pParams(ProcParams)
> Failed while applying queued message to publisher
> Disconnecting from WN055 'WN055'
> Worker Thread 540 : Task Failed
> Disconnecting from WN030 'WN030'
> Processed 29 queued trans, 57 cmds, 0 conflicts
> Queue Reader aborting
>
> It seem's like the subscriber WN030has some problems comunicating with
> publisher-... right? Any hint?
> Fabio
>
>
> Hilary Cotter ha scritto:
>
|||Sorry for my bad english.. but what do you mean by flushing the
queue? comand queue at the distributor or the queue table at the
subscriber? Do u mean i should delete records one by one?
Hilary Cotter ha scritto:

> No, it looks like it is crashing on a single command. Almost like there is a
> command in the queue causing it to crash.
> Deleting the contents of the queue will cause you to lose work. I would stop
> all users working on the subscriber database and try to flush the queue and
> see if there is a command stuck in there.
> keep logging, and run the queue until one command remains and then I would
> consider deleting that one command.
> Something is very wrong here. I think you should open a support incident
> with Microsoft on this one. Where is Raymond when you really want him?
> --
> 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
>
>

Queue Reader fails to start on publisher

We have configured transactional replication with queue updating
subscriptions. The publisher/distributor on serverA pushes a small db
publication to the subscriber on serverB. When both the publisher and
subscriber are continuously connected, modified data (on either server) is
replicated back and forth just fine. During our tests we decided to manually
stop the SQL server instance on the publisher (which also stops the SQLAgent
service on the publisher) and make data changes on the subscriber. Since the
publisher is unavailable, transactions on the subscriber are put in a queue
per design. When we then manually restart the publisher SQL Server instance,
few strange things happen:
- the SQLServerAgent service on the publisher is not started automatically.
- once we manually start the SQLServerAgent service on the publisher, the
QUEUE Reader Agent on the subscriber fails to start with a series of error
messages like this:
=============
"Server: ServerA, Database mydb : ODBC Error:Could not find stored procedure
''?$?Aw???A?.??''.
"Failed while applying queued message to publisher"
"Queue Reader aborting. The step failed"
=============
In this scenario, the Queue Reader agent remains in "Failed" status (it
doesn't restarts) and therefore the data changes previoulsy made on the
subscriber are not propagated back to the publisher.
Once we manually restart the Queue Reader agent on the publisher, the
changed data is replicated to the subscriber successfully.
Our environment is:
Windows 2003 Server ED
SQL Server 2000 SP3
Is this the expected behavior? Ideas?
can you locate this stored procedure? Is it where it should be?
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
"batuka" <abraxas1969@.hotmail.com> wrote in message
news:O4hT1zLTFHA.3540@.TK2MSFTNGP10.phx.gbl...
> We have configured transactional replication with queue updating
> subscriptions. The publisher/distributor on serverA pushes a small db
> publication to the subscriber on serverB. When both the publisher and
> subscriber are continuously connected, modified data (on either server) is
> replicated back and forth just fine. During our tests we decided to
manually
> stop the SQL server instance on the publisher (which also stops the
SQLAgent
> service on the publisher) and make data changes on the subscriber. Since
the
> publisher is unavailable, transactions on the subscriber are put in a
queue
> per design. When we then manually restart the publisher SQL Server
instance,
> few strange things happen:
>
> - the SQLServerAgent service on the publisher is not started
automatically.
> - once we manually start the SQLServerAgent service on the publisher, the
> QUEUE Reader Agent on the subscriber fails to start with a series of error
> messages like this:
>
> =============
> "Server: ServerA, Database mydb : ODBC Error:Could not find stored
procedure
> ''?$?Aw???A?.??''.
> "Failed while applying queued message to publisher"
> "Queue Reader aborting. The step failed"
> =============
>
> In this scenario, the Queue Reader agent remains in "Failed" status (it
> doesn't restarts) and therefore the data changes previoulsy made on the
> subscriber are not propagated back to the publisher.
>
> Once we manually restart the Queue Reader agent on the publisher, the
> changed data is replicated to the subscriber successfully.
>
> Our environment is:
> Windows 2003 Server ED
> SQL Server 2000 SP3
>
> Is this the expected behavior? Ideas?
>
>
|||I couldn't locate it but by looking at this MS article it appears to be the
fix for this. Only that SP4 doesn't seem to be available any time soon I
believe.
http://support.microsoft.com/default...b;en-us;884854
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23PojRkMTFHA.2560@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> can you locate this stored procedure? Is it where it should be?
> --
> 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
> "batuka" <abraxas1969@.hotmail.com> wrote in message
> news:O4hT1zLTFHA.3540@.TK2MSFTNGP10.phx.gbl...
is[vbcol=seagreen]
> manually
> SQLAgent
> the
> queue
> instance,
> automatically.
the[vbcol=seagreen]
error
> procedure
>

Queue Reader fails occasionally

I am using transactional replication with queued updating between two servers
running SQL Server 2000 SP3. Publisher and distributor run both on the same
server (a cluster machine). There is one subscriber. The Queue Reader Agent
starts successfully, and transactions originating on either side are properly
replicated. However, the Queue Reader occasionally fails. I enabled logging,
but the output file looks normal to me; several queries for queued data, but
then it seems to timeout. It just sits there for 3 minutes, then fails and
retries. No error message in the output file. Finally (after specified count
of retries) the agent shuts down with the message "Remote procedure call
failed". When I try to restart Queue Reader Agent, same behavior. I have to
examine the queue (table MSreplication_queue) and delete the first
respectively first few rows. Before deleting I execute the corresponding
queries (sp calls of type sp_MSsync_upd_MyTable) in Query Analyzer, what
succeeds. After deleting the rows from MSreplication_queue I can restart
Queue Reader Agent and now all works properly up to the next fail. :-(
Does anyone have any advice? Thanks in advance
Dorrit
What if you run these commands manually from the subscriber using QA? What
I'm thinking is that it might be a locking (blocking) issue which you'd be
able to determine using sp_who2 at the publisher.
HTH
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I'm not sure whether I did understand your reply correctly. What I usually do
to solve the problem is running these commands manually at the publisher
using QA. (I simply copy them from the output file.). This functions properly,
I can even track this by querying the correspondent rows at the subscriber
and at the publisher. Before executing the commands in QA, the changes are
only at the subscriber, afterwards they are at both the subscriber and the
publisher. That's why I think it cannot be a locking issue.
Message posted via http://www.droptable.com
|||If it's definitely not blocking then I'm not too sure. You could use
profiler on the publisher to check the commands are getting that far when
running the queue reader agent. You could also simultaneously run profiler
on teh subscriber to confirm the queue is being read.
Rgds,
Paul Ibison, SQL Server MVP
|||OK, I think you could be right. I'll try then with profiler...
Thanks, Dorrit
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...ation/200507/1

Queue Reader fails

I'm running a clustered distributor on SQL 2000 sp3a.
When I stop the publisher that runs in the same cluster
(diffrent SQL server) the Queue reader first logs
"ODBC Error:SQL Server does not exist or access denied."
(It's dead) then it says "Unable to connect to publisher"
and finaly it says "Queue Reader aborting step failed"
and then the queue reader fails.
Any ideas why the queue reader fails?
Is your Queue Reader on the Publisher or Subscriber?
You might want to do some logging to see what the error message is. Follow
the steps in the below link:
http://support.microsoft.com/default...b;EN-US;312292
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Peter Ericsson" <peter.l.ericsson@.ericsson.com> wrote in message
news:29b3201c4658d$2f264d90$a401280a@.phx.gbl...
> I'm running a clustered distributor on SQL 2000 sp3a.
> When I stop the publisher that runs in the same cluster
> (diffrent SQL server) the Queue reader first logs
> "ODBC Error:SQL Server does not exist or access denied."
> (It's dead) then it says "Unable to connect to publisher"
> and finaly it says "Queue Reader aborting step failed"
> and then the queue reader fails.
> Any ideas why the queue reader fails?
|||When I enabled logging for the agent I saw something that
might have been the problem.
In the "Run Agent" step there is a "Step
name", "Type", "Database" and "Command" option.
The Database option read AMS which is one of our user
databases. I changed that to distribution (name of the
distribution database) and now it seems to work. Is this
a SQL bug?
BTW the queue reader runs on the Distributor.
>--Original Message--
>Is your Queue Reader on the Publisher or Subscriber?
>You might want to do some logging to see what the error
message is. Follow
>the steps in the below link:
>http://support.microsoft.com/default.aspx?scid=kb;EN-
US;312292
>--
>Hilary Cotter
>Looking for a book on SQL Server replication?
>http://www.nwsu.com/0974973602.html
>
>"Peter Ericsson" <peter.l.ericsson@.ericsson.com> wrote
in message[vbcol=seagreen]
>news:29b3201c4658d$2f264d90$a401280a@.phx.gbl...
denied."[vbcol=seagreen]
publisher"
>
>.
>
|||Hi,
I had a similar issue. The Queue Reader Agent would fail, and whenever I
tried to restrart I would get the "Queue Reader aborting step failed" error.
after logging the error messages as Hillary suggested, I saw that it was
failing on startup with the following SQL error
[6/22/2004 12:54:22 PM]MAST.Bill: select top 1 id, name from
MSqreader_agents
Server: MAST, Database Bill : ODBC Error:Invalid object name
'MSqreader_agents'.
"Bill" is a user database; the table MSqreader_agents is in the distribution
database. When I looked at the job step that runs the queue reader agent, I
saw that the database dropdown was et to "Bill". This job was created by the
replication setup wizard and never updated. I changed the step to run with
the distribution database, and I was able to restart the agent. However, the
change doesn't "stick"; if I go back and look at the job step, it's set to
run under the Bill" database.
I first thought something on my server had gotten corrupted, but it sounds
like you have the same problem.
If anyone from Microsift reads this newsgroup, please chime in!
Ed
"Peter Ericsson" <peter.l.ericsson@.ericsson.com> wrote in message
news:299fd01c465ad$498c1000$a501280a@.phx.gbl...[vbcol=seagreen]
> When I enabled logging for the agent I saw something that
> might have been the problem.
> In the "Run Agent" step there is a "Step
> name", "Type", "Database" and "Command" option.
> The Database option read AMS which is one of our user
> databases. I changed that to distribution (name of the
> distribution database) and now it seems to work. Is this
> a SQL bug?
> BTW the queue reader runs on the Distributor.
> message is. Follow
> US;312292
> in message
> denied."
> publisher"
|||can either of you script out your tables, publications, subscriptions so I
or MS folks can repro this?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
<ed.d@.osgbilling.com> wrote in message
news:erbmp3eZEHA.3508@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I had a similar issue. The Queue Reader Agent would fail, and whenever I
> tried to restrart I would get the "Queue Reader aborting step failed"
error.
> after logging the error messages as Hillary suggested, I saw that it was
> failing on startup with the following SQL error
> [6/22/2004 12:54:22 PM]MAST.Bill: select top 1 id, name from
> MSqreader_agents
> Server: MAST, Database Bill : ODBC Error:Invalid object name
> 'MSqreader_agents'.
> "Bill" is a user database; the table MSqreader_agents is in the
distribution
> database. When I looked at the job step that runs the queue reader agent,
I
> saw that the database dropdown was et to "Bill". This job was created by
the
> replication setup wizard and never updated. I changed the step to run with
> the distribution database, and I was able to restart the agent. However,
the
> change doesn't "stick"; if I go back and look at the job step, it's set to
> run under the Bill" database.
> I first thought something on my server had gotten corrupted, but it sounds
> like you have the same problem.
> If anyone from Microsift reads this newsgroup, please chime in!
> Ed
>
> "Peter Ericsson" <peter.l.ericsson@.ericsson.com> wrote in message
> news:299fd01c465ad$498c1000$a501280a@.phx.gbl...
>
|||I don't think it has anything to do with our publications
or subscriptions my guess is that both Ed and I have user
database starting in my case with A (AMS) and in Ed's
case B (Bill) and they both are sorted before D
(distribution). So my guess is that if you add a database
at the distributor with a name that sorts
before "distribution" you will see the problem.
/Peter
>--Original Message--
>can either of you script out your tables, publications,
subscriptions so I[vbcol=seagreen]
>or MS folks can repro this?
>--
>Hilary Cotter
>Looking for a book on SQL Server replication?
>http://www.nwsu.com/0974973602.html
>
><ed.d@.osgbilling.com> wrote in message
>news:erbmp3eZEHA.3508@.TK2MSFTNGP09.phx.gbl...
fail, and whenever I[vbcol=seagreen]
aborting step failed"[vbcol=seagreen]
>error.
I saw that it was[vbcol=seagreen]
name from[vbcol=seagreen]
object name[vbcol=seagreen]
is in the[vbcol=seagreen]
>distribution
queue reader agent,[vbcol=seagreen]
>I
job was created by[vbcol=seagreen]
>the
the step to run with[vbcol=seagreen]
the agent. However,[vbcol=seagreen]
>the
job step, it's set to[vbcol=seagreen]
corrupted, but it sounds[vbcol=seagreen]
chime in![vbcol=seagreen]
in message[vbcol=seagreen]
that[vbcol=seagreen]
the[vbcol=seagreen]
this[vbcol=seagreen]
error[vbcol=seagreen]
scid=kb;EN-[vbcol=seagreen]
wrote[vbcol=seagreen]
sp3a.[vbcol=seagreen]
cluster[vbcol=seagreen]
failed"
>
>.
>
|||Hi,
I have the same problem but I achieved that the DB that appears in log would
be the correct one and continues wrong.
I have proved what you say and it continues without working.
"Peter Ericsson" <peter.l.ericsson@.ericsson.com> escribi en el mensaje
news:2ac8f01c467ed$c0c284a0$a501280a@.phx.gbl...[vbcol=seagreen]
> I don't think it has anything to do with our publications
> or subscriptions my guess is that both Ed and I have user
> database starting in my case with A (AMS) and in Ed's
> case B (Bill) and they both are sorted before D
> (distribution). So my guess is that if you add a database
> at the distributor with a name that sorts
> before "distribution" you will see the problem.
> /Peter
> subscriptions so I
> fail, and whenever I
> aborting step failed"
> I saw that it was
> name from
> object name
> is in the
> queue reader agent,
> job was created by
> the step to run with
> the agent. However,
> job step, it's set to
> corrupted, but it sounds
> chime in!
> in message
> that
> the
> this
> error
> scid=kb;EN-
> wrote
> sp3a.
> cluster
> failed"

Queue Reader agent fails to start when stopped through Enterprise Menager

I've set up transactional replication with queued updating. If I stop the queue reader agent through EM, I can't start it again. Agent's history says "Queue Reader aborting. The step failed."
All servers are SQL Server 2000 SP3.
Help is greatly appreciated!OK, I found what my problem was (actually not really mine - it's all EM's fault). When you stop the Queue Reader agent through EM, in reality that process is not stoped, but continues to run on the machine. However, the EM doesn't see it and when you try to start it again, of course , it doesn't want to start another instance of Queue Reader agent.

Basically, I had to go and manually stop the process, and only then start it again through EM.

Bad, bad Enterprise Manager!