Office 365 for exchange integration using c# is suddenly stop working in azure VM RRS feed

  • Question

  • I created one console application in Visual Studio (C#) for fetching emails from ms365office email account and insert to the database.
    In Azure VM i just placed the exe of this application and scheduled the task in windows scheduler. its working perfectly till Yesterday. 
    But now showing the error  below 
    "Microsoft.Exchange.WebServices.Data.ServiceRequestException: The request failed. Unable to connect to the remote server ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
       at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)"

    the error line is  

    GetUserSettingsResponse grResp = ads.GetUserSettings(MSExEmailID, usSetting);

    Please help me on this. Thanks is advance.!

    Tuesday, May 26, 2020 3:13 PM

All replies

  • Hi praveengopinathan,

    Thanks for reaching out. This query seems to be more of networking issue, hence moving it to Azure Networking forum for better visibility and immediate assistance. 

    Thank you

    If a post helps to resolve your issue, please click the "Mark as Answer" of that post and/or click Answered "Vote as helpful" button of that post. By marking a post as Answered and/or Helpful, you help others find the answer faster.

    Tuesday, May 26, 2020 9:57 PM
  • This is a timeout error, and could be occurring for several reasons. This could be an outage on your mail server, or it could be that the port is now blocked. Have there been any changes in your network that could have blocked the port or destination?
    Friday, May 29, 2020 1:52 AM