Error number: 37000

From: James McMorrough (james.mcmorrough_at_getrid.sqlpersonnel.com)
Date: 11/02/04 

Date: Tue, 2 Nov 2004 14:52:26 -0000

All,

    I've been configuring Transactional replication in accordance with the
'High Availability' standards, and it seems the initial snapshots have been
transferred but when looking at my distribution agent I can see this error:

Last Command:
{CALL sp_MSdel_Alliance UniChem Norge (RBO)$Customer Posting Group ('ALA')}
Transaction sequence number and command ID of last execution batch are
0x0001A7C400002F8C000900000000 and 1.

Error Details:
Syntax error or access violation
(Source: MOSS-KIPPER (ODBC); Error number: 37000)

    Anyone have a rough idea of what to look at?

James McM

Relevant Pages

  • 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: Reconfigure gnome-terminal in SLES 10
    ... yes,the window is much larger on my 20" screen), I just want it to open that way. ... I was hoping someone in the 'group might have some practical experience with "freedesktop" standards and could point me to the place where Gnome has placed the configuration information so I can change it. ... '--geometry' command line parameter is actually an X Window System ... the standard Linux practice is to have a hidden directory in your home ...
    (alt.os.linux.suse)
  • Re: time out and replication
    ... This means that the distribution agent has issued a command on the ... subscriber and this command is still executing. ... Change querytimeout by right clicking on your distribution agent, ... To change the heartbeat interval Right click Replication Monitor, ...
    (microsoft.public.sqlserver.replication)
  • Stored Procedure Snapshot
    ... I have a publication that consists completely of stored procedures. ... don't feel like sitting and baby sitting the distribution agent for hours.... ... procedure script being applied. ... The command id AND the xact_seqno of the commands that are skipped are both ...
    (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)