Forum Discussion

Ain_t_No_Sunshi's avatar
13 years ago
Solved

Error running Evort - Virtual Directory (Failed)

Hi,

I have a distributed Exchange2007 SP3 CU8 environment running EV9.0.2. There are 2 Cas, 2 Hub, 2 mailbox servers and 2 Edge servers off in the dmz. EV to the Outlook client (Outlook2010) works without issue, but I can’t get EV to work with OWA. In an effort to troubleshoot the issue I’ve ran Evort, which fails to load the Exchange Configuration correctly.

The mailbox cluster and both CAS servers report status Passed. The 2 edge servers are unreachable (as I would expect), but the two hub servers report Failed – Virtual Directory(Failed).

Looking though the trace log I see the following:

 [WmiObjectBase.Connect] Trying to connect to path \\<FQDN of Hub Server>\root\MicrosoftIISV2

 [WmiObjectBase.Connect] Exception raised 'Invalid namespace '

 [ResultsData.GetVirtualDirectoryData] Failed to connect to server, 'Failed'

 

Since these are hub servers they don’t have IIS installed I’m not surprised this fails. Any ideas how I progress this?

Regards

Gary

  • Find out the URL being accessed when you get 'page not displayed' -right click and select properties in IE

    Then see what that resolves to from your client.

    Then check what is being done to pass that request to the correct server...

17 Replies

  • so when you go to the local CAS box all is ok....is it also the same when you go direct to the URL on the CAS...and is this ok for ALL CAS servers?

    Im guessing your original attempts were through the address pointing at the F5 load balancer? In other words it is the F5 missing rules...

     

  • Hi Jeff,

    I've had a word with the F5 guy, looks like the issue is dns/ EV server host name related.

    The issue when connecting to EV externally is that the Archive Explorer / Search Archives buttons link to EV using the hostname “ev01”. This resolves internally but will not work externally due to no domain etc. If we can fix the links in Webmail to use “ev01.gbsh.co.uk” then I can add this to external DNS and provide access through F5.

    Is there any where with either EV or OWA config files where I can set this?

    Regards

    Gary

     

  • Gary,

    Apart from the old traditional 'split DNS' options, you have the option of defining external URLS which are used when the input IP address/domain name matches. You do this in the web.config file, and additionally you can set the external web app url in the desktop policy.

    Have a read of the following tech doc - it covers multiple configuration scenarios and you should be able to find one that matches to your environment fairly closely.

    http://www.symantec.com/docs/TECH63250 

    Regards,

    Jeff

  • Hi Jeff,

    We’re getting there. smiley

    We’ve managed to get the OWA extensions working externally by adding a couple of keys to the web.config file on the CAS servers. I’m now able to retrieve an archived mail with attachment. The only remaining issues are with the ‘Search Archives’ and ‘Archive Explorer’ buttons. When these are clicked the resultant popup windows just displays page cannot be displayed.

    Regards

    Gary

     

     

     

  • Likely you are going to have to add rules to the F5 to point directly at the EV server when the requests are made. Archive explorer and search try and make a direct request to EV rather the request coming from OWA

    Regards,

    Jeff

  • Find out the URL being accessed when you get 'page not displayed' -right click and select properties in IE

    Then see what that resolves to from your client.

    Then check what is being done to pass that request to the correct server...

  • Sorted :-) A few changes have now been made to the F5 rules and we now have external access. Thanks Jeff for your help with this. Regards Gary