Error in Replication how to continue

I have transactional Replication from A to B.

My distribution agent failed becos of a primary key violation error in a table.[i have not included the skip error option].

Then the replication stopped.
The transactions on other tables are also not replicated to B.

IF an error is encountered in one of the tables will the replication stop entirely??.Is there no way for the replication to continue for the rest of the tables..
Pls clarifyI don't think you can skip this error. To use Replication you have to have a primary key in the table you want to replicate.|||The transactions are processed in a serialized fashion, meaning that if one failed nothing else goes through.

Error in Distribution Clean Up Agent

Server 1 SQL 2000 (SP4) Distributor, Publisher
Server 2 SQL 2000 (SP4) Subscriber
Transactional Replication set up between Server 1 and 2.
All the agents are running successfully (Log Reader, Snapshot, Other
Miscellenaous agent...except the Distribution Clean Up Agent
error
Executed as user: COOP\sqladmin. Could not remove directory
'\\ALXCONTGC\ReplData\unc\ALXCONTGC_sales_Pub_Alxo ffc_Anualtrans\20061119100406\'.
Check the security context of xp_cmdshell and close other processes
that may be accessing the directory. [SQLSTATE 42000] (Error 20015)
Replication-@.rowcount_only parameter must be the value 0,1, or 2. 0=7.0
compatible checksum. 1=only check rowcou: agent
distribution@.rowcount_only parameter must be the value 0,1, or 2. 0=7.0
compatible checksum. 1=only scheduled for retry. Could not clean up
the distribution transaction tables. [SQLSTATE 01000] (Message 14152).
The step failed.
?
can you make sure xp_cmdshell is enabled? Do this:
exec master.dbo.sp_configure 'xp_cmdshell'
If run value is 0, do this
exec master.dbo.sp_configure 'xp_cmdshell',1
reconfigure with override
Then start up your distribution clean up task.
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
"noda" <hend_g@.hotmail.com> wrote in message
news:1164102353.485024.276880@.j44g2000cwa.googlegr oups.com...
Server 1 SQL 2000 (SP4) Distributor, Publisher
Server 2 SQL 2000 (SP4) Subscriber
Transactional Replication set up between Server 1 and 2.
All the agents are running successfully (Log Reader, Snapshot, Other
Miscellenaous agent...except the Distribution Clean Up Agent
error
Executed as user: COOP\sqladmin. Could not remove directory
'\\ALXCONTGC\ReplData\unc\ALXCONTGC_sales_Pub_Alxo ffc_Anualtrans\20061119100406\'.
Check the security context of xp_cmdshell and close other processes
that may be accessing the directory. [SQLSTATE 42000] (Error 20015)
Replication-@.rowcount_only parameter must be the value 0,1, or 2. 0=7.0
compatible checksum. 1=only check rowcou: agent
distribution@.rowcount_only parameter must be the value 0,1, or 2. 0=7.0
compatible checksum. 1=only scheduled for retry. Could not clean up
the distribution transaction tables. [SQLSTATE 01000] (Message 14152).
The step failed.
?
|||Is your sql server agent running as an account that is in the sysadmin role?
If not it'll try to use the proxy account that might not have been
configured.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

Error in Distribution Agent

Hello.
We're running SQL Server 2000.
I've created a transactional publication with queued updating at server
"DATASERVER1" .
When I attempt to push a subscription I receive an error in the Distribution
Agent, as follows:
Server 'DATASERVER1' is not configured for DATA ACCESS
Can anyone tell me what this means? I cannot find anything on MSDN.
Thank you in advance,
Mike
Can you check the value of sp_configure 'remote access' on the subscriber.
Also, please check select @.@.servername to ensure the name is the
netbiosname.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Hi, Paul. Thanks for the response.
I ran "sp_configure 'remote access'" and got: minimum=1, maximum=1,
config_value=1, run_value=1.
The name is the NetBios name.
Does it matter that the subscriber and distributor is the same machine?
Thanks again,
Mike
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:uO6qyNGPFHA.1884@.TK2MSFTNGP15.phx.gbl...
> Can you check the value of sp_configure 'remote access' on the subscriber.
> Also, please check select @.@.servername to ensure the name is the
> netbiosname.
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Mike,
this is not a problem. Usually it is the other way round - publisher and
distributor on the same box, though - is there a particular reason you are
implementing it this way? As for the message, I'm not sure what the problem
is . Is there connectivity between the servers? Can you open a QA windon
on the publisher and connect to the subscriber ok? What if you try setting
up a linked server on the subscriber to the publisher as a separate test -
do you get the same error?
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)