You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 1, 2024. It is now read-only.
I have the same issue now. on .Net Core 2.2.
.CreateIfNotExistsAsync() returns the same exception. It worked perfectly for months but now I get this exception without having made changes to the code.
Any update on this?
Well, if I remember correctly I did make some changes by mistake and an uppercase character was in the queue name, which is forbidden, it must all be lowercase.
In my case, I had uppercase letters in the queue-name, like someFancyOutputQueue.
Ensuring that the used queue-name was all lower-case (e.g. somefancyoutputqueue) fixed the issue for me.
funny thing is: we are using a lot of java-/typescript azure functions, where we use mixed-case names in output-bindings.
Nothing complains about this. But the actual queues that get created, are all lower-case, anyway.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Which service(blob, file, queue, table) does this issue concern?
Queue
Which version of the SDK was used?
11.1.3
Which platform are you using? (ex: .NET Core 2.1)
.NET Core 3.1
What problem was encountered?
I am trying to connect to the Storage Account. I get the error message: The specified resource name contains invalid characters
How can we reproduce the problem in the simplest way?
Create an Queue Object an call method CreateIfNotExists.
Have you found a mitigation/solution?
The text was updated successfully, but these errors were encountered: