OWA2003 NLB Cluster

Not as far as I can remember when I set this up on my test system a few months back. In OWA 2003 all of the work is essentially done on the back end and the front end is a proxy. So just install the OWA FE extensions and away you should go.

So can you be more specific with the trouble that you are getting? If you connect directly to the BE server does all OWA functionality work? If so then we are looking at an FE problem if not they the problem is not just your FE's

If you do get functionality on the BE then what do you not get through the FE's?

Thanks for the reply Paul.

The issue I am having is that when I select the ARCHIVE EXPLORER or SEARCH ARCHIVES buttons when external, the webpage it tries does not go through the evproxy.  I get a connect error - nothing like the blnk pages as stated in many support srticles.  My lab works fine but only has 1 fe server and no nlb.

eg lab goes to https://webiste.com.au/enterprisevaultproxy/archiv...
prod goes http://evservername/enterprisevault/archiveexplore...

The https and http above is also different though I am unsure why - it may have something to do with FBA that I am also testing.  My main goal is the EV options through OWA at this time FBA can be later. 

I do not administer firewalls/websites etc but have been informed that the configuration for both the lab and prod owa sites is the same (apart from the prod site using the nlb cluster name rather than the servername as in the lab).

I have even unistalled the owa extensions in both prod and lab and installed them in parallel at the same time, to ensure I was doing everything similarly, with no success.

I am sure this will be something very simple - I just can't see it !

OK so when you click on either AE or Search it will goto http://externalname.com/enterprisevaultproxy/archiveexplorerui.asp

Now this asp file actually resides on the EV server within the EVAnon Virtual Directory so because it does not exist on the FE a 404 IIS error is generated which calls a file called feproxy.asp.

You will get prompted for additional authentication due to another reason which I can go into later if required. I also have FBA configured as well.

So really to fully understand what is happening you would need to implement logging on the FE Server and the BE Server.

So I am a bit confused why your production system goes to http://evservername as your lab looks correct as a URL.

If you are going thgrough ISA or external firewall then you need to implement a rule as described here:-

http://swish.gpk.rnd.veritas.com/Technotes/Enterprise%20Vault%20for%20Microsoft%20Exchange/Technotes/283170.htm

I have just noticed that the Mailbox Policy, under OWA had DIRECT connect instead of USE PROXY like the lab.  It doesn't seem to have changed anything though (I have run provisioning and sync)

That link doesn't work for me  :(

That would do it so maybe that the sync of the change did not work properly. On your BE server find EVBackend.ini in C:\Program Files\Enterprise Vault\OWA.

exchangediagnostics=2
proxydiagnostics=2

Restart IE and login and you should get a logfile created in C:\Program Files\Enterprise Vault\OWA\Logging
Open up the log file and you should see an entry as such:-

[OWAPage::GetClientWebAppUrl] Client web app url: https://2003fe/enterprisevaultproxy/

Where 2003fe is your FE server or NLB Cluster Name in your case.

oops and yes that link will never work for you as it is an internal one!!!!! This is teh external one.

http://support.veritas.com/docs/283170

oops and yes that link will never work for you as it is an internal one!!!!! This is teh external one.

http://support.veritas.com/docs/283170

Is that link specific to ISA - we do not use it

I enabled loggin in BOTH the lab and prod.  I did not get any FE logging in prod but I did in LAB, what would this indicate ?

It would indicate that it is not hitting the BE server which would be correct if your url is still going to try and get to the EV server.

Can you paste in the following into a browser on your client in production:-

https://"name of nlbcluster"/enterprisevaultproxy/archiveexplorerui.asp

Obviously rename the first bit of the url with you NLB Cluster name or your FE server name.

After you enter credentials does AE show OK?

Do the same but replace archiveexplorerui,asp with searcho2k.asp

If they both show OK then the problem is just that your request when clicking on the toolbar button is not going to the correct URL.

I will try those.

Another thing to add.  After the first login with the logging up, it now takes forever to get in (I have usually killed the connect).  Turning logging back down and all is good.

I will also add the the two FE servers are both VM's (same chassis, different blade)

It does not work internally.  I can get to https://nlbname/exchange, or using owa1 or owa2 as servername internally, but the buttons still do not work. 

I think this is a step further as I thought they were working at one stage.

It works fo rthe lab (http://servername/enterprisevaultproxy/archiveexpl...)

EVFrontend.ini contains

ip1.exchangevirtualserver=owa1
ip2.exchangevirtualserver=owa1
ip2.exchangevirtualserver=nlbname
ip3.exchangevirtualserver=owa2

where ip1 is ip of owa1, ip2 is ip of nlb, and ip3 is ip of owa2.  The last two lines I added manually.

evbackend.ini

ip1.exchangevirtualserver=physical1
ip2.exchangevirtualserver=physical2
ip3.exchangevirtualserver=physical3
ip4.exchangevirtualserver=virtualexchange1
ip5.exchangevirtualserver=virtualexchange2

Found an error in my backend log which I can find nothing on the Symantec EV Support site

(sorry bout the formatting)

22/09/2009 4:28:27 PM : Debug   : ConfigurePublicFolderInfoStore       : Registering for : CN=Public Folder Store (BNE-EX2K3-V1),CN=CSQ Storage Group,CN=InformationStore,CN=BNE-EX2K3-V1,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=CORP,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=corp,DC=detir,DC=qld,DC=gov,DC=au
22/09/2009 4:28:27 PM : Debug   : ConfigurePublicFolderInfoStore       : Public folder LDAP query: <LDAP://CN=First Administrative Group,CN=Administrative Groups,CN=CORP,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=corp,DC=detir,DC=qld,DC=gov,DC=au>;(&(objectClass=msExchPFTree)(msExchPFTreeType=1)(msExchOwningPFTreeBL=CN=Public Folder Store (BNE-EX2K3-V1),CN=CSQ Storage Group,CN=InformationStore,CN=BNE-EX2K3-V1,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=CORP,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=corp,DC=detir,DC=qld,DC=gov,DC=au));name;subTree
22/09/2009 4:28:27 PM : Debug   : ConfigurePublicFolderInfoStore       : Found 1 matching public folder(s)
22/09/2009 4:28:27 PM : Debug   : ConfigurePublicFolderInfoStore       : Registering forms for public folder: Public Folders
22/09/2009 4:28:27 PM : Debug   : ConfigureSchema                      : Creating ADODB Connection...
22/09/2009 4:28:27 PM : Error   : ConfigureSchema                      : ADO connection error: -2146105340
22/09/2009 4:28:27 PM : Error   : ConfigureSchema                      : Failed to make ADO connection to: http://BNE-EX2K3-V1/exadmin/admin/corp.detir.qld.g...

Saw something on the forum stating this can happen if you logon domain is different from your smtp domain (which mine is)  This did work in the lab though.

Yeh you can ignore that error in this case as that is regarding getting the extensions working for your public folders. It is very difficult to investigate OWA issues over a forum as there are so many components to look into so it may be better if you raise a case with us so some proper analysis can be done for you.,

Thanks heaps Paul