Re: Suspended Merge Replication Job

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Shahin Yousefi (shahin_yousefi_mcse_at_hotmail.com)
Date: 10/14/04 

Date: Thu, 14 Oct 2004 08:19:55 -0400

No, that's not the error message. The error message is actually being
returned by the JOB (from Enterprise Manager, browse to the server >
Management > SQL Server Agent > Jobs). This isn't the subscription as shown
through the Replication Monitor. ANY job could become suspended, not just
replication jobs.

Reinitialization isn't an option. The WAN link isn't fast enough and the
publication is too large.

- Shahin

"Hilary Cotter" <hilary.cotter@gmail.com> wrote in message
news:OlwZvVesEHA.3604@TK2MSFTNGP15.phx.gbl...
> I suspect you are mistranslating as I am unaware of the "suspend" error
> message.
>
> Is this the error number/message you are getting?
>
> 14157 The subscription created by Subscriber '%s' to publication
'%s'
> has expired and has been dropped.
>
> or
>
> 20538 Replication: expired subscription dropped
>
> or
>
> 21056 The subscription to publication '%s' has expired and does not
> exist.
>
> If so you will have to run your snapshot agent again to redeploy it.
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
>
> "Shahin Yousefi" <shahin_yousefi_mcse@hotmail.com> wrote in message
> news:%23yvXrBXsEHA.3136@TK2MSFTNGP11.phx.gbl...
> > Hello all,
> > I have a merge publication on one end of a slow WAN link and a
> subscription
> > to said publication on the other end of the aforementioned slow WAN
link.
> >
> > Recently, the link decided to take a vacation for a week or two and was
> (for
> > all intents and purposes) inoperable. Upon finally fixing the link, I
came
> > to realize that the pull subscription job wasn't running as it should be
> > (I'm supposing it decided seize the opportunity and vacation as well).
> When
> > I attempted to start the job manually I was told that the job couldn't
be
> > run because of "Error 22022: SQLServerAgent Error: Request to run job
> > BlahBlahBlahBlah (from User BLAH\BlahBlah) refused because the job has
> been
> > suspended."
> >
> > Naturally I was alarmed at the cavalier nature of a rogue job refusing
to
> > run at my beck and call at which point I sought to find out where this
> > treacherous "suspended" flag was raised.
> >
> > I was unable to a) locate the table in which this "suspended" value was
> > stored, but I believe it to be returned by the extended stored procedure
> > "xp_sqlagent_enum_jobs"; b) find out how to un-suspend my vacationing
job;
> > c) find any information in the KB and/nor through search engines
regarding
> > this specific problem.
> >
> > Has anyone run into this before and, if so, what was done to resolve
it...
> > and, if not, any other tips?
> >
> > Best regard and TIA,
> > Shahin Yousefi
> >
> >
>
>

Relevant Pages

  • Re: Host Name Change and Replication
    ... the msdb.sysjobs did still contain PDB01 as the server originator and this caused the 14274 error about the MSX. ... I then added accountName user to the Security folder again, reenabled replication, and then made sure each agent was using the accountName and tested the replication. ... Unfortunately on DGP09 and TDB10 in their> subscription folder each had a push subscription pointing to PDB01 which no> longer exsists. ...
    (microsoft.public.sqlserver.server)
  • Re: Merge/FTP schema propogation failure
    ... Got two boxes running SQL Server 2000, ... Trying to set up Merge replication between them, using FTP. ... Creating a subscription from another machine (also in the same Domain, ...
    (microsoft.public.sqlserver.replication)
  • NT Group user not in PAL, error in Snapshot Agent log
    ... We are using merge replication from a SQL Server 2008 server to SQL ... subscription whose credentials are a user in that NT group, ...
    (microsoft.public.sqlserver.replication)
  • Re: SQLEXPRESS Replication?
    ... I set up Merge replication but it fails and the links in the error message go nowhere. ... The documentation says I can but isn't really specific if SQL Express can do this. ... I was trying to use replication to give the remote site users faster read access but still allow updates from the subscriber. ... When I tried this with Virtual Server to test I got a different error saying I need to run sp_link_publication on the subscriber to set a password for the sa account. ...
    (microsoft.public.sqlserver.replication)
  • Re: NTDS Replication error 2042, despite increased tombstone lifetime
    ... The tombstone lifetime was increased to 360 days. ... After a few months, the server was brought ... The error message states that the tombstone lifetime is only 60 days, ... The "Allow Replication With Divergent and Corrupt Partner" registry key ...
    (microsoft.public.windows.server.active_directory)