Microsoft.Graph.ServiceException: Code: ExtensionError - InternalServerError

Question

Microsoft.Graph.ServiceException: Code: ExtensionError - InternalServerError

Kloth, Ralf 1

When deleting (or creating) a subscription for presence notifications sometimes the request takes 25 seconds and we see the error "InternalServerError". The strange thing is that we run this request every 30 minutes and most of the time it runs without problems and sometimes the error (randomly) occurs.
Does anybody know what the problem is? Or how I can analyze the problem?

The exception returned is:
Status Code: InternalServerError
Microsoft.Graph.ServiceException: Code: ExtensionError
Message: Operation: Delete; Exception: [A task was canceled.]
Inner error:
AdditionalData:
date: 2022-12-09T07:00:26
request-id: 90753951-3b87-4ed4-9b34-4b81b76c9333
client-request-id: 90753951-3b87-4ed4-9b34-4b81b76c9333
ClientRequestId: 90753951-3b87-4ed4-9b34-4b81b76c9333

at Microsoft.Graph.HttpProvider.SendAsync(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationToken cancellationToken)
at Microsoft.Graph.BaseRequest.SendRequestAsync(Object serializableObject, CancellationToken cancellationToken, HttpCompletionOption completionOption)
at Microsoft.Graph.BaseRequest.SendAsyncT
at Microsoft.Graph.SubscriptionRequest.DeleteAsync(CancellationToken cancellationToken)
at PresenceHubAboManager.Services.AboManagerService.Run() in C:\work\Source\Repos\AurenzPresenceHub\PresenceHubAboManager\Services\AboManagerService.cs:line 238

In Application Insights the error shows like this (you can see that the request took 25 seconds)!

Nivedipa-MSFT 3,956 Reputation points Microsoft External Staff Moderator

2022-12-12T07:09:47.77+00:00

@Kloth, Ralf - Could you please share your request ID and timestamp to investigate further?
Kloth, Ralf 1 Reputation point

2022-12-12T08:39:45.067+00:00

The request-id and timestamp (is already included in the description above - see: The exception returned is):

date: 2022-12-09T07:00:26
request-id: 90753951-3b87-4ed4-9b34-4b81b76c9333

If you need another (or you meant something different) information please let me know.
Nivedipa-MSFT 3,956 Reputation points Microsoft External Staff Moderator

2022-12-13T08:23:20.557+00:00

@Kloth, Ralf - There is no logs available for this request-id and timestamp. We are checking this with engineering team. We will update you soon.
Kloth, Ralf 1 Reputation point

2022-12-16T06:25:29.287+00:00

Have you been able to figure out what the problem is? - Could you give me an update, please?
Nivedipa-MSFT 3,956 Reputation points Microsoft External Staff Moderator

2022-12-23T12:41:41.997+00:00

@Kloth, Ralf - Apologies for the delay. Engineering team has confirmed that API failed in SubscriptionService. We are checking this with graph webhook engineering team. We will let you know once we get any updates from them.
Nivedipa-MSFT 3,956 Reputation points Microsoft External Staff Moderator

2023-01-09T11:57:46.957+00:00

@Kloth, Ralf - We have raised an ICM for this. We will let you know once we get any updates on it.
Nivedipa-MSFT 3,956 Reputation points Microsoft External Staff Moderator

2023-01-13T06:12:58.1266667+00:00

@Kloth, Ralf - Could you please share the latest client-id and timestamp?
Kloth, Ralf 1 Reputation point

2023-01-23T06:43:28.8333333+00:00
@Nivedipa-MSFT

Note: Because we changed the logic from "delete and create" to "renew", the error does not happen that often.

The last error with http result code 500 was (the request took 5.2 seconds):

request-id: 24594fa3-c8f7-4980-8bf4-82f0d2cd6775

date: 2023-01-12T10:43:06

client-request-id: 24594fa3-c8f7-4980-8bf4-82f0d2cd6775

Note:

We also had a 503 error (this only as a note - maybe it helps). The request took 19.3 seconds.

request-id: c7b0a968-282e-44ae-85e2-1b35bd776a5f

client-request-id: c7b0a968-282e-44ae-85e2-1b35bd776a5f

Date: Mon, 16 Jan 2023 23:30:33 GMT
Nivedipa-MSFT 3,956 Reputation points Microsoft External Staff Moderator

2023-02-08T07:01:16.41+00:00

@Kloth, Ralf - Engineering team is working on the ICM. We will let you know once we get any updates from them.

1 answer

Your answer

Nivedipa-MSFT 3,956 Reputation points Microsoft External Staff Moderator

2022-12-12T07:09:47.77+00:00

@Kloth, Ralf - Could you please share your request ID and timestamp to investigate further?
Kloth, Ralf 1 Reputation point

2022-12-12T08:39:45.067+00:00

The request-id and timestamp (is already included in the description above - see: The exception returned is):

date: 2022-12-09T07:00:26
request-id: 90753951-3b87-4ed4-9b34-4b81b76c9333

If you need another (or you meant something different) information please let me know.
Nivedipa-MSFT 3,956 Reputation points Microsoft External Staff Moderator

2022-12-13T08:23:20.557+00:00

@Kloth, Ralf - There is no logs available for this request-id and timestamp. We are checking this with engineering team. We will update you soon.
Kloth, Ralf 1 Reputation point

2022-12-16T06:25:29.287+00:00

Have you been able to figure out what the problem is? - Could you give me an update, please?
Nivedipa-MSFT 3,956 Reputation points Microsoft External Staff Moderator

2022-12-23T12:41:41.997+00:00

@Kloth, Ralf - Apologies for the delay. Engineering team has confirmed that API failed in SubscriptionService. We are checking this with graph webhook engineering team. We will let you know once we get any updates from them.
Nivedipa-MSFT 3,956 Reputation points Microsoft External Staff Moderator

2023-01-09T11:57:46.957+00:00

@Kloth, Ralf - We have raised an ICM for this. We will let you know once we get any updates on it.
Nivedipa-MSFT 3,956 Reputation points Microsoft External Staff Moderator

2023-01-13T06:12:58.1266667+00:00

@Kloth, Ralf - Could you please share the latest client-id and timestamp?
Kloth, Ralf 1 Reputation point

2023-01-23T06:43:28.8333333+00:00

@Nivedipa-MSFT

Note: Because we changed the logic from "delete and create" to "renew", the error does not happen that often.

The last error with http result code 500 was (the request took 5.2 seconds):

request-id: 24594fa3-c8f7-4980-8bf4-82f0d2cd6775

date: 2023-01-12T10:43:06

client-request-id: 24594fa3-c8f7-4980-8bf4-82f0d2cd6775

Note:

We also had a 503 error (this only as a note - maybe it helps). The request took 19.3 seconds.

request-id: c7b0a968-282e-44ae-85e2-1b35bd776a5f

client-request-id: c7b0a968-282e-44ae-85e2-1b35bd776a5f

Date: Mon, 16 Jan 2023 23:30:33 GMT
Nivedipa-MSFT 3,956 Reputation points Microsoft External Staff Moderator

2023-02-08T07:01:16.41+00:00

@Kloth, Ralf - Engineering team is working on the ICM. We will let you know once we get any updates from them.

Answer 1

HarmeetSingh7172 4,831

Hello @Kloth, Ralf

Looking at the exception details, it seems like there could be a possibility that the actual subscription was originally removed, and notifications are not being sent. Sometimes, subscriptions could be orphaned in the system. For this, we need to wait for the subscription to be removed properly from the system. Also, please note that the "free" azure accounts don't have teams' licenses, one guess that the subscription call will fail with something.

In case if you are still experiencing this issue, I would recommend you to raise a support case with Microsoft Graph, a Support Engineer will be able to assist you better. You can raise support ticket from http://aad.portal.azure.com/ or https://admin.microsoft.com/#/support/requests.

Hope this helps.

If the answer is helpful, please click Accept Answer and kindly upvote. If you have any further questions about this answer, please click Comment.

Kloth, Ralf 1 Reputation point

2023-01-09T08:14:13.083+00:00
Thanks for your comment.

Some notes about it;

We use a paid account, so this should not be the problem.

We first call the list of subscriptions and then delete the subscription. So, when the delete call fails (especially with 500 - "internal server error" - after 25 seconds) this seems to be a bug in MS Graph API. If the subscription does not exist (or something other) I would expect another response (e.g. 404 - "not found").

We changed the handling of the subscription to "extend" the subscription (update the subscription). This is a workaround - as the exception does not happen. But in the end I'm not really satisfied with this and when the exception occurs again I will raise a support ticket with the MS Graph team.

Note: As this is not really a solution for my problem I cannot "accept this as an answer". I'm thankful for that you looked at the problem.

Share via

Microsoft.Graph.ServiceException: Code: ExtensionError - InternalServerError

1 answer

Your answer