Azure-docs: Custom Endpoint Creation

[GuuB]

Hello,

Following the tutorial, I am trying to create a Messaging Route called "GBQueueRoute".
But I am stuck trying to link the service bus endpoint to the route on the _Add a route_ form page.
I have successfully created the Service Queue Namespace ("GBServiceQueueNamespace") and a queue ("gbqueue").
In the _Add a service bus endpoint_ form page these are listed. I type my Endpoint name ("CriticalQueue") and click Create. A success message appears. Great!
But when I try to select the newly created endpoint it is not listed in the drop-down.

What am I missing?
Thank you,

Guy

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: f233412c-4242-e9a6-e09d-c5b07775dd00
• Version Independent ID: 3a940d2c-77bb-b8ff-8864-9fc6ef16c122
• Content: Configure message routing with Azure IoT Hub (.NET)
• Content Source: articles/iot-hub/tutorial-routing.md
• Service: iot-hub
• GitHub Login: @robinsh
• Microsoft Alias: robinsh

[mimckitt]

Thanks for the feedback! We are currently investigating and will update you shortly.

[asergaz]

Hello @GuuB are you sitll experiencing this issue? This seems to be a portal issue. Please let us know if you are still blocked? We had some Azure Portal issues which I am wondering if it can be related...

Thank you!

[myszon01]

Hi,

I think I have a similar issue. I can create route and custom endpoint in my IoT hub but this endpoint is in status Uknown, and when I send messages from IoT device they are not getting delivered to the service bus queue. Both resources are located in East region.

Thank you

[robinsh]

@myszon01 I don't really know why, but my status for the endpoint is always Unknown. I'll pass this on to the PM. Are you sending messages from the IoT device to the service bus queue as described in the article? Or are you writing them to a service bus queue in a different way? The article describes how to set up an endpoint for the service bus queue and route messages to it from the sample application when level="critical" ? Are you using the sample to send the messages, and are any of the messages going through, like the ones to the stream analytics or the ones to blob storage? This would tell if the routing is working at all, or if there was a problem with the hub.

[robinsh]

@guub Just curious; if you refresh the page, does the endpoint show up?

[GuuB]

@sergaz-msft I just tried on a different laptop & browser and the issue persists. I will take a look into the other issues.

@robinsh I Sadly no.
I have not tried sending messages to the service bus queue. I can try tomorrow.

Thanks!

[robinsh]

(my answer regarding another's issue)

@guub You can't get the endpoint to show up in the Add list? When you save the endpoint on the create-an-endpoint screen, it should return to the add-a-route screen with the endpoint info populated, and then you can just save the route. Is it not doing that?

[myszon01]

@robinsh When I was deploying new custom endpoint a week or two ago the status was always Healthy and routing is working. Yes, I am using the sample application when level="critical" and it is working but now when I am deploying new custom endpoints it seems like something doesn't work and I am doing exactly same steps as I did on my previous development. I will double check if routing is working and I will let you know today. Also, I noticed that when I am trying to synchronize keys for Service Bus Queue from IoT Hub I am getting following error "Error synchronizing access keys on service bus topic..."

[myszon01]

@robinsh routing is working when I send messages to the BLOB storage also I noticed that when I created the custom endpoint for the Blob the status was Healthy

[robinsh]

@myszon01 Just have to check. Your last comment above says "error synchronizing access keys on service bus topic". Are you using a topic or a queue? I haven't tried this with a topic, so have no idea how that would work. Be sure you're adding it as a queue and not as a topic?
I still have one of these deployed, and I checked it, and the status is healthy, so at least that's working.

[myszon01]

Yes, I have double check and I am using Service Bus Queue I have no clue why I am getting this error.

[myszon01]

Now it is working. I have deployed a new service bus.

[robinsh]

@myszon01 That's great news! I'm glad you got it working.

[robinsh]

@guub How's it going? Have you had any success getting the tutorial to work?

[GuuB]

@robinsh

When you save the endpoint on the create-an-endpoint screen, it should return to the add-a-route screen with the endpoint info populated, and then you can just save the route.

I have saved the endpoint on the _create-an-endpoint_ screen and it returns to the _add-a-route_ screen but the endpoint is not populated nor is it in the drop-down. (I still get the success message: "_Successfully created service bus endpoint: 'CriticalQueue'._")
At first, I was using my work account when following the tutorial. Today I started over with my personal account and the service bus queue endpoint problem persists.

I have run the simulated device and confirmed that the _storage level_ messages are stored in my container.

Please let me know what I can try to create the service bus queue endpoint.

Thanks!

[robinsh]

@guub Are you open to doing a skype meeting and letting me see what you're doing? If so, e-mail me at robin dot shahan at microsoft dot com. This is really strange, and I'd like to see it if that's possible.

[asergaz]

Hello @GuuB since we have not heard back from you we will now proceed to close this thread. If there are further questions regarding this matter, please tag me or @robinsh in your reply. We will gladly continue the discussion and we will reopen the issue.

[RogerFraserZa]

Hi @GuuB I am also following this tutorial and have exactly the same issue .

Iothub Message Routing -> Add
Click Add next to endpoint Select service bus queue
Endpoint name CriticalQueue ,Select drop down Service bus and queue
Click create it returns back to the Message Routing add form shows :Success
16:41
Successfully created service bus endpoint: 'CriticalQueue'.

but does not populate the endpoint dropdown with the new service bus endpoint.

[asergaz]

I'm reopening the issue. I believe we have a similar issue also on MSDN - https://social.msdn.microsoft.com/Forums/en-US/acde3b16-e14f-4ec3-9092-2164e1ce9a7c/routing-to-a-service-bus-queue?forum=azureiothub

@robinsh were you able to reproduce the issue?
Thanks!

[robinsh]

I have run through this tutorial a bunch of times, and have never seen this problem. I think the next question for those having problems is have you edited the script used to create the resources? Are you creating a hub with an S1 sku, or are you using a free hub? You can't use a free hub, it only allows 1 endpoint, and to do this tutorial, you need more than one. So what sku are you using for your hub?

[RogerFraserZa]

Hi Robin

My IOT hub is a F1 free hub .I don’t get any error message when creating the endpoint to the affect that there is only one endpoint allowed it actually returns successfully created message .

Roger Fraser

From: Robin Shahan [e-mail]
Sent: 15 November 2018 01:21 AM
To: MicrosoftDocs/azure-docs [e-mail]
Cc: RogerFraserZa [e-mail]; Comment [e-mail]
Subject: Re: [MicrosoftDocs/azure-docs] Custom Endpoint Creation (#16613)

I have run through this tutorial a bunch of times, and have never seen this problem. I think the next question for those having problems is have you edited the script used to create the resources? Are you creating a hub with an S1 sku, or are you using a free hub? You can't use a free hub, it only allows 1 endpoint, and to do this tutorial, you need more than one. So what sku are you using for your hub?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/MicrosoftDocs/azure-docs/issues/16613#issuecomment-438856063 , or mute the thread https://github.com/notifications/unsubscribe-auth/Am74Le1mCsPK7viwljaaJLf7KU_vZ-jxks5uvKVJgaJpZM4XWWSK . https://github.com/notifications/beacon/Am74LUAHwZiRIegv8TkIjIZk4jv_SAuFks5uvKVJgaJpZM4XWWSK.gif

[robinsh]

@RogerFraserZa I've talked to the engineer and the PM that own that feature. We're going to meet on Monday to finalize the action we'll take. I think we'll end up adding a note to the tutorial warning people not to use a free hub, and they will make it so you can't add more than 1 endpoint, and it gives you an error message. I'll report back early next week.

@Guub Are you also using a free IoT hub rather than the S1 hardcoded in the script used to create the hub?

[asergaz]

@GuuB please can you confirm that you used free IoTHub as well? I have assigned the issue to @robinsh that will enhance the doc based on your feedback.

Thanks!

[GuuB]

@sergaz-msft @robinsh I can confirm I was using the free F1 IoT Hub pricing tier.
Glad you guys found the cause! Thanks.

[robinsh]

I've updated the article to have a note that explains you can't use a free IoT Hub for this tutorial.

[robinsh]

This issue can be closed. The problem was that they were using a Free IoT Hub, and you can't do that for this tutorial, as it requires you to set up multiple endpoints.

please-close

[asergaz]

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.