Web Services fail after Installing Exchange 2013 CU2.


After working on an Exchange server for six hours or so, it starts to blur together. If you experience any connection issues with Exchange 2013 Client Access servers (CAS) after installing CU2 then you may be interested in this issue.

In this circumstance, you may find the Proxy logs show that connections to the CAS work and the CAS sends information to the Mailbox server. However, the Mailbox server is not effectively allowing the CAS server to access the database. In my experience mail still got to the mailbox server but that was about it. OWA was notably not working and other communication to the mailbox server we not occurring.  Basically web services do not work. Run this command and…. I hope this helps

Set-MailboxServer -Identity {server name} -DatabaseCopyAutoActivationPolicy:unrestricted


This is not supposed to be set by default, but may be as a result of upgrading to CU2 from CU1.

3 thoughts on “Web Services fail after Installing Exchange 2013 CU2.

  1. I’ve read a few good stuff here. Definitely worth bookmarking for revisiting.

    I wonder how a lot attempt you set to create one of
    these great informative site.


  2. Thanks for the auspicious writeup. It if truth be told used to be
    a entertainment account it. Glance complex to more introduced agreeable from you!
    By the way, how could we be in contact?


  3. I read this paragraph completely concerning the resemblance of newest and preceding technologies, it’s awesome article.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s