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
>