cancel
Showing results for 
Search instead for 
Did you mean: 

EV 8.0 SP3 + Exchange 2007 + OWA = Archived Item Unavailable

LilWashu
Level 3
I have a new EV 8.0 SP3 install running on Windows Server 2008 SP2. We have a clustered Exchange 2007 mailbox server role and a CAS/HT server with the EV OWA extensions from the EV 8.0 SP3 CD installed on it. Exchange servers are running Windows 2003 SP2 x64 and Exchange 2007 SP1 rollup 6.

I have tested archiving on a mailbox and everything seems to work from an Outlook client. In OWA (testing inside our network but the same issue occurs externally) I get the EV shortcuts and can search the archive and open Archive Explorer successfully. However when I open an archived e-mail, I get the "Archived item is unavailable" error and attachments won't open.

I have turned on OWA logging and get the following errors:

1/27/2010 9:20:53 AM [6008,6] [WebDAVRequest::Send] Adding Depth header: 0
1/27/2010 9:20:53 AM [6008,6] [WebDAVRequest::Send] Request body: <?xml version="1.0"?><d:propfind xmlns:d="DAV:" ><d:prop><mapi:x0FFF0102 xmlns:mapi="http://schemas.microsoft.com/mapi/proptag/" /><exch:outlookmessageclass xmlns:exch="http://schemas.microsoft.com/exchange/" /></d:prop></d:propfind>
1/27/2010 9:20:53 AM [6008,6] [WebDAVRequest::Send] Exception sending WebDAV request: System.Net.WebException: The remote server returned an error: (404) Not Found.
   at System.Net.HttpWebRequest.GetResponse()
   at Symantec.EnterpriseVault.Owa.ExchangeStoreAccess.WebDAVRequest.Send()
1/27/2010 9:20:53 AM [6008,6] [EVServerRequest::CreateRequest] Sending request to: https://archive.blah.co.uk/EnterpriseVault/restoreo2k.asp?vaultid=11971E3B3DFECBE4EB34929D48384EA0A1... Items
1/27/2010 9:20:53 AM [6008,6] [EVServerRequest::CreateRequest] Request timeout (milliseconds): 30000
1/27/2010 9:20:53 AM [6008,6] [EVServerRequest::AddHeader] Set header: EV-OWA-2007-Extensions-Version=8.0.3.0
1/27/2010 9:20:53 AM [6008,6] [EVServerRequest::CreateRequest] Making request for user: DOMAIN\test
1/27/2010 9:20:53 AM [6008,6] [EVServerRequest::AddHeader] Set header: X-EVOWA-User-Encoded=54004D00430053004C004F00430041004C005C006D006A007400650073007400
1/27/2010 9:20:53 AM [6008,6] [RestoreRequest::Send] Exception sending request to restore item: System.Net.WebException: The remote server returned an error: (401) Unauthorized.
   at System.Net.HttpWebRequest.GetResponse()
   at Symantec.EnterpriseVault.Owa.EVServerRequests.RestoreRequest.Send()
1/27/2010 9:20:53 AM [6008,6] [RequestProcessor::RestoreAndActOnItem] Item not restored
1/27/2010 9:20:53 AM [6008,6] [Id::OwaId] Returning cached OwaId: RgAAAAAZ/jqrsI54Q7jcEvKFu4cnBwCXc/tnxIuGTbrysN9SS52QAOLcSI3jAACXc/tnxIuGTbrysN9SS52QAOLcSXcTAAAJ
1/27/2010 9:20:53 AM [6008,6] [RequestProcessor::RestoreAndActOnMailboxItem] Redirecting client to: /owa/?ae=Item&a=Open&t=ipm.note.enterprisevault.shortcut&id=RgAAAAAZ%2fjqrsI54Q7jcEvKFu4cnBwCXc%2ftnxIuGTbrysN9SS52QAOLcSI3jAACXc%2ftnxIuGTbrysN9SS52QAOLcSXcTAAAJ&EVItemUnavailable=1
1/27/2010 9:20:53 AM [6008,6] [RequestProcessor:StopImpersonation] Stopped impersonation
1/27/2010 9:20:53 AM [6008,6] Request processing finished

Having read through various KBs I have checked the authentication on the OWA and Exchange virtual directories - both are set to Basic. It was also mentioned that the EVAnon virtual directory should be checked but I don't seem to have one of these. Does anyone have any pointers on how to make this work?
1 ACCEPTED SOLUTION

Accepted Solutions

Gonz
Level 5
Employee

In the Enterprise Vault server, go to the IIS manager.

Expand Websites, Expand Default Web Site, you should have there a virtual directory called EVAnon.

If you have the EVAnon, the proceed as follows:
 

  1. Right click, edit the properties of the Website, go to the Directory Security Tab

 

  1. Click on the Edit button under "Authentification and access control" and Verify that Enable Anonymous Access checkbox it is marked and that an anoymous user it is specified.

 

  1. Click on the Edit button under "IP address and domain mail restrictions" and ensure that by default all computers should be denied access, and in Except the following you have listed the IP address of the CAS server.


If you do not have the EVAnon in the Enterprise Vault Server, you need to execute owauser.wsf in the Enterprise Vault Server
For OWA 2003 and OWA 2007, owauser.wsf creates (or updates) the virtual directory, EVAnon, that points to the Enterprise Vault\WebApp folder and assigns anonymous access permissions to the OWA anonymous user.

Please refer to the Setting Up Exchange Server Archiving in the documentation of the product for more info.

 

View solution in original post

3 REPLIES 3

bagrationi
Level 5
Approximately  same problem in my environment..................

Gonz
Level 5
Employee

In the Enterprise Vault server, go to the IIS manager.

Expand Websites, Expand Default Web Site, you should have there a virtual directory called EVAnon.

If you have the EVAnon, the proceed as follows:
 

  1. Right click, edit the properties of the Website, go to the Directory Security Tab

 

  1. Click on the Edit button under "Authentification and access control" and Verify that Enable Anonymous Access checkbox it is marked and that an anoymous user it is specified.

 

  1. Click on the Edit button under "IP address and domain mail restrictions" and ensure that by default all computers should be denied access, and in Except the following you have listed the IP address of the CAS server.


If you do not have the EVAnon in the Enterprise Vault Server, you need to execute owauser.wsf in the Enterprise Vault Server
For OWA 2003 and OWA 2007, owauser.wsf creates (or updates) the virtual directory, EVAnon, that points to the Enterprise Vault\WebApp folder and assigns anonymous access permissions to the OWA anonymous user.

Please refer to the Setting Up Exchange Server Archiving in the documentation of the product for more info.

 

LilWashu
Level 3
 Gonz: It was the lack of the EVAnon virtual directory and associated setup that did it - I read a guide that said that was no longer required with Exchange 2007 which is clearly wrong!

I have set it up now as per the instructions in the guide and it works great (although not from OWA Light but I guess we can't have everything). Thanks for your help.