Re: SBS2K, Exch. 2K, Public Folder error 80040e19
- From: "Steve Foster [SBS MVP]" <steve.foster@xxxxxxxxxxxxx>
- Date: Wed, 31 Aug 2005 09:14:56 -0700
Dvord Direwood wrote:
"Steve Foster [SBS MVP]" <steve.foster@xxxxxxxxxxxxx> wrote in news:xn0e6mfz73guj8001@xxxxxxxxxxxxxxxxxxxx:
<SNIP>
You have to run the IIS Lockdown wizard a second time, and it asks if you'd like to roll back the IIS config to before it was run. This was one of the things I didn't like about it, since it appears to simply backup the IIS config at the point it's installed and use that as reference point for uninstalling itself. Catch is that any IIS changes made post-lockdown are lost.
Well, the good news is that when I rolled back the IIS config, public folders worked fine.
Ok, we're making progress - of a sort.
The bad news is, when I did that, my Outlook clients on the LAN couldn't connect to the Exchange server.
Hmmm, one step forward, two steps back... :(
The only thing I can think of (quickly) here is that the IIS lockdown rollback would have resulted in an IIS restart. So various services that Exchange "borrows" from IIS (NNTP, SMTP principally) would have been temporarily unavailable. Given the IIS changes, it's also possible that they wouldn't have properly restarted.
I put IISlockdown back on, and Outlook-Exchange functionality returned, however public folders went back to that same old error.
This was a manual install, where you got to specify that your server was an SBS, right?
If SBS was not one of the choices, you're using an old version of IISLockdown.
My "expert" opinion is something about ISA is preventing me from viewing the public folders with ESM. That 'something' may or may not affect Exchange functionality. It remains to be seen.
Hmm, the IIS lockdown rollback suggests not, but the interplay between ISA and IIS is a [remote-ish] possibility.
I still have a little time before I want to run ICW. I didn't suspect that IISLockdown would have affected normal Exchange operation (short of OWA of course), and resulted in the Outlook client outage otherwise I would have waited on that until tonight too.
I'll reply again once I've done ICW to see if that impacts the problem at all.
Best course of action is probably to remove IIS Lockdown and URLScan, and rerun the ICW at that point. That's the most likely course to result in a complete working state.
If it does, you should be able to reinstall the IIS Lockdown and URLScan at that point and still be functional.
-- Steve Foster [SBS MVP] --------------------------------------- MVPs do not work for Microsoft. Please reply only to the newsgroups. .
- Follow-Ups:
- Re: SBS2K, Exch. 2K, Public Folder error 80040e19
- From: Dvord Direwood
- Re: SBS2K, Exch. 2K, Public Folder error 80040e19
- Prev by Date: VBscript Error on SBS2k3
- Next by Date: RE: Offline Files/Folder Redirect and My Pictures
- Previous by thread: VBscript Error on SBS2k3
- Next by thread: Re: SBS2K, Exch. 2K, Public Folder error 80040e19
- Index(es):
Relevant Pages
|
