trans repl - distribution agent doesn't deliver transactions

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

From: OJ (anonymous_at_discussions.microsoft.com)
Date: 12/17/04 

Date: Thu, 16 Dec 2004 19:47:53 -0800

Just to add something... Meanwhile I turned on verbose
logging of distribution agent, and I noticed, here and
there, several errors in this log file:

37000 Line 1: Incorrect syntax near '2004-12-15
00:00:00.000'. 170
Last transaction timestamp: 0x000008da0004fa9b002c00000000
Transaction seqno: 0x000008da0004fa9b002c
Command Id: 19
Partial: 0
Type: 0
Command:
Failed command = {CALL sp_InsertOrder
(214763321, 'Install ', 0, 'acÇ@?pwà@?', -1, 0)}{.......

Last transaction timestamp: 0x000008da0004fa9b002c00000000
Transaction seqno: 0x000008da0004fa9b002c
Command Id: 18
Partial: 0
Type: 0
Command: {CALL sp_InsertOrder(214763321, 'Operatio ',
{ts '2004-06-16 00:00:00.000'}, 1, -1, {ts '2003-05-19
00:00:00.000'}, {ts '2003-06-04 00:00:00.000'}, 0)}

***************************************************
What I don't understand is, how syntax errors, if any,
can stop distribution agent from replicating
transactions...
OJ

Relevant Pages

  • Re: Distribution Agent fails with error: Line 1: Incorrect syntax near ,null,
    ... You mentioned manipulating the command in the msrepl_commands table. ... transaction capable: 2 ... Last transaction timestamp: 0x000004810000069f000900000000 ... Transaction seqno: 0x00000481000006e70001 ...
    (microsoft.public.sqlserver.replication)
  • Re: Distribution Agent fails with error: Line 1: Incorrect syntax near ,null,
    ... > You mentioned manipulating the command in the msrepl_commands table. ... > transaction capable: 2 ... > Last transaction timestamp: 0x00000481000006e7000100000000> Transaction seqno: 0x00000481000006e70001> Command Id: 2 ...
    (microsoft.public.sqlserver.replication)
  • Re: Replication Issues
    ... Looking for a SQL Server replication book? ... The above command will indicate which table on the subscriber is ... Please also check that the distribution agent is ether running ... Last transaction timestamp: 0x0000042d000003ff000100000000 ...
    (microsoft.public.sqlserver.replication)
  • Re: Distribution Agent Startup Parameters
    ... have a manageable log size when a concurrent snapshot is applied in ... transaction log for large tables? ... the SQL2000 index creation logic in the distribution agent is not very ... having problems with the transaction log growing so large on the ...
    (microsoft.public.sqlserver.replication)
  • Re: Error 207 doing Transactional replication via Internet
    ... the command that is causing the problem (you may have to check against the ... last recorded transaction to arrive in the subscriber to find the subsequent ... run it in QA on the subscriber and check the ...
    (microsoft.public.sqlserver.replication)