Open LauranceOrLaurent opened 1 week ago
Thanks for raising this @LauranceOrLaurent
Are you able to share the following to help us understand the issue better?
logs of the errors reported of the client
The call is like this:
deltaEvents = await GraphServiceClient.Users[userMailAddress].Calendar.Events.Delta.GetAsync(delegate (RequestConfiguration
_deltaEvents = null on Server 2019, _deltaEvents is ok filled in Windows 10
version of the Graph SDK being used(does this error happen with the latest version)
sample code of how you are intializing the GraphClient
Tested on two different server 2019. So the problem ist not related to a specific server installation.
Any Idea?
I'm not sure what could be wrong here. Any chance you can try adding a responseHandler option to the request as shown in the example here to get the raw native response object?
I would then try to log the properties(headers, status code and content values) of the response object to see if indeed the API is returning a meaningful response here to isolate where the problem could be.
I did that with: https://github.com/microsoftgraph/msgraph-sdk-dotnet/blob/dev/docs/upgrade-to-v5.md#native-response-object
As I described before: The Response is also still NULL after 1 minute. No exceptions. Looks like MSGraph.dll can not work/send on Server 2019.
Did you try this on Server 2019 and it worked?
So:
The program works well on Windows 10 (in all aspects!)
The program is not working from Windows Server 2019 o More detailed: The request via the MS.Graph.dll results in an unspecified http-request exception (after about 1 minute). o I have build in the same request as raw http-request and that works perfect (on Windows 10 and Server 2019)
We have already excluded following issues on the Server: o Internet/Porxy access (I can do requests from e.g. POSTMAN to the Graph-Rest-Service, that works as expected) o .net Framework 4.8 and dotnet 8 is installed and works o Authentication works, access token is valid and works an both Platforms (Windows 10 and Server 2019)
The remaining component therefore seems to be between Server 2019 and the dotnet MS.Graph.dll library(s). Something on the Server prevents the work of MS.Graph.dll's