Why did Outlook Web Access stop working? But SMTP continues....

Outlook Web Access stopped working; but, everything else is working.  What can I check on get the O.W.A. to begin working again?


This past weekend, I used vMotion to migrate the Exchange Server from 1 Specific ESXI Host server to a new ESXI host server.  I was actually using the Outlook Web Access before and after the migration and it did work before and after.  Since then I have restart the Exchange Server several times; but, I recently discovered that after I login to the O.W.A web portal an http:// 500 error message comes up ( https://mail.XXX.net/owa/auth.owa )

The other Exchange related services work just fine (Email, activesync, smtp (mobile phones).  Why is the "Outlook Web Access" not working?  What can I check?

I do not think it is the migration of the Virtual Exchange Server from 1 Host to another because that would have neen instant.  This problem did not instantly happen.
LVL 1
PkafkasNetwork EngineerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jose Gabriel Ortega CastroCEO Faru Bonon IT - EE Solution ExpertCommented:
Well clearly,  something messed up with the migration.

1st of all, check the event viewer, you can use this script:
https://gallery.technet.microsoft.com/Get-event-logs-errors-and-6871f163

2nd check the exchange services that are marked as "auto" are started and running.

3rd Open the PowerShell console and check if it's working or not.


Owa works over HTTP/HTTPS (port 80/443)
all the services you mention works on these ports.

SMTP goes over port 25, so one thing doesn't relate to another (port 443 with port 25).

is it still on the old server?, do they have the same IP?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
viktor grantExchange ServersCommented:
Hi,

Try to connect with the following link: https://localhost/owa in the Exchange server. Do you have the same error?

Please try to restart IIS with the following command: iisreset

Cheers
Viktor
PkafkasNetwork EngineerAuthor Commented:
I logged on to the Exchange Server and I noticed that 2 services that were set for Auto, were not actually started.

  • Microsoft Exchange Forms-Based Authentication Service
  • Microsoft Exchange Protected Service Host

The Forms-Based service is specifically designed authentication for Outlook Web Access.  After I stated this service then the O.W.A. began working.  I then started the other service (Protected Service Host) and the O.W.A. continued to work.  I wonder why these 2 services did not start automatically after the server restart?

I never had this problem before.... I guess I will just have to manually look for this after a restart.  Any suggestions if this continue to happen after the server restarts?
timgreen7077Exchange EngineerCommented:
@Pkafkas, sometimes the services fail to start because they time out waiting for other service dependencies to start, so you can
set the service to automatically start with a delay. The delay option allows other dependencies to start before the service starts. Also anytime you restart exchange I always check to verify my services have started. After Exchange reboots, give it about 2 minutes and they in the exchange management shell run the following:

test-servicehealth -server "exchangeserver"

This will show you if all the required services for exchange are running or not. I personally don't set the delay but its an option. Always verify services started after reboot, and the cmdlets will help you check with the need to log into the server.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.