When the Snapshot Agent runs after you make schema changes to the underlying tables of a publication, the Snapshot Agent may fail. You may receive a syntax error message that is similar to the following:

Back to the top

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

Hotfix information

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

   Date         Time   Version            Size    File name
   --------------------------------------------------------------------
   31-May-2003  18:45  2000.80.818.0      78,400  Console.exe      
   28-Oct-2003  04:21  2000.80.873.0     315,968  Custtask.dll     
   02-Oct-2003  20:59  2000.80.867.0      33,340  Dbmslpcn.dll     
   25-Apr-2003  02:12                    786,432  Distmdl.ldf
   25-Apr-2003  02:12                  2,359,296  Distmdl.mdf
   30-Jan-2003  01:55                        180  Drop_repl_hotfix.sql
   12-Sep-2003  03:26  2000.80.859.0   1,905,216  Dtspkg.dll       
   26-Aug-2003  20:16  2000.80.854.0     528,960  Dtspump.dll      
   23-Jun-2003  22:40  2000.80.837.0   1,557,052  Dtsui.dll        
   23-Jun-2003  22:40  2000.80.837.0     639,552  Dtswiz.dll       
   24-Apr-2003  02:51                    747,927  Instdist.sql
   10-Oct-2003  18:52                    745,961  Instmsdb.sql
   03-May-2003  01:56                      1,581  Inst_repl_hotfix.sql
   08-Feb-2003  06:40  2000.80.765.0      90,692  Msgprox.dll      
   01-Apr-2003  02:07                      1,873  Odsole.sql
   05-Apr-2003  01:46  2000.80.800.0      62,024  Odsole70.dll     
   07-May-2003  20:41  2000.80.819.0      25,144  Opends60.dll     
   02-Apr-2003  21:48  2000.80.796.0      57,904  Osql.exe         
   02-Apr-2003  23:15  2000.80.797.0     279,104  Pfutil80.dll     
   04-Aug-2003  18:17                    550,780  Procsyst.sql
   12-Sep-2003  00:37                     12,305  Qfe469315.sql
   22-May-2003  22:57                     19,195  Qfe469571.sql
   06-Sep-2003  01:36                  1,090,932  Replmerg.sql
   06-Sep-2003  07:18  2000.80.858.0     221,768  Replprov.dll     
   06-Sep-2003  07:18  2000.80.858.0     307,784  Replrec.dll      
   06-Sep-2003  00:00                  1,087,150  Replsys.sql
   13-Aug-2003  16:28                    986,603  Repltran.sql
   02-Jan-2004  19:42  2000.80.904.0     287,304  Rinitcom.dll     
   22-Oct-2003  00:08  2000.80.871.0      57,916  Semnt.dll        
   29-Jul-2003  20:13  2000.80.819.0     492,096  Semobj.dll       
   31-May-2003  18:27  2000.80.818.0     172,032  Semobj.rll
   02-Jan-2004  19:42  2000.80.904.0      53,832  Snapshot.exe     
   05-Aug-2003  21:06                    127,884  Sp3_serv_uni.sql
   02-Jan-2004  19:41  2000.80.904.0      28,672  Sqlagent.dll     
   02-Jan-2004  19:42  2000.80.904.0     311,872  Sqlagent.exe     
   01-Jun-2003  01:01  2000.80.818.0   4,215,360  Sqldmo.dll       
   07-Apr-2003  17:44                     25,172  Sqldumper.exe    
   19-Mar-2003  18:20  2000.80.789.0      28,672  Sqlevn70.rll
   27-Sep-2003  04:42  2000.80.865.0     180,792  Sqlmap70.dll     
   03-Sep-2003  02:56  2000.80.857.0     188,992  Sqlmmc.dll       
   02-Sep-2003  23:03  2000.80.857.0     479,232  Sqlmmc.rll
   22-Oct-2003  00:08  2000.80.871.0     401,984  Sqlqry.dll       
   08-Feb-2003  06:40  2000.80.765.0      57,920  Sqlrepss.dll     
   28-Dec-2003  01:55  2000.80.904.0   7,606,353  Sqlservr.exe     
   25-Jul-2003  21:44  2000.80.845.0     590,396  Sqlsort.dll      
   08-Feb-2003  06:40  2000.80.765.0      45,644  Sqlvdi.dll       
   02-Oct-2003  20:59  2000.80.867.0      33,340  Ssmslpcn.dll     
   01-Jun-2003  01:01  2000.80.818.0      82,492  Ssnetlib.dll     
   01-Jun-2003  01:01  2000.80.818.0      25,148  Ssnmpn70.dll     
   28-Oct-2003  04:21  2000.80.873.0     123,456  Stardds.dll      
   01-Jun-2003  01:01  2000.80.818.0     158,240  Svrnetcn.dll     
   31-May-2003  18:59  2000.80.818.0      76,416  Svrnetcn.exe     
   30-Apr-2003  23:52  2000.80.816.0      45,132  Ums.dll          
   02-Jul-2003  00:19  2000.80.834.0      98,816  Xpweb70.dll      

Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.

This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.

Back to the top

If you run a profiler trace on the distributor when the problem occurs, you see the following command:

exec sp_MSadd_repl_command @publisher_id = 1, @publisher_db  =
		  N'PublishDb1', @type = -2147483639, @article_id = 250, @xact_id =
		  0x000000000000, @xact_seqno = 0x0001527500001926000100000001, @command_id =
		  1328, @partial_command = 0, @command =
		  0x7b00630061006c006c002000730070005f00610064006400730079006e00630074007200690067006700650072007300200028004e002700740062006c005f00720073005f0061006e0061006c007900730074005f006d0061006e006100670065006d0065006e0074005f007300630068006500640075006c00650027002c0020004e0027006e0075006c006c0027002c0020004e002700530051004c00530031004e004a00320055005300300031005c00500044003000310027002c0020004e002700500068006f0065006e00690078004e004a00320027002c0020004e002700500068006f0065006e00690078004e004a00320027002c0020004e002700730070005f004d005300730079006e0063005f0069006e0073005f00740062006c005f00720073005f0061006e0061006c007900730074005f006d0061006e006100670065006d0065006e0074005f007300630068006500640075006c0065005f00310027002c0020004e002700730070005f004d005300730079006e0063005f007500700064005f00740062006c005f00720073005f0061006e0061006c007900730074005f006d0061006e006100670065006d0065006e0074005f007300630068006500640075006c0065005f00310027002c0020004e002700730070005f004d005300730079006e0063005f00640065006c005f00740062006c005f00720073005f0061006e0061006c007900730074005f006d0061006e006100670065006d0065006e0074005f007300630068006500640075006c0065005f00310027002c0020004e002700730070005f004d0053006300660074005f00500068006f0065006e00690078004e004a0032005f00740062006c005f00720073005f0061006e0061006c007900730074005f006d0061006e006100670065006d0065006e0074005f007300630068006500640075006c00650027002c0020004e002700640062006f0027002c0020004e00270061006e0061006c007900730074005f006d0061006e006100670065006d0065006e0074005f007300630068006500640075006c0065005f006900640027002c0020004e0027006e0075006c006c0027002c0020004e0027006e0075006c006c0027002c00200030007800300031003000300030003000300030002c00200030002c0031002c004e002700530051004c00530031004e004a00320055005300300033005c0050004400300036002700200029007d00
		  004e0027???3Ÿ3??004c00530031004e004a00320055005300300033005c0050004400300036002700200029007d00

This command was being inserted into the distribution database when the problem occurred. This command is exactly 2,048 characters long, as shown in the following query.

Note The hexidecimal BLOB was truncated where the end of the command should be.

select datalength(' exec sp_MSadd_repl_command @publisher_id = 1, @publisher_db  = N''PublishDb1'', @type = -2147483639, @article_id = 250, @xact_id = 0x000000000000, @xact_seqno = 0x0001527500001926000100000001, @command_id = 1328, @partial_command = 0, @command = 0x7b00630061006c006c002000730070005f00610064006400730079006e00630074007200690067006700650072007300200028004e002700740062006c005f00720073005f0061006e0061006c007900730074005f006d0061006e006100670065006d0065006e0074005f007300630068006500640075006c00650027002c0020004e0027006e0075006c006c0027002c0020004e002700530051004c00530031004e004a00320055005300300031005c00500044003000310027002c0020004e002700500068006f0065006e00690078004e004a00320027002c0020004e002700500068006f0065006e00690078004e004a00320027002c0020004e002700730070005f004d005300730079006e0063005f0069006e0073005f00740062006c005f00720073005f0061006e0061006c007900730074005f006d0061006e006100670065006d0065006e0074005f007300630068006500640075006c0065005f00310027002c0020004e002700730070005f004d005300730079006e0063005f007500700064005f00740062006c005f00720073005f0061006e0061006c007900730074005f006d0061006e006100670065006d0065006e0074005f007300630068006500640075006c0065005f00310027002c0020004e002700730070005f004d005300730079006e0063005f00640065006c005f00740062006c005f00720073005f0061006e0061006c007900730074005f006d0061006e006100670065006d0065006e0074005f007300630068006500640075006c0065005f00310027002c0020004e002700730070005f004d0053006300660074005f00500068006f0065006e00690078004e004a0032005f00740062006c005f00720073005f0061006e0061006c007900730074005f006d0061006e006100670065006d0065006e0074005f007300630068006500640075006c00650027002c0020004e002700640062006f0027002c0020004e00270061006e0061006c007900730074005f006d0061006e006100670065006d0065006e0074005f007300630068006500640075006c0065005f006900640027002c0020004e0027006e0075006c006c0027002c0020004e0027006e0075006c006c0027002c00200030007800300031003000300030003000300030002c00200030002c0031002c004e002700530051004c00530031004e004a00320055005300300033005c0050004400300036002700200029007d00 ')

The function that was manipulating the command string was not null-terminating the string if its length was an exact multiple of 2,048. Depending on the number and the arrangement of articles in the publication, the problem might not appear from one snapshot generation to the next snapshot generation. This hotfix makes sure that the resulting string is null-terminated, even when its length is an exact multiple of 2,048.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top