Re: SBS2K, Exch. 2K, Public Folder error 80040e19

Tech-Archive recommends: Speed Up your PC by fixing your registry

"Steve Foster [SBS MVP]" <steve.foster@xxxxxxxxxxxxx> wrote in message
news:xn0e6mcf72i73e200n@xxxxxxxxxxxxxxxxxxxxxxx
> Dvord Direwood wrote:
>
<SNIP>
>
> Oops, there was supposed to be a question bit at the end of that line.
>
> The point here is that you have event log errors relating to OWA usage of
> public folders, which are likely to be related to ESM's inability to
> manage public folders. Yet you appear to be dismissing that possibility
> almost out of hand ("wild goose chase"), while at the same time not
> providing enough information on those symptoms for anyone here trying to
> help you to examine that possibility.

I went to EventID.net. I plugged the error into the search engine. It
offered the following possibility:

http://support.microsoft.com/?id=811358

I was pretty dubious about "In Exchange 2000 Server, you cannot recover
deleted items from or modify the contents of public folders through
Microsoft Outlook" since it doesn't apply to my situation (primarly because
I can modify the contents of public folders through Microsoft Outlook). I
did check the permissions as suggested in the article and they are fine.

I am answering each request for information completely. Some sub-threads
have split off on this topic though, and your answer might not be in this
particular thread.

What information have I failed to provide? I will provide it immediately.

>>>>Still back at square one.
>>>
>>>Have you uninstalled and reinstalled the IIS Lockdown and URLScan tools
>>>yet, as suggested?
>>
>>Yup, I did. Didn't make any difference in the nature or symptoms of the
>>problem.
>
> Now you see, you could have told us that first time we asked...

I did, in another part of this thread. Also, I couldn't work on the issue
much over the weekend as I'd hoped due to other circumstances which are
irrelevant to the discussion.

> Quick summary then:
>
> ESM still can't open public folders when:
>
> * DNF is removed
> * IISLockdown & URLScan removed
> * OWA works perfectly

Yes, .NET was removed. I don't see where IISLockdown and URLScan are
different entities. I could find no distinction, and no separate installer
for IISLockdown. AFAIK, IISLockdown is currently disabled. Yes OWA is
fine.

> Can you run the Internet Connection Wizard with the server in this
> condition? preferably, setting all options as you go (ie not selecting "Do
> Not change xxx" ever).

I haven't tried, but I will try that tonight when everyone has gone home.

> Is OWA living on the normal Default WebSite?

Yes that's right.

> BTW, just an FYI, the SBS2000 newsgroup is
> microsoft.public.backoffice.smallbiz2000. This group is focussed primarily
> on SBS2003.

It would have been helpful to have 2003 in the newsgroup name. I seem to be
getting some help at the moment, and I'd really like to refrain from doing a
bunch of troubleshooting again if I can help it.



.

Relevant Pages

  • Re: Any easy way to publish public calendar folder as web page?
    ... I understand that when you tried to use OWA ... to access public folders, ... On a SBS LAN client, check if those users can access that sub-folder. ... Moreover, based on my experience, this issue can also occur if the URLScan ...
    (microsoft.public.windows.server.sbs)
  • Re: Can forward/reply to PF message in OWA?
    ... Unlike earlier versions of OWA, OWA 2003 lets you reply and forward messages ... folder server) must be running Exchange 2003 for this functionality to work ... > Public folders if you are using OWA? ...
    (microsoft.public.exchange.admin)
  • Re: Can forward/reply to PF message in OWA?
    ... Unlike earlier versions of OWA, OWA 2003 lets you reply and forward messages ... folder server) must be running Exchange 2003 for this functionality to work ... > Public folders if you are using OWA? ...
    (microsoft.public.exchange.clients)
  • RE: Access intranet through Public folders
    ... you may get the problem if you enable FBA on OWA. ... If administrative groups are enabled, expand Administrative Groups. ... try to access the Public Folders via http://FQDN/public. ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: Public folder problem...
    ... It could be URLScan, if you've installed that on the server. ... google search for 'urlscan' and 'public folders' or similar - you should ... For Exchange news, links, and tips, check: ...
    (microsoft.public.exchange2000.admin)