Issue with configuring the stream analytics job

Question

I had created a stream analytics job which takes the data from event hub and need to be pushed to a sql table in dedicated sql pool. when i am trying to configure the output the sql pool i am getting the following error.

Connection test failed
Error connecting to staging blob storage for Synpase SQL pool output The specified container does not exist.
RequestId:0dc91e9f-b01e-000f-4493-1cebb6000000
Time:2022-12-30T21:14:54.0240699Z. [SessionID: 8436914a09d8452c94a6c5e25cc455ae]

I had configured the storage account which is pointing to the synapse analytics workspace, granted the blob contributor access to the stream analytics managed identity as well.
But still getting the error.

Can someone help me in fixing this.

Answer 1

Hello @Admin (KK) ,

Thanks for the question and using MS Q&A platform.

There are several things you can try to fix this issue:

• Make sure that the container specified in the output configuration for the Stream Analytics job exists in the storage account you are using. You can check this by navigating to the storage account in the Azure portal and looking for the container in the "Blob service" blade.
• Make sure that the Stream Analytics managed identity has been granted the necessary permissions to access the container. You can do this by navigating to the "Access control (IAM)" blade in the storage account and adding a role assignment for the Stream Analytics managed identity with the "Blob Contributor" role.
• Check the logs for the Stream Analytics job to see if there are any more detailed error messages that may help identify the cause of the problem. You can view the logs by navigating to the job in the Azure portal and clicking on the "Logs" button in the "Monitoring" section.
• Make sure that the Stream Analytics job is using the correct storage account and container in the output configuration. You can verify this by double-checking the output configuration in the Stream Analytics job.
• If the issue persists, you may want to try creating a new storage account and container and using that for the output configuration, to rule out any problems with the existing storage account and container.

I hope this helps! Let me know if you have any other questions.