Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: You receive a "The process could not bulk copy into table '<TableName>' " error message when you run the Distribution Agent or the Merge Agent after you run the Snapshot Agent in SQL Server 2000

FIX: You receive a "The process could not bulk copy into table '<TableName>' " error message when you run the Distribution Agent or the Merge Agent after you run the Snapshot Agent in SQL Server 2000

View products that this article applies to.

Symptoms

After you run the Snapshot Agent to perform snapshot replication, merge replication, or transactional replication, you receive the following error message when you run the Distribution Agent or the Merge Agent in Microsoft SQL Server 2000:
The process could not bulk copy into table 'TableName'
This problem occurs if the following conditions are true:
  • The table contains exactly 65,535 rows.
  • The Subscriber does not have schema information or data information.

↑ Back to the top

Resolution

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:
290211 How to obtain the latest SQL Server 2000 service pack

Hotfix information

Prerequisites

Microsoft Data Access Components (MDAC) 2.8 is required.

Restart requirement

You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File 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
   --------------------------------------------------------------
   27-Oct-2004  16:11  2000.85.1054.0     73,728  Dbnetlib.dll     
   27-Oct-2004  16:12  2000.85.1054.0     28,672  Dbnmpntw.dll     
   27-Oct-2004  16:11  2.80.1054.0       315,392  Msadce.dll       
   27-Oct-2004  16:11  2.80.1054.0       135,168  Msadco.dll       
   27-Oct-2004  16:12  2.80.1054.0        49,152  Msadcs.dll       
   27-Oct-2004  16:11  2.80.1054.0       147,456  Msadds.dll       
   27-Oct-2004  16:11  2.80.1054.0       507,904  Msado15.dll      
   27-Oct-2004  16:12  2.80.1054.0       163,840  Msadomd.dll      
   27-Oct-2004  16:12  2.80.1054.0       184,320  Msadox.dll       
   27-Oct-2004  16:11  2.80.1054.0        53,248  Msadrh15.dll     
   27-Oct-2004  16:12  2.80.1054.0       225,280  Msdaora.dll      
   27-Oct-2004  16:11  2.80.1054.0       192,512  Msdaprst.dll     
   27-Oct-2004  16:11  2.80.1054.0       147,456  Msdart.dll       
   27-Oct-2004  16:11  2.80.1054.0       303,104  Msdasql.dll      
   27-Oct-2004  16:12  2.575.1054.0      139,264  Msorcl32.dll     
   27-Oct-2004  16:11  3.525.1054.0      221,184  Odbc32.dll       
   27-Oct-2004  16:12  2000.85.1054.0     24,576  Odbcbcp.dll      
   27-Oct-2004  16:11  2.80.1054.0       442,368  Oledb32.dll      
   27-Oct-2004  16:11  2000.85.1054.0    503,808  Sqloledb.dll     
   27-Oct-2004  16:11  2000.85.1054.0    401,408  Sqlsrv32.dll     
   27-Oct-2004  01:19  2000.85.1054.0    208,896  Sqlxmlx.dll

↑ Back to the top

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 Data Access Components 2.8 Service Pack 1. This service pack is included with Microsoft SQL Server 2000 Service Pack 4.

↑ Back to the top

More information

For more information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packages
For more information about the terminology that Microsoft uses for software updates, 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

↑ Back to the top

Keywords: kbhotfixserver, kbsqlserv2000presp4fix, kbfix, kbprb, kberrmsg, kbbug, kbqfe, KB885460

↑ Back to the top

Article Info
Article ID : 885460
Revision : 5
Created on : 6/1/2006
Published on : 6/1/2006
Exists online : False
Views : 570