Knowledge Base

You receive an "80040E19" error message when you try to connect to public folders by using Exchange System Manager

Article ID: 282125

Article Last Modified on 12/3/2007

APPLIES TO

Microsoft Exchange Server 2003 Standard Edition
Microsoft Exchange Server 2003 Enterprise Edition
Microsoft Exchange 2000 Enterprise Server
Microsoft Exchange 2000 Server Standard Edition
Microsoft Exchange Server 5.5 Standard Edition
Microsoft Windows Small Business Server 2003 Premium Edition
Microsoft Windows Small Business Server 2003 Standard Edition

This article was previously published under Q282125

This article is a consolidation of the following previously available articles: 319240, 328659, and 282125.

SYMPTOMS

When you try to connect to public folders by using Exchange System Manager, you receive the following error message:

The Object is no longer available. Press F5 to refresh the display, and then try again.

ID no: 80040E19
Exchange System Manager

CAUSE

This issue may occur for one of the following reasons:

A misconfigured TCP port
The default configuration of the IISLockdown or URLScan security tools
Multiple or incorrect IP addresses
An incompatible directory name from Microsoft Exchange Server 5.5
An incorrect virtual directory path in IIS
The HTTP virtual service is not started
An incorrect host header

RESOLUTION

A misconfigured TCP port
This error message may occur if the virtual server that hosts the Exadmin virtual folder has been set to use a port other than port 80 for the bound interface. Exchange System Manager requests information about public folders by using an HTTP request to the Exadmin virtual folder. Therefore, the virtual server that contains Exadmin must use port 80.

To resolve this issue, configure the virtual server that hosts the Exadmin virtual folder to use port 80. Additionally, make sure that the Loopback interface that is configured for the virtual server is set to use port 80. To confirm the port number that the virtual server uses, follow these steps:
1. Click Start, point to Programs, point to Administrative Tools, and then click Internet Services Manager.
2. Expand the list of virtual servers.
3. Expand the list of virtual folders for each virtual server until you see the Exadmin virtual folder.
4. Right-click the virtual server on which the Exadmin virtual folder is located, and then click Properties.
  
  Note The virtual server on which the Exadmin virtual folder is located is typically the default Web site. However, the Exadmin virtual folder can be on any virtual server that is using port 80.
5. Click the Web Site tab. Verify that the TCP port is set to use port 80.
6. Next to the IP Address box, click Advanced, and then verify that the Loopback address, if one is present, is configured to use port 80.
If you have more than one virtual server and if one of the virtual servers is set to use port 80, you can copy the Exadmin virtual folder to that server. For more information about how to move the Exadmin virtual folder to the server on port 80, click the following article number to view the article in the Microsoft Knowledge Base:

325920 Error message when you view public folders in Exchange System Manager

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

313721 Error message: "The requested operation is forbidden" when you try to modify a public folder
The default configuration of the IIS lockdown or URLScan security tools
This issue may occur because the default configuration of the IISLockdown and URLScan security tools assumes that the server is serving static content only. Microsoft Exchange 2000 Server components use Web Distributed Authoring and Versioning (WebDAV) and other HTTP verbs that are not allowed by the default configuration. Exchange Server 5.5 components use Active Server Pages (ASP) pages. ASP pages are disabled by the default configuration.

To resolve this issue, follow these steps:
1. Open the Urlscan.ini file in the following location:
  
  windir\System32\Inetsrv\Urlscan
2. Modify the Urlscan.ini file based on the Exchange computer role.
If you experience additional difficulties when you try to make HTTP requests with URLScan enabled, examine the Urlscan.log file for the list of requests that are being rejected. The default location of the Urlscan.log file is as follows:

windir\System32\Inetsrv\Urlscan

The URLscan configuration file for Exchange System Manager management of public folders is as follows:
```
[Options] 
UseAllowVerbs=1 
UseAllowExtensions=0 
NormalizeUrlBeforeScan=1 
VerifyNormalization=1 
AllowHighBitCharacters=1 
AllowDotInPath=1 
RemoveServerHeader=0 
EnableLogging=1 
PerProcessLogging=0 
AllowLateScanning=0 

[AllowVerbs] 
PROPFIND 
SEARCH 
PROPPATCH 
DELETE 
MKCOL 
MOVE 
COPY 
OPTIONS 

[DenyVerbs] 

[DenyHeaders] 
If: 
Lock-Token: 

[DenyExtensions] 
.asp 
.cer 
.cdx 
.asa 
.exe 
.bat 
.cmd 
.htw 
.ida 
.idq 
.htr 
.idc 
.shtm 
.shtml 
.stm 
.printer 
.ini 
.log 
.pol 
.dat 
```
Note You can add ".com" to the DENYEXTENSIONS list if the internal Domain Name System (DNS) does not contain ".com."
```
[DenyUrlSequences] 
.. 
./ 
\ 
% 
& 
```
For more information about IISLockdown and URLScan configuration in Exchange 2000 and in Exchange Server 5.5, click the following article number to view the article in the Microsoft Knowledge Base:

309508 IIS lockdown and URLscan configurations in an Exchange environment

For more information about the URLScan tool, click the following article number to view the article in the Microsoft Knowledge Base:

326444 How to configure the URLScan tool

For more information about the URLScan tool, read the Urlscan.txt file. The Urlscan.txt file is located in the c:\systemroot\System32\Inetsrv\Urlscan folder.
Multiple or incorrect IP addresses
This issue may occur if all the following conditions are true:
- There are multiple Web sites (virtual servers) that are configured on the Exchange computer.
- The network adaptor is assigned multiple IP addresses.
- The IP address that is assigned to the default Web site is not the first address that is assigned to the network adaptor.
- A host header entry exists that has an IP address that does not exist.
  
  To resolve this issue, set the default Web site to use the first IP address to which the network adaptor is assigned. To do this, follow these steps:
  1. Right-click My Computer, and then click Manage.
  2. Double-click Service and Applications, double-click Internet Information Services, and then right-click Default Web Site.
  3. Click Properties, and then click the Web Site tab.
  4. Click the arrow in the IP Address box, and then click the first IP address that is assigned to the network card.
    
    To identify the first IP address that is assigned to the network card, follow these steps:
    1. Click Start, point to Settings, and then click Network and Dial-up Connections.
    2. Right-click Local Area Connection, and then click Properties.
    3. Click Internet Protocol (TCP/IP), click Properties, and then click Advanced.
    4. Note the first IP address that is listed under IP Addresses.
    5. Click Cancel three times.
  5. Click OK to close the Default Web Site Properties dialog box.
  6. Reopen Exchange System Manager, and then expand Public Folders.
    
    For more information about the "80040E19" error message that you receive when you try to access public folders, click the following article number to view the article in the Microsoft Knowledge Base:
    
    325920 Error message when you view public folders in Exchange System Manager
An incompatible directory name from Exchange Server 5.5
This issue occurs if the Exchange organization directory name or the Exchange site directory name contains characters that Exchange 2000 and Microsoft Exchange Server 2003 do not support.

Exchange 2000 and Exchange 2003 do not support directory names that contain the following characters:
- A question mark (?)
- Parentheses (( ))
- An asterisk (*)
To resolve this issue if the prohibited characters exist only in the display name of the organization or the site, change the display name of the organization or the site by using the Microsoft Exchange Administrator tool so that the organization name or the site name does not contain these characters. If this issue persists after you modify the display name of the organization or the site, push a replica of the public folder data to the Exchange 2000 computer or to the Exchange 2003 computer.

If the directory name of the organization or the site contains the prohibited characters, we recommend that you not install Exchange 2003 or Exchange 2000 to join this organization. If you do install Exchange 2000 or Exchange 2003, this issue will persist in your public folders. Instead, consider migrating to a new Exchange organization that does not contain the prohibited characters.

For more information about the incompatible directory name from Exchange Server 5.5, click the following article number to view the article in the Microsoft Knowledge Base:

822588 You receive a "The object is no longer available" message when you expand Public Folders in Exchange System Manager in Exchange 2000 or in Exchange 2003
An incorrect virtual directory path in IIS
This issue may occur for either of the following reasons:
- The Exadmin virtual directory is missing or was renamed.
- The local path of the Exadmin virtual directory points to an incorrect directory.
Exchange System Manager uses HTTP to connect to a public folder store and connects to the Exadmin virtual directory under the default Web site. This virtual directory is created by the Setup program during installation. If this virtual directory is missing or was renamed, Exchange System Manager cannot connect to the public folders on this server, and you may receive the error message that is mentioned in the "Symptoms" section.

If the Exadmin virtual directory was deleted, run the Setup program from the Exchange CD to reinstall the virtual directory. The Setup program recognizes that this virtual directory is missing and re-creates the virtual directory. If the Exadmin virtual directory was renamed, rename the virtual directory back to "Exadmin."

If the issue still exists, examine the local path of the Exadmin virtual directory. To do this, follow these steps:
1. Start Internet Information Services Manager on the Exchange computer.
2. Expand Default Web Site.
3. Right-click the Exadmin virtual directory, and then click Properties.
4. Verify that the local path on the Virtual Directory tab points to \\.\BackOfficeStorage.
  
  Note If you make any changes to the configuration, stop and then restart the default Web site.
If the Exadmin virtual directory was deleted, you cannot re-create it by using the Internet Information Services (IIS) snap-in. Additionally, you cannot use the user interface to add many of the entries that are added during setup.
The HTTP virtual service is not started
On a clustered Exchange-based computer, you can stop the HTTP virtual service by using Cluster Administrator. If the HTTP server is stopped, you may receive the error message that is mentioned in the "Symptoms" section when you try to connect to public folders in Exchange System Manager.
An incorrect host header
If the Web site that the Exadmin virtual directory is a member of does not have a blank host header name, you may receive the error message that is mentioned in the "Symptoms" section.

To resolve this issue, verify that the Web site has a blank host header name. To do this, follow these steps:
1. Start Internet Services Manager, and then open the properties of the default Web site.
2. Click Advanced.
3. Make sure that a valid IP address has been entered and that the host header name is blank.
The Exchange System Manager uses the network basic input/output system (NetBIOS) name of the computer to try to connect to its management server by using HTTP. In Exchange-based cluster servers, if host headers are configured, they should be the NetBIOS names of the Exchange virtual servers or the NetBIOS names of the nodes.

Additional query words: 80040E19 esm exch2kp2w ism XADM

Keywords: kberrmsg kbprb KB282125

Microsoft KB Archive/282125

Contents