01-24-2013 09:14 AM
I've tried to deploy the OWA extensions for Exchange 2007 on to the CAS server (this environment has one mailbox and one CAS/HT server). The archived items now show up with the correct icon indicating they are archived.
I don't get the EV icons appear, and I'm unable to open any archived items, only the stubs are visible. When I open the stub it shows the message "The archived item is currently unavailable." then below "Click here to preview the original item". When I click on the last bit of text it displays a 404 error.
I turned on OWA logging to see if I could identify the cause. Below is an extract of a test user that is having the problem, with the error being a https 500 error. I read various articles on the error, and I've tried a lot of things! One suggested accessing the URL in the log below directly from Internet Explorer, and see if I get a 500 error there as well, I didn't - and unfortunately it didn't suggest what to do if that worked!
I've run the tool to confirm OWA is working correctly, and everything comes back as good. http://www.symantec.com/business/support/index?page=content&id=TECH126141
I have already confirm all IIS components on the CAS server match this document: http://www.symantec.com/business/support/index?page=content&id=TECH147800
I've run through the config, including the OWAUSER script. I'm unsure what else try.... any ideas?
Solved! Go to Solution.
01-29-2013 09:29 AM
The problem that you have is when the extension tried to open the mailbox is using the following address:
https://localhost/exchange/Drew.Hoff@xxxx.com and the request should go to the mailbox server.
To fix that you should remove the EnterpriseVault_WebDavRequestHost = Localhost from the CAS server, that will replace the localhost for the mailbox server name. After that we need to continue troubleshooting to see if you have more errors. Please post the new logs.
Check this technote to see how to remove that line.
Enterprise Vault 2007, 8.0, and 9.0 Web.config options for Microsoft Exchange 2007 Outlook Web Access (OWA)
01-25-2013 10:29 AM
Can you confirm which IP addresses you have got in your ExchangeServers.txt file on the EV server, and what was in there when you ran OWAUSER.WSF ?
I would also take a look at your favourite search engine and try to validate that EWS is correctly configured, and working on your server.
01-28-2013 02:55 AM
01-28-2013 03:34 AM
Looks like an issue with WebDAV. Check the IIS logs on CAS / MBX to determine which one is producing the 500 error. I suspect you'll see an entry on the MBX for with a 500, and the CAS will simply proxy that back (and also report it in it's IIS log).
I have a vague recollection that someone once had an issue where WebDAV wasn't installed on the MBX server. I can't find a tech note about it, but check that the WebDAV IIS feature is installed on the MBX server.
01-29-2013 09:29 AM
The problem that you have is when the extension tried to open the mailbox is using the following address:
https://localhost/exchange/Drew.Hoff@xxxx.com and the request should go to the mailbox server.
To fix that you should remove the EnterpriseVault_WebDavRequestHost = Localhost from the CAS server, that will replace the localhost for the mailbox server name. After that we need to continue troubleshooting to see if you have more errors. Please post the new logs.
Check this technote to see how to remove that line.
Enterprise Vault 2007, 8.0, and 9.0 Web.config options for Microsoft Exchange 2007 Outlook Web Access (OWA)