Skip to content

Commit 390821d

Browse files
authored
Merge pull request #293671 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
2 parents 16554d9 + 012ef65 commit 390821d

File tree

4 files changed

+21
-1
lines changed

4 files changed

+21
-1
lines changed

articles/automation/troubleshoot/extension-based-hybrid-runbook-worker.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -397,6 +397,22 @@ The Hybrid Runbook Worker machine hasn't pinged Azure Automation for more than 3
397397

398398
Start the worker machine, and then re-register it with Azure Automation. For instructions on how to install the runbook environment and connect to Azure Automation, see [Deploy a Windows Hybrid Runbook Worker](../automation-windows-hrw-install.md).
399399

400+
401+
### Scenario: Hybrid Runbook Worker job execution on Azure Arc-enabled Windows server that uses a custom credential is unexpectedly suspended
402+
403+
#### Issue
404+
405+
Runbook jobs executed from an Azure Arc-enabled server that use a custom credential suddenly begin to go into a suspended state.
406+
407+
#### Cause
408+
409+
This is caused by a known issue where folder permissions are removed when the Azure Connected Machine agent is updated. The folder permissions on `C:\ProgramData\AzureConnectedMachineAgent\Tokens` are removed when the Azure Connected Machine agent is updated.
410+
411+
#### Resolution
412+
413+
The current resolution is to reapply the folder permissions to `C:\ProgramData\AzureConnectedMachineAgent\Tokens` when the Azure Connected Machine agent is updated. See [Permissions for Hybrid worker credentials](../extension-based-hybrid-runbook-worker-install.md#permissions-for-hybrid-worker-credentials).
414+
415+
400416
## Next steps
401417

402418
If you don't see your problem here or you can't resolve your issue, try one of the following channels for more support:

articles/container-apps/storage-mounts.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,9 @@ A container app has access to different types of storage. A single app can take
2121
| [Replica-scoped storage](#replica-scoped-storage) | Ephemeral storage for sharing files between containers in the same replica | Data is available until replica shuts down | The main app container writing log files that a sidecar container processes. |
2222
| [Azure Files](#azure-files) | Permanent storage | Data is persisted to Azure Files | Writing files to a file share to make data accessible by other systems. |
2323

24+
> [!NOTE]
25+
> Azure Container Apps does not support mounting file shares from Azure NetApp Files or Azure Blob Storage.
26+
2427
## Ephemeral storage
2528

2629
A container app can read and write temporary data to ephemeral storage. Ephemeral storage can be scoped to a container or a replica. The total amount of container-scoped and replica-scoped storage available to each replica depends on the total number of vCPUs allocated to the replica.

articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-service-capacity-limits.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ Maximum values allowed for various components of dedicated SQL pool in Azure Syn
7171
| SELECT |Columns per JOIN |1,024 columns<br/><br/>You can never have more than 1,024 columns in the JOIN. There is no guarantee that you can always have 1024. If the JOIN plan requires a temporary table with more columns than the JOIN result, the 1024 limit applies to the temporary table. |
7272
| SELECT |Bytes per GROUP BY columns. |8060<br/><br/>The columns in the GROUP BY clause can have a maximum of 8,060 bytes. |
7373
| SELECT |Bytes per ORDER BY columns |8,060 bytes<br/><br/>The columns in the ORDER BY clause can have a maximum of 8,060 bytes |
74-
| Identifiers per statement |Number of referenced identifiers |65,535<br/><br/> The number of identifiers that can be contained in a single expression of a query is limited. Exceeding this number results in SQL Server error 8632. For more information, see [Internal error: An expression services limit has been reached](https://support.microsoft.com/help/913050/error-message-when-you-run-a-query-in-sql-server-2005-internal-error-a). |
74+
| Constants and identifiers per expression |Number of constants and referenced identifiers |65,535<br/><br/> The number of constants and identifiers that can be contained in a single expression of a query is limited. Exceeding this number results in SQL Server error 8632. For more information, see [Internal error: An expression services limit has been reached](https://support.microsoft.com/help/913050/error-message-when-you-run-a-query-in-sql-server-2005-internal-error-a). |
7575
| String literals | Number of string literals in a statement | 32,500 <br/><br/>The number of string constants in a single expression of a query is limited. Exceeding this number results in SQL Server error 8632.|
7676

7777
## Metadata

articles/virtual-network/troubleshoot-vm-connectivity.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,7 @@ To resolve these problems, follow the steps in the following section.
2727
> You can use the following:
2828
> * `netstat -an` to list the ports that the VM is listening to
2929
> * Test-NetConnection module in PowerShell to display diagnostic information for a connection such as ping test and tcp test
30+
> * Ensure to utilize tcping or other TCP-based testing tools, as ICMP traffic is deprioritized by many networking devices. Using TCP tests provides more consistent and reliable results, especially in Azure environments.
3031
>
3132
## Resolution
3233

0 commit comments

Comments
 (0)