Hi, I have a 2k8 server running 2k7 Exchange (SP1) with all updates installed. Ihave OWA accessable and working from the outside world. The only problem is that it will not display properly. It almost gets it right, but misses icons in the left hand pane eg. Inbox icon, Sent Items icon, Junk Mail icon etc. (at random). It always misses the "Options" icon at the top right. If you log out, then log back in you just get a screen of plain text - no theme, no colours, no formatting, just plain text (in Times New Roman) displayed all over the page. This happens locally too, but locally it does not miss any icons the first time round. Log out, then log in and I get the same results as if I was logging in from the outside with plain text displayed. If I leave the system for 5 mins then try logging back in I get the theme back? Any ideas appreciated.

hi could you provide more info in order to troubleshooting the issue? (1) when you logon in local exchange server by OWA , whether it's OK ? (2) when the issue occurs, which IISversion are you runningto access OWAin client ? IIS 6.0 or IIS 7.0? (3) the exchange 2k7 sp1 certification of IIS is self-signed or CA publich ? please type get-exchangecertification -full >.txt in PS , then post the .txt to forum ; (4)which item are you running execute permission of IIS ? detailed path: right click default web site -click home directory -execute permissions - ? hope it helps i am look forward to your reply,if anthing is unclear,please free time to let me know ; thanks; -Jack

Hi Jack, To answer your questions, 1. OWA is now only displaying text now - no theme at all - when you turn off Forms Based Authentication (the issue seems to be getting worse!). If I set everything to Basic Authentication I get text. If I turn on FBA, I now get an error in IE7 (local OR remote): Line: 7 Char: 1 Error: Syntax error Code: 0 URL: https://<domain>/OWA/auth/logon.aspx?url=https://<domain>/owa/&reason=0 2. I am running IIS 7. 3. The Server is using a GoDaddy SSL certificate. 4. Authenticated users of the OWAdirectory have Read Only permissions. Thanks, Dominic

Thanks for your help Jack, but the problem is now solved (after 2x 2hour calls to M/Soft). For anybody else having the same problem, the issue was that OWA was acting as an application (not sure why).

Hello domquark, I am having the same issue. How do you change OWA from acting as an application?

Ok, found how to switch it from an application user, but I still have the same problem. One thing I do notice in the IIS logs is that everything is returned with 200 OK, but both the source and client IP's are IPv6 addresses. Could that have something to do with it?

Hi Viper, sorry for not getting back to you sooner. Firstly, the nice chap from M/Soft backed up the contents of the OWA "folder" in IIS. He then deleted the existing OWA folder, created a new one, then put the backup back into the new folder. Note the folder icon should look like a standard (plain) yellow folder icon - if it doesn't, then it's probably still acting like an app. As for it only using IPv6, I must admit I'm not sure. One thing I do know is, that DO NOT REMOVE (or disable) IPv6 under any circumstances! I did, and I can tell you from personal experience - all *** breaks loose on Ex2007! I will try to look at the logs on my customer's server to see if it logs the IPv6 address too. Can you get OWA working locally,remotely, or both?

Sorry Viper, Just to clarify my earlier post, the main OWA icon looks like a "World", it's the sub-directory that should look like a normal folder. Sorry if I wasn't clear.

No problem! Thank you for your reply. I actually started banging my head against the wall after looking at this issue for six hours. Since this setup is only for a test environment, I had the luxury of being able to reformat everything and start over. This time I was very careful and moved slowly. I did two things differently. First, I left the default organization name of First Organization. Second, I made sure the static and IIS6 compatibility features were installed before installing Exchange. I think they were before, but I was not completely sure. In fact I installed all IIS features except for FTP. I then updated to rollup 3 on Exchange and OWA worked perfectly!