RE: SBS2K, Exch. 2K, Public Folder error 80040e19
- From: v-natliu@xxxxxxxxxxxxxxxxxxxx ("Nathan Liu [MSFT]")
- Date: Fri, 26 Aug 2005 06:57:10 GMT
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.
>
>
>
.
- Follow-Ups:
- RE: SBS2K, Exch. 2K, Public Folder error 80040e19
- From: Dvord Direwood
- RE: SBS2K, Exch. 2K, Public Folder error 80040e19
- References:
- SBS2K, Exch. 2K, Public Folder error 80040e19
- From: Dvord Direwood
- SBS2K, Exch. 2K, Public Folder error 80040e19
- Prev by Date: RE: Setting up a VPN through SBS 2003
- Next by Date: RE: Cannot run wizards after SBS SP1 install
- Previous by thread: SBS2K, Exch. 2K, Public Folder error 80040e19
- Next by thread: Re: SBS2K, Exch. 2K, Public Folder error 80040e19
- Index(es):
Relevant Pages
|
Loading
