You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 18, 2024. It is now read-only.
Good afternoon, I'm seeking some assistance to see if anyone can point me in the correct direction on an issue. Backstory is an agency is using some software that relies on the ews-java-api, it was working fine up until 3ish months ago and has suddenly broke. Since it involves outlook calendar I somehow got to spearhead fixing this though it is not my software nor and issue directly with my groups responsibilities, so I'm the liaison.
Agency has a software that handles scheduling. Currently it works but only sometimes. Below are the error messages and a comment made by the software devs. As far as I'm aware nothing has change with our exchange environment and this is network related. The other issue is in the communication chain early on they stated it was happening to other customers, but then later changed to it just being an issue with us, and that they only use this specific web API for our agency.
I’m seeing an issue with creating appointments in both our local regions and customer regions. Ironically it works in our local dev environments though. My best guess right now is a network issue. These are the errors we are seeing:
Local regions:
[4/6/22 10:13:02:170 EDT] 000000b2 RetryExec I org.apache.http.impl.execchain.RetryExec execute I/O exception (java.net.SocketException) caught when processing request to {s}->https://outlook.office365.com:443: Connection reset
Customer regions:
[4/6/22 7:45:45:466 CDT] 000000b8 RetryExec I org.apache.http.impl.execchain.RetryExec execute I/O exception (java.net.SocketException) caught when processing request to {s}->https://outlook.office365.com:443: Invalid argument (Read failed)
Techs thoughts:
This appears to be an issue with MS failover to a secondary ip.
[4/6/22 7:45:45:466 CDT] 000000b8 RetryExec I org.apache.http.impl.execchain.RetryExec execute I/O exception (java.net.SocketException) caught when processing request to {s}->https://outlook.office365.com:443: Invalid argument (Read failed)
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Good afternoon, I'm seeking some assistance to see if anyone can point me in the correct direction on an issue. Backstory is an agency is using some software that relies on the ews-java-api, it was working fine up until 3ish months ago and has suddenly broke. Since it involves outlook calendar I somehow got to spearhead fixing this though it is not my software nor and issue directly with my groups responsibilities, so I'm the liaison.
Agency has a software that handles scheduling. Currently it works but only sometimes. Below are the error messages and a comment made by the software devs. As far as I'm aware nothing has change with our exchange environment and this is network related. The other issue is in the communication chain early on they stated it was happening to other customers, but then later changed to it just being an issue with us, and that they only use this specific web API for our agency.
I’m seeing an issue with creating appointments in both our local regions and customer regions. Ironically it works in our local dev environments though. My best guess right now is a network issue. These are the errors we are seeing:
Local regions:
[4/6/22 10:13:02:170 EDT] 000000b2 RetryExec I org.apache.http.impl.execchain.RetryExec execute I/O exception (java.net.SocketException) caught when processing request to {s}->https://outlook.office365.com:443: Connection reset
Customer regions:
[4/6/22 7:45:45:466 CDT] 000000b8 RetryExec I org.apache.http.impl.execchain.RetryExec execute I/O exception (java.net.SocketException) caught when processing request to {s}->https://outlook.office365.com:443: Invalid argument (Read failed)
Techs thoughts:
This appears to be an issue with MS failover to a secondary ip.
[4/6/22 7:45:45:466 CDT] 000000b8 RetryExec I org.apache.http.impl.execchain.RetryExec execute I/O exception (java.net.SocketException) caught when processing request to {s}->https://outlook.office365.com:443: Invalid argument (Read failed)
The text was updated successfully, but these errors were encountered: