Microsoft graph .Net error OAuth2 in windows server to access mailbox - WINHTTP_CALLBACK_STATUS_REQUEST_ERROR

Question

Microsoft graph .Net error OAuth2 in windows server to access mailbox - WINHTTP_CALLBACK_STATUS_REQUEST_ERROR

AMRUTH KARANTH 31

I have an application using microsoft graph to access mailbox. it works on dev machine with windows 10.
In the server, i am getting the error given below. (windows server 2016 and windows server 2012)

"System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.Http.WinHttpException: Error 12002 calling WINHTTP_CALLBACK_STATUS_REQUEST_ERROR, 'The operation timed out'."

detailed error

Status Code: 0
Microsoft.Graph.ServiceException: Code: generalException
Message: An error occurred sending the request.
---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.Http.WinHttpException: Error 12002 calling WINHTTP_CALLBACK_STATUS_REQUEST_ERROR, 'The operation timed out'.
at System.Threading.Tasks.RendezvousAwaitable1.GetResult() at System.Net.Http.WinHttpHandler.<StartRequestAsync>d__122.MoveNext() --- End of inner exception stack trace --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Graph.RedirectHandler.<SendAsync>d__6.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Graph.RetryHandler.<SendAsync>d__9.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Graph.CompressionHandler.<SendAsync>d__2.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Graph.AuthenticationHandler.<SendAsync>d__16.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Graph.HttpProvider.<SendRequestAsync>d__19.MoveNext() --- End of inner exception stack trace --- at Microsoft.Graph.HttpProvider.<SendRequestAsync>d__19.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Graph.HttpProvider.<SendAsync>d__18.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Graph.BaseRequest.<SendRequestAsync>d__40.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Graph.BaseRequest.<SendAsync>d__341.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Graph.MailFolderMessagesCollectionRequest.<GetAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()

David Kennerley 30 Reputation points

2023-12-15T13:10:46.79+00:00

Did anyone figure out the cause of this?
Andrew Teece 1 Reputation point

2023-12-15T13:17:12.3166667+00:00

@David Kennerley In our scenario we got this as a new error when upgrading from an old .net Graph SDK, and then only on 1 particular server.

We found the root cause to be that the older SDK version ignored the machine-wide proxy setup, but the newer SDK (correctly) followed the configuration.

And in our case the proxy configuration was wrong, a throwback to a previous configuration that until now had gone unused and un-noticed.

The easy check was to run "netsh winhttp show proxy" from the command prompt.
Anonymous

2023-12-15T13:28:24.26+00:00
The error message you provided indicates that there is a timeout issue when sending a request to Microsoft Graph API. The error code "12002" typically points to a timeout in the communication between your application and the server.

Here are some steps you can take to troubleshoot and resolve this issue:

Check Network Connectivity:

Ensure that the server has proper network connectivity and can reach the Microsoft Graph API endpoint. Check for any network issues, firewalls, or proxies that might be causing the timeout.

Firewall and Proxy Settings:

Verify that the firewall and proxy settings on the server allow outgoing connections to the Microsoft Graph API endpoint. Ensure that there are no restrictions that might cause timeouts.

DNS Resolution:

Confirm that the server can resolve the Microsoft Graph API endpoint's DNS properly. Check DNS settings and try pinging the Graph API endpoint from the server.

Server Time Synchronization:

Make sure that the server's system clock is synchronized with a reliable time source. Time discrepancies can sometimes cause authentication and communication issues.

Increase Timeout Values:

Depending on your application framework, you may be able to adjust timeout values for HTTP requests. Consider increasing the timeout duration to see if it resolves the issue. However, be cautious with this approach, as it might mask underlying problems.

Update Libraries and Dependencies:

Ensure that you are using the latest version of the Microsoft Graph API library and any related dependencies in your application. There might be improvements or bug fixes in newer releases.

Logging and Monitoring:

Implement detailed logging in your application to capture additional information about the requests and responses. This can help identify patterns or specific endpoints causing the timeout.

Test from Another Environment:

If possible, test your application from another environment or machine to see if the issue persists. This can help determine if the problem is specific to the server configuration.

Contact Microsoft Support:

If the issue persists after trying the above steps, consider reaching out to Microsoft Support for assistance. They can provide insights into any known issues or specific configurations related to Microsoft Graph API.

Remember to make changes cautiously, especially when adjusting timeout values or firewall settings, and consider the security implications of any modifications.