How to fix Error 2260 on Windows Server 2025 / Windows 11

by

Troubleshooting Guide: SQL Server Error 2260 – “There is no element named ‘%ls'”

Why This Error Happens

Error 2260 typically occurs when SQL Server attempts to resolve a named element (such as an XML schema component, Service Broker element, or extended properties reference) that does not exist in the expected collection or namespace. This is frequently caused by a corrupted or incomplete XML schema collection, a mismatched Service Broker contract/message type definition, or metadata corruption resulting from an improperly restored or upgraded database. It can also surface after an in-place upgrade to SQL Server 2025 on Windows Server 2025/Windows 11 if system catalog views reference objects that were dropped or renamed outside of a transactional context.

Step-by-Step Resolution Guide

Step 1: Identify the Specific Element and Context

  • Check the SQL Server Error Log (C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Log\ERRORLOG) for the full error text, which will include the exact element name and the object (XML schema, Service Broker, etc.) involved.
  • Run SELECT * FROM sys.messages WHERE message_id = 2260; to confirm severity and context.
  • Note whether the error occurs during a specific query, stored procedure execution, or during a database restore/upgrade process.

Step 2: Validate and Repair XML Schema Collections

  • If the error references an XML schema, run SELECT name, xml_schema_namespace(SCHEMA_NAME(schema_id), name) FROM sys.xml_schema_collections; to inspect registered collections.
  • Drop and recreate the affected schema collection using DROP XML SCHEMA COLLECTION [SchemaName]; followed by a fresh CREATE XML SCHEMA COLLECTION statement using the original, validated XSD source file.
  • Ensure the XSD source file is accessible and not corrupted; re-import from a known-good backup copy if needed.

Step 3: Check Service Broker Objects (If Applicable)

  • Run SELECT * FROM sys.service_broker_endpoints; and SELECT * FROM sys.service_contracts; to confirm all referenced message types and contracts exist.
  • Recreate any missing or orphaned MESSAGE TYPE, CONTRACT, or SERVICE definitions using the original deployment scripts.
  • Restart the SQL Server Service Broker using ALTER DATABASE [YourDB] SET ENABLE_BROKER; if it was disabled during troubleshooting.

Step 4: Run Database Consistency Checks

  • Execute DBCC CHECKDB ('YourDatabaseName') WITH NO_INFOMSGS, ALL_ERRORMSGS; to rule out underlying catalog or page-level corruption.
  • Review output for any catalog consistency errors (Msg 2501-series) that may be contributing to the missing element reference.
  • If corruption is found, restore from the most recent clean backup rather than attempting REPAIR_ALLOW_DATA_LOSS.

Step 5: Reapply Service Pack or Cumulative Update

  • Confirm your SQL Server 2025 build number via SELECT @@VERSION; and compare against the latest Cumulative Update (CU) on the Microsoft Update Catalog.
  • Reinstall or reapply the latest CU through SQL Server Installation Center, as this error is sometimes tied to a known metadata-handling bug fixed in later builds.
  • Reboot the Windows Server 2025/Windows 11 host after the update completes to ensure all SQL services fully reinitialize.

Alternative or Verification Steps

  • After applying fixes, re-run the original query or operation that triggered Error 2260 and confirm it completes without exception.
  • If the issue persists, export the database schema using SQL Server Management Studio (SSMS) → Generate Scripts, create a new empty database, and reapply the schema/data incrementally to isolate the specific corrupted element.