The Snapshot Agent corresponding to the publication ‘%s’ could not be dropped.

Details
Product: SQL Server
Event ID: 20010
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: The Snapshot Agent corresponding to the publication ‘%s’ could not be dropped.
   
Explanation
This error occurs when dropping a merge replication publication. sp_dropmergepublication cannot drop the Snapshot Agent for the specified publication. The specified publication name may not exist in the publishing database. Perhaps a prior attempt to remove replication from the database did not completely remove all remnants of merge replication.
   
User Action
If other errors occur at the same time as this error, troubleshoot them first.

Run SQL Profiler against the relevant SQL Server instance to capture “Errors and Warnings” events. Sometimes this will capture errors that are otherwise not seen.

You may need to manually remove the replication. For more information about how to manually remove replication, see Microsoft Knowledge Base article 324401.

Related:

FOR XML EXPLICIT stack overflow occurred. Circular parent tag relationships are not allowed.

Details
Product: SQL Server
Event ID: 6805
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: FOR XML EXPLICIT stack overflow occurred. Circular parent tag relationships are not allowed.
   
Explanation
The XML is not well-formed because the element tag nesting level has exceeded the number of columns in the table, one or more tags is self-referencing, or both. For more information about FOR XML EXPLICIT, see “Using EXPLICIT Mode” in Books Online.
   
User Action
When you specify EXPLICIT mode, you must assume the responsibility for ensuring that the generated XML is well-formed and valid (in case of an XML-DATA schema). Do not include self-referencing element tags in the hierarchy.

Related:

XML document could not be created because server memory is low. Use sp_xml_removedocument to release XML documents.

Details
Product: SQL Server
Event ID: 6624
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: XML document could not be created because server memory is low. Use sp_xml_removedocument to release XML documents.
   
Explanation
When you execute sp_xml_preparedocument, a parsed XML document is stored in the internal cache of SQL Server 2000. The MSXML parser uses up to one-eighth the total memory available for SQL Server. There is not enough memory in the portion of cache allocated to MSXML to open the document specified in the sp_xml_preparedocument statement. This may be because the specified document is very large or because documents already in that memory space do not leave enough space for the new document.

For more information about parsing XML documents, see “sp_xml_preparedocument” and “sp_xml_removedocument” in Books Online.

   
User Action
Execute sp_xml_removedocument to remove documents from memory. Verify that your code always calls sp_xml_removedocument when you have finished processing a document. Your code should account for the possibility that a connection or transaction is interrupted between the sp_xml_preparedocument and the sp_xml_removedocument calls. To accomplish this, you may need to store open document handles in a table where you can reference them if a batch is interrupted.

Related:

XML error: %.*ls

Details
Product: SQL Server
Event ID: 6600
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: XML error: %.*ls
   
Explanation
This message passes through XML errors generated outside of SQL Server. The text after “XML error:” will vary. The cause will depend on the exact XML error passed through.
   
User Action
Research the text that occurs after “XML error:” and take the actions appropriate to that text.

Attempt to load the problematic XML document using an XML editor to see if there are more details about what failed in the XML parsing.

Related:

User does not have permission to use the KILL statement.

Details
Product: SQL Server
Event ID: 6102
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: User does not have permission to use the KILL statement.
   
Explanation
KILL permissions default to the members of the sysadmin and processadmin fixed database roles, and are not transferable.
   
User Action
Log in as a member of the sysadmin or processadmin fixed database roles. Then reissue the KILL statement.

Related:

You do not have permission to run the RECONFIGURE statement.

Details
Product: SQL Server
Event ID: 5812
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: You do not have permission to run the RECONFIGURE statement.
   
Explanation
RECONFIGURE permissions default to members of the sysadmin and serveradmin fixed server roles, and are not transferable.
   
User Action
Log in as a member of the sysadmin or serveradmin fixed server roles and re-execute the RECONFIGURE command.

Related:

You do not have permission to run DISK statements.

Details
Product: SQL Server
Event ID: 5116
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: You do not have permission to run DISK statements.
   
Explanation
DISK INIT can only be executed by a member of the sysadmin or diskadmin fixed server roles.

NOTE: DISK INIT has limited support in SQL Server 2000. For more information, see “Level 3: Updating to Improve Earlier Functionality” in Books Online.

   
User Action
Log in as a member of the sysadmin or diskadmin fixed server role to execute DISK INIT.

Because DISK INIT is included only for backwards compatibility, it is recommended that you replace DISK INIT with CREATE DATABASE syntax.

Related:

Warning: Changing default collation for database ‘%.*ls’, which is used in replication. It is recommend that all replication database have the same default collation.

Details
Product: SQL Server
Event ID: 5076
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: Warning: Changing default collation for database ‘%.*ls’, which is used in replication. It is recommend that all replication database have the same default collation.
   
Explanation
You have issued the ALTER DATABASE statement with the COLLATE clause to change the default collation on an existing database. The database is configured as a Publisher (sp_replicationdboption was used to set the “merge publish” and/or “publish” option to true), or the database is configured as a distribution database.

Microsoft recommends that all databases in a replication topology have the same collation to avoid potential case sensitivity, sorting, and translation issues.

The following is not a comprehensive list of all potential problems; it is a subset of the high-level types of issues you might encounter:

  • For example, consider the scenario where the publishing database has a case-sensitive collation, but the subscriber has a case-insensitive collation. On the publisher you have a row with the primary key equal to “Test” and a row with the primary key equal to “TEST”. But if you try to replicate that data to a case-insensitive Subscriber, replication will fail with a duplicate key error. The same scenario could occur with a difference in accent sensitivity, kanatype sensitivity, or width sensitivity.
  • Even with the same case-sensitivity and with all unicode data types, you could have different results on servers with different collations. For example, an application that returns the top 10 rows could return completely different data sets on a dictionary order collation compared with a binary order collation. Result set differences could also occur if the difference is between a sort order with uppercase preference and one without uppercase preference.

For more information about collations, see “SQL Server Collation Fundamentals” and “Copying Data Between Different Collations” in Books Online and Microsoft Knowledge Base article 325335.

   
User Action
It is recommended that you use the same collation for all databases in your replication topology. If you must have different default collations for databases within the same replication toplogy, thoroughly test your specific replication scenario with realistic data, and adjust your configuration to account for any anomalies that could occur.

Related:

Could not drop publication. A subscription exists to it.

Details
Product: SQL Server
Event ID: 14005
Source: MSSQLServer
Version: 10.0
Component: SQL Server Database Engine
Message: Could not drop publication. A subscription exists to it.
   
Explanation

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.

   
User Action

Drop the subscriptions before dropping the publication. If you use SQL Server Management Studio 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 How to: Delete a Push Subscription (Replication Transact-SQL Programming) and How to: Delete a Pull Subscription (Replication Transact-SQL Programming).

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.

   
   
Version: 9.0
Component: SQL Server Database Engine
Message: Could not drop publication. A subscription exists to it.
   
Explanation

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.

   
User Action

Drop the subscriptions before dropping the publication. If you use SQL Server Management Studio 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 How to: Delete a Push Subscription (Replication Transact-SQL Programming) and How to: Delete a Pull Subscription (Replication Transact-SQL Programming).

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.

   
   
Version: 8.0
Component: SQL Engine
Message: Could not drop publication. A subscription exists to it.
   
Explanation
You have tried to drop a publication that has one or more associated subscriptions. A publication can only be dropped if there are no associated subscriptions.
   
User Action
Drop the subscriptions before dropping the publication. If you use SQL Enterprise Manager to drop the publication, it will give you the option to automatically drop all associated subscriptions before dropping the publication.

If no subscriptions appear to exist for the publication or if you see this error when you create a publication, you may have a previous subscription that was not completely cleaned up after it was removed. The exact steps to remove the leftover replication will depend on your situation. For more details on removing replication manually, see the Microsoft Knowledge Base article, 324401.

Related:

Extending database by %.2f MB on disk ‘%.*ls’.

Details
Product: SQL Server
Event ID: 5005
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: Extending database by %.2f MB on disk ‘%.*ls’.
   
Explanation
You have added a file to an existing database. The size of the newly added file is indicated in the message.
   
User Action
No user action is required.

Related: