Exchange Server Forums

owa and red cross

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2007] >> Outlook Web Access >> owa and red cross

Page: [1]

Message

<< Older Topic Newer Topic >>

owa and red cross - 27.Feb.2009 7:02:35 AM

ancos

Posts: 39
Joined: 7.Jan.2009
Status: offline

all my users get red crosses when logging into owa; does anybody now a sollution for that?? thanks

Post #: 1

Featured Links*

RE: owa and red cross - 27.Feb.2009 10:29:14 AM

John Weber

Posts: 1236
Joined: 20.Apr.2005
From: Portland, Oregon
Status: offline

If this was e2k3, I would say that you have perms issues on the Exchange folder that OWA is using.

I assume that you should start looking at that. Google "OWA red x"

_____________________________

John Weber [Lync MVP] http://tsoorad.blogspot.com

(in reply to ancos)

Post #: 2

RE: owa and red cross - 27.Feb.2009 3:28:43 PM

jveldh

Posts: 2335
Joined: 12.Apr.2008
From: The Netherlands
Status: offline

Hi,

If it's Exchange 2003 then check the security settings on the exchweb directory. If the checkmark is placed before request ssl then uncheck it and try it again.

_____________________________

Best regards,

Johan Veldhuis

Visit my Exchange blog

(in reply to ancos)

Post #: 3

RE: owa and red cross - 27.Feb.2009 3:38:24 PM

Elan Shudnow

Posts: 897
Joined: 4.Jan.2007
From: Chicago, IL
Status: offline

You can try bumping up Diagnostic Logging to see if it sees anything. Here are the OWA Diagnostic Logging Events:
MSExchange OWA\FormsRegistry                                         Lowest
MSExchange OWA\Core                                                  Lowest
MSExchange OWA\Configuration                                         Lowest
MSExchange OWA\Themes                                                Lowest
MSExchange OWA\SmallIcons                                            Lowest
MSExchange OWA\Proxy                                                 Lowest
MSExchange OWA\Transcoding                                           Lowest
MSExchange OWA\ADNotifications                                       Lowest

You can read this to learn how to bump up the Diagnostic Logging:
http://technet.microsoft.com/en-us/library/bb201670.aspx

_____________________________

Elan Shudnow
Exchange MVP
http://www.shudnow.net

(in reply to jveldh)

Post #: 4

RE: owa and red cross - 19.Mar.2009 6:05:24 AM

jeglent

Posts: 1
Joined: 14.Jan.2008
Status: offline

Hi, I think I have the same problem. I'am running Exch2007SP1 on W2K8.
After innstalling Exchange, Windows Update had severall urgent updates I innstalled. Amongst them an Rollup update. When I finally tried OWA, I was able to log on, but the graphics is missing. Just red crosses. You can see some text representing e-mail headings etc. but nothing works.

I found out from searching Google that this had been an issue before SP1 as well, concerning Rollupupdate2.

With a tweak I got it functioning. Read below:

Under PROGRAMFILES\EXCHANGE SERVER\ CLIENT ACCESS\OWA
You have a lot of folders.
The folder name CURRENT holds the web files i.e. graphic files for the owa website. Today this folder is populated with the right files.
The problem is that for some reason OWA doesn't read this folder.
Paralell to OWA there are to folders named 8.1.240.5 and 8.1.336.0 whom I guess are folders created by patches/Rollup updates.
The 8.1.240.5 had subfolders wich was empty, but the 8.1.336.0 had sub-folders with the same files as in CURRENT.
Now I copied the subfolder structure from CURRENT and replaced the ones in the 8.1.240.5 folder.
Restarted IIS and Bob's your uncle!

OWA works.
So it's clear that an update from Microsoft has gone wrong. It has updated the files in the CURRENT folder, but for some reason changed a value in OWA stating wich folder to use. The next update has updated the CURRENT folder and cleared allcontents from the first update folder. This folder is still refferenced by OWA. Hence all graphic dissapear when you try to open SERVERNAME/OWA.
This is only a temporary solution, because the next update would again update the CURRENT folder which is still not beeing used.
Hence no update would be applied.