The error "The remote server returned an error: (404) Not Found." is displayed when attempting to view an item using OWA (Outlook Web Access).

Article:TECH50232  |  Created: 2006-01-23  |  Updated: 2014-08-17  |  Article URL http://www.symantec.com/docs/TECH50232
Article Type
Technical Solution


Issue



The error "The remote server returned an error: (404) Not Found." is displayed when attempting to view an item using OWA (Outlook Web Access).


Error



The remote server returned an error: (404) Not Found.


Solution




Overview:

The error "The remote server returned an error: (404) Not Found." is displayed when attempting to view an item using OWA (Outlook Web Access) because IIS is not configured properly or the Web services on the Enterprise Vault server is not configured properly. Refer to Figure 1 and Figure 2 to view the behavior. In Figure 1 click on the banner that reads "The archived item is currently unavailable." and the 404 error will be displayed as in Figure 2.

Figure (1)
 

Figure (2)
 


Resolution:
 
1. Follow Enterprise Vault technical note TECH48560 in the Related Documents section of this article first to verify the "Proxy.asp" and the "Feproxy.asp" have been properly configured on the Exchange backend and frontend  servers. If the 404 custom errors are correct on the Exchange server then the next step is to check the configuration on the Enterprise Vault server.
 
2. On the Enterprise Vault Directory server verify that the "EVAnon" virtual directory has the proper path configured in IIS.
 
a. Open the IIS Manager on the Enterprise Vault server.
 
b. Expand "Default Web Site". (The EV virtual directories may be on a different Web site.)
 
c. Right click on the "EVanon" directory then click on "Properties". Verify that the "Local path" location is correct. Click on the "Browse" button to verify the path is correct. An incorrect path to the Webapp directory will cause a 404 error.
 
d. Click "OK"  to close the window.
 
3. On the Enterprise Vault Directory server verify the following:
 
a. Open IIS.
 
b. Click on "Web Service Extensions"
 
c. Verify that "Active Server Pages" and "ASP.NET" are allowed.
 


 



Legacy ID



286680


Article URL http://www.symantec.com/docs/TECH50232


Terms of use for this information are found in Legal Notices