problem pushing subscriber updates to publisher in transactional replication -

I have a primary and secondary servers both running Windows 2000 SP3 with SQL 2000 SP3. I have set up transactional replication with the primary server as publisher and the secondary server has the distributor and subscriber DB. I am testing the scenerio where my primary server goes down and I have to make updates to the secondary server until my primary server comes back up. I am able to update my subscriber database and the transactions go into the MSreplication_queue table to be pushed back to the primary when it comes back up. When I bring the primary server back up and start the queue agent job it starts pushing the transactions over and then stops after 4 or 5 transactions with the error "Failed while applying queued message to publisher". I have attached part of the log file for the agent below

dbserver2.Old_Processing: {? = call dbo.sp_getsqlqueueversion (?, ?, ?, ?)}
dbserver2.Old_Processing: {? = call dbo.sp_replsqlqgetrows (N'DBSERVER', N'Old_Processing', N'Old_Processing')}
[4/15/2004 3:59:47 PM]dbserver2.distribution: exec dbo.sp_helpdistpublisher @.publisher = N'DBSERVER'
Connecting to DBSERVER 'DBSERVER.Old_Processing'
DBSERVER.Old_Processing: {? = call dbo.sp_getqueuedarticlesynctraninfo (N'Old_Processing', 21)}
SQL Command : <exec [dbo].[sp_MSsync_ins_IQ2KProcSystem_1] N'dbserver2', N'Old_Processing', '072175', '2004-03-19 00:00:00.000', 1>
DBSERVER.Old_Processing: {? = call dbo.sp_getqueuedarticlesynctraninfo (N'Old_Processing', 15)}
SQL Command : <exec [dbo].[sp_MSsync_ins_NightlyProcess_1] N'dbserver2', N'Old_Processing', '072175', '2004-03-19 00:00:00.000', '2004-04-15 15:56:44.623000000', 'Begin ProcessIQ2KSystem', 'AB14E5D7-C81D-4A39-A8F5-51F1C48227B0', '17E5D98F-EDF0-41D0-9991-97511B850720', 1>
SQL Command : <exec [dbo].[sp_MSsync_upd_IQ2KProcSystem_1] N'dbserver2', N'Old_Processing', '072175', '2004-03-19 00:00:00.000', 1>
DBSERVER.Old_Processing: {? = call dbo.sp_getqueuedarticlesynctraninfo (N'Old_Processing', 7)}
SQL Command : <exec [dbo].[sp_MSsync_upd_TheatreProcess_1] N'dbserver2', N'Old_Processing', '072175', 1, '2004-03-19 00:00:00.000', 1, NULL, '79A114D6-FF31-4E37-AC2D-90C0A0114F40', '072175', 1, '2004-03-19 00:00:00.000', 0, NULL, 'AF61A098-44A3-45D7-B25B-E8EA9CD464A1', 0x2800, 1>
Failed while applying queued message to publisher
Disconnecting from DBSERVER 'DBSERVER'
Worker Thread 692 : Task Failed
Disconnecting from dbserver2 'dbserver2'
Processed 3 queued trans, 3 cmds, 0 conflicts
Queue Reader aborting

In the sql server logs I am getting this message:
Replication-Replication Transaction Queue Reader Subsystem: agent Repl Queue Reader failed. Failed while applying queued message to publisher.
Error: 14151, Severity: 18, State: 1

Any help would be greatly appreciatedFew suggestions:
Refer to SQLAgent log for further information.
Meanwhile, stopping and restarting SQLServerAgent may allow you to temporarily resolve the problem that you are experiencing.

Did you try to forcefully terminate any replication agents in task manager by any chance?

Finally, running the snapshot agent from the command line may allow you to determine whether it was the snapshot agent that crashed unexpectedly.|||Originally posted by Satya
Few suggestions:
Refer to SQLAgent log for further information.
Meanwhile, stopping and restarting SQLServerAgent may allow you to temporarily resolve the problem that you are experiencing.

Did you try to forcefully terminate any replication agents in task manager by any chance?

Finally, running the snapshot agent from the command line may allow you to determine whether it was the snapshot agent that crashed unexpectedly.

The SQLAgent log did not have any errors in it

Stopping and restarting SQLServerAgent did not allow me to temporarily resolve this problem. I still get the same error.

I did not forcefully terminate any replication agents in task manager.

Should I run the snapshot agent from the command line or the queue agent since the queue agent is what is failing?

I tried running the queue agent from the command line and it failed with the same error as above|||Check whether the KBA [http://support.microsoft.com/default.aspx?scid=kb;EN-US;294970] is any good to you.|||I don't think that is my problem. The only way I have been able to get the queue agent to work again is to either drop and readd the subscription or reinitialize the subscription. Of course when I do this it wipes out any updates that have been done to the subscriber.

Problem installing SQL Server 2005 SP2

The problem seems to be with the authentication. It froze when Windows
updates attempted to install it, so I downloaded the exe from the ms
site. However this freezes too while running the "Authentication
Verification". This also happens if I just click the Test button.
I tried both Windows Authentication and SQL authentication and same
happens on both.
Any ideas what could cause this problem?
Thanks,
zoro.I've seen it during upgrade of a piece of ... PC ( 4GB HD, 128MB RAM, P
III ). It didn't really locked up though,
but it took good 10 minutes... could it be resource related in your case
too?
r
"Zoro" <ilzoro@.gmail.com> wrote in message
news:1175276243.694408.227930@.l77g2000hsb.googlegroups.com...
> The problem seems to be with the authentication. It froze when Windows
> updates attempted to install it, so I downloaded the exe from the ms
> site. However this freezes too while running the "Authentication
> Verification". This also happens if I just click the Test button.
> I tried both Windows Authentication and SQL authentication and same
> happens on both.
> Any ideas what could cause this problem?
> Thanks,
> zoro.
>|||On 30 Mar, 21:26, "Rafael Lenartowicz" <rafa...@.rcl-consulting.com>
wrote:
> I've seen it during upgrade of a piece of ... PC ( 4GB HD, 128MB RAM, P
> III ). It didn't really locked up though,
> but it took good 10 minutes... could it be resource related in your case
> too?
> r
> "Zoro" <ilz...@.gmail.com> wrote in message
> news:1175276243.694408.227930@.l77g2000hsb.googlegroups.com...
> > The problem seems to be with the authentication. It froze when Windows
> > updates attempted to install it, so I downloaded the exe from the ms
> > site. However this freezes too while running the "Authentication
> > Verification". This also happens if I just click the Test button.
> > I tried both Windows Authentication and SQL authentication and same
> > happens on both.
> > Any ideas what could cause this problem?
> > Thanks,
> > zoro.
No - this pc is a P4 3 GHz, 1GB memory and about 6 GB free disk space.
I also let it run for about an hour before I used the Task Manager to
kill it.
zoro.|||Hi
"Zoro" wrote:
> On 30 Mar, 21:26, "Rafael Lenartowicz" <rafa...@.rcl-consulting.com>
> wrote:
> > I've seen it during upgrade of a piece of ... PC ( 4GB HD, 128MB RAM, P
> > III ). It didn't really locked up though,
> > but it took good 10 minutes... could it be resource related in your case
> > too?
> > r
> >
> > "Zoro" <ilz...@.gmail.com> wrote in message
> >
> > news:1175276243.694408.227930@.l77g2000hsb.googlegroups.com...
> >
> > > The problem seems to be with the authentication. It froze when Windows
> > > updates attempted to install it, so I downloaded the exe from the ms
> > > site. However this freezes too while running the "Authentication
> > > Verification". This also happens if I just click the Test button.
> > > I tried both Windows Authentication and SQL authentication and same
> > > happens on both.
> > > Any ideas what could cause this problem?
> > > Thanks,
> > > zoro.
> No - this pc is a P4 3 GHz, 1GB memory and about 6 GB free disk space.
> I also let it run for about an hour before I used the Task Manager to
> kill it.
> zoro.
>
You may have connectivity problems to the AD? What do the upgrade logs say?
John