Merge pull request #9159 from MicrosoftDocs/main

Auto push to live 2025-06-18 18:07:40

Author: Deland-Han

support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-sync-errors.md

@@ -176,6 +176,7 @@ If a file or directory fails to sync due to an error, an event is logged in the
 | 0x8007007b | -2147024773 | ERROR_INVALID_NAME | The file or directory name is invalid. | Rename the file or directory in question. See [Handling unsupported characters](?tabs=portal1%252cazure-portal#handling-unsupported-characters) for more information. |
 | 0x80070459 | -2147023783 | ERROR_NO_UNICODE_TRANSLATION | The file or directory name has unsupported surrogate pair characters. | Rename the file or directory in question. See [Handling unsupported characters](?tabs=portal1%252cazure-portal#handling-unsupported-characters) for more information. |
 | 0x80c80255 | -2134375851 | ECS_E_XSMB_REST_INCOMPATIBILITY | The file or directory name is invalid. | Rename the file or directory in question. See [Handling unsupported characters](?tabs=portal1%252cazure-portal#handling-unsupported-characters) for more information. |
+| 0x80c8026d | -2134375827 | ECS_E_SYNC_ITEM_RESTRICTED_AT_ROOT | The specified item name is restricted at the root of the sync share and thus cannot be synced.  | No action required. See [File System Compatibility](/azure/storage/file-sync/file-sync-planning#file-system-compatibility) for more information. |
 | 0x80c80018 | -2134376424 | ECS_E_SYNC_FILE_IN_USE | The file can't be synced because it's in use. The file will be synced when it's no longer in use. | No action required. Azure File Sync creates a temporary VSS snapshot once a day on the server to sync files that have open handles. |
 | 0x80c86013 | -2134351853 | ECS_E_SYNC_CLOUD_FILE_IN_USE | The cloud file can't be synced because it's in use. This error occurs when an application holds an open handle to a file in the cloud, preventing sync operations from being performed until the application releases the handle. | Check the open file handles and close them if they're no longer needed. For more information, see [List Handles](/rest/api/storageservices/list-handles) and [Force Close Handles](/rest/api/storageservices/force-close-handles). |
 | 0x80c8031d | -2134375651 | ECS_E_CONCURRENCY_CHECK_FAILED | The file has changed, but the change hasn't yet been detected by sync. Sync will recover after this change is detected. | No action required. |
@@ -213,6 +214,8 @@ If a file or directory fails to sync due to an error, an event is logged in the
 | 0x80c80201 | -2134375935 | ECS_E_SYNC_UNPROCESSABLE_ITEM_REPARSEPOINT | The sync failed due to the presence of a reparse point. | Remove the reparse point or replace it with regular file content before attempting the sync again. |
 | 0x80c80362 | -2134375582 | ECS_E_ITEM_PATH_COMPONENT_HAS_TRAILING_DOT | The item failed to sync because one of its path components has trailing dots. | Rename the item by removing any trailing dots that appear in the path. |
 | 0x80c8024e | -2134375858 | ECS_E_SYNC_ITEM_SKIP_CONSTRAINT_CONFLICT_NOT_ALLOWED | This error indicates a constraint conflict that was detected but was unable to be reported. The item will be skipped. | If the error persists, create a support request. |
+| 0x80c80208 | -2134375928 | ECS_E_SYNC_ITEM_RECONCILIATION_SKIP | A file or directory was skipped during the synchronization pass to rebuild the sync client's metadata. It will be synchronized in the next full synchronization attempt. | If the error persists for several days, create a support request. |
+
 
 ### Handling unsupported characters
 
@@ -958,6 +961,17 @@ To resolve this issue, delete and recreate the sync group by performing the foll
 
 No action is required. This error occurs because sync detected the replica has been restored to an older state. Sync will now enter a reconciliation mode, where it recreates the sync relationship by merging the contents of the Azure file share and the data on the server endpoint. When reconciliation mode is triggered, the process can be very time consuming, depending upon the namespace size. Regular synchronization doesn't happen until the reconciliation finishes, and files that are different (last modified time or size) between the Azure file share and server endpoint will result in file conflicts.
 
+<a id="-2134375775"></a>**Sync failed because the path for the server endpoint has changed**  
+
+| Error | Code |
+|-|-|
+| **HRESULT** | 0x80c802a1 |
+| **HRESULT (decimal)** | -2134375775 |
+| **Error string** | ECS_E_SYNC_ROOT_VOLUME_CHANGED |
+| **Remediation required** | No |
+
+This error occurs because the path at which the server endpoint is provisioned is currently located on a different volume than where it was originally provisioned. When this issue occurs, create a support request and we will contact you to help you resolve this issue.
+
 <a id="-2145844941"></a>**Sync failed because the HTTP request was redirected**  
 
 | Error | Code |
@@ -1195,6 +1209,20 @@ If the error persists for more than a day, create a support request.
 | **Error string** | WININET_E_INCORRECT_HANDLE_STATE |
 | **Remediation required** | No |
 
+| Error | Code |
+|-|-|
+| **HRESULT** | 0x80c87093 |
+| **HRESULT (decimal)** | -2134347629 |
+| **Error string** | ECS_E_MGMT_DATA_PLANE_INTERNAL_ERROR |
+| **Remediation required** | No |
+
+| Error | Code |
+|-|-|
+| **HRESULT** | 0x80c87005 |
+| **HRESULT (decimal)** | -2134347771 |
+| **Error string** | ECS_E_MGMT_INTERNAL_ERROR |
+| **Remediation required** | No |
+
 No action required. This error should automatically resolve. If the error persists for several days, create a support request.
 
 <a id="-2146233079"></a>**An internal error occurred.**

support/sql/database-engine/replication/sql-replication-agents-not-run.md

@@ -1,22 +1,22 @@
 ---
 title: SQL Server replication agents can't run
 description: This article provides workarounds for the problem that occurs when you configure many SQL Server replication agents to run on a server, and some replication agents can't run.
-ms.date: 03/16/2020
+ms.date: 06/18/2025
 ms.custom: sap:Replication, Change Tracking, Change Data Capture, Synapse Link
-ms.reviewer: akshaym
+ms.reviewer: akshaym, jopilov
 ---
 # Some SQL Server replication agents can't run when you configure many replication agents to run on a server
 
 This article helps you work around the problem where some replication agents can't run when you configure many SQL Server replication agents to run on a server.
 
-_Original product version:_   SQL Server 2014, SQL Server 2012  
+_Original product version:_   SQL Server  
 _Original KB number:_   949296
 
 ## Symptoms
 
 Consider the following scenario:
 
-- You configure many Microsoft SQL Server 2014 or SQL Server 2012 replication agents to run on a server. For example, you configure more than 200 replication agents to run on a server.
+- You configure many Microsoft SQL Server replication agents to run on a server. For example, you configure more than 200 replication agents to run on a server.
 
 In this scenario, some replication agents can't run. Additionally, the following error message is logged in the system log:
 
@@ -59,78 +59,6 @@ You can evaluate the publisher-subscriber pairs and see whether you can change s
 
 This behavior is by design.
 
-## How to examine the use of the desktop heap
-
-Each account that starts the SQL Server Agent service corresponds to one noninteractive desktop heap. Additionally, all replication agents that are managed by the SQL Server Agent service share the desktop heap of the account.
-
-You can use the Desktop Heap Monitor tool to examine the use of the desktop heap. Then, you can decide whether you have to increase or reduce the size of the noninteractive desktop heap. Usually, you have to increase the size.
-
-> [!IMPORTANT]
-> The Desktop Heap Monitor tool does not work in Windows Server 2008 or a later version of Windows. If you are using one of these versions of Windows, you can use LiveKD to get desktop heap values. For information about how to do this, go to the next section.
-
-To use the Desktop Heap Monitor tool to examine the use of the desktop heap, follow these steps:
-
-1. Download the Desktop Heap Monitor tool.
-2. Install the Desktop Heap Monitor tool. To do this, follow these steps:
-   1. Double-click the package to extract the files.
-   2. Click **Start**, click **Run**, type **cmd**, and then click **OK**.
-   3. At the command prompt, run the following command:
-
-      ```console
-      CD ExtractFolder\kktools\dheapmon8.1\Platform
-      ```
-
-      > [!NOTE]
-      > **ExtractFolder** is a placeholder for the folder where you extract the files. **Platform** is a placeholder for the name of the folder that corresponds to the specific platform.
-   4. Run the following command:
-
-      ```console
-      dheapinst.exe -y srv*http://msdl.microsoft.com/download/symbols
-      ```
-
-3. Load the driver. To do this, run the following command:
-
-    ```console
-    dheapmon.exe -l
-    ```
-
-4. Run the Desktop Heap Monitor tool. To do this, run the following command:
-
-   ```console
-   dheapmon.exe -s
-   ```
-
-The output resembles the following:
-
-```console
-Desktop Heap Information Monitor Tool (Version 8.1.2925.0)
-Copyright (c) Microsoft Corporation. All rights reserved.
--------------------------------------------------------------
-Session ID: 0
-Total Desktop: ( 7872 KB - 12 desktops)
-WinStation\Desktop Heap Size(KB) Used Rate(%)
--------------------------------------------------------------
-WinSta0\Default 3072 24.2
-WinSta0\Disconnect 64 4.5
-WinSta0\Winlogon 128 10.0
-Service-0x0-3e7$\Default 512 40.9
-Service-0x0-3e4$\Default 512 10.0
-Service-0x0-3e5$\Default 512 6.9
-SAWinSta\SADesktop 512 0.5
-__X78B95_89_IW\__A8D9S1_42_ID 512 0.5
-Service-0x0-1d419$\Default 512 2.4
-Service-0x0-1da0b$\Default 512 2.4
-Service-0x0-25c2e$\Default 512 13.5
-Service-0x0-2461f$\Default 512 98.6
--------------------------------------------------------------
-```
-
-In this output, the `Service-0x0-2461f$\Default` item represents the account that starts the SQL Server Agent service. All replication agents run under the security context of this account. If you run more replication agents, the use of the desktop heap will increase. If the use of the desktop heap is more than 98 percent or 99 percent, no desktop heap resources can be allocated. Therefore, you cannot start any new replication agents.
-
-In this output, the use of the desktop heap of the account is 98.6 percent. In this situation, increase the size of the noninteractive desktop heap by increasing the third value of the `SharedSection` parameter. After you increase the third value, the problem is resolved after you restart the server. Then, you can use the Desktop Heap Monitor tool to examine if the new value accommodates all the replication agents.
-
-We recommend that the desktop heap use remain between 80 percent and 90 percent. If you increase the third value of the `SharedSection` parameter, we recommend that you increase the value by 512 every time.
-
 ## Steps to use LiveKD to enumerate the desktop heap values
 
 1. Download [Debugging Tools for Windows as part of the SDK](https://developer.microsoft.com/windows/downloads/sdk-archive/).
@@ -199,7 +127,7 @@ We recommend that the desktop heap use remain between 80 percent and 90 percent.
     1. `"3e5$Service-0x0- 3e5 $\Default" -> 0x3e5 == 997`.
     2. Open **wbemtest** from the **Run** command in Windows.
     3. Connect to the `root\cimv2` namespace.
-    4. Click **Query**, and then type `select * from win32_logonsession`.
+    4. Select **Query**, and then type `select * from win32_logonsession`.
     5. Double-click the entry that contains 997.
     6. Select **UUID** in the object editor, and then click **Associators** to show the actual logon name. Refer to the following screenshot:
 
@@ -219,9 +147,9 @@ If the server is configured as a terminal server, the Win32k.sys driver allocate
 
 A terminal server and terminal services are different. You install the Terminal Server component in **Add or Remove Programs**. After you install the Terminal Server component, the server becomes a terminal server. Terminal services are a service that exists in the Services Microsoft Management Console (MMC) snap-in. If you remove the Terminal Server component from the server, client computers can still connect to the server by using RDP. Therefore, consider removing the Terminal Server component to obtain the 48 MB of buffer address space for the desktop heap.
 
-## How jobs in SQL Server 2005 affect the desktop heap
+## How jobs in SQL Server affect the desktop heap
 
-In SQL Server 2005, you may have different jobs that run under different proxy accounts. For each proxy account, the noninteractive desktop heap for that proxy account will be allocated. For example, the third value of the
+In SQL Server, you may have different jobs that run under different proxy accounts. For each proxy account, the noninteractive desktop heap for that proxy account will be allocated. For example, the third value of the
  SharedSection parameter is 512. If you use a proxy account to start a job, the 512-KB desktop heap will be allocated, even if the job itself uses only 10 KB of the desktop heap.
 
 > [!NOTE]
@@ -231,4 +159,4 @@ This may result in many desktops when the SQL Server Agent service is started. T
 
 ## References
 
-For more information about the values of the `SharedSection` parameter, see [User32.dll or Kernel32.dll fails to initialize](https://support.microsoft.com/help/184802).
+For more information about the values of the `SharedSection` parameter, see [User32.dll or Kernel32.dll fails to initialize](/previous-versions/troubleshoot/windows/win32/user-32-kernel-32-not-initialize).

support/sql/database-engine/replication/sql-transaction-log-grows.md

@@ -1,7 +1,7 @@
 ---
 title: SQL Transaction log grows continuously
 description: This article helps you resolve the problem where you notice continuous transaction log growth for a CDC enabled database.
-ms.date: 04/23/2025
+ms.date: 06/18/2025
 ms.custom: sap:Replication, Change Tracking, Change Data Capture, Synapse Link
 ---
 # SQL Transaction log grows when you use Change Data Capture for Oracle by Attunity
@@ -15,7 +15,8 @@ _Original KB number:_   2871474
 
 Consider the following scenario:
 
-- You use Microsoft SQL Server 2017 on Windows, SQL Server 2016, 2014, or 2012 Change Data Capture for Oracle by Attunity.
+- You use SQL Server 2017, SQL Server 2016, SQL Server 2014, or SQL Server 2012 on Windows.
+- You use Change Data Capture for Oracle by Attunity.
 - You create a CDC instance to capture changes from Oracle database tables.
 - The change capture values are stored in SQL Server change capture databases.
 - The transaction log on the SQL Server database grows, and transactions aren't marked for truncation as data changes are captured.
@@ -103,6 +104,6 @@ For more information, see [Manage the size of the transaction log file](/previou
 ## More information
 
 For more information, see
-[Troubleshoot CDC instance errors in Microsoft change data capture for Oracle by Attunity](https://social.technet.microsoft.com/wiki/contents/articles/7642.troubleshoot-cdc-instance-errors-in-microsoft-change-data-capture-for-oracle-by-attunity.aspx).
+[Troubleshoot CDC instance errors in Microsoft change data capture for Oracle by Attunity](/archive/technet-wiki/7642.troubleshoot-cdc-instance-errors-in-microsoft-change-data-capture-for-oracle-by-attunity).
 
 The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

support/sql/database-engine/security/use-pfx-formatted-certificates.md

@@ -1,15 +1,15 @@
 ---
 title: Use PFX-formatted certificates
 description: This article describes the Microsoft PVKConverter for SQL Server tool. This tool supports the conversion of a certificate that uses the PFX format into PVK/DER format.
-ms.date: 09/25/2020
+ms.date: 06/18/2025
 ms.custom: sap:Security, Encryption, Auditing, Authorization
-ms.reviewer: vencher
+ms.reviewer: vencher, jopilov
 ---
 # Use PFX-formatted certificates in SQL Server
 
-This article introduces the Microsoft PVKConverter for SQL Server tool. This tool supports the conversion of a certificate that uses the PFX format into PVK/DER format.
+This article introduces the Microsoft PVKConverter for SQL Server tool. This tool supports the conversion of a certificate that uses the PFX format into PVK/DER format. In SQL Server 2022 (16.x) or later versions, certificates with private keys can be backed up or restored directly to and from files or binary blobs using the public key pairs (PKCS) #12 or personal information exchange (PFX) format. For more information, see [CREATE CERTIFICATE (Transact-SQL)](/sql/t-sql/statements/create-certificate-transact-sql).
 
-_Original product version:_   SQL Server 2014, SQL Server 2012, SQL Server 2008, SQL Server 2005  
+_Original product version:_   SQL Server  
 _Original KB number:_   2914662
 
 ## Summary
@@ -34,10 +34,10 @@ To use certificates that are in the PFX format in Microsoft SQL Server, use Micr
     > [!NOTE]
     > The number of PVK/DER files that are generated depends on the number of public/private key pairs that are contained in the PFX file. One PVK/DER file pair is generated for each public/private key pair.
 
-3. Use SQL Query Analyzer to run the following Transact-SQL script:
+3. Run the following Transact-SQL script:
 
     ```sql
-    CREATE CERTIFICATE >Certificate name>
+    CREATE CERTIFICATE <Certificate name>
      FROM FILE = '<PVK/DER format file>.cer'
      WITH PRIVATE KEY (FILE = '<PVK/DER format file>.pvk',
      DECRYPTION BY PASSWORD = '<Encryption password>');
@@ -58,36 +58,3 @@ Windows Certificate Manager supports the export to PFX format only of existing c
 - For Microsoft SQL Server 2014 Service Pack 1, see [3082513 FIX: TDE certificate creation fails in SQL Server 2014 SP1 if the serial number is greater than 16 bytes](https://support.microsoft.com/help/3082513).
 
 - For other versions of SQL Server, see [Not able to use PFX format certificate in SQL Server?](https://techcommunity.microsoft.com/t5/sql-server-support/not-able-to-use-pfx-format-certificate-in-sql-server/ba-p/318593).
-
-## Applies to
-
-- SQL Server 2014 Developer
-- SQL Server 2014 Developer
-- SQL Server 2014 Enterprise
-- SQL Server 2014 Enterprise
-- SQL Server 2014 Web
-- SQL Server 2014 Web
-- SQL Server 2014 Standard
-- SQL Server 2014 Standard
-- SQL Server 2014 Express
-- SQL Server 2014 Express
-- SQL Server 2012 Developer
-- SQL Server 2012 Enterprise
-- SQL Server 2012 Web
-- SQL Server 2012 Standard
-- SQL Server 2012 Express
-- SQL Server 2008 R2 Datacenter
-- SQL Server 2008 R2 Developer
-- SQL Server 2008 R2 Enterprise
-- SQL Server 2008 R2 Web
-- SQL Server 2008 R2 Standard
-- SQL Server 2008 R2 Express
-- SQL Server 2008 Developer
-- SQL Server 2008 Enterprise
-- SQL Server 2008 Workgroup
-- SQL Server 2008 Web
-- SQL Server 2008 Express
-- Microsoft SQL Server 2005 Enterprise Edition
-- Microsoft SQL Server 2005 Workgroup Edition
-- Microsoft SQL Server 2005 Standard Edition
-- Microsoft SQL Server 2005 Express Edition