| title | MSSQL_ENG014005 | Microsoft Docs | |
|---|---|---|
| ms.custom | ||
| ms.date | 03/04/2017 | |
| ms.prod | sql | |
| ms.prod_service | database-engine | |
| ms.reviewer | ||
| ms.technology | replication | |
| ms.topic | conceptual | |
| helpviewer_keywords |
|
|
| ms.assetid | f168f0d6-cb11-45d4-9781-c374d7f388ee | |
| author | MashaMSFT | |
| ms.author | mathoma | |
| monikerRange | =azuresqldb-mi-current||>=sql-server-2016||=sqlallproducts-allversions |
[!INCLUDEappliesto-ss-asdbmi-xxxx-xxx-md]
| Product Name | SQL Server |
| Event ID | 14005 |
| Event Source | MSSQLSERVER |
| Component | [!INCLUDEssDEnoversion] |
| Symbolic Name | |
| Message Text | Could not drop publication. A subscription exists to it. |
You have tried to drop a publication which has one or more associated subscriptions. A publication can only be dropped if there are no associated subscriptions.
Drop the subscriptions before dropping the publication. If you use [!INCLUDEssManStudioFull] to drop the publication, it will give you the option to automatically drop all associated subscriptions before dropping the publication. If you use stored procedures, you must explicitly drop the subscriptions first. For more information, see Delete a Push Subscription and Delete a Pull Subscription.
If no subscriptions appear to exist for the publication or if you see this error when you create a publication, you might have a previous subscription that was not completely cleaned up when it was removed. Execute sp_removedbreplication (Transact-SQL) on the database to remove all objects and settings related to replication.