Outlook 2010 Out of Office 'Server Currently Unavailable'
Hi,
We've been have a problem with a few of our users whereby they cannot set their Out of Office via Outlook - it's working via Outlook Web App. Our Exchange version is 2010.
The following message appears:
"Your automatic reply settings cannot be displayed, because the server is currently unavailable: try again later"
We have tried re-creating outlook profiles, but to no avail. Also might be worth nothing that my profile which is fine, on one of the client machines in question, when configured for outlook, will also bring up this error message.
I believe I have correctly checked/created the autodiscover internal and external urls in the exchange management shell as many people suggest - Please note we have been in this environment with Exchange 2010 for over a year, with this problem not having been present until last week.
Interestingly, in IIS Manager (7.0), under the default website (on the Exchange Server) - which hosts EWS, Autodiscover, etc, when I change the Application Pools .NET Framework version from 2.0 to 4.0, it stops working on mine too, and also when I changed 'Enable 32-bit applications' to TRUE from FALSE ; the only combination of these which limits the error to the select few is .NET 2.0 and FALSE.
I've exhausted the articles out there, and suggestions would be much appreciated!
Many Thanks,
Kevin
We've been have a problem with a few of our users whereby they cannot set their Out of Office via Outlook - it's working via Outlook Web App. Our Exchange version is 2010.
The following message appears:
"Your automatic reply settings cannot be displayed, because the server is currently unavailable: try again later"
We have tried re-creating outlook profiles, but to no avail. Also might be worth nothing that my profile which is fine, on one of the client machines in question, when configured for outlook, will also bring up this error message.
I believe I have correctly checked/created the autodiscover internal and external urls in the exchange management shell as many people suggest - Please note we have been in this environment with Exchange 2010 for over a year, with this problem not having been present until last week.
Interestingly, in IIS Manager (7.0), under the default website (on the Exchange Server) - which hosts EWS, Autodiscover, etc, when I change the Application Pools .NET Framework version from 2.0 to 4.0, it stops working on mine too, and also when I changed 'Enable 32-bit applications' to TRUE from FALSE ; the only combination of these which limits the error to the select few is .NET 2.0 and FALSE.
I've exhausted the articles out there, and suggestions would be much appreciated!
Many Thanks,
Kevin
ASKER
Hi chestor2,
Testing Exchange Connectivity for autodiscover fails on all addresses, please advise!
Regards,
Kevin
Testing Exchange Connectivity for autodiscover fails on all addresses, please advise!
Regards,
Kevin
ASKER
Hi vijayhackers,
1. How could this happen? I haven't modified the settings on the exchange and/or any user accounts in AD or Exchange 2010.
2. It all resolves internally, what should I be looking for in terms of configuration?
3. How can I verify the certificate, also, it's probably 5 of 200+ users having this issue.
4. Anonymous Authentication is enabled across the board, with the except of OWA which has Basic Authentication enabled only in IIs, should I change this?
Many Thanks,
Kevin
1. How could this happen? I haven't modified the settings on the exchange and/or any user accounts in AD or Exchange 2010.
2. It all resolves internally, what should I be looking for in terms of configuration?
3. How can I verify the certificate, also, it's probably 5 of 200+ users having this issue.
4. Anonymous Authentication is enabled across the board, with the except of OWA which has Basic Authentication enabled only in IIs, should I change this?
Many Thanks,
Kevin
ASKER
Please see attached results from Autodiscover in Outlook Icon > Test Email Auto-Configuration with only 'Autodiscover' ticked (in the log).
The left result is from my pc, a working Out of Office, and the other is from my colleagues pc in identical circumstances (policies, versions, updates etc).
I Hope this helps in some way also.
Regards,
Kevin
AutoDiscover.gif
The left result is from my pc, a working Out of Office, and the other is from my colleagues pc in identical circumstances (policies, versions, updates etc).
I Hope this helps in some way also.
Regards,
Kevin
AutoDiscover.gif
have you created the DNS record for the Autodiscover? Also is it included in the Exchange certificate?
Did you configure an autodiscover ?
http://www.jaapwesselius.com/2012/04/12/exchange-2010-and-autodiscover-part-i/
http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/exchange-autodiscover.html
http://technet.microsoft.com/en-us/library/aa995956%28v=exchg.141%29.aspx
http://www.jaapwesselius.com/2012/04/12/exchange-2010-and-autodiscover-part-i/
http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/exchange-autodiscover.html
http://technet.microsoft.com/en-us/library/aa995956%28v=exchg.141%29.aspx
ASKER
@systechadmin
Apologies for not making clear the circumstances of this error: please note this has never been a problem in the 18months we have been on Exchange 2010 since migrating, hence yes there is an autodiscover DNS record present.
How can I check the Exchange Certificate for this?
@Chestor2
As with systechadmin I imagine I confused the matter by implying this was a fresh install? None of the configuration has been knowingly changed. The .NET Framework update is the only tangible change here
Many Thanks,
Kevin
Apologies for not making clear the circumstances of this error: please note this has never been a problem in the 18months we have been on Exchange 2010 since migrating, hence yes there is an autodiscover DNS record present.
How can I check the Exchange Certificate for this?
@Chestor2
As with systechadmin I imagine I confused the matter by implying this was a fresh install? None of the configuration has been knowingly changed. The .NET Framework update is the only tangible change here
Many Thanks,
Kevin
Open the OWA you can check the certificate from there. Also check if Application Pool for Autodiscover service is not crashed in IIS
You need to configure Autodiscover!
Follow those instructions:
http://www.jaapwesselius.com/2012/04/12/exchange-2010-and-autodiscover-part-i/
http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/exchange-autodiscover.html
http://technet.microsoft.com/en-us/library/aa995956%28v=exchg.141%29.aspx
Firstly you must add DNS A-record (autodiscover.domain.com) to your CAS Array or Server.
Then you must add to CAS server information about autodiscover service (Set-ClientAccessServer -Identity "CAS-01" -AutoDiscoverServiceIntern
http://technet.microsoft.com/ru-ru/library/bb125157%28v=exchg.150%29.aspx
Follow those instructions:
http://www.jaapwesselius.com/2012/04/12/exchange-2010-and-autodiscover-part-i/
http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/exchange-autodiscover.html
http://technet.microsoft.com/en-us/library/aa995956%28v=exchg.141%29.aspx
Firstly you must add DNS A-record (autodiscover.domain.com) to your CAS Array or Server.
Then you must add to CAS server information about autodiscover service (Set-ClientAccessServer -Identity "CAS-01" -AutoDiscoverServiceIntern
http://technet.microsoft.com/ru-ru/library/bb125157%28v=exchg.150%29.aspx
ASKER
@systechadmin
Application Pools working OK (restarted also to make sure) and OWA certificate is correct too, no difference between the functioning and non-functioning PCs.
@Chestor2
More than happy to try this, just wanted to confirm that this solution would be applicable if only 5% of PCs/Users had a problem?
Regards,
Kevin
Application Pools working OK (restarted also to make sure) and OWA certificate is correct too, no difference between the functioning and non-functioning PCs.
@Chestor2
More than happy to try this, just wanted to confirm that this solution would be applicable if only 5% of PCs/Users had a problem?
Regards,
Kevin
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Internal and External OWA URLs, as well as autodiscover entries added to Proxy Exceptions (in this case a wpad.dat file that was newly implemented)
I found several solutions:
http://social.technet.microsoft.com/Forums/exchange/en-US/94c5828f-07ab-4646-a551-6c4cf868d2d9/exchange-2010-out-of-office-error
http://social.technet.microsoft.com/Forums/exchange/en-US/1b9b50b5-6622-461d-80b6-a36b909403c1/exchange-2010-out-of-office-assistant-not-working
http://www.slipstick.com/exchange/cmdlets/out-of-office-doesnt-work-with-exchange-2007-or-2010/
Did you check Exchange connectivity by https://www.testexchangeconnectivity.com ?