BUG: sp_addsubscription Fails with Error 14096 When Subscribing

Last reviewed: February 9, 1998
Article ID: Q180359
The information in this article applies to:
  • Microsoft SQL Server, versions 6.5
BUG #: WINDOWS NT :17776 (6.5)

SYMPTOMS

The replication stored procedure, sp_addsubscription, can fail with the following error when creating a subscription for a valid article:

   Msg 14096, Level 16, State 1
   The path and name of the table creation script must be specified
   if the pre-creation command is DROP.

CAUSE

This problem occurs when multiple articles are created with the same name and one of the articles is manually configured incorrectly. Specifically, an article that is invalid because it is configured with a pre-creation_cmd "1" (DROP Table First), but does not include a creation script, will cause the problem. The sp_addsubscription stored procedure will fail for all articles that share the same name with the invalid article.

WORKAROUND

To avoid the problem, ensure that all articles using the pre-creation_cmd "1" (DROP Table First) include the creation script.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Keywords          : kbbug6.50 SSrvRep
Version           : WinNT:6.5
Platform          : winnt


================================================================================


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 9, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.