Microsoft KB Archive/837231

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 18:13, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Article ID: 837231

Article Last Modified on 11/2/2007


APPLIES TO

  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Personal Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Workgroup Edition
  • Microsoft SQL Server 2000 Desktop Engine (Windows)
  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Enterprise Edition 64-bit


Bug #: 471158 (SQL Server 8.0)


Microsoft SQL Server 2000 fixes are distributed as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2000 fix release.

SYMPTOMS

When you add a column to a published article or drop a column from a published article, and the article is participating in a transactional replication, the corresponding Distribution Agent may not run successfully. You may receive an error message that is similar to the following:

Unclosed quotation mark before the character string 'Column Name'.

This problem may occur when the following conditions are true:

  • The article is configured to use SQL commands to replicate the INSERT command, the UPDATE command, or the DELETE command to the corresponding subscribers.
  • The changes, such as inserts, updates, or deletes, that are made in the article at the Publisher are not yet applied at the Subscribers.


RESOLUTION

Service pack information

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

290211 How to obtain the latest SQL Server 2000 service pack


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 
   30-Jan-2004  16:29  2000.80.911.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 
   03-May-2003  01:56                     1,581  Inst_repl_hotfix.sql 
   30-Jan-2004  16:29  2000.80.911.0     90,692  Msgprox.dll 
   01-Apr-2003  02:07                     1,873  Odsole.sql 
   30-Jan-2004  16:29  2000.80.911.0     62,024  Odsole70.dll 
   30-Jan-2004  16:29  2000.80.911.0     25,144  Opends60.dll 
   30-Jan-2004  16:28  2000.80.911.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 
   30-Jan-2004  01:16                 1,090,380  Replmerg.sql 
   30-Jan-2004  16:29  2000.80.911.0    221,768  Replprov.dll 
   30-Jan-2004  16:29  2000.80.911.0    307,784  Replrec.dll 
   29-Jan-2004  23:24  2000.80.911.0    159,813  Replres.rll 
   06-Sep-2003  00:00                 1,087,150  Replsys.sql 
   13-Aug-2003  16:28                   986,603  Repltran.sql 
   30-Jan-2004  16:29  2000.80.911.0    287,304  Rinitcom.dll 
   30-Jan-2004  16:29  2000.80.911.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 
   09-Dec-2003  20:07                   117,834  Sp3_serv_uni.sql 
   05-Feb-2004  00:46  2000.80.913.0     28,672  Sqlagent.dll 
   05-Feb-2004  00:47  2000.80.913.0    311,872  Sqlagent.exe 
   19-Feb-2004  18:02  2000.80.916.0    168,001  Sqlakw32.dll 
   30-Jan-2004  16:29  2000.80.911.0  4,215,360  Sqldmo.dll 
   07-Apr-2003  17:44                    25,172  Sqldumper.exe 
   29-Jan-2004  23:17  2000.80.911.0     28,672  Sqlevn70.rll 
   05-Mar-2004  17:13  2000.80.922.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 
   30-Jan-2004  16:29  2000.80.911.0     57,920  Sqlrepss.dll 
   09-Mar-2004  19:54  2000.80.922.0  7,614,545  Sqlservr.exe 
   30-Jan-2004  16:29  2000.80.911.0    590,396  Sqlsort.dll 
   30-Jan-2004  16:29  2000.80.911.0     45,644  Sqlvdi.dll 
   30-Jan-2004  16:29  2000.80.911.0    106,588  Sqsrvres.dll
   30-Jan-2004  16:29  2000.80.911.0     33,340  Ssmslpcn.dll
   30-Jan-2004  16:29  2000.80.911.0     82,492  Ssnetlib.dll 
   30-Jan-2004  16:29  2000.80.911.0     25,148  Ssnmpn70.dll 
   28-Oct-2003  04:21  2000.80.873.0    123,456  Stardds.dll 
   30-Jan-2004  16:29  2000.80.911.0    158,240  Svrnetcn.dll 
   30-Jan-2004  16:29  2000.80.911.0     76,416  Svrnetcn.exe 
   30-Apr-2003  23:52  2000.80.816.0     45,132  Ums.dll 
   30-Jan-2004  16:29  2000.80.911.0     98,872  Xpweb70.dll

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

WORKAROUND

To work around this problem, you must configure the article to use the stored procedures to replicate the INSERT command, the UPDATE command, or the DELETE command to the corresponding subscribers. To do this, follow these steps at the Publisher:

  1. Run the following code to drop all subscriptions to your article:

    USE Publication Database
GO

EXEC sp_dropsubscription 
    @publication=N'Publication Name', 
    @subscriber = N'all', 
    @article = N'Article Name', 
    @destination_db = N'all'
GO

  2. Run the following code to drop the article from your current transactional publication:

    USE Publication Database
GO

EXEC sp_droparticle 
    @publication = N'Publication Name', 
    @article = 'Article Name',
    @force_invalidate_snapshot = 1
GO

  3. Add your article to your current transactional publication so that the article uses stored procedures to replicate the INSERT command, the UPDATE command, or the DELETE command to the corresponding subscribers. To do this, run the following code:

    USE Publication Database
GO

EXEC sp_addarticle 
    @publication = N'Publication Name', 
    @article = N'Article Name', 
    @source_owner = N'dbo', 
    @source_object = N'Source Table Name', 
    @destination_table = N'Destination Table Name', 
    @type = N'logbased', 
    @creation_script = null, 
    @description = null, 
    @pre_creation_cmd = N'drop', 
    @schema_option = 0x00000000000000F3, 
    @status = 16, 
    @vertical_partition = N'false', 
    @ins_cmd = N'sp_MSins_Article Name', 
    @del_cmd = N'sp_MSdel_Article Name', 
    @upd_cmd = N'sp_MSupd_Article Name', 
    @filter = null, 
    @sync_object = null, 
    @auto_identity_range = N'false'
GO

    Note Make sure that you modify the following parameters before you run the Transact-SQL statements:

    • @publication: Name of the current publication
    • @article: Name of the new article
    • @source_object: Name of the underlying table that is represented by the new article
    • @destination_table: Name of the destination table that will be created at the Subscriber
    • @ins_cmd: CALL sp_MSins_Article Name
    • @del_cmd: CALL sp_MSdel_Article Name
    • @upd_cmd: MCALL sp_MSupd_Article Name
    • @force_invalidate_snapshot: 1, if a snapshot is already generated for the publication

    Additionally, if your article contains an identity column, and you want SQL Server to manage the identity range handling, you must set the parameter @auto_identity_range to true.

  4. Add subscriptions to the article that is added to your transactional publication:

    • For each push subscription that subscribes to your current transactional publication, run Transact-SQL statements that are similar to the following in SQL Query Analyzer at the Publisher on the publication database:

      USE Publication Database
GO

EXEC sp_addsubscription 
    @publication = N'Publication Name', 
    @article = N'Article Name', 
    @subscriber = N'Subscriber Name', 
    @destination_db = N'Destination Database', 
    @sync_type = N'automatic', 
    @update_mode = N'read only', 
    @offloadagent = 0, 
    @dts_package_location = N'distributor'
GO

      Note Make sure that you modify the following parameters before you run the Transact-SQL statements:

      • @publication: Name of the current publication
      • @article: Name of the new article
      • @subscriber: Name of the Subscriber
      • @destination_db: Name of the destination database that contains the subscription

      Additionally, make sure that the parameters that may change the existing properties of the subscription are not modified.

    • To add subscriptions to your article in the pull subscriptions for all the existing Subscribers to your transactional publication, run Transact-SQL statements that are similar to the following in SQL Query Analyzer at the Publisher on the publication database:

      USE Publication Database
GO

EXEC sp_refreshsubscriptions 
    @publication = N'Publication Name'
GO
  5. Run the Snapshot Agent that corresponds to the current transactional publication at the distributor.
  6. Run the Distribution Agent that corresponds to each subscription that subscribes to the current transactional publication.


STATUS

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

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

REFERENCES

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

824684 Description of the standard terminology that is used to describe Microsoft software updates


Keywords: kbbug kbfix kbqfe kbsqlserv2000presp4fix kbhotfixserver KB837231



Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.


Retrieved from ‘https://www.betaarchive.com/wiki/index.php?title=Microsoft_KB_Archive/837231&oldid=203395’
the Creative Commons 3.0 ShareAlike (except the Microsoft KB Archive).
Powered by MediaWiki