An Azure real-time analytics service designed for mission-critical workloads.
Hi @Naveen S Kumar Thanks for describing your issue in detail. It's unusual to encounter this error only when adding a 7th dataset to your Azure Stream Analytics job.
The error message:
Value cannot be null.
Parameter name: s
is a .NET-level exception, and in the context of Azure Stream Analytics, it typically points to a missing or improperly configured string parameter — often something like an input alias, name, or configuration value being set to null.
Based on your description, here’s what stands out:
- You can onboard up to 6 datasets without issue.
- Adding a 7th dataset (regardless of which one) results in a failure.
- Removing an existing dataset and adding a new one works — confirming the issue isn’t with the dataset content but with the job’s configuration or internal limits.
Possible Cause
This usually happens when one of the following parameters such as name, alias, or a required configuration is missing, empty, or null during the creation of the input. The Stream Analytics backend expects a valid string and throws this error when it receives null.
It’s also possible you’re hitting a soft limit or internal resource constraint related to job complexity or metadata handling when adding more inputs.
Suggested Fixes
- Check the 7th dataset input configuration: Ensure the
nameoraliasis not empty and follows naming conventions (alphanumeric, no special characters, no spaces). Avoid copy-pasting from existing inputs without renaming. - Review the input JSON definition: If using the Azure Portal: Open the input in JSON view and check for any
nullor missing values. If using ARM templates or CLI: Make sure each input’s"name"and"properties"fields are correctly populated. - Test with a simplified input: Try adding a new 7th input with a minimal configuration and a simple name. Don’t reference it in the query yet just see if it saves and the job starts.
- Check Stream Analytics job limits: There are documented limits on: Number of inputs, Query complexity, Streaming Unit (SU) capacity. If needed, scale up the job to increase capacity.
You can review limits here: Azure Stream Analytics Limits
Hope this helps. Do let us know if you any further queries.
If this answers your query, do click Accept Answer and Yes for was this answer helpful.