Re: 404 (substatus 0) on mail with special chars

anonymous_at_discussions.microsoft.com
Date: 05/25/04


Date: Tue, 25 May 2004 16:03:21 -0700


>-----Original Message-----
>This has nothing to do with IIS6 nor special characters.
>
>I would suggest that you take a backup metabase from
BEFORE you
>inadvertently screwed up the system configuration and use
it. IIS6 keeps
>such backup copies for you, unless the backup has already
aged off due to
>you making many other random changes, for exactly this
purpose -- if you
>screw up a major configuration setting like this, you can
immediately roll
>back to an earlier backup.

Hindsight is 2020, isn't it Mr. Wang?

>The 404 is showing up because it's a real "file not
found". OWA has at
>least one special application extension configured in its
vdir that
>interprets this URL:
>/exchange/walnut/Drafts/RE:+RBL's-2.EML?Cmd=reply&Create=0
>
>into proper access of the Exchange data store. Since
that application
>extension was wiped out on your misconfiguration error,
it is no longer
>interpreting this URL and hence IIS is trying to find
some file that doesn't
>exist in the filesystem (the file exists in the Exchange
data store).

Not true. The original file is there, it can be found by
OWA, and it can be read/previewed through the browser.
Older email's without colons in the subject line can also
be read (e.g., messages delivered before and after my
change). When IIS/OWA interprets $_REQUEST['cmd']
== 'reply', it forwards the instruction to Exchange...
IIS/OWA/Exchange is not "trying to find some file that
doesn't exist in the filesystem" --rather, Exchange
prepares this message to be sent back to the IIS/OWA
component, but before doing so it prepends the subject
line with an "Re:" <-- note the use of the colon. It's
this behavior which causes IIS to throw the 404.... not a
broken filepath.

>I do not know what application extension(s) are used by
OWA, nor how it
>should be configured, nor how SBS has customized your
server. You will be
>better served by asking an Exchange newsgroup about the
IIS configuration
>necessary for OWA and SBS for the customizations.
>
Thanks, I've already tried that.

>If I were you, I would highly suggest that you either use
a backup metabase,
>and if that's not possible, reinstall everything. I do
not think you will
>reconstruct the application extensions correctly
everywhere since SBS does
>customize a lot of those settings for integration
purposes, and I doubt your
>settings are correct even though it appears to function
right now. There is
>a high chance that things will only be randomly breaking
as time goes on and
>it will get harder to fix. Take it as a lesson that you
need to keep good
>backup of your system configuration and use it.

Lesson learned. I really like how it's all or nothing with
MS. Either you've got your a$$ hanging out in the wind and
the only way to cover it is through the use of third party
solutions, or your wearing armor & chainmail from the 17th
century.

>
>--
>//David
>IIS
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>//
>"walnut" <anonymous@discussions.microsoft.com> wrote in
message
>news:1219601c44269$32e90db0$a001280a@phx.gbl...
>IIS 6.0, Windows Server 2003 SBS
>Exchange Server 2003
>
>Issues ruled out (?): Urlscan not installed and the errors
>are not the result of the IIS lockdown utiltity.
>
>Cause: I inadvertantly applied "inheritance override" to
>child nodes under Default Web Site when adding an
>application extension script map for PHP... I've since
>been able to re-create a HTTP Virutal Server for OWA, and
>use its settings to modify the setings of the exchange owa
>server under the default web site.
>
>Things are normal aside from this behavior with messages
>containing colons, double quotes, etc... in the subject
>line.
>
>Here's the log entries showing the error:
>
>#Software: Microsoft Internet Information Services 6.0
>#Version: 1.0
>#Date: 2004-05-25 06:03:13
>#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query
>s-port cs-username c-ip cs(User-Agent) sc-status sc-
>substatus sc-win32-status sc-bytes cs-bytes
>*error codes follow -- 404's, etc*
>2004-05-25 06:03:28 XXX.XXX.XXX.XXX
>GET /exchange/walnut/Inbox/Re:+fixed?.EML cmd=preview 443
>local.domain\walnut XXX.XXX.XXX.XXX Mozilla/4.0+
>(compatible;+MSIE+6.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322)
>404 0 2 1830 659
>2004-05-25 06:10:00 XXX.XXX.XXX.XXX
>GET /exchange/walnut/Inbox/RBL's.EML Cmd=reply 443
>local.domain\walnut XXX.XXX.XXX.XXX Mozilla/4.0+
>(compatible;+MSIE+6.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322)
>302 0 0 374 491
>2004-05-25 06:10:00 XXX.XXX.XXX.XXX
>GET /exchange/walnut/Drafts/RE:+RBL's-2.EML
>Cmd=reply&Create=0 443 local.domain\walnut XXX.XXX.XXX.XXX
>Mozilla/4.0+
>(compatible;+MSIE+6.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322)
>404 0 2 1830 509
>
>thanks,
>walnut
>
>
>.
>



Relevant Pages

  • Re: CEICW Wizard Fails...
    ... We can let Exchange regenerate the OWA folders from AD to see if that takes ... In order to allow Exchange to replicate a new set of virtual directories: ... Make a backup of the current configuration. ...
    (microsoft.public.windows.server.sbs)
  • OWA not working (exchange 2003 ent, server 2003 ent)
    ... We'll get a page can not be displayed error with OWA when we try to browse ... it online, and try to browse to it, the DefaultAppPool dies on us, and we ... IIS configuration for the Exchange Virtual Server, ...
    (microsoft.public.exchange.admin)
  • Re: one Exch2K3/Win2K3 server, OWA installation help
    ... There is no configuration that needs to be done internally. ... is installed, OWA is fully functional. ... internal Exchange server. ... If you want to set up a certificate, you need to install the certificate on ...
    (microsoft.public.exchange.admin)
  • Re: Exchange recovery
    ... someone restore from an ARCServe 2000 backup. ... configuration, but the restore created a failure log that gave me clues ... Manager for Exchange to recover the data from the stores... ...
    (microsoft.public.exchange.admin)
  • RE: OWA users can not open mail
    ... please check the message format configuration of your Exchange ... To view this configuration information in Exchange Server 2003: ... Does the issue occur when they use OWA Basic when users logon the OWA? ...
    (microsoft.public.windows.server.sbs)