Skip to content

Commit 3bdda59

Browse files
mamccreamamccrea
committed
error codes build
1 parent cd32bc8 commit 3bdda59

File tree

2 files changed

+123
-0
lines changed

2 files changed

+123
-0
lines changed

‎articles/stream-analytics/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -223,6 +223,8 @@
223223
href: stream-analytics-job-diagnostic-logs.md
224224
- name: Data errors
225225
href: data-errors.md
226+
- name: Error codes
227+
href: error-codes.md
226228
- name: Integrate with machine learning
227229
items:
228230
- name: Sentiment analysis with ML models

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

Lines changed: 121 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,121 @@
1+
---
2+
title: Troubleshoot with Azure Stream Analytics error codes
3+
description:
4+
ms.author: mamccrea
5+
author: mamccrea
6+
ms.topic: conceptual
7+
ms.date: 05/06/2020
8+
ms.service: stream-analytics
9+
---
10+
11+
# Troubleshoot with Azure Stream Analytics 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 error code that can occur for the following error categories:
14+
15+
* Configuration error
16+
* Data error
17+
* External availability error
18+
* External error
19+
* Internal error
20+
21+
## Configuration error
22+
23+
Configuration errors are related to your job configuration, or input and output configurations. See all configuration error codes in the following table:
24+
25+
|Error code|Description|
26+
|-----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
27+
| KafkaInvalidPermission | The Stream Analytics job do not have the proper permission to perform certain actions, detailed error is [{0} - {1}]. |
28+
| KafkaInvalidConfiguration | Certain configurations on the Kafka adapter are invalid, detailed error is [{0} - {1}]. |
29+
| KafkaInvalidTimestampType | The timestamp type used by Kafka topic \[{0}] is invalid. Expecting {1} but got {2}. |
30+
| EventHubUnauthorizedAccess | Encountered Unauthorized Access error from Event Hub: {0} |
31+
| EventHubReceiverEpochConflict | There is more than one receiver with different epoch value connected to the same {0}. Please ensure Service Bus Explorer or an EventProcessorHost application is not connected while this Stream Analytics job is running. |
32+
| EventHubReceiverQuotaExceeded | We cannot connect to {0} partition \[{1}] because the maximum number of allowed receivers per partition in a consumer group has been reached. Ensure that other Stream Analytics jobs or Service Bus Explorer are not using the same consumer group. The following information may be helpful in identifying the connected receivers: {2} |
33+
| EventHubOutputThrottled | An error occurred while writing data to Event Hub due to throttling. Please upgrade the throughput if it is happening consistently. |
34+
| EventHubOutputInvalidConnectionConfig | The connection configuration provided is incorrect. Please correct the configuration and restart the job. |
35+
| EventHubOutputInvalidHostname | The Event Hub host is unreachable. Please make sure the supplied host name is correct. |
36+
| EventHubOutputUnexpectedPartitionCount | EventHub sender encounters unexpected EventHub partition count. Please restart the job if EventHub's partition count has changed. |
37+
| CosmosDBPartitionKeyNotFound | Failed to find the partition key of Cosmos DB collection \[{0}] in database \[{1}]. Please ensure there is a valid partition key specified for the collection in Cosmos DB. |
38+
| CosmosDBInvalidPartitionKeyColumn | The partition key can only be a leaf node at the top level. {0} is neither a leaf node nor at the top level. |
39+
| CosmosDBInvalidIdColumn | The query output cannot contain the column \[id] if a different column '{0}' is chosen as the primary key property. |
40+
| CosmosDBDatabaseNotFound | Cannot find database \[{0}]. |
41+
| CosmosDBCollectionNotFound | Failed to find Cosmos DB collection: \[{0}] in database:\[{1}]. |
42+
| CosmosDBOutputWriteThrottling | An error occurred writing data due to throttling by Cosmos DB. Please upgrade collection performance tier and tune the performance of your database. |
43+
| SQLDatabaseConnectionStringError | The ASA job has encountered an authentication error at {0}. Please ensure that the SQL Database connection string is correct. |
44+
| SQLDatabaseManagedIdentityAuthenticationError | The ASA job has encountered an authentication error at {0}. Please ensure that the account name is configured properly and the job's Managed Identity has access to the SQL Database. |
45+
| SQLDatabaseOutputNoTableError | Cannot find schema information for table {0} at {1}: {2}. |
46+
| SQLDWOutputInvalidServiceEdition | SQL Database is not supported. Please use Synapse SQL pool. |
47+
48+
## Data error
49+
50+
Data errors occur when there is bad data in the stream, such as an unexpected record schema. See all data error codes in the following table:
51+
52+
| Error code | Description |
53+
|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
54+
| InputDeserializationError | Error while deserializing input message Id: {0}. Hit following error: {1} |
55+
| InputEventTimestampNotFound | Unable to get timestamp for resource '{0}' due to error '{1}' |
56+
| InputEventTimestampByOverValueNotFound | Unable to get value of TIMESTAMP BY OVER COLUMN |
57+
| InputEventLateBeyondThreshold | Input event with application timestamp '{0:o}' and arrival time '{1:o}' was sent later than configured tolerance. |
58+
| InputEventEarlyBeyondThreshold | Input event arrival time '{0:o}' is earlier than input event application timestamp '{1:o}' by more than {2} minutes. |
59+
| AzureFunctionMessageSizeExceeded | There is a problem outputting to Azure Functions. The message size limit of {0} bytes has been exceeded. Size of the message is {1} bytes. |
60+
| EventHubOutputRecordExceedsSizeLimit | An output record exceeds the maximum size limit of {0} {1} when writing to Event Hub. |
61+
| CosmosDBOutputInvalidId | The value \[{0}] or the type of the column \[id] is invalid. Please provide unique non-empty strings that are no longer than 255 characters. |
62+
| CosmosDBOutputInvalidIdCharacter | The output record's document id value \[{0}] contains an invalid character. |
63+
| CosmosDBOutputMissingId | The output record does not contain the column \[id] to use as primary key property. |
64+
| CosmosDBOutputMissingIdColumn | The output record does not contain the document id property: \[{0}]. Ensure the query output contains the column \[{0}] with a unique non-empty string less than '255' characters. |
65+
| CosmosDBOutputMissingPartitionKey | The output record is missing the column '{0}' (case-sensitive) to use as the partition key property. |
66+
| CosmosDBOutputSingleRecordTooLarge | A single record write to Cosmos DB is too large. |
67+
| SQLDatabaseOutputDataError | Cannot write event(s) to SQL Database due to issues in the data. Detailed Error: {0} |
68+
69+
## External availability error
70+
71+
External availability errors occur when a dependent service is unavailable. See all external availability error codes in the following table:
72+
73+
| Error code | Description |
74+
|----------------------------|---------------------------------------------------------------------|
75+
| ExternalServiceUnavailable | {0} is temporarily unavailable, retrying. |
76+
| KafkaServerNotAvailable | The Kafka server is not available, detailed error is [{0} - {1}]. |
77+
| EventHubMessagingError | Encountered error when communicating with EventHub: {0} |
78+
79+
## External error
80+
81+
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. See all external error codes in the following table:
82+
83+
| Error code | Description |
84+
|------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
85+
| AdapterInitializationError | An error occurred when initializing the {0} adapter. |
86+
| AdapterFailedToWriteEvents | An error occurred writing data to {0}. |
87+
| KafkaServerError | The Kafka server returns an error: [{0} - {1}]. |
88+
| AzureFunctionHttpError | An HTTP error is returned from Azure functions. |
89+
| AzureFunctionFailedToSendMessage | Failed to write events to Azure Function. |
90+
| AzureFunctionRedirectError | There is a problem outputting to Azure Functions. The following information may be useful in diagnosing the issue. Error received: '{0} ({1})'. RequestId: '{2}'. |
91+
| AzureFunctionClientError | There is a problem outputting to Azure Functions. The error received: '{0} ({1})' indicates client side error. RequestId: '{2}'. |
92+
| AzureFunctionServerError | There is a problem outputting to Azure Functions. The error received: '{0} ({1})' indicates server side error. RequestId: '{2}' |
93+
| AzureFunctionHttpTimeOutError | Writing to Azure functions failed as the http request exceeded {0} seconds. Please check your Azure Functions logs for potential delays. Request Id: {1}. |
94+
| EventHubArgumentError | Input offsets are invalid. This may be due to a failover. Stream Analytics job will have to be restarted from last output time. Exception: {0} |
95+
| EventHubFailedToWriteEvents | An error occurred while sending data to Event Hub. The following information can be helpful in diagnosing the issue: {0} {1}. |
96+
| CosmosDBConnectionFailureAfterMaxRetries | Failed to connect to the Cosmos DB account {0} after {1} retries. |
97+
| CosmosDBFailureAfterMaxRetries | Failed to query the Cosmos DB database and collection after {0} retries. |
98+
| CosmosDBFailedToCreateStoredProcedure | Cannot create stored procedure after several retries. Error: {0} |
99+
| CosmosDBOutputRequestTimeout | Upsert stored procedure returned error {0} for batch size {1}, this operation will be retried. Detailed error message: {2}." |
100+
| SQLDatabaseOutputInitializationError | Cannot initialize SQL Database output with database info: {0}. |
101+
| SQLDatabaseOutputWriteError | Cannot write {0} events to SQL Database output at {1}. Detailed Error: {2} |
102+
| SQLDWOutputInitializationError | An error occurred when initializing Synapse SQL pool output. |
103+
| SQLDWOutputWriteError | An error occurred when writing output to Synapse SQL pool. |
104+
105+
## Internal error
106+
107+
Internal errors are generic errors that are thrown within the Stream Analytics platform when Stream Analytics can't distinguish if
108+
109+
| Error code | Description |
110+
|---------------------------------|-----------------------------------------------------------------------------------------------|
111+
| KafkaInvalidRequest | The request sent to the Kafka server is invalid, detailed error is \[{0] - {1}]. |
112+
| KafkaInputError | Kafka input encounters an issue: [{0} - {1}]. |
113+
| CosmosDBOutputBatchSizeTooLarge | The batch size used to write to Cosmos DB is too large, retrying with a smaller batch size. |
114+
115+
## Next steps
116+
117+
* [Troubleshoot input connections](stream-analytics-troubleshoot-input.md)
118+
* [Troubleshoot Azure Stream Analytics outputs](stream-analytics-troubleshoot-output.md)
119+
* [Troubleshoot Azure Stream Analytics queries](stream-analytics-troubleshoot-query.md)
120+
* [Troubleshoot Azure Stream Analytics by using resource logs](stream-analytics-job-diagnostic-logs.md)
121+
* [Azure Stream Analytics data errors](data-errors.md)

0 commit comments

Comments
 (0)