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

1. The Exchange organization directory name has not changed nor does it
contain question marks, parentheses or an asterisk.

2. I uninstalled URLScan. The problem persisted. I could not find
IISLockdown as an installed package through either Add/Remove Programs or
Add/Remove Windows Components. Could they be one and the same?

Further troubleshooting:

1. URLScan is still uninstalled until I can determine if IISLockdown is
part of URLScan or not.

2. Results from exchutil attached in private e-mail, as site-specific
information is enclosed.

3. We are using SBS2000, not 2003. I did find the log in the path given,
but the date on the file was from SBS installation, dated April 17th, 2004
which is when we built the server last.

4. Followed instructions for enabling full logging of w3svc1 service.
Reproduced the error, but no corresponding entries were placed in the w3svc1
log. There was no indication of an attempt to browse folders through ESM.
To make sure the logging was working I browsed our website, logged into OWA
and browsed public folders. The log indicates these actions without error
that I could see. This log was also sent privately.

Thanks again for working with me on this.


""Nathan Liu [MSFT]"" <v-natliu@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:22zoKWHrFHA.1208@xxxxxxxxxxxxxxxxxxxxxxxx
> Hi Dvord,
>
> Thank you for your reply.
>
> Also, many thanks for Steve and Susan's great input.
>
> I'm sorry for my mistake, I will send the ExchUtil.exe tool via email,
> please kindly check it.
>
> To troubleshoot this issue, please perform the below steps:
>
> 1. Please also check if the Exchange organization directory name or the
> Exchange site directory name contains characters that Exchange 2000 Server
> does not support. Exchange 2000/2003 Server does not support directory
> names that contain the following characters:
>
> - Question mark
> - Parentheses
> - Asterisk
>
> For more information, take a look at the article below:
> 822588 You receive a "The object is no longer available" message when you
> http://support.microsoft.com/?id=822588
>
> 2. Based on your description, I know you have installed IIS lockdown or
> URLScan tools. According to my knowledge, both tools may cause unexpected
> negative impact to OWA. In order to narrow down the issue, please
> temporarily uninstall IIS lockdown and URLScan tools, then verify whether
> the issue disappears.
>
> If the problem disappears after removing IIS Lockdown and URLScan, it
> proves that these tools caused the particular issue. So we can keep these
> tools uninstalled to work around this issue. However, if you are still
> willing to use these tools, please refer to the following article to
> correct the configuration of IIS lockdown or URLScan tools compatible with
> Exchange Server, please have a look at the following article.
>
> 309508 XCCC: IIS Lockdown and URLscan Configurations in an Exchange
> Environment
> http://support.microsoft.com/?id=309508
>
> If this issue still persists, please help me gather the below information
> for further troubleshooting:
>
> 1. Open the Urlscan.ini and Urlscan.log files in the following location:
> windir\System32\Inetsrv\Urlscan, paste the content of it in your reply.
>
> 2. Use the ExchUtil.exe tool to collect the information of the Exchange
> Server.
>
> 3. Please locate the Errorlog.txt from the ..\Program Files\Microsoft
> Integration\Windows Small Business Server 2003\Logs folder, and check
> whether there are any error messages noted on this issue, then paste the
> full context in your reply.
>
> 4. Please help me gather the IIS logs for checking. To enable the
> logging, please:
>
> (1) In Internet Information Services console, please open the Properties
> page of the web site.
> (2) In the Web Site tab, please check the option "Enable logging".
> (3) Select W3C Extended Log File Format from the list below.
> (4) Click the Properties button beside. In the General Properties tab,
> please confirm the following settings:
>
> Check the option Daily
> Check the option "Use local time for file naming and rollover"
> Confirm the setting for "Log file directory" to be
> "%WinDir%\System32\LogFiles"
>
> (5) In the Extended Properties tab, please check all the Extended
> Logging
> Options. Click OK. Click OK.
> (6) Then, reproduce the problem. All actions will be logged under the
> folder "C:\WINNT\System32\LogFiles\W3SVC#" (# is a number. The number for
> the Default Web Site is 1).
>
> To get additional detailed information, you may refer to the following KB
> article:
>
> 309508 IIS lockdown and URLscan configurations in an Exchange environment
> http://support.microsoft.com/?id=309508
>
> 328659 Error 80040E19 when you try to expand public folders in Exchange
> 2000
> http://support.microsoft.com/?id=328659
>
> 326444 How to configure the URLScan Tool
> http://support.microsoft.com/?id=326444
>
> I am appreciated your time and cooperation. If anything is unclear, please
> feel free to let me know. I am looking forward to hearing from you.
>
> Best regards,
>
> Nathan Liu (MSFT)
> Microsoft CSS Online Newsgroup Support
>
> Get Secure! - www.microsoft.com/security
> ======================================================
> This newsgroup only focuses on SBS technical issues. If you have issues
> regarding other Microsoft products, you'd better post in the corresponding
> newsgroups so that they can be resolved in an efficient and timely manner.
> You can locate the newsgroup here:
> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>
> When opening a new thread via the web interface, we recommend you check
> the
> "Notify me of replies" box to receive e-mail notifications when there are
> any updates in your thread. When responding to posts via your newsreader,
> please "Reply to Group" so that others may learn and benefit from your
> issue.
>
> Microsoft engineers can only focus on one issue per thread. Although we
> provide other information for your reference, we recommend you post
> different incidents in different threads to keep the thread clean. In
> doing
> so, it will ensure your issues are resolved in a timely manner.
>
> For urgent issues, you may want to contact Microsoft CSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.
>
> Any input or comments in this thread are highly appreciated.
> ======================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> --------------------
>>Reply-To: "Dvord Direwood" <dvord@xxxxxxxxxxx>
>>From: "Dvord Direwood" <dvord@xxxxxxxxxxx>
>>References: <uPdn9rYqFHA.3192@xxxxxxxxxxxxxxxxxxxx>
> <AM9yjtgqFHA.3520@xxxxxxxxxxxxxxxxxxxxx>
>>Subject: Re: SBS2K, Exch. 2K, Public Folder error 80040e19
>>Date: Fri, 26 Aug 2005 10:21:28 -0700
>>Lines: 544
>>Organization: Meteorlogical Destruction, Inc.
>>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>>X-RFC2646: Format=Flowed; Original
>>Message-ID: <OKvmbKmqFHA.564@xxxxxxxxxxxxxxxxxxxx>
>>Newsgroups: microsoft.public.windows.server.sbs
>>NNTP-Posting-Host: 67-134-35-34.dia.cust.qwest.net 67.134.35.34
>>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx.gbl
>>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:148163
>>X-Tomcat-NG: microsoft.public.windows.server.sbs
>>
>>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.
>>
>>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.
>>
>>3. I executed the steps to set to maximum all logging for the public
>>folders, I then reproduced the error and checked the system and
>>application
>>event logs for any entries. There were none.
>>
>>4. I did not see the exchutil tool attached to either this post or the
>>e-mail I received from you. I tried to find it on the web but didn't have
>>much luck.
>>
>>Thanks for the prompt reply, I look forward to working this through.
>>
>>
>>
>>""Nathan Liu [MSFT]"" <v-natliu@xxxxxxxxxxxxxxxxxxxx> wrote in message
>>news:AM9yjtgqFHA.3520@xxxxxxxxxxxxxxxxxxxxxxxx
>>> Hello Dvord,
>>>
>>> Thank you for posting in the SBS newsgroup.
>>>
>>> According to your description, I understand that you received the error
>>> message "The object is no longer available. Press F5 to refresh the
>>> display, and then try again. ID no. 80040e19 Exchange System Manager",
>>> when
>>> you access the Public Folders in the Exchange System Manager (ESM). If I
>>> have misunderstood your concern, please don't hesitate to let me know.
>>>
>>> To narrow down this issue, please answer and perform the below questions
>>> and steps:
>>>
>>> 1. As you mentioned, can I assume you have installed the .NET
>>> Framework
>>> software? Let's temporarily uninstall the .NET software, then check if
> the
>>> issue can be reproduced. Alternatively, you may do the lasted update for
>>> the .NET software:
>>>
>>> NET Framework Downloads
>>>
> http://www.microsoft.com/downloads/results.aspx?productID=&freetext=.net+fra
>>> mework&DisplayLang=en
>>>
>>> 2. As you mentioned, you have tried the KB article 309508, 325920,
> 282125
>>> and 822588, but it still didn't work. Based on my research on this
>>> error,
>>> I
>>> find the many causes for this kind of issue.
>>>
>>> Cause 1: The issue is caused by the incorrect IP address assigned to the
>>> default Web site.
>>>
>>> If it is the case in your side, please follow the instruction in the
>>> article below.
>>>
>>> 325923 You Cannot Expand Public Folders Through Exchange System Manager
>>> http://support.microsoft.com/?id=325923
>>>
>>> Cause 2: The error 80040e19 may indicate that the name you are using for
>>> the new public folder contains invalid characters which are disallowed
>>> by
>>> Active Directory.
>>>
>>> For your reference, the following list shows the valid characters that
> you
>>> can use in your Exchange 2000 or Exchange 2003 Directory object names:
>>>
>>> - A through Z
>>> - a through z
>>> - 0 through 9
>>> - Space
>>> - Hyphen/dash
>>>
>>> The following characters are the characters that you must not use in
>>> your
>>> Exchange 2000 or Exchange 2003 directory object names:
>>>
>>> ~ ` ! @ # $ % ^ & * ( ) _ + = { [ } ] | \ : ; " '' < , > . ? /
>>>
>>> Cause 3: The issue will appear if there are IISlockD or URLScan
>>> installed
>>> on the Exchange server. Please first check if these tools are installed
> or
>>> not. If
>>> these tools are installed, please troubleshoot the issue according to
>>> the
>>> instructions documented in the following article:
>>>
>>> XADM: Error 80040E19 When You Try to Expand Public Folders
>>> http://support.microsoft.com/?id=328659
>>>
>>> If the issue persists after the steps above, it seems related to IIS
>>> configuration. In order for me to identify the issue precisely, please
>>> collect the following information.
>>>
>>> 1. Have you changed the settings in your IIS recently that might cause
>>> this
>>> issue?
>>>
>>> 2. Please do a screen capture of this issue, and attach it in your
>>> reply.
>>>
>>> 3. In Exchange System Manager, please right-click the server, choose
>>> properties, click "Diagnostic Logging" tab, expand MSExchangeIS and set
>>> all
>>> options in Public to maximum. And reproduce the issue, and then check
>>> the
>>> application and system event logs, paste the contents of the logs in
>>> your
>>> reply.
>>>
>>> 4. Exchutil Summary
>>>
>>> ExchUtil is a tool that can be used to collect information to aid in
>>> troubleshooting many Exchange issues. Please create a folder named
>>> ExchUtil
>>> on the Exchange 2000 server, copy the ExchUtil.exe tool I include in
>>> this
>>> e-mail to this folder. Run cmd to open the command prompt line window
>>> and
>>> enter the ExchUtil folder. Run the following command:
>>>
>>> exchutil /all
>>>
>>> After the command is completed, two files (Summary_<ServerName>.htm and
>>> Full_<ServerName>.txt) will be created in the same folder. Please also
>>> paste the contents of the files in your reply.
>>>
>>> I am appreciated your time and cooperation. If anything is unclear,
> please
>>> feel free to let me know. I am looking forward to hearing from you.
>>>
>>> Best regards,
>>>
>>> Nathan Liu (MSFT)
>>> Microsoft CSS Online Newsgroup Support
>>>
>>> Get Secure! - www.microsoft.com/security
>>> ======================================================
>>> This newsgroup only focuses on SBS technical issues. If you have issues
>>> regarding other Microsoft products, you'd better post in the
> corresponding
>>> newsgroups so that they can be resolved in an efficient and timely
> manner.
>>> You can locate the newsgroup here:
>>> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>>>
>>> When opening a new thread via the web interface, we recommend you check
>>> the
>>> "Notify me of replies" box to receive e-mail notifications when there
>>> are
>>> any updates in your thread. When responding to posts via your
>>> newsreader,
>>> please "Reply to Group" so that others may learn and benefit from your
>>> issue.
>>>
>>> Microsoft engineers can only focus on one issue per thread. Although we
>>> provide other information for your reference, we recommend you post
>>> different incidents in different threads to keep the thread clean. In
>>> doing
>>> so, it will ensure your issues are resolved in a timely manner.
>>>
>>> For urgent issues, you may want to contact Microsoft CSS directly.
>>> Please
>>> check http://support.microsoft.com for regional support phone numbers.
>>>
>>> Any input or comments in this thread are highly appreciated.
>>> ======================================================
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>>
>>> --------------------
>>>>Reply-To: "Dvord Direwood" <dvord@xxxxxxxxxxx>
>>>>From: "Dvord Direwood" <dvord@xxxxxxxxxxx>
>>>>Subject: SBS2K, Exch. 2K, Public Folder error 80040e19
>>>>Date: Thu, 25 Aug 2005 08:38:05 -0700
>>>>Lines: 27
>>>>Organization: Meteorlogical Destruction, Inc.
>>>>X-Priority: 3
>>>>X-MSMail-Priority: Normal
>>>>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>>>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>>>>X-RFC2646: Format=Flowed; Original
>>>>Message-ID: <uPdn9rYqFHA.3192@xxxxxxxxxxxxxxxxxxxx>
>>>>Newsgroups: microsoft.public.windows.server.sbs
>>>>NNTP-Posting-Host: 67-134-35-34.dia.cust.qwest.net 67.134.35.34
>>>>Path:
>>>
> TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP1
>>> 0.phx.gbl
>>>>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:147777
>>>>X-Tomcat-NG: microsoft.public.windows.server.sbs
>>>>
>>>>This is an oft-reported problem, yet few solutions are found.
>>>>
>>>>When opening Public Folders within the Exchange System Manager, the
>>>>following error occurs:
>>>>
>>>>"The object is no longer available. Press F5 to refresh the display,
>>>>and
>>>>then try again.
>>>>ID no. 80040e19
>>>>Exchange System Manager"
>>>>
>>>>Before you answer back with an article number please look at the list
> I've
>>>>tried and haven't worked:
>>>>
>>>>309508, 325920, 282125 and 822588
>>>>
>>>>The port did not change, it's still port 80. URLScan logs don't show
>>>>any
>>>>errors related to opening public folders with the Exchange System
> Manager.
>>>>
>>>>I suspect .NET, since I detected the problem after it was installed.
> Does
>>>>ANYONE know that .NET will not play well with IIS and Exchange 2000 on
>>> Small
>>>>Business Server 2000? Installing .NET is the ONLY thing that changed on
>>> the
>>>>server prior to the error occurring with ESM.
>>>>
>>>>Usually I can find a workaround for something but I'm hitting a brick
> wall
>>>>here.
>>>>
>>>>
>>>>
>>>
>>
>>
>>
>>
>>---------------------------------------------------------------------------
> -----
>>
>>
>>
>>
>>
>>
>


.