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

Dvord Direwood wrote:

Thanks Nathan!

1. Yes .NET is installed. I have 1.1 already. Unfortunately this is a production server, I will uninstall tonight as removing .NET will render our website inoperable.

2. Cause 1: The IP address did not change for the website. Regardless I verified this using the steps you posted here and the accompanying article. The IP address for the website is set to All Unassigned. If I change it to the IP address of the internal network adapter, the web site stops working. If I change it to the external network adapter IP address, the website works. In both cases the Public Folder problem persists.

Cause 2: It's not a new public folder. The folder I'm trying to open is named "Public Folders" as created by the SBS2000 server wizard.

Cause 3: Yes URLScan is installed, it's part of SBS2000. I have to assume IISLOCKD is installed as well. I have used method 1 in the attached article to eliminate the errors within the urlscan(date).log It did not impact the issue.

URLScan/IISLockdown are not part of SBS2000. These were released after SBS2000. Installing the .Net Framework will install them if they are not already there, IIRC. I suspect that this is the problem, because an automated install of the IISLockdown wizard implements the tightest lockdown. Installing it manually offers the opportunity to specify what sort of server is being locked down (and SBS is on the list).

You can uninstall the IIS Lockdown and URLScan without removing the Framework, I believe. You could then reinstall them manually, making sure to specify the correct server type when prompted.



IIS Configuration:

1. No, the only changes to IIS since before Public Folders stopped working was installing .NET and one or two recent patches from Microsoft. The last time public folders worked was about a month ago, so any patches released by MS since then are the ones we've applied, since I use a WSUS server for patching.

2. Screenshot of error attached.

You may get additional clues by trying to access the Public Folders through OWA. When ESM fails with this error, OWA usually fails too, but with a more precise error message.

--
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.
.

Relevant Pages

  • Re: no frontpage extensions in WinXP pro IIS 5.1 ???
    ... Try manually installing them: ... > I have had a very simple website for about 18 months on my computer under ... > me that my server doesn't have frontpage server extensions installed. ...
    (microsoft.public.inetserver.iis)
  • Re: Reinstall XP
    ... Now a good starting website for *installing* is the Microsoft website; ... even when i do reinstall it. ...
    (microsoft.public.windowsxp.general)
  • Re: OWA and STS
    ... To access STS i go to the server IP address, ... When installing SBS I did not supply disk 4 for outlook. ... Uninstall sharepoint - ... >You shouldn't remove FPSE from the Default Website. ...
    (microsoft.public.windows.server.sbs)
  • Replace XP Pro with XP Home
    ... reinstalling follow the directions EXACTLY for installing ... you don't have them they are also on the hp website. ... printer but the compatability stinks. ... >Will the notebook still function, ...
    (microsoft.public.windowsxp.general)
  • Re: IIS web services in W2K Professional
    ... installing IIS. ... >have the possibility to create another website. ... >Kristofer Gafvert - IIS MVP ... >www.ilopia.com - FAQ and Tutorials for Windows Server ...
    (microsoft.public.inetserver.iis)
Loading