cancel
Showing results for 
Search instead for 
Did you mean: 

EV 11 Outlook 2010 Do not show archived elements with LTE

MON_AB
Level 4

Hello guys,

we have the following constellation:

+ EV 11.0.1.3683 AND Exchange 2013 AND Outlook 2010 with Win7/10

I am able to see inside the local network all archived mails including the attachments, because I have installed the EV addin in Outlook.

I am able to see on OWA 2013 all archived mails including the attachments, because I have bought and installed a SSL certificate and forwarded 443 to the EV server on the firewall.

But when I have a Windows 7/10 tablet with Outlook 2010 and installed EV addin, it is not possible to open attachments of archived mails over LTE. (Not connection on the LAN) I thought this would works as well after the changes I made for the OWA access. Or do I have to make something additional? In this moment I get the message in outlook that the server cannot be found.

The target would be that the users have only internet access and are able to access the archived attachments.

Using the OWA for that, is quite slow and therefore I was hoping there is a possibilily to access the attachments right away from outlook itself and maybe a little bid faster that OWA.

Any ideas, or advices?

1 ACCEPTED SOLUTION

Accepted Solutions

It sounds like all the forwarding stuff is correct. The problem is that your Outlook Add-in is still using the internal URL ("DefaultWebAppURL") instead of the RPCOVERHTTPPROXYURL that you have set.

 

In your client log, a few hundred lines from the start, you should see something like the following:

15/01/2018 10:00:28.490[10652][H]: Environment:
15/01/2018 10:00:28.490[10652][H]:     Enterprise Vault Client 12.1.0.1424 (Full functionality enabled)
15/01/2018 10:00:28.491[10652][H]:     Microsoft Windows 10 Professional (build 16299), 64-bit
15/01/2018 10:00:28.491[10652][H]:     Intel(R) Core(TM) i7-6650U CPU @ 2.20GHz Intel64 Family 6 Model 78 Stepping 3;
15/01/2018 10:00:28.492[10652][H]:     Microsoft Outlook 2016 Click-to-Run, 64-bit (16.0.0.8730)
15/01/2018 10:00:28.492[10652][H]:         [RPC over HTTP not enabled]
15/01/2018 10:00:28.492[10652][H]:     Microsoft Internet Explorer 11.125.16299.0

In this section you can see whether the Outlook Add-in has detected that RPC over HTTP is enabled or not. (In my example above it is not enabled.)

The RPCOVERHTTPPROXYURL won't be used unless the Add-in detects that RPC over HTTP is enabled. Ordinarily, we detect this state by looking for the MAPI property "PR_ROH_FLAGS" in the profile.

15/01/2018 10:00:28.416[10652][L]: DesktopCommon::UseRPCOverHTTP: Read PR_ROH_FLAGS: 0x0
15/01/2018 10:00:28.417[10652][M]: Could not find PR_ROH_FLAGS
15/01/2018 10:00:28.417[10652][H]: RPC over HTTP is not enabled (flags = 0)
15/01/2018 10:00:28.417[10652][L]: ~DesktopCommon::UseRPCOverHTTP: Read PR_ROH_FLAGS: 0x40380

There is a known issue with this detection on Outlook 2016; I haven't heard of this affecting Outlook 2010, but perhaps it's worth trying that solution anyway, since it's just upgrading the EV Outlook Add-in. You can download the 12.2.2 (current latest ) Outlook Add-in from this article; try that and see if the detection of the RPC over HTTP state is improved. It should go without saying, but do not attempt to upgrade anything else in your EV 11 environment with that download; just use the installers in the "...\Veritas Enterprise Vault\Outlook Add-In" folder to upgrade the Add-in on the LTE device.

 

--Chris

View solution in original post

10 REPLIES 10

VirgilDobos
Moderator
Moderator
Partner    VIP    Accredited Certified

Hi mate,

Is the EV server URL reachable from outside the LAN?

--Virgil

I bought a SSL certificate bound to an external DNS record. f.i. ev.test.com

Behind the ev.test.com is an official IP address.

On the company firewall I forwarded inbound traffic from this official ip address and port 443 to the local ip address of my enterprise vault server. That's the reason why it is working on the OWA accessing the archived attachment when accessing it from an external computer.

Do I need to open additional ports to make it work with an outlook 2010 client?

Or are there special settings which I need to enter on the EV Addin on Outlook?

Over which protocoll communicates the outlook 2010 with the EV server when it tries to access the attachments of archived items?

If you have got external access working well for OWA, then you've done the hard part (publishing, forwarding, etc.).

The piece you're missing is the Exchange Desktop Policy setting "Alternative Web Application URL" (also called "RPC Over HTTP Proxy URL" in earlier versions). The setting can be found on the Advanced tab, under the list of settings for Outlook. Set it to the externally published address of your EV server, e.g., https://ev.test.com. This tells the Outlook Add-in "If you can't connect using the regular web application URL, you might be on an external network, so try this other URL before conceding failure."

Set the policy, sync the mailbox, and then give it another go from your LTE connection. If it still doesn't work, include a client trace with your next post to help us troubleshoot.

 

--Chris

Thanks for the reply.

I have entered now vault.test.com in the "Web Application URL" in my default Desktop Policy.

Clicked on Synchronize and waited 1 hour.

Then I logged in on my tablet with a LAN Adaptor, and opened Office 2010. So I thought it would get all new informations from the EV server via LAN.

Then I disabled LAN and activated my LTE SIM card.

I started Outlook 2010 and tried to open a mail with attachment.

But I got the response that the server is not reachable.

Then I made the client trace.

It seams that the record which I set, wasn't properly updated.

Because I can't find vault.test.com in the client trace. Only a lot of other records and names of my local network.

--

Intranet Zone Trusted Sites:

mail.test.com

ev.test.lan

mail.test.lan

evsrv1.test.lan

evsrv1

 

ADDSERVERTOINTRANETZONE = mail.test.lan;evsrv1.test.lan;mail.test.com

DEFAULTWEBAPPURL = http://ev.test.lan/EnterpriseVault

EVSERVERS = ev.test.lan;EVSRV1;

OWAWEBAPPURL = http://ev.test.lan/EnterpriseVault

Value: ev.test.lan; EVSRV1;

Value: mail.test.lan;evsrv1.test.lan;mail.test.com

Value: http://ev.test.lan/EnterpriseVault

Value: http://ev.test.lan/EnterpriseVault

HaveConnection::ExecuteTest - Connection test to: ev.test.lan/EnterpriseVault/clienttest.gif failed

Downloading from: http://ev.test.lan/EnterpriseVault/download.asp?VaultID=1C911110000evserver&SaveSetID=208128539C6841...

Downloading: http://ev.test.lan/EnterpriseVault/download.asp?VaultID=1C1110000evserver&SaveSetID=201701~2000~Z~70...

HaveConnection::ExecuteTest - Connection test to: ev.test.lan/EnterpriseVault/clienttest.gif failed

RPCOVERHTTPPROXYURL = https://mail.test.com/

 

Attached you will find some screenshots from my EV environment.

mail.test.lan is the local dns name of our mailserver.

evsrv1.test.lan is the local dns name of my EV server.

mail.test.com ist the external AND local dns name of our mailserver.

ev.test.lan is an alias for the local dns name of our EV server.

vault.test.com is the external dns name for our EV server. (Which we use at the moment for accessing the attchments of archived items via OWA)

 

 Any ideas and suggesttions why it is not working?

 

You put the vault.test.com in the wrong setting. You say you put it in "Web Application URL", which is not what we need here. The setting you need is called "RPC over HTTP Proxy URL" in version 11. (In version 12.1 we changed the name to "Alternative Web Application URL"). Sorry I didn't make that clearer last time.

--Chris

No problem, I am happy for every help I can get. :)

Now I entered https://vault.test.com/EnterpriseVault in RPC over HTTP connection and left Web Application URL blank. (see attached picture)

But when I try to open a mail with archived attachment, it still says that the server is not reachable.

When I look into the logs, I can see now that the entry is now changed: RPCOVERHTTPPROXYURL = https://vault.test.com/EnterpriseVault

So that looks good from this spot.

But in the logs I can see, that when I try to open an archived mail/attachment it is still refering to the alias name of the EV server. (evsrv1.test.lan)

http://evsrv1.test.lan/EnterpriseVault/download.asp?VaultID=1C9E000evsrv1&SaveSetID=201704~Z~701D1&F...

 

When I change this record to https://vault.test.com and copy paste it on my LTE tablet, I get a login prompt. When I login properly I can download the archive mail/attachment. So the forwarding of the firewall via HTTPS is working properly.

 

https://vault.test.com/EnterpriseVault/download.asp?VaultID=1C9E000evsrv1&SaveSetID=201704~Z~701D1&F...

 

Now the only thing which is left is that the Outlook should point automatically to https://vault.test.com instead of http://evsrv1.test.local. So the overwriting is not working or Outlook Client is not notified to use the RPC Link.

 

Any ideas what I have to do, to complete that part. Am I am missing a final setting?

 

I checked in addition our exchange 2013 and the Outlook Anywhere is working properly.

For the external and internal name mail.test.com has been entered.

 

Is this a problem when we use mail.test.com for the Outlook Anywhere and OWA?

And parallel vault.test.com for the EV Server?

 

443 on mail.test.com from external is forwarding to our mailserver.

443 on vault.test.com from external is forwarding to our EV server.

Both have different SSL certificates.

Any ideas about this problem?

It sounds like all the forwarding stuff is correct. The problem is that your Outlook Add-in is still using the internal URL ("DefaultWebAppURL") instead of the RPCOVERHTTPPROXYURL that you have set.

 

In your client log, a few hundred lines from the start, you should see something like the following:

15/01/2018 10:00:28.490[10652][H]: Environment:
15/01/2018 10:00:28.490[10652][H]:     Enterprise Vault Client 12.1.0.1424 (Full functionality enabled)
15/01/2018 10:00:28.491[10652][H]:     Microsoft Windows 10 Professional (build 16299), 64-bit
15/01/2018 10:00:28.491[10652][H]:     Intel(R) Core(TM) i7-6650U CPU @ 2.20GHz Intel64 Family 6 Model 78 Stepping 3;
15/01/2018 10:00:28.492[10652][H]:     Microsoft Outlook 2016 Click-to-Run, 64-bit (16.0.0.8730)
15/01/2018 10:00:28.492[10652][H]:         [RPC over HTTP not enabled]
15/01/2018 10:00:28.492[10652][H]:     Microsoft Internet Explorer 11.125.16299.0

In this section you can see whether the Outlook Add-in has detected that RPC over HTTP is enabled or not. (In my example above it is not enabled.)

The RPCOVERHTTPPROXYURL won't be used unless the Add-in detects that RPC over HTTP is enabled. Ordinarily, we detect this state by looking for the MAPI property "PR_ROH_FLAGS" in the profile.

15/01/2018 10:00:28.416[10652][L]: DesktopCommon::UseRPCOverHTTP: Read PR_ROH_FLAGS: 0x0
15/01/2018 10:00:28.417[10652][M]: Could not find PR_ROH_FLAGS
15/01/2018 10:00:28.417[10652][H]: RPC over HTTP is not enabled (flags = 0)
15/01/2018 10:00:28.417[10652][L]: ~DesktopCommon::UseRPCOverHTTP: Read PR_ROH_FLAGS: 0x40380

There is a known issue with this detection on Outlook 2016; I haven't heard of this affecting Outlook 2010, but perhaps it's worth trying that solution anyway, since it's just upgrading the EV Outlook Add-in. You can download the 12.2.2 (current latest ) Outlook Add-in from this article; try that and see if the detection of the RPC over HTTP state is improved. It should go without saying, but do not attempt to upgrade anything else in your EV 11 environment with that download; just use the installers in the "...\Veritas Enterprise Vault\Outlook Add-In" folder to upgrade the Add-in on the LTE device.

 

--Chris

I have checked the mentioned sections in my log file, but they seam to be okay. (see attached pictures)

It says RPC over HTTP is enabled.

Then I downloaded the EV 12 as you suggested and updated the EV Addin on my LTE tablett.

Now it is working like charm. Perfect. Thank you so much for the assistance.

 

But do you have an idea why it is not working with the EV11 Outlook Addin? It is just because of interest.

For me it is okay, because I wanted to update anyway to EV12 and EV11 server is always working one version backward with the Addins. 

Sorry, based on what you've shown so far, I don't have any idea why the 11 client is not using the RPC Over HTTP Proxy URL that you specified. It does seem to be detecting that Outlook is connected via RPC over HTTP. More investigation would require the full client log as a starting point. It can be useful to compare the client log from the working 12 and from the nonworking 11 and see where they diverge.

Regardless, I'm glad to hear it's working now.

--Chris