microsoftgraph / microsoftgraph/microsoft-graph-comms-samples

RemoteMediaSample Failing During Execution

Open
#308 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
253
Forks
275
Avg merge
1d 5h
Merged PRs (30d)
1

Description

I have the RemoteMediaSample deployed.

The sample calls the first attendee in list but then fails:

The first attendee gets promoted to join, joins the meeting but the hears nothing. Of course the code has already failed by then.

The code failing is a blackbox:
** var statefulCall = await this.Client.Calls().AddAsync(call, scenarioId: scenarioId).ConfigureAwait(false);
**

Our JSON being posted to the Incident services is:
**{
"name": "OOPS2",
"time": "2009-06-15T13:45:30",

"tenantId": "1c0ccdda-a992-4767-b5e4-c019b06d5ecb",
"objectIds": [
    "{a96ba647-5d8c-42c3-83e4-894b7c2467d7}",
    "{5561c52e-a854-44b2-9baf-d797b8f99958}"
],

"joinURL": "https://teams.microsoft.com/l/meetup-join/19%3a4e7f52e4aad54ef28c650b9435475547%40thread.skype/1597417291530?context=%7b%22Tid%22%3a%221c0ccdda-a992-4767-b5e4-c019b06d5ecb%22%2c%22Oid%22%3a%22a96ba647-5d8c-42c3-83e4-894b7c2467d7%22%7d",
"removeFromDefaultRoutingGroup": true,
"allowConversationWithoutHost": true

}**

What are we missing?

Status Code: InternalServerError
Microsoft.Graph.Communications.Core.Exceptions.ServiceException: Code: 9999
Message: Unkown internal Server Error.
Scenario Id: efec6d49-ba67-49a5-a9af-613167c64e54
Inner error:
AdditionalData:
date: 2020-08-14T15:10:09
request-id: 5491fdbc-6e41-41b4-a074-aa4554978cb4
---> Microsoft.Graph.Communications.Core.Exceptions.ServiceException: Code: 9999
Message: Unkown internal Server Error.
Inner error:
AdditionalData:
date: 2020-08-14T15:10:09
request-id: 5491fdbc-6e41-41b4-a074-aa4554978cb4

at Microsoft.Graph.Communications.Client.Transport.GraphAuthClient.d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Graph.Communications.Client.Transport.GraphAuthClient.d__42.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Graph.Communications.Client.Transport.GraphClientWrapper.<ValidateAndWrapAsync>d__121.MoveNext()
--- End of inner exception stack trace ---
at Microsoft.Graph.Communications.Client.Transport.GraphClientWrapper.d__121.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Graph.Communications.Client.Transport.GraphClientWrapper.<SendAsync>d__112.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Graph.Communications.Resources.StatefulResourceCollection4.<GenerateEntityAsync>d__26.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Graph.Communications.Calls.StatefulCallCollection.<GenerateEntityAsync>d__9.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Graph.Communications.Resources.StatefulResourceCollection4.d__31.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Graph.Communications.Resources.StatefulResourceCollection4.<GenerateStatefulResourceAsync>d__22.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1.ConfiguredTaskAwaiter.GetResult()
at Sample.IncidentBot.Bot.Bot.d__29.MoveNext() in C:\Projects\Samples\V1.0Samples\RemoteMediaSamples\IncidentBot\Bot\Bot.cs:line 342
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1.ConfiguredTaskAwaiter.GetResult() at Sample.IncidentBot.Bot.Bot.<RaiseIncidentAsync>d__27.MoveNext() in C:\Projects\Samples\V1.0Samples\RemoteMediaSamples\IncidentBot\Bot\Bot.cs:line 222 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1.ConfiguredTaskAwaiter.GetResult()

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at Sample.IncidentBot/Bot/Bot.cs lines 342 and 222, then trace the Calls().AddAsync call and the incident JSON shown in the report. Reproduce the failure using the recorded scenario ID and request ID, and compare the request with the service requirements. Done means the missing cause or required input is identified and the sample call no longer returns the internal-server error.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.