Merge pull request #8782 from MicrosoftDocs/main

Auto push to live 2025-04-23 10:02:10

Author: Deland-Han

support/azure/azure-kubernetes/extensions/troubleshoot-failed-kubernetes-deployment-offer.md

@@ -1,8 +1,8 @@
 ---
 title: Troubleshoot the failed deployment of a Kubernetes application offer
 description: Troubleshoot the failed deployment of a Kubernetes application offer that was made on the Azure Marketplace.
-ms.date: 01/24/2024
-ms.reviewer: chiragpa, atchub, v-leedennis
+ms.date: 04/22/2025
+ms.reviewer: chiragpa, atchub, v-leedennis, mnasser
 editor: v-jsitser
 ms.service: azure-kubernetes-service
 #Customer intent: As an Azure Marketplace user, I want to troubleshoot the failed deployment of a Kubernetes application after I accept an offer on the Marketplace.

support/sql/database-engine/connect/toc.yml

@@ -9,10 +9,10 @@ items:
   href: cannot-generate-sspi-context-error.md
 - name: Can't use Kerberos unconstrained delegation
   href: windows-prevents-unconstrained-delegation.md
-- name: Change NETMON parser port for SQL Server
-  href: change-netmon-parser-port-for-sql-server.md
 - name: Certificate validation failure
   href: certificate-validation-failure.md
+- name: Change NETMON parser port for SQL Server
+  href: change-netmon-parser-port-for-sql-server.md
 - name: Consistent authentication connectivity issues
   href: consistent-authentication-connectivity-issues.md
   items:

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: 03/16/2020
+ms.date: 04/23/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
@@ -37,10 +37,10 @@ DBCC execution completed. If DBCC printed error messages, contact your system ad
 
 You may have a non-distributed LSN because CDC for Oracle uses CDC for SQL stored procedures, and that, in turn, uses the replication log reader. This non-distributed LSN corresponds to the log entries to add the mirrored table in the Attunity CDC database.
 
-If you run this query, the `log_reuse_wait_desc` option returns a value of `REPLICATION`, indicating the cause. Select the `log_reuse_wait_desc` name from `sys.databases`, where the name is \<your_cdc_database\>:
+If you run this query, the `log_reuse_wait_desc` option returns a value of `REPLICATION`, indicating the cause.
 
 ```sql
-REPLICATION <your_cdc_database>
+SELECT log_reuse_wait_desc FROM sys.databases WHERE name = '<your_cdc_database>'
 ```
 
 ## Resolution
@@ -78,23 +78,23 @@ REPLICATION <your_cdc_database>
     DBCC execution completed. If DBCC printed error messages, contact your system administrator.
     ```
 
-4. To make sure that the transaction log can be reused, confirm that there is no other reuse reason indicated on the database:
+4. To make sure that the transaction log can be reused, confirm that there's no other reuse reason indicated on the database:
   
     ```sql
-    SELECT log_reuse_wait_desc, NAME FROM sys.databases WHERE NAME = 'your_cdc_database'
+    SELECT log_reuse_wait_desc, NAME FROM sys.databases WHERE NAME = '<your_cdc_database>'
     ```
 
     This returns output that resembles the following:
 
     ```output
     log_reuse_wait_desc name
-    NOTHING your_cdc_database
+    NOTHING <your_cdc_database>
     ```
 
 5. Now you should be able to truncate the Transaction log by using log backups. You should also be able to shrink the transaction log file to reduce the disk space that's consumed. For example, run the following:
 
     ```sql
-    BACKUP LOG your_cdc_database TO DISK='c:\folder\logbackup.trn'
+    BACKUP LOG <your_cdc_database> TO DISK='c:\folder\logbackup.trn'
     DBCC SHRINKFILE (yourcdcdatabase_log, 1024)
     ```
 

support/windows-server/active-directory/active-directory-domain-join-troubleshooting-guidance.md

@@ -87,45 +87,7 @@ For more information, see [Error code 0xa8b: An attempt to resolve the DNS name
 
 ### Error code 0x40
 
-The following error messages occur when you try to join the computer to the domain:
-
-> The specified network name is no longer available
-
-:::image type="content" source="media/active-directory-domain-join-troubleshooting-guidance/domain-join-error-message.png" alt-text="Screenshot of the dialog box showing the error message for error code 0x40.":::
-
-Here's an example from the *netsetup.log* file:
-
-```output
-mm/dd/yyyy hh:mm:ss:ms NetpValidateName: checking to see if '<domain_name>' is valid as type 3 name
-mm/dd/yyyy hh:mm:ss:ms NetpCheckDomainNameIsValid [ Exists ] for '<domain_name>' returned 0x0
-mm/dd/yyyy hh:mm:ss:ms NetpValidateName: name '<domain_name>' is valid for type 3
-mm/dd/yyyy hh:mm:ss:ms NetpDsGetDcName: trying to find DC in domain '<domain_name>', flags: 0x40001010
-mm/dd/yyyy hh:mm:ss:ms NetpDsGetDcName: failed to find a DC having account 'CLIENT1$': 0x525, last error is 0x0
-mm/dd/yyyy hh:mm:ss:ms NetpDsGetDcName: status of verifying DNS A record name resolution for 'DCA.<domain_name>': 0x0
-mm/dd/yyyy hh:mm:ss:ms NetpDsGetDcName: found DC '\\<dc_fqdn>' in the specified domain
-mm/dd/yyyy hh:mm:ss:ms NetpJoinDomainOnDs: NetpDsGetDcName returned: 0x0
-mm/dd/yyyy hh:mm:ss:ms NetpDisableIDNEncoding: using FQDN <domain_name> from dcinfo
-mm/dd/yyyy hh:mm:ss:ms NetpDisableIDNEncoding: DnsDisableIdnEncoding(UNTILREBOOT) on '<domain_name>' succeeded
-mm/dd/yyyy hh:mm:ss:ms NetpJoinDomainOnDs: NetpDisableIDNEncoding returned: 0x0
-mm/dd/yyyy hh:mm:ss:ms NetUseAdd to \\<dc_fqdn>\IPC$ returned 64
-mm/dd/yyyy hh:mm:ss:ms NetpJoinDomainOnDs: status of connecting to dc '\\<dc_fqdn>': 0x40
-mm/dd/yyyy hh:mm:ss:ms NetpJoinDomainOnDs: Function exits with status of: 0x40
-mm/dd/yyyy hh:mm:ss:ms NetpResetIDNEncoding: DnsDisableIdnEncoding(RESETALL) on '<domain_name>' returned 0x0
-mm/dd/yyyy hh:mm:ss:ms NetpJoinDomainOnDs: NetpResetIDNEncoding on '<domain_name>': 0x0
-mm/dd/yyyy hh:mm:ss:ms NetpDoDomainJoin: status: 0x40
-```
-
-This error is logged when the client computer lacks network connectivity on TCP port 88 between the client machine and the DC. To troubleshoot this issue, you can run the following command to test the connection:
-
-```PowerShell
-Test-NetConnection <IP_address_of_the_DC> -Port 88
-```
-
-Expected Output:
-
-:::image type="content" source="media/active-directory-domain-join-troubleshooting-guidance/test-netconnection-output-88.png" alt-text="Screenshot that shows the Test-NetConnection command for TCP port 88 output.":::
-
-The output indicates that the Kerberos Port TCP 88 is open between the client and the DC.
+For more information, see [Domain join error 0x40 "The specified network name is no longer available"](domain-join-error-0x40-the-specified-network-name-is-no-longer-available.md).
 
 ### Error code 0x54b
 
@@ -218,71 +180,11 @@ When you enter the domain name, make sure you enter the DNS Domain Name rather t
 
 ### Error code 0x3a
 
-The following error occurred when attempting to join the domain:
-
-> The specified server cannot perform the requested operation.
-
-:::image type="content" source="media/active-directory-domain-join-troubleshooting-guidance/error-0x3a-message.png" alt-text="Screenshot of the dialog box showing the error message for error code 0x3a.":::
-
-Here's an example from the *netsetup.log* file:
-
-```output
-mm/dd/yyyy hh:mm:ss:ms NetpLdapBind: ldap_bind failed on <dc_fqdn>: 81: Server Down
-mm/dd/yyyy hh:mm:ss:ms NetpJoinCreatePackagePart: status:0x3a.
-mm/dd/yyyy hh:mm:ss:ms NetpJoinDomainOnDs: Function exits with status of: 0x3a
-mm/dd/yyyy hh:mm:ss:ms NetpJoinDomainOnDs: status of disconnecting from '\\<dc_fqdn>': 0x0
-mm/dd/yyyy hh:mm:ss:ms NetpResetIDNEncoding: DnsDisableIdnEncoding(RESETALL) on '<domain_name>' returned 0x0
-mm/dd/yyyy hh:mm:ss:ms NetpJoinDomainOnDs: NetpResetIDNEncoding on '<domain_name>': 0x0
-mm/dd/yyyy hh:mm:ss:ms NetpDoDomainJoin: status: 0x3a
-```
-
-Error 0x3a is logged when the client computer lacks network connectivity on TCP port 389 between the client computer and the DC. To troubleshoot this issue, use the following command to test the connection:
-
-```PowerShell
-Test-NetConnection <IP_address_of_the_DC> -Port 389
-```
-
-Expected Output:
-
-:::image type="content" source="media/active-directory-domain-join-troubleshooting-guidance/test-netconnection-output-389.png" alt-text="Screenshot that shows the Test-NetConnection command for TCP port 389 output.":::
-
-It indicates that the LDAP Port TCP 389 is open between the client and the DC.
+For more information, see [Status code 0x3a: The specified server cannot perform the requested operation](status-code-0x3a-server-not-perform-operation.md).
 
 ### Error code 0x216d
 
-The following error occurred when attempting to join the domain:
-
-> Your computer could not be joined to the domain. You have exceeded the maximum number of computer accounts you are allowed to create in this domain. Contact your system administrator to have this limit reset or increased.
-
-:::image type="content" source="media/active-directory-domain-join-troubleshooting-guidance/error-0x216d-message.png" alt-text="Screenshot of the dialog box showing the error message for error code 0x216d.":::
-
-```output
-mm/dd/yyyy hh:mm:ss:ms NetpMapGetLdapExtendedError: Parsed [0x216d] from server extended error string: 0000216D: SvcErr: DSID-031A124C, problem 5003 (WILL_NOT_PERFORM), data 0
-mm/dd/yyyy hh:mm:ss:ms NetpModifyComputerObjectInDs: ldap_add_s failed: 0x35 0x216d
-mm/dd/yyyy hh:mm:ss:ms NetpCreateComputerObjectInDs: NetpModifyComputerObjectInDs failed: 0x216d
-mm/dd/yyyy hh:mm:ss:ms NetpProvisionComputerAccount: LDAP creation failed: 0x216d
-mm/dd/yyyy hh:mm:ss:ms NetpProvisionComputerAccount: Retrying downlevel per options
-mm/dd/yyyy hh:mm:ss:ms NetpManageMachineAccountWithSid: NetUserAdd on '<dc_fqdn>' for 'CLIENT1$' failed: 0x216d
-mm/dd/yyyy hh:mm:ss:ms NetpProvisionComputerAccount: retry status of creating account: 0x216d
-mm/dd/yyyy hh:mm:ss:ms ldap_unbind status: 0x0
-mm/dd/yyyy hh:mm:ss:ms NetpJoinCreatePackagePart: status:0x216d.
-mm/dd/yyyy hh:mm:ss:ms NetpJoinDomainOnDs: Function exits with status of: 0x216d
-mm/dd/yyyy hh:mm:ss:ms NetpJoinDomainOnDs: status of disconnecting from '\\<dc_fqdn>': 0x0
-mm/dd/yyyy hh:mm:ss:ms NetpResetIDNEncoding: DnsDisableIdnEncoding(RESETALL) on '<domain_name>' returned 0x0
-mm/dd/yyyy hh:mm:ss:ms NetpJoinDomainOnDs: NetpResetIDNEncoding on '<domain_name>': 0x0
-mm/dd/yyyy hh:mm:ss:ms NetpDoDomainJoin: status: 0x216d
-```
-
-Error 0x216d is logged in one of these conditions:
-
-- The user account trying to join the machine to the domain has exceeded the limit of 10 machines joined to the domain.
-- There is a GPO restriction to block authenticated users from joining a machine to the domain.
-
-Verify that the user account is a member of the group mentioned in the **Add Workstations to domain** policy of the **Default Domain Controller Policy** GPO or the **Winning** GPO.
-
-The GPO setting is located at **Computer Configuration** > **Policies** > **Windows Settings** > **Security Settings** > **Local Policies User Rights Assignment** > **Add workstations to domain**.
-
-To verify the default limit to the number of workstations a user can join to the domain, see [Default limit to number of workstations a user can join to the domain](default-workstation-numbers-join-domain.md).
+For more information, see [Status code 0x216d: Your computer could not be joined to the domain](status-code-0x216d-not-joined-domain.md).
 
 ### Other errors that occur when you join Windows-based computers to a domain