03-05-2015 07:16 AM
We are running 3 exchange 2003 servers with OWA front end.
So far 3 users have reported they are unable to access archived emails from OWA, i have tested different accounts which have the mailbox on the same mail servers and i can see the EV icons and access archived emails.
Any suggesitons?
Solved! Go to Solution.
03-05-2015 09:34 AM
Do the users always have the same issues?
Typically your best bet is have them go from one OWA Server to another, especially if they're load balanced
For instance say you have the following
webmail.myCompany.internal -> CASServer1.myDomain.com
webmail.myCompany.internal -> CASServer2.myDomain.com
webmail.myCompany.internal -> CASServer3.myDomain.com
It could be that CASServer2.myDomain.com is broken/mis configured, and when you're testing it, you're going to CASServer1 and CASServer3 and not hitting the broken CAS Server or FE server
So your best bet is to go to each individual FE/CAS Servers, and have them do the same.
And you should enable logging for their mailbox and see if its a specific server thats causing the issue or whether theres an error going on in the background
It could also be a specific EV server having issues like not having a properly configured EVAnon directory etc
03-05-2015 09:34 AM
Do the users always have the same issues?
Typically your best bet is have them go from one OWA Server to another, especially if they're load balanced
For instance say you have the following
webmail.myCompany.internal -> CASServer1.myDomain.com
webmail.myCompany.internal -> CASServer2.myDomain.com
webmail.myCompany.internal -> CASServer3.myDomain.com
It could be that CASServer2.myDomain.com is broken/mis configured, and when you're testing it, you're going to CASServer1 and CASServer3 and not hitting the broken CAS Server or FE server
So your best bet is to go to each individual FE/CAS Servers, and have them do the same.
And you should enable logging for their mailbox and see if its a specific server thats causing the issue or whether theres an error going on in the background
It could also be a specific EV server having issues like not having a properly configured EVAnon directory etc