Microsoft KB Archive/318075

= FIX: Compressed Snapshot CAB Does Not Contain All Necessary Files =

Article ID: 318075

Article Last Modified on 10/11/2005

-

APPLIES TO


 * Microsoft SQL Server 2000 Standard Edition

-



This article was previously published under Q318075



BUG #: 356659 (Shiloh_bugs)



SYMPTOMS
A replication agent fails to apply a compressed snapshot to a subscriber.

If you open the cabinet (CAB) file that stores the compressed snapshot, note that at least one BCP file (a file with a .bcp extension) for a user table is missing from the compressed snapshot.

If the compressed snapshot was generated for a Snapshot or Transactional publication, the Distribution Agent encounters an error. If you view the Distribution Agent Error Details for the failed agent in Replication Monitor, the message in the Error message pane of the dialog box is:

The process could not bulk copy into table '&quot;dbo&quot;.&quot;t1&quot;'.

The Error details pane will contain text similar to the following:

Unable to open BCP host data-file (Source: ServerName\InstanceName (ODBC); Error number: S1000)

If the compressed snapshot was generated for a merge publication, the Merge Agent encounters the error. If you open the Error Details of the Merge Agent dialog box for the failed agent, the Error message pane of the dialog box contains this text:

The process could not deliver the snapshot to the Subscriber.

The Error details pane of the same dialog box contains text similar to:

The process could not deliver the snapshot to the Subscriber. (Source: Merge Replication Provider (Agent); Error number: -2147201001)

The process could not bulk copy into table '&quot;dbo&quot;.&quot;t1&quot;'. (Source: ServerName\InstanceName (Agent); Error number: 20037)

Unable to open BCP host data-file (Source: ServerName\InstanceName (ODBC); Error number: 0)

NOTE: The table names and server names referenced in the preceding error messages will be different in your environment.

To view the Distribution Agent Error Details or the Error Details of the Merge Agent, connect to the server where the respective Distribution Agent or Merge Agent is running. Expand Replication Monitor, expand Agents, and expand Distribution Agents or Merge Agents accordingly. You can either right-click the agent in which you are interested, and then click Error Details from the menu, or double-click the failed agent.



CAUSE
The Snapshot Agent uses parallelism to copy the data concurrently out of articles defined to a given publication. If errors occur on one of the threads that is performing a parallel bcp operation, the Snapshot Agent is not properly handling the error.



RESOLUTION
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:

 Date          Time           Version      Size             File name ---

2002-02-07    8:52:44 PM     8.00.579     283,208 bytes    Rinitcom.dll



STATUS
Microsoft has confirmed that this is a problem in Microsoft SQL Server 2000.

Keywords: kbbug kbfix kbqfe kbhotfixserver KB318075

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.