Exchange/Outlook goes offline

Hello - we are having recurring episodes with our Outlook 2010/Exchange 2003 going offline and we have to reboot the server to get it working again.  Outlook clients will not be able to connect.  There does not appear to be any errors that standout on the server, so this is a mystery to us, and are looking for ideas on things to check pertaining to the health of the server, that might help us flush out the root cause.  The server OS is Windows 2003.  Any ideas would be greatly appreciated.

Thank you,
Damian
Damian_GardnerAsked:
Who is Participating?
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.

Nick RhodeIT DirectorCommented:
Could check the event viewer to see what the issue is.  When it goes offline is the database dismounted?  Also check the exchange services.  One of them could be stopping at that point.

Or you can run some health checks before and after the server goes offline:

http://blogs.msdn.com/b/douggowans/archive/2007/06/06/run-your-own-exchange-server-health-check.aspx
0
Damian_GardnerAuthor Commented:
Thanks for your reply.  I am not sure whether the DB is dismounting or not, and I'm not seeing anything right away in the event viewer, so what I will do is watch for the next time it goes offline (probably tonight) and will take note of the services.  I will also sift through the event viewer again to take a 2nd look for errors or warnings.  I'll run some health checks as well.  Thanks and I'll report back soon.

Damian
0
Damian_GardnerAuthor Commented:
I ran the BPA on the server, and am not sure what to make of one of the problems it found.  I'm attaching a screen shot of it so you can see - but it's complaining that it cannot contact it's Active Directory Connector, which is identifies as a server named "lacomail2" - which is not an AD server, and is not involved with Exchange any longer.  Years ago, it used to be the email server, when we were on Exchange 5.5, but we've since implemented a new server running Exchange 2003 and migrated onto that machine in 2006.  That server is called "Lacomail", and is the only machine we use for email.  So - not sure what to make of this error.
BPA-Result.png
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Nick RhodeIT DirectorCommented:
If you no longer use Exchange 5.5 you should be able to remove ADC and it will not affect Exchange 2003 to clear up that error.

http://technet.microsoft.com/en-us/library/aa997967(EXCHG.80).aspx
0
Damian_GardnerAuthor Commented:
ok. I'll do that.
0
Nick RhodeIT DirectorCommented:
Use this link to set the size limits on your transport:  http://technet.microsoft.com/en-us/library/aa998459(v=exchg.80).aspx

It is always recommended to setup a limit.  I typically use 10mb as max size but it all depends on your business needs and if you have large emails flowing (like blue prints and stuff).
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
Damian_GardnerAuthor Commented:
Great - thanks.  It stayed up and running last night, so still waiting for it to fail so I can check the services and things.  Standby a bit longer.

thanks
0
Damian_GardnerAuthor Commented:
the message limits are set now.  It looks like I can't run the ADC setup, however, since the 2003 server was upgraded to 2008 server 64-bit previously, and the ADC only runs on 32-bit.  Can I simply leave it, until I igrate the mailboxes to the new Exchange 2013 server in the near future?  No harm in leaving the ADC on there in a disabled state, I assume?

thanks,
Damian
0
Damian_GardnerAuthor Commented:
Ok - it went down sometime between Midnight last night and about 6am this morning, which is typical now, when it happens.  what I found was the server remains ping-able, and all Exchange services remain running, yet Outlook reports "Exchange is unavailable".  The C drive where the MDBDATA files are, has 20G space free, and the database files all combined are 80.6GB in size.  I don't see anything standing out in the logs, so Id like to attach the app and sys logs and perhaps you'll see something I don't.  

Thanks,
Damian
0
Damian_GardnerAuthor Commented:
Sorry - had tropuble attaching the logs, so I've shared them online at the following URL for downloading:  https://www.adrive.com/public/VUkVy4/exchange logs.ZIP

Thanks for your help
0
Damian_GardnerAuthor Commented:
clarification on the link:  [https://www.adrive.com/public/VUkVy4/exchange logs.ZIP] (copy the entire link, including "logs.zip")
0
Damian_GardnerAuthor Commented:
No luck with running the BPA and fizing some of the things it found, so we're just limping along with until we can migrate the mailboxes onto Exchange 2010 this weekend.  Hopefully that'll solve everything.

Thanks, for your help.
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.