Skip to content

Commit bd72ace

Browse files
authored
Merge pull request #266782 from WilliamDAssafMSFT/20240215-broken-links
20240220 add known issue
2 parents dd063a5 + 2694a15 commit bd72ace

File tree

1 file changed

+77
-67
lines changed

1 file changed

+77
-67
lines changed

articles/synapse-analytics/known-issues.md

Lines changed: 77 additions & 67 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@ titleSuffix: Azure Synapse Analytics
44
description: Learn about the currently known issues with Azure Synapse Analytics and their possible workarounds or resolutions.
55
author: charithdilshan
66
ms.author: ccaldera
7-
ms.reviewer: wiassaf
8-
ms.date: 02/05/2024
7+
ms.reviewer: wiassaf, joanpo
8+
ms.date: 02/20/2024
99
ms.service: synapse-analytics
1010
ms.subservice: overview
1111
ms.topic: conceptual
@@ -20,85 +20,29 @@ To learn more about Azure Synapse Analytics, see the [Azure Synapse Analytics Ov
2020
## Active known issues
2121

2222
|Azure Synapse Component|Status|Issue|
23-
|---------|---------|---------|
23+
|:---------|:---------|:---------|
24+
|Azure Synapse dedicated SQL pool|[Query failure when ingesting a parquet file into a table with AUTO_CREATE_TABLE='ON'](#query-failure-when-ingesting-a-parquet-file-into-a-table-with-auto_create_tableon)|Has Workaround|
25+
|Azure Synapse dedicated SQL pool|[Queries failing with Data Exfiltration Error](#queries-failing-with-data-exfiltration-error)|Has Workaround|
26+
|Azure Synapse dedicated SQL pool|[UPDATE STATISTICS statement fails with error: "The provided statistics stream is corrupt."](#update-statistics-failure)|Has Workaround|
2427
|Azure Synapse serverless SQL pool|[Query failures from serverless SQL pool to Azure Cosmos DB analytical store](#query-failures-from-serverless-sql-pool-to-azure-cosmos-db-analytical-store)|Has Workaround|
2528
|Azure Synapse serverless SQL pool|[Azure Cosmos DB analytical store view propagates wrong attributes in the column](#azure-cosmos-db-analytical-store-view-propagates-wrong-attributes-in-the-column)|Has Workaround|
2629
|Azure Synapse serverless SQL pool|[Query failures in serverless SQL pools](#query-failures-in-serverless-sql-pools)|Has Workaround|
27-
|Azure Synapse dedicated SQL pool|[Queries failing with Data Exfiltration Error](#queries-failing-with-data-exfiltration-error)|Has Workaround|
28-
|Azure Synapse dedicated SQL pool|[UPDATE STATISTICS statement fails with error: "The provided statistics stream is corrupt."](#update-statistics-failure)|Has Workaround|
2930
|Azure Synapse Workspace|[Blob storage linked service with User Assigned Managed Identity (UAMI) is not getting listed](#blob-storage-linked-service-with-user-assigned-managed-identity-uami-is-not-getting-listed)|Has Workaround|
3031
|Azure Synapse Workspace|[Failed to delete Synapse workspace & Unable to delete virtual network](#failed-to-delete-synapse-workspace--unable-to-delete-virtual-network)|Has Workaround|
3132
|Azure Synapse Workspace|[REST API PUT operations or ARM/Bicep templates to update network settings fail](#rest-api-put-operations-or-armbicep-templates-to-update-network-settings-fail)|Has Workaround|
3233
|Azure Synapse Workspace|[Known issue incorporating square brackets [] in the value of Tags](#known-issue-incorporating-square-brackets--in-the-value-of-tags)|Has Workaround|
3334
|Azure Synapse Workspace|[Deployment Failures in Synapse Workspace using Synapse-workspace-deployment v1.8.0 in GitHub actions with ARM templates](#deployment-failures-in-synapse-workspace-using-synapse-workspace-deployment-v180-in-github-actions-with-arm-templates)|Has Workaround|
3435

35-
## Azure Synapse Analytics serverless SQL pool active known issues summary
36-
37-
### Query failures from serverless SQL pool to Azure Cosmos DB analytical store
38-
39-
Queries from a serverless SQL pool to Azure Cosmos DB analytical store might fail with one of the following error messages:
40-
41-
- `Resolving CosmosDB path has failed with error 'This request is not authorized to perform this operation'`
42-
- `Resolving CosmosDB path has failed with error 'Key not found'`
43-
44-
The following conditions must be true to confirm this issue:
45-
46-
1) The connection to Azure Cosmos DB analytical store uses a private endpoint.
47-
2) Retrying the query succeeds.
48-
49-
**Workaround**: The engineering team is aware of this behavior and following actions can be taken as quick mitigation:
50-
51-
1) Retry the failed query. It will automatically refresh the expired token.
52-
2) Disable the private endpoint. Before applying this change, confirm with your security team that it meets your company security policies.
53-
54-
### Azure Cosmos DB analytical store view propagates wrong attributes in the column
55-
56-
While using views in Azure Synapse serverless pool over Cosmos DB analytical store, if there is a change on files in the Cosmos DB analytical store, the change does not get propagated correctly to the SELECT statements, the customer is using on the view. As a result, the attributes get incorrectly mapped to a different column in the results.
5736

58-
**Workaround**: The engineering team is aware of this behavior and following actions can be taken as quick mitigation:
59-
60-
1) Recreate the view by renaming the columns.
61-
2) Avoid using views if possible.
62-
63-
### Alter database-scoped credential fails if credential has been used
64-
65-
Sometimes you might not be able to execute the `ALTER DATABASE SCOPED CREDENTIAL` query. The root cause of this issue is the credential was cached after its first use making it inaccessible for alteration. The error returned in such case is following:
66-
67-
- "Failed to modify the identity field of the credential '{credential_name}' because the credential is used by an active database file.".
68-
69-
**Workaround**: The engineering team is currently aware of this behavior and is working on a fix. As a workaround you can DROP and CREATE the credentials, which would also mean recreating external tables using the credentials. Alternatively, you can engage Microsoft Support Team for assistance.
70-
71-
### Query failures in serverless SQL pools
72-
73-
Token expiration can lead to errors during their query execution, despite having the necessary permissions for the user over the storage. These error messages can also occur due to common user errors, such as when role-based access control (RBAC) roles are not assigned to the storage account.
74-
75-
Example error messages:
76-
77-
- WaitIOCompletion call failed. HRESULT = 0x80070005'. File/External table name: {path}
78-
79-
- Unable to resolve path '%' Error number 13807, Level 16, State 1, Message "Content of directory on path '%' cannot be listed.
80-
81-
- Error 16561: "External table '<table_name>' is not accessible because content of directory cannot be listed."
82-
83-
- Error number 13822: File {path} cannot be opened because it does not exist or it is used by another process.
84-
85-
- Error number 16536: Cannot bulk load because the file "%ls" could not be opened.
86-
87-
**Workaround**:
88-
89-
The resolution is different depending on the authentication, [Microsoft Entra (formerly Azure Active Directory)](security/synapse-workspace-access-control-overview.md) or [managed service identity (MSI)](synapse-service-identity.md):
90-
91-
For Microsoft Entra token expiration:
92-
93-
- For long-running queries, switch to service principal, managed identity, or shared access signature (SAS) instead of using a user identity. For more information, see [Control storage account access for serverless SQL pool in Azure Synapse Analytics](sql/develop-storage-files-storage-access-control.md?tabs=service-principal#supported-storage-authorization-types).
37+
## Azure Synapse Analytics dedicated SQL pool active known issues summary
9438

95-
- Restart client (SSMS/ADS) to acquire a new token to establish the connection.
39+
### Query failure when ingesting a parquet file into a table with AUTO_CREATE_TABLE='ON'
9640

97-
For MSI token expiration:
41+
Customers who try to ingest a parquet file into a hash distributed table with `AUTO_CREATE_TABLE='ON'` may receive the following error:
9842

99-
- Deactivate then activate the pool in order to clear the token cache. Engage Microsoft Support Team for assistance.
43+
`COPY statement using Parquet and auto create table enabled currently cannot load into hash-distributed tables`
10044

101-
## Azure Synapse Analytics dedicated SQL pool active known issues summary
45+
[Ingestion into an auto-created hash-distributed table using AUTO_CREATE_TABLE is unsupported](/sql/t-sql/statements/copy-into-transact-sql?view=azure-sqldw-latest&preserve-view=true#auto_create_table---on--off-). Customers that have previously loaded using this unsupported scenario should CTAS their data into a new table and use it in place of the old table.
10246

10347
### Queries failing with Data Exfiltration Error
10448

@@ -165,6 +109,72 @@ The error message displayed is "Action failed - Error: Orchestrate failed - Synt
165109

166110
After applying either of these workarounds and successfully deploying, manually update the necessary configurations within the workspace to ensure everything is set up correctly. This might involve editing configuration files, adjusting settings, or performing other tasks relevant to the specific environment or application being deployed.
167111

112+
## Azure Synapse Analytics serverless SQL pool active known issues summary
113+
114+
### Query failures from serverless SQL pool to Azure Cosmos DB analytical store
115+
116+
Queries from a serverless SQL pool to Azure Cosmos DB analytical store might fail with one of the following error messages:
117+
118+
- `Resolving CosmosDB path has failed with error 'This request is not authorized to perform this operation'`
119+
- `Resolving CosmosDB path has failed with error 'Key not found'`
120+
121+
The following conditions must be true to confirm this issue:
122+
123+
1) The connection to Azure Cosmos DB analytical store uses a private endpoint.
124+
2) Retrying the query succeeds.
125+
126+
**Workaround**: The engineering team is aware of this behavior and following actions can be taken as quick mitigation:
127+
128+
1) Retry the failed query. It will automatically refresh the expired token.
129+
2) Disable the private endpoint. Before applying this change, confirm with your security team that it meets your company security policies.
130+
131+
### Azure Cosmos DB analytical store view propagates wrong attributes in the column
132+
133+
While using views in Azure Synapse serverless pool over Cosmos DB analytical store, if there is a change on files in the Cosmos DB analytical store, the change does not get propagated correctly to the SELECT statements, the customer is using on the view. As a result, the attributes get incorrectly mapped to a different column in the results.
134+
135+
**Workaround**: The engineering team is aware of this behavior and following actions can be taken as quick mitigation:
136+
137+
1) Recreate the view by renaming the columns.
138+
2) Avoid using views if possible.
139+
140+
### Alter database-scoped credential fails if credential has been used
141+
142+
Sometimes you might not be able to execute the `ALTER DATABASE SCOPED CREDENTIAL` query. The root cause of this issue is the credential was cached after its first use making it inaccessible for alteration. The error returned in such case is following:
143+
144+
- "Failed to modify the identity field of the credential '{credential_name}' because the credential is used by an active database file.".
145+
146+
**Workaround**: The engineering team is currently aware of this behavior and is working on a fix. As a workaround you can DROP and CREATE the credentials, which would also mean recreating external tables using the credentials. Alternatively, you can engage Microsoft Support Team for assistance.
147+
148+
### Query failures in serverless SQL pools
149+
150+
Token expiration can lead to errors during their query execution, despite having the necessary permissions for the user over the storage. These error messages can also occur due to common user errors, such as when role-based access control (RBAC) roles are not assigned to the storage account.
151+
152+
Example error messages:
153+
154+
- WaitIOCompletion call failed. HRESULT = 0x80070005'. File/External table name: {path}
155+
156+
- Unable to resolve path '%' Error number 13807, Level 16, State 1, Message "Content of directory on path '%' cannot be listed.
157+
158+
- Error 16561: "External table '<table_name>' is not accessible because content of directory cannot be listed."
159+
160+
- Error number 13822: File {path} cannot be opened because it does not exist or it is used by another process.
161+
162+
- Error number 16536: Cannot bulk load because the file "%ls" could not be opened.
163+
164+
**Workaround**:
165+
166+
The resolution is different depending on the authentication, [Microsoft Entra (formerly Azure Active Directory)](security/synapse-workspace-access-control-overview.md) or [managed service identity (MSI)](synapse-service-identity.md):
167+
168+
For Microsoft Entra token expiration:
169+
170+
- For long-running queries, switch to service principal, managed identity, or shared access signature (SAS) instead of using a user identity. For more information, see [Control storage account access for serverless SQL pool in Azure Synapse Analytics](sql/develop-storage-files-storage-access-control.md?tabs=service-principal#supported-storage-authorization-types).
171+
172+
- Restart client (SSMS/ADS) to acquire a new token to establish the connection.
173+
174+
For MSI token expiration:
175+
176+
- Deactivate then activate the pool in order to clear the token cache. Engage Microsoft Support Team for assistance.
177+
168178
## Recently closed known issues
169179

170180
|Synapse Component|Issue|Status|Date Resolved|

0 commit comments

Comments
 (0)