Skip to content
This repository has been archived by the owner on Aug 1, 2024. It is now read-only.

Queue: The specified resource name contains invalid characters #973

Open
florianlenz96 opened this issue Mar 10, 2020 · 4 comments
Open

Comments

@florianlenz96
Copy link

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?

@julienFlexsoft
Copy link

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?

@lxzhu
Copy link

lxzhu commented Oct 19, 2020

any workaroud or progress? I run into this tricky bug today

@julienFlexsoft
Copy link

julienFlexsoft commented Oct 19, 2020

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.

@earloc
Copy link

earloc commented Jan 17, 2024

Had a similar situation today.
Seems like the .net-SDK somewhen decided to get picky about enforcing naming-conventions.

see https://learn.microsoft.com/en-us/rest/api/storageservices/naming-queues-and-metadata#queue-names

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants