Microsoft KB Archive/814916: Difference between revisions
(importing KB archive) |
(No difference)
|
Latest revision as of 18:03, 18 July 2020
Article ID: 814916
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 #: 363726 (SHILOH_BUGS)
SYMPTOMS
The Merge Agent for a filtered publication can fail, and you receive the following error message:
CAUSE
In certain scenarios, SQL Server creates the temporary table name with a dash sign in the table name; however, the dash sign in the table name causes the creation of the temporary table to fail.
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 file attributes) 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 ------------------------------------------------------------------------ 08-Feb-2003 05:43 786,432 bytes Distmdl.ldf 08-Feb-2003 05:43 2,359,296 bytes Distmdl.mdf 30-Jan-2003 01:55 180 bytes Drop_repl_hotfix.sql 01-Feb-2003 00:32 2000.80.763.0 1,557,052 bytes Dtsui.dll 30-Jan-2003 05:18 746,470 bytes Instdist.sql 30-Jan-2003 01:55 1,402 bytes Inst_repl_hotfix.sql 08-Feb-2003 06:40 2000.80.765.0 90,692 bytes Msgprox.dll 08-Feb-2003 03:53 1,065,895 bytes Replmerg.sql 08-Feb-2003 06:40 2000.80.765.0 221,768 bytes Replprov.dll 08-Feb-2003 06:40 2000.80.765.0 307,784 bytes Replrec.dll 30-Jan-2003 05:18 1,084,318 bytes Replsys.sql 08-Feb-2003 06:40 2000.80.765.0 176,696 bytes Sqlmap70.dll 08-Feb-2003 06:40 2000.80.765.0 57,920 bytes Sqlrepss.dll 08-Feb-2003 06:41 2000.80.765.0 7,528,529 bytes Sqlservr.exe 08-Feb-2003 06:40 2000.80.765.0 45,644 bytes Sqlvdi.dll 08-Feb-2003 06:40 2000.80.765.0 82,492 bytes Ssnetlib.dll
Note Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.
Apply this fix to SQL CE subscribers
For SQL Server CE subscribers, you do not have to perform any additional steps if Microsoft Internet Information Services (IIS) and SQL Server are running on the same computer.
If IIS is running on a different computer, follow these steps on the computer that is running IIS to correctly apply this fix:
- Stop the IIS service.
- Rename the following DLLs to
Dllname
_old.dll:- Msgprox.dll
- Replprov.dll
- Replrec.dll
- Copy the following files that are included in the hotfix to computer that is running IIS:
- 08-Feb-2003 06:40 2000.80.765.0 90,692 bytes Msgprox.dll
- 08-Feb-2003 06:40 2000.80.765.0 221,768 bytes Replprov.dll
- 08-Feb-2003 06:40 2000.80.765.0 307,784 bytes Replrec.dll
Reregister the previous DLLs by running regsvr32 using commands that are similar to the following:
regsvr32 DriveLetter:\Program Files\Microsoft SQL Server\80\COM\Replrec.dll
- Restart the IIS service.
- Check Merge Replication Sync to make sure that no errors occurred.
Note The fix must be applied on both the publisher and the subscriber. The hotfix is also available in the security hotfix rollup that is described in the following article in the Microsoft Knowledge Base:
821277 MS03-031: Security patch for SQL Server 2000 Service Pack 3
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.
Keywords: kbbug kbfix kbqfe kbsqlserv2000presp4fix kbhotfixserver KB814916