HTTP Error Administering Public Folders

Exchange 2000 running on Windows 2000 (Windows Small Business Server 2000, actually).

In System Manager, when I attempt to expand the "Public Folders" group, I get a error box with this information:

The operation failed due to HTTP error 405
Facility: Exchange System Manager
ID no: c1030af4
Exchange System Manager

The HTTP error varies -- sometimes it's 501.  The "ID no", however, seems to stay consistent.

This guy had the same problem, but with HTTP error 502.

Doesn't look like he got any help.

I've Googled the crap out of this, with no success.  I dismounted the store, and ran ESEUTIL up, down, and sideways.  The public store has been checked, defragmented, compacted, etc. from here to Timbuktu.  It couldn't be in better shape, yet the error continues.

I'm really intrigued at the concept of an HTTP error in Exchange.  I don't get it.

Who is Participating?

Improve company productivity with a Business Account.Sign Up

ehammersleyConnect With a Mentor Commented:
The big red error sign is deceptive.   That is probably due to the WWW service starting prior to the Exchange IS server... a very common bug in Exchange 2000.  The virtual directories with red stops are really running... they just don't look like it.  The problem there is that the Exchange IS service provides IFS and those specific virtual direcories point to BackOfficeStorage.  There's nothing you can do about that and everything will operate normally even though they have the red error signs.  And yes, this is logged in the Event Log.

Now, the web services.

Port 80 is the key.  When the ExAdmin folder is not located on a virtual server running on port 80 you will receive an error like this.  Check out this article:;en-us;325920&Product=exch2k

If I was you... I would stop apache, set IIS back to port 80, restart IIS and make sure the ESM Public Folder problem is indeed fixed by moving it back to port 80.  Then I would worry about how to fix it around Apache.  Just to make sure you don't do more work than needed.
Right, your store is coming back clean because it's not at fault.  The HTTP error is most likely because Exchange System Manger uses http against IIS to connect to the public folder store.  The error you're receiving is due to a problem with IIS.  Restart IIS, in case you haven't rebooted the server.  ExAdmin is the virtual folder in IIS that you're interested in.

I hate to be so generic with my link but I can't narrow it down further.  This link will take you to Microsoft's KB, there are several articles concerning similar issues with ESM and public folders.  They are ALL connected by IIS, and so is yours.  It will give you a good start to checking the health of IIS.  Two that stand out as most common, changing the default port from 80 and a non-default host header.  Doesn't seem like they should be connected, but they are.

deane_barkerAuthor Commented:
Sure enough -- there's a big, red, "Error" sign next to the folder.  The question is, why?  Is there a log somewhere?

This is also complicated by the fact that I'm running IIS on a different port.  I have Apache on this machine, running on Port 80.  I've moved the Default Web Site off to Port 81.  Does Exchange not like this?
deane_barkerAuthor Commented:
You nailed it -- problem solved, and points well spent.

Very stupid limitation of Exchange, IMHO.  Do you know how trivial it would be to allow the setting of a different port?  Why does Microsoft insist on such tight integration to the exclusion of everything else?  Frustrating.
I'm glad you atleast identified the root cause.  I hope you are able to create a solution that fits into your current configuration somehow.

I agree on the Microsoft issue.  It's tough to identify issues like this during development but in my opinion you don't hardcode something as flexable as a port number.  I wish you all the luck on this work around.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.