[isapros] Re: Error publishing exchange 2003 with path redirection
- From: "Greg Mulholland" <gmulholland@xxxxxxxxxxxx>
- To: <isapros@xxxxxxxxxxxxx>
- Date: Tue, 29 May 2007 09:01:52 +1000
The paths have not been modified and are exactly what the rule itself
creates
<same as internal> /exchange etc etc
And turning off link translation on the rule makes no difference.
From: isapros-bounce@xxxxxxxxxxxxx [mailto:isapros-bounce@xxxxxxxxxxxxx] On
Behalf Of Jim Harrison
Sent: Tuesday, 29 May 2007 1:23 AM
To: isapros@xxxxxxxxxxxxx
Subject: [isapros] Re: Error publishing exchange 2003 with path redirection
You say that you're "having the same issues as..", but you don't detail the
problem?
Does your deployment meet the :cause" requirements:
CAUSE
This problem occurs if the following conditions are true:
.
The external path that is specified in the OWA Web publishing rule is "/."
Be aware that the "/" is used without quotation marks.
.
The internal path that is specified in the OWA Web publishing rule is
URL-encoded. Characters that are URL-encoded are replaced by a percent sign
(%) that is followed by a particular number.
.
Link translation is enabled for the OWA Web publishing rule.
In fact, the whole purpose of the Exch 2007 update for IUSA 2006 is because
they're not the same.
From: isapros-bounce@xxxxxxxxxxxxx [mailto:isapros-bounce@xxxxxxxxxxxxx] On
Behalf Of Greg Mulholland
Sent: Monday, May 28, 2007 2:10 AM
To: isapros@xxxxxxxxxxxxx
Subject: [isapros] Error publishing exchange 2003 with path redirection
Having issues trying to re-direct the OWA path when publishing exchange 2003
here using isa 2006 se
I am seeing the very same symptoms as the article below describes (event #
21177)
http://support.microsoft.com/kb/930415
I have tried a number of different scenarios to try and get this working,
even installed the fix remotely and bounced the machine and i still see the
same thing.
The article describes it as a fix for publishing exchange 2007, but i assume
it is the same deal for exchange 2003, can someone confirm? jim?
Thanks
Greg
All mail to and from this domain is GFI-scanned.
Other related posts:
