I have a single public facing Exchange 2007 server running both the Client Access and Hub Transport roles. Everything is working fine except for Microsoft Entourage 2008(the Mac counterpart to Outlook) which uses WebDav to communicate with Exchange. I am confident the client is configured properly. If Iopen any of theExchange Legacy Virtual Directories(/Exchange, /ExchWeb, /ExAdmin or /Public)in a web browserthen I get a 500 "Internal Server Error"; my assumption is that this is the core problem. If I go to"Server Configuration: Mailbox: WebDav" I can see all four virtual directories, each with the proper website association. My event log is littered with the error "DAVEX to be shutdown. Version: 8.1.336.0" (Source: DAVEX, Event ID: 101). In the past, I've resolved issues with OWA by recreating the virtual directory using the Exchange Management Shell (set-owavirtualdirectory). There doesn't appear, however, to be an equivelent cmdlet for the other virtual directories. I'm a bit lost in terms of what troubleshooting steps to take next. Thoughts? Update: If I view the /Exchange folder via the server I get additional debug information which I should include in this post: Module:IsapiModule Notification: ExecuteRequestHandler Handler: AboMapperCustom-3685315 Error Code: 0x80004005 Requested URL:https://DOMAIN:443/exchange/USER@DOMAIN Physical Path: \\.\BackOfficeStorage\DOMAIN\MBX\USER@DOMAINLogon Method: Basic Logon User:USER (PII removed). Jeremy

Still having this error. Any help with troubleshooting steps would be appreciated.

Is your Exchange server running on Windows 2003 or 2008?Mike Crowley: MCT, MCSE, MCTS, MCITP: Enterprise Administrator / Messaging Administrator

Hey Mike, this is on Windows Server 2008. (It is Exchange Server 2007 Service Pack 2, to note). Let me know what you think - we've completed our migration and, currently, Macintosh users are limited to Outlook Web Access or IMAP only (no Exchange support).

Exchange sp2 as in beta? Mike Crowley: MCT, MCSE, MCTS, MCITP: Enterprise Administrator / Messaging Administrator

Shoot; that was meant to read "Service Pack 1" (the one required to run Exchange 2007 on Windows 2008). I am not running Exchange SP2. As an aside, I had originally misunderstood the documentation for New-OwaVirtualDirectory; using this andRemove-OwaVirtualDirectory I was able to remove and recreate each of the legacy folders (Exchange, ExchWeb, ExAdmin, Public). I thought this might help, but the results are the same. I also found discussion of this problem elsewhere on the forums(the user "Jvangent100" describes my precise symptoms). One user's problem was resolved by removing the new Microsoft FTP Server for IIS7; I tried this, but no luck.

slightly unrelated, but have a look at this: http://www.microsoft.com/mac/itpros/entourage-ews.mspxMike Crowley: MCT, MCSE, MCTS, MCITP: Enterprise Administrator / Messaging Administrator

Not really a technical answer, but I've had "strange things" done to a CAS before and removing and reinstalling the CAS role helped.Mike Crowley: MCT, MCSE, MCTS, MCITP: Enterprise Administrator / Messaging Administrator

Hey Mike - thanks for these suggestions. The EWS beta for Entourage is on my research list; looks like I should prioritize it. There's part of me that's being stubborn about it as I hate having things not work "as promised" on fresh installs. The pragmatist in me needs to remember that this is legacy support for a small number of clients! I've read other reviews of people talking about reinstalling the CAS role. I've been reluctant to do this since it's a production CAS. It also sounds like this is a relatively painless and routine process that shouldn't require too much re-configuration so I think I'll give it a shot during our next scheduled maintenance period. Thanks again for your help!Jeremy