Re: OWA in 2007

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Yes, that placeholder (specifically, the red x) means that the client could
not successfully get the image from the server. Have a look in the IIS log
file for your typed request for the image, and see how the server responded.


"Lar" <Lar@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:633E291B-7687-450A-8729-FEE8CB131999@xxxxxxxxxxxxxxxx
By images I mean little square box frames with red 'X's in the middle, a
placeholder for an image. You can tell that the URLs actually take you to
a
different page however all that you can actually see is text and image
(icon)
placeholders.
Thanks again for your help and advise.

"Lee Derbyshire [MVP]" wrote:


Can you describe a bit more what you mean by 'placeholders'? You say the
images open in another window, but the results are more placeholders.
I'm
afraid I don't know what that means. Can you see the image?

"Lar" <Lar@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:40AFD904-FBA6-4EBD-8931-6FF10FF3404E@xxxxxxxxxxxxxxxx
The URLs do open in another window/tab however the results are more
placeholders. So the URLs do go somewhere however that somewhere still
does
not want to show properly.

"Lee Derbyshire [MVP]" wrote:

Best to fix it without FBA first. Right-click one of the image
placeholders
(you mean like a red x?), and note its full URL. Then manually type
it
into
the address bar. You should see either the image appear, or another
red
x.
If you didn't mean to say that you see red x's instead of images, let
me
know.

"Lar" <Lar@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9A407419-3ECC-4B05-8A65-F4C5EA4DC339@xxxxxxxxxxxxxxxx
Do not see any. First line - 301 0 0 343: second line - 401 2 5 77:
third
line - 200 0 0 6895: fourth line - 200 0 0 233; all other lines
end
with
200 x x xxx. All .js lines end with 200. This is if I turn off FBA.
If I
turn on FBA, first line ends with -301 0 0 311: second line - 401 2
5
93,
the
'flogon.js' ends with 200 0 0 249

"Lee Derbyshire [MVP]" wrote:

301 indicates the 'courtesy' redirect to /owa/ (i.e. IIS wants you
to
use
a
/ on the end of the URL when you use a directory name like /owa,
but
is
prepared to supply it for you if you don't).
401 indicates that it wants you to logon.
200 indicates that it has accepted your logon, and everything is
okay.

Is there any request after that which doesn't have a 20x or 30x
status?


"Lar" <Lar@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BC7A91E8-0925-4477-8757-D11E95A79E15@xxxxxxxxxxxxxxxx
OK, installed 'Web Server (IIS) Support" to get logs. In logs,
*..GET
/owa -
80 - ..IP.. is 301 and next line *..GET /owa/ - 80 - ..IP.. is
401.
All
others are 200. What DOES that mean?

"Lee Derbyshire [MVP]" wrote:

It sounds like IE isn't executing some of the page's scripting
functions.
In your IE status bar, it will show (at the bottom right) what
zone
your
browser has put the server in. It may say something like
'Internet'.
That
isn't usually a problem, unless you have changed some of the
scripting
permissions for that zone in your IE security options. If you
think
you
might have done that, you can either reset the zone permissions
so
that
they
are not so restrictive (i.e. more active scripting is allowed),
or
put
the
server into a different zone, such as 'Local Intranet' or
'Trusted
Sites'.

Also, make sure that the browser is getting the required
scripting
files
in
the first place. Look in the server's IIS log, and just after
you
see
the
log in to /owa, look for requests for .js files. If you see
them,
make
sure
that the server response near the end of each logged line is
something
like
200 or 301 or 302 (responses beginning with 2 or 3 are 'good').
If
the
respone is 401 (access denied) or 404 (not found), that's a bad
sign.


"Lar" <Lar@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:98DE9523-13D4-4B13-B123-CA2B47323604@xxxxxxxxxxxxxxxx
Thank you. Upon turning off FBA and retrying access, users
get
the
small
logon window. Upon loging on, a page with only blue text and
image
place
holders appear. You can not access any mail, contact, etc.
Where
to
from
here?
Thank you for all your assistance.

"Lee Derbyshire [MVP]" wrote:


Ah, right. I didn't know that it was displaying a blank
page.
First
thing
I would try is to turn off Forms-based Authentication for the
problem
server
in EMC. That way you will at least know that if you can't
get
FBA
working,
you will at least have some other way of logging in. Then,
if
you
still
prefer to use FBA, turn it back on again, and we can try to
fix
it.

"Lar" <Lar@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9BE53A31-2802-4F6C-8F6C-00236B14E8F6@xxxxxxxxxxxxxxxx
Thank you for your reply, but what is the solution. I am
certain
the
address
is correct, the page does not even arrive at the log on
session
therefore
you
do not even have the opportunity to put in you login or
password.
The
page
simply comes up blank with 'done' at the bottom.
All the answers I've received say 'it's normal' but my
users
still
have
no
access to their email via OWA and no one offers a solution!
Still open to ideas.

"Lee Derbyshire [MVP]" wrote:

That's normal. You are being redirected to the server's
OWA
FBA
logon
page.
The reason code simply tells the server and the browser
that
it
is
the
first
time in the session you have seen the page, and that you
are
not
being
shown
the page a second time because you previously typed in the
wrong
password,
or something like that.

"Lar" <Lar@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DF035BA0-7C68-4B7B-AC24-30C4FBB0D637@xxxxxxxxxxxxxxxx
I have two Exchange2007 servers in two different
organizations.
In
one,
OWA
works great. In the other, my user keep getting this
message -
http://domain.xxx/owa/auth/logon.aspx?url=http://domain.xxx/owa/&reason=0.
I've compared settings in both and cannot find any
difference
in
configuration. What does this "&reason=0" mean? Any
advise
greatly
appreciated.

Larry




















.

Relevant Pages

  • Re: OWA in 2007
    ... When you typed the address of the image name into your browser (and it ... not successfully get the image from the server. ... Can you describe a bit more what you mean by 'placeholders'? ... permissions for that zone in your IE security options. ...
    (microsoft.public.exchange.connectivity)
  • Re: OWA in 2007
    ... I guess it was a corrupted OWA site. ... not successfully get the image from the server. ... Can you describe a bit more what you mean by 'placeholders'? ... permissions for that zone in your IE security options. ...
    (microsoft.public.exchange.connectivity)
  • Re: OWA in 2007
    ... but the results are more placeholders. ... 200 indicates that it has accepted your logon, ... it will show what zone ... browser has put the server in. ...
    (microsoft.public.exchange.connectivity)
  • Re: OWA in 2007
    ... Can you describe a bit more what you mean by 'placeholders'? ... 200 indicates that it has accepted your logon, ... it will show what zone ... browser has put the server in. ...
    (microsoft.public.exchange.connectivity)
  • Re: Server Sync and OMA Wont work.
    ... Please enable IIS logging and reproduced the issue (sync with the SBS ... access the OMA site) and collect IIS log and IIS metabase. ... Restart the Default Website and try Server Activesync to reproduce the ...
    (microsoft.public.windows.server.sbs)