Unable to connect to Enterprise Vault 7.5 SP6 from Microsoft Exchange 2003 OWA

[MPR]

I just upgraded Enterprise Vault 7.5 SP3 to SP6 (Long story but I can't move to EV2008 yet) Everything seems to work fine through Outlook. If I use a IE link to http:///EnterpriseVault/ArchiveExplorerUI.asp or http:///enterprisevault/search.asp I can search or explore the archive(s) with no problem. If someone tries to access an archived item from within OWA however, they get the message below: [i]The archived item is currently unavailable.[/i] [i]If you choose reply or forward, only the content shown below will be included. [/i] [i]Click here to preview the original item. [/i] If they try to access the Archive Explorer or Search Archives via the links on the left margin of OWA, you get a HTTP Error 403.6 - Forbidden: IP address of the client has been rejected from inside or outside the local network. The link it shows in the address bar is [i]http://mail./enterprisevaultproxy/archiveexplorerui.asp?OWA2003=1&OWA2003Url=http%3A%2F%2F%2Fexchange%2F%40%2F&mbx=&server=[/i] I am assuming we have a problem with the proxy setup on the Exchange server. When I run BackEnd2003Setup.wsf I get the following error in the log: [i]7/22/2010 12:03:00 PM : Error : ConfigureSchema : ADO connection error: -2146105340 [/i] [i]7/22/2010 12:03:00 PM : Error : ConfigureSchema : Failed to make ADO connection to: http:///exadmin/admin/corp.mpr.com/Public%20Folders/%23%23SchemaURI%23%23/[/i] Thanks for any help you can give me.

[Mohawk_Marvin]

Does the ExchangeServers.txt file have all the IP's of the Exchange Servers in it? I suspect not because of the 403 error.
Add all the relevant IP's and then re-run the OWA set up scripts.

[MPR]

There was an erro in the ExchangeServers.txt on our EV server.  I fixed it and ran BackEnd2003Setup.wsf again, any other scripts I need to run?  Still got the error mentioned in the first post.

More importantly, the OWA is still not connecting correctly.  BTW, we are only running one Exchange 2003 server (we don't have a front-end server).

[Mohawk_Marvin · Accepted solution]

There is another script to run. Try running the owauser.wsf script. Destruction on this in this TN
http://seer.entsupport.symantec.com/docs/295497.htm

[MPR]

Thanks Mohawk!  That worked.  Made an error entering the IP address in ExchangeServers.txt and that caused me all these headaches.  After running OWAUSER.WSF everything seems to be resolved.  Thanks for the help!