Exchange 2003 Activesync and OWA stop working after 1-2 days

Exchange 2003 Activesync and OWA stop working after 1-2 days and server needs to be rebooted.  Email is working fine other than ActiveSync and OWA.  Browsing to OWA shows RESET error on the browser or site not available.

IISRESET does not solve the issue nor does starting/stopping all Exchange services.  Only a full reboot solves the issue. Thoughts ?
jtd1Asked:
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.

ecarboneCommented:
Next time it happens, view your Services control panel and check to see if the World Wide Web Publishing Service is stopped. Then check the Event Log to see what's causing it to stop. Do you have the latest Cumulative Updates and all other Windows and Exchange updates installed?

Are there any other programs running on your Exchange Server?

Does it always stop at the same time? If so, check the Task Scheduler on your Exchange Server to see if something is running at that time.

How many users are on this Exchange Server? I highly recommend working on a migration to a newer version, since support (and updates) for Exchange 2003 ended over 4 years ago.
0
jtd1Author Commented:
As patched as it can get.  Hangs on different times, different days.  Sometimes a week, last time 24 hours.  Nothing else running on Exchange except Trend Micro Office scan. Customer has been warned for 10 years to get off this server.  Can't force them.  Will check WWW Publishing service status next time. ABout 100 users with about 200 GB of mail files.
0
ecarboneCommented:
Trend Micro? Is this actively scanning anything on Exchange Server?
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

jtd1Author Commented:
Absolutely required.  Since exchange server is exposed (80, 443) to internet, absolutely required.
0
MAS (MVE)EE Solution Guide - Technical Dept HeadCommented:
Did you install any updates recently?
If yes please check if there is any updates related to IIS. uninstall the recent IIS related updates and check.
0
jtd1Author Commented:
there has not been many updates to install in years.  We did have a ransomware attack on that server so we tightened up some Trend OfficeScan Parameters.  Thinking these parameter changes are the most likely cause so have opened a case with Trend Micro.  Cant put the parameters back however as they changes made are required.
0
Aaron GuilmetteTechnology Solutions ProfessionalCommented:
You need to make sure the EDB, STM, and associates log files are excluded from scanning.

Anything in the event log (app or system) around the witching hour?
0

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
jtd1Author Commented:
EDB, STM were already excluded, added .LOG to exclusion list for all scan types. No error messages around midnight in either APP or SYSTEM.
0
jtd1Author Commented:
Also excluded the entire G:\LOG FILES directory
0
Aaron GuilmetteTechnology Solutions ProfessionalCommented:
Also, if you haven’t seen it, this is a great guide that has 90% of the stuff hat plagues Exchange 2003.

https://www.experts-exchange.com/articles/1798/Exchange-2003-Activesync-Connection-Problems-FAQ.html

I would pay attention to the .NET framework version in particular.  Also, Exchange 2003 experiences weird behavior if you don’t have the correct settings in boot.ini (typically /3GB and /USERVA=3030), especially if your server has 4GB or more of memory. (I know I’m dating myself here).
0
jtd1Author Commented:
THanks - issue was resolved by excluding some Trend Micro file locations and additional extensions.  Thanks !
0
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.