This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(44.800000000000004, 9%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EN%3C/text%3E%3C/svg%3E)
We installed Exchange Server 2013 CU23 on our server. It got to a screen to install server roles and wouldn't let us advance, but we rebooted and verified that the new version was running.
After having done this, messages are getting through. But when a user tries to set Automatic Replies, it just says "Your automatic reply settings cannot be displayed because the server is currently unavailable." ECP works, but OWA gives a generic "Something went wrong" error whenever I try to access it.
We tried restarting IIS and that didn't fix the problem. We made sure that all the Exchange services were running and component states set to Active, but it still wouldn't work. We even tried reverting to an older SSL cert, as that had tripped us up in the CU install, but the same errors happened. BinSearchFolder is pointing to the correct place in our install.
It was suggested to me that we could try using UpdateCas.ps1, but this didn't fix it.
I found that Forms Authentication had been enabled in IIS. I disabled this for Default Web Site and automatic replies are now working again. OWA is still giving errors.
Hi @Nicholas94 ,
Appreciate your sharing and reply.
Since you could solve your OOF issue by change the Authentication settings, will your OWA login issue be related to your Authentication settings as well? It is suggested for you to checked the Authentication settings of your Owa virtualdirectory and see if there is any difference.
Here are my Owa virtualdirectory Authentication settings in my Exchange 2013 CU23, for your reference:
Settings in IIS:
Settings in EMS:
Hope this can be helpful.
The authentication settings are the same as those and it's giving the error.
I tried enabling Anonymous Authentication for OWA, as this is enabled for ECP, but that resulted in 'You do not have permission' errors and didn't even show the login page.
At one point did it fail? what was the error in the setup logs?
Are all the services started and server components active?
Test-Servicehealth
Get-ServerComponentState -Identity Mailbox01
This is what happens when I run Test-ServiceHealth:
Role : Mailbox Server Role
RequiredServicesRunning : True
ServicesRunning : {IISAdmin, MSExchangeADTopology, MSExchangeDelivery, MSExchangeIS,
MSExchangeMailboxAssistants, MSExchangeRepl, MSExchangeRPC, MSExchangeServiceHost,
MSExchangeSubmission, MSExchangeThrottling, MSExchangeTransportLogSearch, W3Svc, WinRM}
ServicesNotRunning : {}
Role : Client Access Server Role
RequiredServicesRunning : True
ServicesRunning : {IISAdmin, MSExchangeADTopology, MSExchangeIMAP4, MSExchangeMailboxReplication,
MSExchangePOP3, MSExchangeRPC, MSExchangeServiceHost, W3Svc, WinRM}
ServicesNotRunning : {}
Role : Unified Messaging Server Role
RequiredServicesRunning : True
ServicesRunning : {IISAdmin, MSExchangeADTopology, MSExchangeServiceHost, MSExchangeUM, W3Svc, WinRM}
ServicesNotRunning : {}
Role : Hub Transport Server Role
RequiredServicesRunning : True
ServicesRunning : {IISAdmin, MSExchangeADTopology, MSExchangeEdgeSync, MSExchangeServiceHost,
MSExchangeTransport, MSExchangeTransportLogSearch, W3Svc, WinRM}
ServicesNotRunning : {}
As I mentioned, all component states are Active.
Sorry, missed that
where did it fail?
What do you mean by 'were did it fail'?
You said:
t got to a screen to install server roles and wouldn't let us advance,
What do the Exchange setup logs shows?
I've attached the log for that stage119952-cu23-log.txt
According to the logs, CU23 was already installed: The locally installed version is 15.0.1497.2.
Hi @Nicholas94 ,
OWA gives a generic "Something went wrong" error whenever I try to access it.
I did some research about the error message you offered and there were much similar errors. Would you mind providing us with the full detailed error information so that we can conduct further research about that?
Besides, are there any event errors in your Event Viewer?
Please try the steps in the article which Andy mentioned above and see if the issue would have any difference. Any update, please feel free to post back.
SharedWebConfig.config is in both folders.
Here's an example of an OWA error from the logs: 120018-owa-error.txt
I had to restart the installer multiple times when I encountered errors such as the SSL one I mentioned. Here are the complete logs: 120102-cu23-log-a.txt120096-cu23-log-b.txt120065-cu23-log-c.txt
I tried rebooting the server, but the same error happens.
I tried regenerating those files and restarting IIS, but it's still not fixed.
Hi @Nicholas94 ,
Thanks for your reply.
Can the Availability Service(free/busy) feature work fine now? In order to confirm if your issue is related to your Autodiscover or EWS, please try the "Test Email Autoconfiguration" tool in Outlook desktop client and see if the OOF URL in the test result is the same as the URL you set in the EWS virtual directories on EAC. You can also try visiting the OOF URL you get in browser and see if you can get the proper results.
The OOF URL is the same as the EWS virtual direcotry. This has 'Proxy endpoint' set to disabled. When I navigate to the URL, it gives a 404 error for /login.aspx.
Hi @Nicholas94 ,
Thanks for your reply.
I tried to detailed review all the information we have collected above, it's not hard to refer that your issue might indeed be related to your reboot behavior when updating. There are so many errors related to missing files or services in your log files, like .NET service, Microsoft Exchange Search Host Controller service, Microsoft.Exchange.Core.Strings and many other missing .dll files. It is conceivable that this will be a very large and complicated project to repair them and that should be a hard work.
Have you ever created a restore point before? If yes, it would be more suggested for you to recover your system from your back up. Or you could try to migrate all your mailbox to anther Exchange server which can save your time as much as possible.
I believe the missing file is /FrontEnd/HttpProxy/EWS/login.aspx. I re-downloaded the installer and it wasn't there when I extracted it. We have a snapshot from before installing CU23 that we can revert to and see if the file is there, but I'm wary of doing this as it might have compatibility issues.
Hi @Nicholas94 ,
I have a work-fine test environment Exchange 2013 CU23 and I checked the files under the path like below:
There indeed no such files under the path and seems the login.aspx file you mentioned might not be the key point of your issue.
Besides, may I know which kind of compatibility issues are you concerning about here? Compatibility between the newly prepared AD Schema and the restored old Exchange version? Or something else?
For your concerns about compatibility between the newly prepared AD Schema and the restored old Exchange version, you might could first check if there is any changes from your previous version to the CU23 version: Exchange 2013 Active Directory schema changes.
By the way, based on my knowledge, newer AD Schema version along with old Exchange version should not be a problem. It is easy to refer that when we finished the extend schema operation during update, our old Exchange server can still work fine.