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

by

Troubleshooting Guide: Error 10770 – REMOTEDATAARCHIVE Configuration Failure in SQL Server 2025

Why This Error Happens

This error occurs when the ALTER DATABASE statement attempts to enable REMOTE_DATA_ARCHIVE without properly specifying the required SERVER option alongside either a CREDENTIAL or FEDERATED_SERVICE_ACCOUNT = ON clause. SQL Server 2025 enforces this dependency because Stretch Database and Remote Data Archive functionality rely on an authenticated link to the remote Azure endpoint, and without both a target server and a valid authentication method, the engine cannot establish or validate that connection. This is typically a syntax or script-authoring oversight rather than a system-level permissions or corruption issue.

Step-by-Step Resolution Guide

Step 1: Review the Current ALTER DATABASE Syntax

  • Open the T-SQL script or job that triggered the error in SQL Server Management Studio (SSMS) connected to your SQL Server 2025 instance.
  • Confirm whether the SERVER = '<server_name>' clause is present in the WITH options of the REMOTE_DATA_ARCHIVE statement.
  • Check if either CREDENTIAL = <credential_name> or FEDERATED_SERVICE_ACCOUNT = ON is included; missing both is the direct cause of Error 10770.

Step 2: Create or Verify the Required Database Credential

  • If using CREDENTIAL, ensure it exists by running: SELECT * FROM sys.database_credentials;
  • If it does not exist, create one with: CREATE DATABASE CREDENTIAL [RDA_Credential] WITH IDENTITY = '<identity>', SECRET = '<secret>';
  • Verify the credential maps correctly to your Azure SQL remote endpoint used for data archiving.

Step 3: Correct and Re-run the ALTER DATABASE Statement

  • Rewrite the statement to include both required elements, for example:
  • ALTER DATABASE [YourDB] SET REMOTE_DATA_ARCHIVE = ON (SERVER = 'yourserver.database.windows.net', CREDENTIAL = [RDA_Credential]);
  • Alternatively, for federated identity scenarios, use FEDERATED_SERVICE_ACCOUNT = ON instead of CREDENTIAL if your environment uses Windows Server 2025 integrated authentication with Azure AD.

Step 4: Validate Network and Firewall Configuration

  • Confirm Windows Server 2025 firewall rules allow outbound traffic on port 1433 to the Azure remote endpoint.
  • Check that the server name specified matches the fully qualified domain name (FQDN) of the remote Azure SQL Database used for archiving.

Alternative or Verification Steps

  • After re-running the corrected script, confirm success by querying sys.databases and checking the is_remote_data_archive_enabled column equals 1 for your target database.
  • If the error persists, drop and recreate the database credential using DROP DATABASE CREDENTIAL followed by CREATE DATABASE CREDENTIAL, ensuring the secret and identity values exactly match your Azure remote server’s authentication requirements.