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

by

Troubleshooting Guide: Error 8469 – “Remote Service Has Been Altered”

Why This Error Happens

Error 8469 in SQL Server 2025 typically occurs when the Service Broker’s remote service binding references a service that has since been dropped, renamed, or modified, causing a mismatch between the cached routing information and the actual service definition. This often happens after a database restore, replication topology change, or manual alteration of Service Broker services without updating the corresponding SYS.SERVICES or SYS.ROUTES metadata. Certificate mismatches between the initiator and target databases during dialog security validation can also trigger this error.

Step-by-Step Resolution Guide

Step 1: Verify the Remote Service Binding

  • Run the following query to check the current service binding status:
SELECT * FROM sys.remote_service_bindings;
  • Confirm the service_contract_name and remote_service_name match the actual service defined in the target database.
  • Check for orphaned bindings pointing to a service that no longer exists using sys.services.

Step 2: Drop and Recreate the Remote Service Binding

  • Drop the stale binding:
DROP REMOTE SERVICE BINDING [BindingName];
  • Recreate it with the correct certificate and user mapping:
CREATE REMOTE SERVICE BINDING [BindingName]
TO SERVICE 'TargetServiceName'
WITH USER = [CertificateUser];
  • Ensure the certificate used was issued after the last service alteration; expired or outdated certs are a common cause.

Step 3: Synchronize Service Broker Routes

  • Navigate to sys.routes and validate the address and service_name columns align with the current endpoint configuration.
  • Update the route if the service name was changed:
ALTER ROUTE [RouteName]
WITH SERVICE_NAME = 'CorrectServiceName',
ADDRESS = 'TCP://ServerName:4022';
  • Restart the SQL Server Service Broker task using ALTER DATABASE [DBName] SET ENABLE_BROKER; if dialogs remain stuck.

Step 4: Validate Windows Server Firewall and Endpoint Config

  • On Windows Server 2025 / Windows 11, confirm TCP port 4022 (default Service Broker port) is open:
New-NetFirewallRule -DisplayName "SQL Broker" -Direction Inbound -Protocol TCP -LocalPort 4022 -Action Allow
  • Verify the Service Broker endpoint state is STARTED via sys.database_mirroring_endpoints or sys.service_broker_endpoints.

Alternative or Verification Steps

  • Send a test message through the dialog conversation and confirm it reaches the target service queue without generating Error 8469 in the SQL Server error log.
  • If the issue persists, drop and fully recreate the Service Broker service, contract, and queue chain from scratch on both the initiator and target databases to eliminate any residual metadata corruption.