-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The Autodiscover service couldn't be located #106
Comments
I'm also having the same issue on a new service. Everything works but I keep getting the auto discover error |
We are also facing this issue. Did you find a solution for this? |
If you are getting 401 after specifying the autod url, it's likely a bad password or your exchange server might have limited EWS access for the account you are using. Try:
|
We are having the same issue - after testing with https://testconnectivity.microsoft.com/tests/exo the issue appears to due to Basic Auth being deprecated and disabled in our EWS environment. No option to use OAuth as it looks like: #129 |
Hi Team,
We were using Mail2Bug tool since long time and having an error The Autodiscover service couldn't be located after password change. we had to change the password and since then we couldn't use mail2Bug code due to autodiscover service.
I am able to use same credentials to test the connectivity without issues using the new password. When I run through the code we are getting error as "The Autodiscover service couldn't be located".
I tried to avoid autodiscover call and pass the service URL instead but getting error as UnAuthorized user with 401 code where I am able to login to the service using the same credentials.
Can some one help...!
The text was updated successfully, but these errors were encountered: