Error on partition ""

Alex Fang 230

I am trying to run this sample code using my connection string, and I am encountering the following error:

Error on partition "" : MessagingError: The messaging entity 'sb://....servicebus.windows.net/

Alex Fang 230 Reputation points

2023-07-25T15:03:01.24+00:00

Hi @LeelaRajeshSayana-MSFT

To run the sample from the first link, I have set the shared access policy connection string to the service connection string. Once I run it with node file_name.js I get the error as seen above. Similar code from this tutorial is fine and able to connect, although when I ran it to make sure it works today, it is no longer working properly as a new iteration of the same device is being created each time telemetry is being sent rather than it being one device on the dropdown.

For the second sample, I have used the iothubowner connection string, however the properties and partitionKey are undefined for some reason. You can view this by just printing out the message as a whole. I am not sure why it is undefined for either.
LeelaRajeshSayana-MSFT 15,801 Reputation points Microsoft Employee

2023-07-25T22:13:40.2066667+00:00

Hi @Alex Fang thank you for your response. Can you let me know if you have assigned any variable values using the .env file as mentioned in the Setup step

For the sample for this code you would need to pass the IoT Hub built in end point connection string and not the IoT Hub owner connection string. Please refer the below image.

Hope this helps. Please let us know if you still encounter any problems with testing the code. We would be glad to connect with you offline and assist you further.
Alex Fang 230 Reputation points

2023-07-26T14:52:19.6466667+00:00

@LeelaRajeshSayana-MSFT I did not set up a .env file for the first sample.

For the second sample, I am using the correct connection string as you have shown.
LeelaRajeshSayana-MSFT 15,801 Reputation points Microsoft Employee

2023-07-26T15:24:43.7+00:00

Hi @Alex Fang For a deeper investigation and immediate assistance on this issue, could you please send an email with the below details, so that we can work closely on this matter.

Thread URL: Link to this thread.

Azure Subscription ID:

Email Subject : Attn Leela
Alex Fang 230 Reputation points

2023-07-26T20:05:30.4333333+00:00

I have the sent email. I also played around a little with the connection string.

Instead of calling convertIotHubToEventHubsConnectionString to get the built-in endpoint connection string for iothubowner, I just directly set it to the Event Hub compatible endpoint from the Azure portal. This worked for me.

Comparing the two strings, one from the portal and the one produced by the above function, it seems that the function is messing up the EntityPath of the endpoint connection string. It is setting it to just the IoT Hub name but in the connection string from the portal, the EntityPath value is completely different.

Edit: I replaced the return statement for the function from the sample with the return statement from the same function in the web tutorial and it seems to work.
LeelaRajeshSayana-MSFT 15,801 Reputation points Microsoft Employee

2023-07-26T23:42:52.7066667+00:00

Hi @Alex Fang Thank you so much for your response and letting us know what has helped you resolve the issue. We did receive your email and have been testing the code trying to replicate the same error.

It is strange that the EntityPath in the end point connection string has a different value other than the IoT Hub name. This value is auto generated and is typically assigned to the IoT Hub name. I am not sure what could have caused the Entity path to contain a different value. I am glad you caught that. This is not easy thing to narrow down to. Kudos to you.

I have provided a response below capturing this fix. I appreciate it if you can mark the response as Accepted Answer for the benefit of the community. Please do let us know if you have any further questions or need additional assistance.

Accepted answer

LeelaRajeshSayana-MSFT 15,801 Reputation points Microsoft Employee

2023-07-25T00:50:34.87+00:00

@Alex Fang Could you please let us know the steps you have followed in executing the sample from the first link you shared? The code sample needs refer to the IoT Hub shared access policy connection string to be set in Line 130 of the code. You can get the connection string value by navigating to Security Settings --> Shared Access Policies --> select service policy and get the primary connection string. Once you have this set and execute the code sample, you should be able to receive events without any issues.

I appreciate it if you can let me know the steps you have followed to execute the second sample as well. Seeing that you are trying to receive events from built in end point, you need to provide the connection string of your IoT Hub built in end point on Line 38 You can get the connection string value by navigating to Built-in endpoints section and looking under Event Hub-compatible endpoint setting. Setting this should execute the code as expected. Here is the response I get from the code

I also did not notice any part of the provided sample where partition key for the end point is accessed explicitly. I am not sure why you are facing this error. I appreciate if you can share more details on the error or any error stack to help us better understand this issue.

Issue:

The Default end point URL is generated from the connection string is not the same as the End point URL noticed from the portal.

Resolution:

Modified the code to ensure that the Entity path in the Line 113 is correct and the end point URL matches the connection string observed on the Azure portal built-in end point connection string.

If the response helped, please do click Accept Answer and Yes for the answer provided. Doing so would help other community members with similar issue identify the solution. I highly appreciate your contribution to the community.
Please sign in to rate this answer.
Alex Fang 230 Reputation points

2023-07-27T14:52:36.91+00:00

To execute the first sample, I did set the connection string in line 130 to one of the primary connection strings from the shared access policies as you described. However, this resulted in the error that I described in my original post. In trying to fix this issue, I noticed that the connection string produced by the function convertIotHubToEventHubsConnectionString was not the same as the one on my Azure portal. To fix this, I replaced the return statement in the sample's convertIotHubToEventHubsConnectionString function to this:

, which is from the same function in this tutorial script. Notice that the code from the tutorial and the sample are pretty much the same except for this part I believe. This did manage to fix my issue and I am now able to connect to the built-in endpoint. The ONLY ISSUE I am now encountering for this sample is that the speed of telemetry received is super fast (a few messages per second) as compared to the one message every few seconds that I received in running the tutorial code.

In regards to the second sample, I did use the endpoint connection string in line 38.

NEW ISSUE:

I am now noticing that the issue of having undefined as the value for properties and partitionKey seems to be a universal issue for me. As seen above, it is in the message that I get when running the second sample.

I ALSO am getting the same issue when I run the first sample.

CONCLUSION:

I am able to read messages sent from a device by using the built-in endpoint but the messages I am receiving are incomplete. I hope to get further help in resolving this issue. @LeelaRajeshSayana-MSFT

Alex Fang 230 Reputation points

2023-07-27T14:53:06.25+00:00

I will leave this thread unresolved for now as I try to fix my undefined value issue for properties and partitionKey.

LeelaRajeshSayana-MSFT 15,801 Reputation points Microsoft Employee

2023-07-27T15:14:30.3+00:00

Hi @Alex Fang Greetings! I have reached out to you through the email you have contacted us with the next steps on this issue. Please let us know if you have received it and can follow the steps provided.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Error on partition ""

0 additional answers

Your answer