Skip to main content

Troubleshooting for ADLS Reader

This topic lists common errors you may encounter when using the ADLS Reader and suggests resolutions.

Exception / Error

Resolutions

ADLSContainerNotFoundException

  • Verify that the storage AccountName and Container values are correct and the container exists.

  • Confirm the Microsoft Entra ID application has Storage Blob Data Reader (or Contributor) access on the storage account or container.

  • If using private endpoints, ensure DNS resolves to the private endpoint and the Striim host can reach it.

EntraIdCredentialsException (authentication failed)

  • Check ClientId, TenantId, and ClientSecret values. If ClientSecret_encrypted is set to true, ensure the secret is stored in the encrypted field.

  • Confirm the Entra ID app is single-tenant (or multi-tenant as intended) and not disabled or expired.

  • Verify system time on the Striim host (large clock skew can break token acquisition).

AzurePermissionException (AuthorizationFailed / 403)

  • Grant the Entra ID application the Storage Blob Data Reader (read-only) or Storage Blob Data Contributor role at the storage account or container scope.

  • Re-authenticate after role changes; RBAC propagation can take a few minutes.

LogAnalyticsAccessException (when ObjectDetectionMode=LogAnalytics)

  • Ensure Log Analytics Reader role is assigned to the Entra ID application for the workspace.

  • Verify diagnostic settings on the storage account: provider blob enabled and StorageWrite category is sent to the correct workspace.

  • Check LogAnalyticsWorkspaceId matches the workspace and that logs are flowing (consider the 5–10 minute ingestion delay).

CloudStorageConnectionException (timeouts / 429 / 503)

  • Validate outbound network access from the Striim host to Azure Storage and (if applicable) Log Analytics endpoints.

  • Tune ConnectionRetryPolicy (for example, increase retryInterval and maxRetries) and increase PollingInterval to reduce API pressure.

  • Check firewall rules, proxy configuration, and VPN policies.

LocalFileSystemException (download mode / Parquet)

  • Ensure sufficient disk space and permissions on the download path. Adjust Download Policy limits if applicable.

  • If object names exceed the OS filename length, switch to streaming (set UseStreaming to true) or shorten object names.

  • On restart, unprocessed temporary files are cleared and re-downloaded; verify the directory is writable.

CustomerProvidedKeyMismatch (SSE with customer-provided keys)

  • If the storage account uses customer-provided keys for server-side encryption, configure the same key in the reader’s Customer Provided Key property (properly base64-encoded).

  • Confirm the key ID/algorithm matches the object encryption settings.

StartTimestampParseException

  • Provide Start Timestamp in a supported ISO format, for example YYYY-MM-DD'T'hh:mm:ss.sssTZD.

  • Note that during recovery the checkpoint position takes precedence over Start Timestamp.

UnsupportedCompressionFormat

  • Only gzip is supported. Re-compress files as gzip or leave Compression Type blank for uncompressed objects.

ObjectMissingAfterDiscovery

  • This occurs when an object is deleted after its metadata is fetched but before read begins. Re-run the application or ensure upstream processes do not delete files mid-ingest.

  • Consider using Log Analytics mode for lower metadata-fetch overhead in high-churn environments.