Outlook Out Of Office Reply - Error

do you have your activesync published in DNS? because if it is not that can cause the issue.

sorry it was not activesync it should have been autodiscovery  see the link below

http://social.technet.microsoft.com/Forums/exchange/en-US/e27c4dcc-f19e-496b-972e-de347c00df21/ms-outlook-error-your-automatic-reply-settings-cannot-be-displayed-because-the-server-is-currently?forum=exchangesvrgenerallegacy

disabled IPv6 on nontunnel interfaces

and also try this one
Did you by chance go down this road...? Ensuring you have the necessary SRV record in your external DNS zone?

http://support.microsoft.com/kb/940881

Which version of Outlook are you using?  If 2013 there is a known issue with some updates that have caused the Autodiscover service to stop working -- which is what gives this exact error message.

See this article for detailed info:
http://www.infoworld.com/t/microsoft-windows/botched-outlook-2013-patches-kb-2837618-and-kb-2837643-break-out-of-office-reply-freebusy-and-more-232055

Removing those updates should fix the problem for you.

Md. Mojahid,
I did what you said, I disabled IPv6 on nontunnel interface and now I am having huge issues. It takes 45 minutes to an hour for my server to come up after reboot, My Exchange services won't start, my services.msc, and network connections won't open. There is an X next to my network connection in the system tray. When I try to open it, it freezes.

There is no System Restore, it is Windows 2008 SBS. I tried following the instructions on this link to get it back but no cigar - please help!!! http://blogs.technet.com/b/sbs/archive/2008/10/24/issues-after-disabling-ipv6-on-your-nic-on-sbs-2008.aspx

Ok, I figured it out. Exchange/server is back to normal. That scared the shit out of me. Was up all night. Anyways, back to square one.

Jeffrey, most people do not use Outlook 2013. But I will look into this as that is what I have been using for testing in this scenario.

I've requested that this question be deleted for the following reason:

No one has been answering.  I still have the issue. I know issue is with IIS but I cannot figure it out. Resolutions here didn't work.

So, I'm sorry that I missed your last postings.  But I do believe I may have the solution for you.

Check out this article:
http://www.petenetlive.com/KB/Article/0000897.htm

Essentially it points to EITHER having a proxy server configured on the client workstations, OR incorrect Virtual Folder Permissions.

Hi Jeffrey,
Thanks for your response. I tried the IIS option. I checked the proxy and that is not the issue. The link you sent seems pretty straightforward. I did get stuck somewhere though. Some virtual directories are managed through the EMC and I cannot find where they are in the EMC. The Virtual Directories I had trouble with are "Exchange" and "Exchweb". Both of those have Windows Authentication method disabled and I need to enable them. I just don't know where to do that in the EMC.

Thanks again, I appreciate your help.

Did you do the "Test Email AutoConfiguration" on the workstation?

You definitely need to be sure that AutoDiscover is working internally.

Oh, and to enable Windows Authentication for the Virtual Directories?  That's done in IIS, not EMC.

As the article states:

"Another common problem, is that the EWS virtual directory has misconfigured permissions in IIS."

And then it goes on to show you specifically where to change it in IIS.

Hi Jeffrey,

1. Yes, I did the Test AutoConfiguration and it failed.
2. The only virtual directories I am having issues with are "Exchange" and "Exchweb". When I try to enable Windows Authentication for both of them I get an error message, which I attached here.

Thanks for your help.
iiserror.JPG

This has nothing at all to do with the Exchange and Exchweb virtual directories.  You shouldn't even be touching those.

The issue is caused by problems with the EWS virtual directory.

Furthermore, the Exchange and Exchweb directories are irrelevant to your environment.  They are only there to assist with migrations from Exchange 2003, as 2007 and later uses the OWA directory instead.

Settings for THAT directory (OWA) should not be made in IIS, but rather in the Exchange Management Console >  Server Config > Client Access > Outlook Web Access > OWA (SBS Web Applications) > properties

The fact that your AutoConfiguration Test failed is the root of the problem.  It has to do with DNS, so don't monkey with any of the permissions settings -- that's not going to help you.

You should essentially be able to access the following URL from INSIDE your network:
https://remote.yourdomain.com/ews/exchange.asmx

(unless you specified something other than the default "remote" when you set up your domain name)

If you cannot resolve this URL internally then you need to run the following wizards in your SBS Console > Network > Connectivity Tab:

Set up your Internet Address Wizard
and then run the
Fix My Network wizard

These will resolve most all of your issues by rewriting the appropriate entries to DNS.

Jeffrey,
I was able to access https://remote.yourdomain.com/ews/exchange.asmx from within my network, it redirects me to a services.wsdl page full of xml. This server is also a DNS server. It has DNS forwarders to OpenDNS IPs. Everything else looks normal. Still having the issue with Out of Office opening on Outlook client.

Thanks

I ran the Microsoft Analyzer tool which had a bunch of errors. I attached it here, I don't fully understand it to use it as direction for what to do next. Can you "decipher" it?

Thanks!!

I see that no one has responded for quite a few days.  There is no file attached to your last post, so nothing to analyze.  If you want someone to look at it, please post the file.

Just as an offhand comment, I would advise removing the DNS forwarders and use the root hints only.  If this problem is DNS-related, this should resolve any issues in that regard.  Also, as advised by Jeffrey Kane, you should rerun the wizards to make sure that the SBS settings for your domain are applied correctly.

Please upload the file.

Furthermore, NEVER disable IPv6 unless there a specific Microsoft based KB that shows to disable it (and you disable it through the registry). You will most likely break a lot of things by unchecking the IPv6 checkbox... mainly the TCP/IP stack.

Hypercat/Adam,
Thanks for your response. I actually thought I uploaded it. It is attached now.

-eshiram
exchangeconnectivitytest.pdf

This test was done externally right?  Is this the normal situation when users are having a problem contacting your server, or are they having problems internally as well?

There are some autodiscover errors as well as a problem with your SSL certificate.  First thing I'd check is to see if your SSL certificate is missing or invalid.  Is the server using a self-signed or public certificate?

As for the autodiscover errors, the error message states that the domain is non-existent. Since you were doing this test as a remote test, then it appears that your public DNS zone doesn't have an autodiscover record for your domain.

yes it was done externally. problems happen internally and externally.

my public dns zone has an srv record for autodiscover. when i go to owa outside it does not give me an SSL error. SSL is through GoDaddy.

Run the following:

Get-ExchangeCertificate | FL

Let us know the output, I dont think something is right here.

Ok, I ran the command and attached it here. I replaced my primary domain, secondary domain, hostname, and company name with domain, secondarydomain, hostname, and Full Company Name - respectively. I know that information is usually concealed in these forums so I am just following suit.

Thanks for helping,
Cert.txt

First thing - you have many certificates that are assigned to the various Exchange services that are invalid/expired.  I can see that your GoDaddy certificate is correctly assigned to all Exchange services (IMAP, POP, SMTP and IIS).  I would remove any other certificates that are expired, and also remove the self-signed certificate (thumbprint 6A685515F3281FFA0EE72CCCFA35A1ABAD4CD16F) that is assigned to the POP and SMTP services. That one is valid, and you don't want to delete it completely, but just un-assign to from the Exchange services.

Hypercat,
I can delete the expired ones and disable the self-signed? Is the following command the right way to unassign the cert?

Remove-ExchangeCertificate -Thumbprint 6A685515F3281FFA0EE72CCCFA35A1ABAD4CD16F

Thanks!!

No - you want to use Enable-ExchangeCertificate:

Enable-ExchangeCertificate -Server Servername -Services ""  -Thumbprint [your thumbprint]

I think this will work to leave the certificate in place but remove any assigned services. If it doesn't work (I haven't tested it), then you can use the Remove-ExchangeCertificate, which will actually delete the certificate but that shouldn't cause any problems.

Hypercast,
I tried enable first but it didn't work. It said this certificate doesn't apply to Exchange - even though I was removing services. I did remove also but it messed things up so I readded it.

I have only seen this error if the user is in an older database than the main server.

Let's say if your user is in a 2010 mailbox server and your CAS server is a 2013.

Moving the mailbox to the latest server should do the trick.

Also, someone reported once that outlook 2003 will have issues if not fully updated and 2007 too.

I had a friend help me with this. I am not sure what he did exactly. I know he did some troubleshooting with SBS console wizards that helped lead him to his solution.