03-17-04 01:38 AM
Charles,
I would do two things to try and narrow down your problem. First I would
create a new TLH (a new public folders tree) and a new pf store pointing to
that TLH, then try to create pf's in ESM on that new tree. If that works
most likely your problem is with your HTTP VS as the error message seems to
indicate. Then, the second thing I would do would be to recreate the
exadmin vroot. The way you do this is as follows: In IIS delete the Exadmin
Vroot. (The Exadmin Vroot will not be deleted in ESM because we only
replicate from the DS to the Metabase.)
Then here's a trick to get it to replicate quickly back again to IIS:
Using ADSI edit, (adsiedit.msc)
a. Expand your configuration container.
b. Services.
c. Microsoft Exchange.
d. Your Org.
e. Administrative Groups.
f. Your Admin Group.
g. Servers.
h. Your Server.
i. Protocols.
j. HTTP
k. Right-click on Exadmin->Properties.
l. In the Attributes, double-click the AdminDescription.
m. Type something like, Hi.
n. Click on Ok.
o. Click on Ok.
p. Wait for a few minutes while we replicate the changes to the metabase.
q. In ESM try to access Public Folders again.
Hope it helps!
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only."
"Charles" <anonymous@discussions.microsoft.com> wrote in message
news:89A004A1-672A-4B87-9623-E616063B9735@microsoft.com...
> Configuration: Windows 2003 Server(std. edition), Exchange 2003(enterprise
edition).
>
> In Exchange 2003, whenever I try to create a public folder in Exchange
System Manager,, I receive the following error:
>
> "The operation failed due to an invalid format in the HTTP request.
Verify that the host header is correct for the virtual server. ID no:
c1030af0."
>
> I have already done the reg-hack I found in KB 292262 but it didn't do
anything.
> I also checked everything in KB Q319240, and everything is as Microsoft
requires in this article.
> The host header for the default web site is blank.
> The port on the virtual server is 80.
>
> ATTN: Microsoft moderators: This appears to be a common problem. The KB
articles for Ex 2000 do not resolve the issue in Ex 2003. I also did a
google search on c1030af0 and a lot of people are having this problem and no
one knows how to fix it. Microsoft should really resolve this issue ASAP.
Please forward to the powers to be.
>
> Any suggestion on how to resolve this issue would be greatly appreciated.
thanks
>
> Charles
>
[ Post a follow-up to this message ]
|