Skip to content

Commit ef40bbf

Browse files
SyntaxC4SyntaxC4
authored
Merge pull request #115280 from MicrosoftDocs/release-build-stream-analytics
Release build stream analytics to master
2 parents dfd08dc + 0180ccd commit ef40bbf

16 files changed

+534
-9
lines changed

‎articles/stream-analytics/TOC.yml

Lines changed: 28 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -58,6 +58,7 @@
5858
items:
5959
- name: Outputs overview
6060
href: stream-analytics-define-outputs.md
61+
displayName: adls, sql, blob, event hubs, power bi, table, service bus, cosmos, functions
6162
- name: Output to Cosmos DB
6263
href: stream-analytics-documentdb-output.md
6364
- name: Output to Azure SQL DB
@@ -127,14 +128,22 @@
127128
href: copy-job.md
128129
- name: Pair jobs for reliability
129130
href: stream-analytics-job-reliability.md
130-
- name: Authenticate with managed identity - ADLS Gen 1 output
131-
href: stream-analytics-managed-identities-adls.md
132131
- name: Use SQL reference data
133132
href: sql-reference-data.md
134-
- name: Authenticate with managed identity - Blob output
135-
href: blob-output-managed-identity.md
136-
- name: Authenticate with managed identity - Power BI
137-
href: powerbi-output-managed-identity.md
133+
- name: Authenticate with managed identity
134+
items:
135+
- name: ADLS Gen 1
136+
href: stream-analytics-managed-identities-adls.md
137+
displayName: managed identity, identities, authenticate
138+
- name: Blob storage
139+
href: blob-output-managed-identity.md
140+
displayName: managed identity, identities, authenticate
141+
- name: Power BI
142+
href: powerbi-output-managed-identity.md
143+
displayName: managed identity, identities, authenticate
144+
- name: Azure SQL DB
145+
href: sql-database-output-managed-identity.md
146+
displayName: managed identity, identities, authenticate
138147
- name: Encrypt your data
139148
href: data-protection.md
140149
- name: Build solutions
@@ -226,7 +235,19 @@
226235
href: stream-analytics-job-diagnostic-logs.md
227236
- name: Data errors
228237
href: data-errors.md
229-
- name: Integrate with machine learning
238+
- name: Error codes
239+
items:
240+
- name: Configuration errors
241+
href: configuration-error-codes.md
242+
- name: Data errors
243+
href: data-error-codes.md
244+
- name: External availability errors
245+
href: external-availability-error-codes.md
246+
- name: External errors
247+
href: external-error-codes.md
248+
- name: Internal errors
249+
href: internal-error-codes.md
250+
- name: Integrate with machine learnings
230251
items:
231252
- name: Sentiment analysis with ML models
232253
href: stream-analytics-machine-learning-integration-tutorial.md

‎articles/stream-analytics/configuration-error-codes.md

Lines changed: 112 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,112 @@
1+
---
2+
title: Configuration error codes - Azure Stream Analytics
3+
description: Troubleshoot Azure Stream Analytics issues with configuration error codes.
4+
ms.author: mamccrea
5+
author: mamccrea
6+
ms.topic: conceptual
7+
ms.date: 05/07/2020
8+
ms.service: stream-analytics
9+
---
10+
11+
# Azure Stream Analytics configuration error codes
12+
13+
You can use activity logs and resource logs to help debug unexpected behaviors from your Azure Stream Analytics job. This article lists the description for every configuration error code. Configuration errors are related to your job configuration, or input and output configurations.
14+
15+
## KafkaInvalidPermission
16+
17+
* **Cause**: The Stream Analytics job doesn't have the proper permission to perform certain actions.
18+
19+
## KafkaInvalidConfiguration
20+
21+
* **Cause**: Certain configurations on the Kafka adapter are invalid.
22+
23+
## KafkaInvalidTimestampType
24+
25+
* **Cause**: The timestamp type used by Kafka is invalid.
26+
27+
## EventHubUnauthorizedAccess
28+
29+
* **Cause**: Event Hub threw an *Unauthorized Access* error.
30+
31+
## EventHubReceiverEpochConflict
32+
33+
* **Cause**: There is more than one Event Hub receiver with different epoch values.
34+
* **Recommendation**: Ensure *Service Bus Explorer* or an *EventProcessorHost* application is not connected while your Stream Analytics job is running.
35+
36+
## EventHubReceiverQuotaExceeded
37+
38+
* **Cause**: Stream Analytics can't connect to a partition because the maximum number of allowed receivers per partition in a consumer group has been reached.
39+
* **Recommendation**: Ensure that other Stream Analytics jobs or Service Bus Explorer are not using the same consumer group.
40+
41+
## EventHubOutputThrottled
42+
43+
* **Cause**: An error occurred while writing data to Event Hub due to throttling.
44+
* **Recommendation**: If this happens consistently, upgrade the throughput.
45+
46+
## EventHubOutputInvalidConnectionConfig
47+
48+
* **Cause**: The connection configuration provided is incorrect.
49+
* **Recommendation**: Correct the configuration and restart the job.
50+
51+
## EventHubOutputInvalidHostname
52+
53+
* **Cause**: The Event Hub host is unreachable.
54+
* **Recommendation**: Ensure the supplied host name is correct.
55+
56+
## EventHubOutputUnexpectedPartitionCount
57+
58+
* **Cause**: The EventHub sender encountered an unexpected EventHub partition count.
59+
* **Recommendation**: Restart your Stream Analytics job if the EventHub's partition count has changed.
60+
61+
## CosmosDBPartitionKeyNotFound
62+
63+
* **Cause**: Stream Analytics couldn't find the partition key of a particular Cosmos DB collection in the database.
64+
* **Recommendation**: Ensure there is a valid partition key specified for the collection in Cosmos DB.
65+
66+
## CosmosDBInvalidPartitionKeyColumn
67+
68+
* **Cause**: Thrown when a partition key is neither a leaf node nor at the top level.
69+
70+
## CosmosDBInvalidIdColumn
71+
72+
* **Cause**: The query output can't contain the column \[id] if a different column is chosen as the primary key property.
73+
74+
## CosmosDBDatabaseNotFound
75+
76+
* **Cause**: Stream Analytics can't find a CosmosDB database.
77+
78+
## CosmosDBCollectionNotFound
79+
80+
* **Cause**: Stream Analytics can't find a particular Cosmos DB collection in a database.
81+
82+
## CosmosDBOutputWriteThrottling
83+
84+
* **Cause**: An error occurred while writing data due to throttling by Cosmos DB.
85+
* **Recommendation**: Upgrade the collection performance tier and tune the performance of your database.
86+
87+
## SQLDatabaseConnectionStringError
88+
89+
* **Cause**: The Stream Analytics job has encountered an authentication error.
90+
* **Recommendation**: Ensure that the SQL Database connection string is correct.
91+
92+
## SQLDatabaseManagedIdentityAuthenticationError
93+
94+
* **Cause**: The Stream Analytics job has encountered an authentication error.
95+
* **Recommendation**: Ensure that the account name is configured properly and the job's Managed Identity has access to the SQL Database.
96+
97+
## SQLDatabaseOutputNoTableError
98+
99+
* **Cause**: Stream Analytics can't find the schema information for a particular table.
100+
101+
## SQLDWOutputInvalidServiceEdition
102+
103+
* **Cause**: SQL Database is not supported.
104+
* **Recommendation**: Use Synapse SQL pool.
105+
106+
## Next steps
107+
108+
* [Troubleshoot input connections](stream-analytics-troubleshoot-input.md)
109+
* [Troubleshoot Azure Stream Analytics outputs](stream-analytics-troubleshoot-output.md)
110+
* [Troubleshoot Azure Stream Analytics queries](stream-analytics-troubleshoot-query.md)
111+
* [Troubleshoot Azure Stream Analytics by using resource logs](stream-analytics-job-diagnostic-logs.md)
112+
* [Azure Stream Analytics data errors](data-errors.md)

‎articles/stream-analytics/data-error-codes.md

Lines changed: 79 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,79 @@
1+
---
2+
title: Data error codes - Azure Stream Analytics
3+
description: Troubleshoot Azure Stream Analytics issues with data error codes.
4+
ms.author: mamccrea
5+
author: mamccrea
6+
ms.topic: conceptual
7+
ms.date: 05/07/2020
8+
ms.service: stream-analytics
9+
---
10+
11+
# Azure Stream Analytics configuration error codes
12+
13+
You can use activity logs and resource logs to help debug unexpected behaviors from your Azure Stream Analytics job. This article lists the description for every data error error code. Data errors occur when there is bad data in the stream, such as an unexpected record schema.
14+
15+
## InputDeserializationError
16+
17+
* **Cause**: There was an error while deserializing input data.
18+
19+
## InputEventTimestampNotFound
20+
21+
* **Cause**: Stream Analytics is unable to get a timestamp for resource.
22+
23+
## InputEventTimestampByOverValueNotFound
24+
25+
* **Cause**: Stream Analytics is unable to get value of `TIMESTAMP BY OVER COLUMN`.
26+
27+
## InputEventLateBeyondThreshold
28+
29+
* **Cause**: An input event was sent later than configured tolerance.
30+
31+
## InputEventEarlyBeyondThreshold
32+
33+
* **Cause**: An input event arrival time is earlier than the input event application timestamp threshold.
34+
35+
## AzureFunctionMessageSizeExceeded
36+
37+
* **Cause**: The message output to Azure Functions exceeds the size limit.
38+
39+
## EventHubOutputRecordExceedsSizeLimit
40+
41+
* **Cause**: An output record exceeds the maximum size limit when writing to Event Hub.
42+
43+
## CosmosDBOutputInvalidId
44+
45+
* **Cause**: The value or the type of a particular column is invalid.
46+
* **Recommendation**: Provide unique non-empty strings that are no longer than 255 characters.
47+
48+
## CosmosDBOutputInvalidIdCharacter
49+
50+
* **Cause**: The output record's Document ID contains an invalid character.
51+
52+
## CosmosDBOutputMissingId
53+
54+
* **Cause**: The output record doesn't contain the column \[id] to use as the primary key property.
55+
56+
## CosmosDBOutputMissingIdColumn
57+
58+
* **Cause**: The output record doesn't contain the Document ID property.
59+
* **Recommendation**: Ensure the query output contains the column with a unique non-empty string less than '255' characters.
60+
61+
## CosmosDBOutputMissingPartitionKey
62+
63+
* **Cause**: The output record is missing the a column to use as the partition key property.
64+
65+
## CosmosDBOutputSingleRecordTooLarge
66+
67+
* **Cause**: A single record write to Cosmos DB is too large.
68+
69+
## SQLDatabaseOutputDataError
70+
71+
* **Cause**: Stream Analytics can't write event(s) to SQL Database due to issues in the data.
72+
73+
## Next steps
74+
75+
* [Troubleshoot input connections](stream-analytics-troubleshoot-input.md)
76+
* [Troubleshoot Azure Stream Analytics outputs](stream-analytics-troubleshoot-output.md)
77+
* [Troubleshoot Azure Stream Analytics queries](stream-analytics-troubleshoot-query.md)
78+
* [Troubleshoot Azure Stream Analytics by using resource logs](stream-analytics-job-diagnostic-logs.md)
79+
* [Azure Stream Analytics data errors](data-errors.md)

‎articles/stream-analytics/external-availability-error-codes.md

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
---
2+
title: External availability error codes - Azure Stream Analytics
3+
description: Troubleshoot Azure Stream Analytics issues with external availability error codes.
4+
ms.author: mamccrea
5+
author: mamccrea
6+
ms.topic: conceptual
7+
ms.date: 05/07/2020
8+
ms.service: stream-analytics
9+
---
10+
11+
# Azure Stream Analytics external availability error codes
12+
13+
You can use activity logs and resource logs to help debug unexpected behaviors from your Azure Stream Analytics job. This article lists the description for every external availability error code. External availability errors occur when a dependent service is unavailable.
14+
15+
## ExternalServiceUnavailable
16+
17+
* **Cause**: A service is temporarily unavailable.
18+
* **Recommendation**: Stream Analytics will continue to attempt to reach the service.
19+
20+
## KafkaServerNotAvailable
21+
22+
* **Cause**: The Kafka server is not available.
23+
24+
## EventHubMessagingError
25+
26+
* **Cause**: Stream Analytics encountered error when communicating with EventHub.
27+
28+
29+
## Next steps
30+
31+
* [Troubleshoot input connections](stream-analytics-troubleshoot-input.md)
32+
* [Troubleshoot Azure Stream Analytics outputs](stream-analytics-troubleshoot-output.md)
33+
* [Troubleshoot Azure Stream Analytics queries](stream-analytics-troubleshoot-query.md)
34+
* [Troubleshoot Azure Stream Analytics by using resource logs](stream-analytics-job-diagnostic-logs.md)
35+
* [Azure Stream Analytics data errors](data-errors.md)

‎articles/stream-analytics/external-error-codes.md

Lines changed: 99 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,99 @@
1+
---
2+
title: External error codes - Azure Stream Analytics
3+
description: Troubleshoot Azure Stream Analytics issues with external error codes.
4+
ms.author: mamccrea
5+
author: mamccrea
6+
ms.topic: conceptual
7+
ms.date: 05/07/2020
8+
ms.service: stream-analytics
9+
---
10+
11+
# Azure Stream Analytics external error codes
12+
13+
You can use activity logs and resource logs to help debug unexpected behaviors from your Azure Stream Analytics job. This article lists the description for every external error code. External errors are generic errors thrown by an upstream or downstream service that Stream Analytics can't distinguish as a data error, configuration error, or external availability error.
14+
15+
## AdapterInitializationError
16+
17+
* **Cause**: An error occurred when initializing the an adapter.
18+
19+
## AdapterFailedToWriteEvents
20+
21+
* **Cause**: An error occurred while writing data to an adapter.
22+
23+
## KafkaServerError
24+
25+
* **Cause**: The Kafka server returned an error:
26+
27+
## AzureFunctionHttpError
28+
29+
* **Cause**: An HTTP error was returned from Azure functions.
30+
31+
## AzureFunctionFailedToSendMessage
32+
33+
* **Cause**: Stream Analytics failed to write events to Azure Function.
34+
35+
## AzureFunctionRedirectError
36+
37+
* **Cause**: There is a redirect error when outputting to Azure Functions.
38+
39+
## AzureFunctionClientError
40+
41+
* **Cause**: There is a client error outputting to Azure Functions.
42+
43+
## AzureFunctionServerError
44+
45+
* **Cause**: There is a server error outputting to Azure Functions.
46+
47+
## AzureFunctionHttpTimeOutError
48+
49+
* **Cause**: Writing to Azure functions failed as the http request exceeded the timeout.
50+
* **Recommendation**: Check your Azure Functions logs for potential delays.
51+
52+
## EventHubArgumentError
53+
54+
* **Cause**: Input offsets are invalid. This may be due to a failover.
55+
* **Recommendation**: Restart your Stream Analytics job from last output time.
56+
57+
## EventHubFailedToWriteEvents
58+
59+
* **Cause**: An error occurred while sending data to Event Hub.
60+
61+
## CosmosDBConnectionFailureAfterMaxRetries
62+
63+
* **Cause**: Stream Analytics failed to connect to a Cosmos DB account after the maximum number of retries.
64+
65+
## CosmosDBFailureAfterMaxRetries
66+
67+
* **Cause**: Stream Analytics failed to query the Cosmos DB database and collection after the maximum number of retries.
68+
69+
## CosmosDBFailedToCreateStoredProcedure
70+
71+
* **Cause**: CosmosDB can't create a stored procedure after several retries.
72+
73+
## CosmosDBOutputRequestTimeout
74+
75+
* **Cause**: The upsert stored procedure returned an error.
76+
77+
## SQLDatabaseOutputInitializationError
78+
79+
* **Cause**: Stream Analytics can't initialize the SQL Database output.
80+
81+
## SQLDatabaseOutputWriteError
82+
83+
* **Cause**: Stream Analytics can't write events to the SQL Database output.
84+
85+
## SQLDWOutputInitializationError
86+
87+
* **Cause**: An error occurred when initializing a Synapse SQL pool output.
88+
89+
## SQLDWOutputWriteError
90+
91+
* **Cause**: An error occurred when writing output to a Synapse SQL pool.
92+
93+
## Next steps
94+
95+
* [Troubleshoot input connections](stream-analytics-troubleshoot-input.md)
96+
* [Troubleshoot Azure Stream Analytics outputs](stream-analytics-troubleshoot-output.md)
97+
* [Troubleshoot Azure Stream Analytics queries](stream-analytics-troubleshoot-query.md)
98+
* [Troubleshoot Azure Stream Analytics by using resource logs](stream-analytics-job-diagnostic-logs.md)
99+
* [Azure Stream Analytics data errors](data-errors.md)

0 commit comments

Comments
 (0)