Re: Replication Failure with Event ID 203

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

From: Hilary Cotter (hilaryk_at_att.net)
Date: 07/25/04


Date: Sun, 25 Jul 2004 08:51:32 -0400

it looks like your distribution agent has no problems connecting to your
Publisher, but is having a problem connecting to your Distributor. I take it
you are using a local distributor on the server MSSQLServer. Is this the
name of your Publisher?

Can you also expand replication monitor, expand agents, expand distribution
agent, right click on your distribution agent, select agent properties, go
to the steps tab, and click on commands and tell me your values for

-Distributor
and
-DistributorSecurityMode

-- 
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Terry Glass" <Terry Glass@discussions.microsoft.com> wrote in message
news:53C96240-EB20-4CE5-8669-22F6F60CA76E@microsoft.com...
> I set up a test computer running Windows 2000 Advanced Server with SP4
called INST. It has Exchange 2000 with SP3 on it and is the only domain
controller for its forest.
> I loaded two instances of SQL 2000 Enterprise, default instance and
another called SECOND. SQL has SP3A loaded.
> I sent up snapshot replication with the distributor and publisher running
on the default instance, to a database on the second instance. Should be no
problem but the distribution agent is failing and the event log has the
following:
>
> Source: SQLServerAgent
> Category: Job Engine
> Event ID: 203
> Description:
> SubSystem Message - Job 'Inst-docsdb-INST\Second - 1'
(0X10CBFD71D9B6AA4EB7B6B6FE875521A4). step 2 - The process could not connect
to Distributor 'MSSQLServer'.
>
> The service agent is a member of the administrator and domain adminstrator
groups, both SQL instances are using the same service account for both
MSSQLServer and SQLServerAgent. I have System Administrator rights in SQL on
both instances. I tried uninstalling then reinstalling SQL with and without
SQL SP3A, same problem. I have set this up before, the only difference is
Windows has Service Pack 4 on it. As we are going to be ugrading to SP4 on
our SQL servers I would like to figure out what is going on.
>
> Help would be appreciated.
>
>


Relevant Pages

  • Re: The distribution agent says "No Replicated Transactions are Available" but I dont believe it.
    ... The published database is very large. ... Both servers are SQL Server 2000 SP4. ... It turned out that these were due to the distribution ... clean-up agent locking the distribution database. ...
    (microsoft.public.sqlserver.replication)
  • Re: Deadlock between Distribution Agent and Distribution Agent Cle
    ... Another option will be to put your distribution database in bulk copy ... Looking for a SQL Server replication book? ... The Distribution Agent Cleanup job code ... and only reading the transactions committed some ...
    (microsoft.public.sqlserver.replication)
  • Re: Moving Distribution mdf/ldf (maintain logical drive/path) ?
    ... you can't do with the distribution database or published databases. ... Looking for a SQL Server replication book? ... respectively are now logical drives on top of a hardware RAID array so ...
    (microsoft.public.sqlserver.replication)
  • Re: Agent Deadlock Errors
    ... I am not sure about updating the statistics in the distribution database. ... clean up agent is locking with. ... Looking for a SQL Server replication book? ...
    (microsoft.public.sqlserver.replication)
  • Re: Moving Distribution mdf/ldf (maintain logical drive/path) ?
    ... I will shut down SQL Service at the Publisher/Distributor, then filecopy at the O/S level the distribution mdf/ldf files to a temp location, then copy them back to the same logical drive letter and path once I create them under a new raid array config. ... I need to do this so I can get both distribution mdf/ldf files off single disk volumes (logical drives), and onto RAID arrays for fault tolerance. ...
    (microsoft.public.sqlserver.replication)