Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Technical Question] HttpClientHelper error code 400030 #3436

Closed
Pabzt opened this issue Feb 27, 2024 · 3 comments
Closed

[Technical Question] HttpClientHelper error code 400030 #3436

Pabzt opened this issue Feb 27, 2024 · 3 comments
Labels
question Further information is requested.

Comments

@Pabzt
Copy link

Pabzt commented Feb 27, 2024

We ran into this exception when trying to get device twins from our IoT-Hub. If we retry the call a few minutes later it just works fine. I could not manage to find any documentation of the following error code and what to do about it:

"System.ArgumentException":
{
"Message":
{
"errorCode":400030,
"message":"400",
"trackingId":"FC7347D22C034F439FE952810E759C0D-G2:-TimeStamp:2024-02-27T17:27:48.272248437+00:00",
"timestampUtc":"2024-02-27T17:27:48.272248437+00:00",
"info":null
}, "ExceptionMessage":""
}
at Microsoft.Azure.Devices.HttpClientHelper.ExecuteAsync(HttpClient httpClient, HttpMethod httpMethod, Uri requestUri, Func3 modifyRequestMessageAsync, Func2 isMappedToException, Func3 processResponseMessageAsync, IDictionary2 errorMappingOverrides, CancellationToken cancellationToken)

We have not changed the implementation in a year or so and never had this issues before and now we had it twice in 10 days. We are using the latest version of Microsoft.Azure.Devices

@Pabzt Pabzt added the question Further information is requested. label Feb 27, 2024
@Pabzt
Copy link
Author

Pabzt commented Mar 10, 2024

We got this again today. I want to know what it is. Please explain what is doing on that causes this error.

@abhipsaMisra
Copy link
Member

The tracking ID accompanying the exception message indicates that this error is being returned by the service. I'd recommend reaching out to the IoT Hub service team with the tracking ID; they'd be able to help you debug this issue.

@timtay-microsoft
Copy link
Member

Closing this thread since this is probably a service bug and not an SDK bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested.
Projects
None yet
Development

No branches or pull requests

3 participants