OWA 2010 with EV 2010 'The archived item is currently unavailable....'

[Firewall1976]

I've installed the OWA plugin on my CAS box and get the following message on vaulted mails 'The archived item is currently unavailable. If you choose reply or forward, only the content shown will be included. Click here to preview the original item'

Now when I click on this link the item displays in a seperate window direct from the EV  but I obviously want the embedded functionality in the OWA message for my users.

I've searched the net for answers but all the 'fixes' I've come across involve the item not displaying even when clicking on the link in OWA message so are related to my issue.

Can any help?

[Firewall1976]

I can't forward or reply to messages which are archived....

I can however do this with non-archived messages

[ZeRoC00L]

Is this a new exchange server, or did it work in the past ?

If it is a new server, make sure to update exchangeservers.txt and run the owausers.wsf script:

http://www.symantec.com/business/support/index?page=content&id=TECH49352

[Firewall1976]

I didn't think the EVSERVERS.TXT file applies to them?

[ZeRoC00L]

Yes, you will need to add every Exchange CAS server to the exchangeservers.txt and run the script owauser.wsf.

[Firewall1976]

Couple of queries about the command.

Do I have to put a /exch2010 switch into this and does the actual exchangeserver.txt file contain the IP addresses of the CAS servers?

The older doc references 'back-end OWA boxes' which obviously don't exist in an Ex2010 environment...

Cheers

[ZeRoC00L]

Add all Exchange 2003, Exchange 2007 CAS and Exchange 2010 CAS servers to the file exchangeservers.txt and run this command: (there is no /exch2010 option):

cscript owauser.wsf /domain:domain /user:username /password:password

To display help for the cscript command, type:

cscript owauser.wsf /?

[LCT]

Do you have a mixed Exchange Environment or just exchange 2010 servers?

From Exchange 2007 onwards you no longer need EVServers.txt. The switch /exch2003 will work for exchange 2003/2007/2010 as the CAS server now handles EVProxying. Symantec should really update their command switch to cause less confusions.

You should test OWA by connect directly to the CAS server using https://casserver.domain.local/owa and fully test OWA internally, you should find that all funstions should work as expected.

For external OWA testing, in order for the links embedded into the shortcuts such as "view original items" and attachments these will only work if you have ISA/TMG to do the links translations, without this function this will not work, alternatively you can publish your EV server to the web using HTTPs but it is not recommended. 

[John_Chisari]

Lots of guessing going on here.

Can you post a OWA log after setting  <add key="EnterpriseVault_LogEnabled" value="true"/> in the web.config.  Would make it a lot simpler to see what is happening.

This is a good article - http://www.symantec.com/docs/TECH68743 - i know it's for the buttons not showing, but gives you some info ont he interaction between OWA and EV.

Can you also give us some details on your Exchange topology.. ie. Mailbox and CAS separate servers, how many etc.

[Firewall1976]

We have a mixed Ex2003 and Ex2010 organisation. We are in the process of testing the new Ex2010 servers and this is one aspect which isn't working as expected. Nothing is live on EX2010

Currently have a physical environment for Ex2003 which consists of:-

2 External OWA boxes

2 Bridgehead boxes

4 node Mailbox cluster with 3 live instances of Exchange running

EX2010 consists of:-

3 Virtual CAS/HUB servers

3 Maibox servers in a DAG. (2 in Prod site one in DR site)

I have added the 3 CAS boxes to the exchangeservers.txt file and ran the script and it still doesn't work. If I check the IISlogs on our EV box there are NO entries when a user accesses archived mail from the Ex2010 CAS boxes.

I'll amend the web.config file and post the output soon 

[Firewall1976]

2012-01-20 09:33:13 ::1 POST /ews/exchange.asmx - 443 - ::1 ExchangeServicesClient/14.01.0218.002 401 0 0 15
 2012-01-20 09:33:13 ::1 POST /ews/exchange.asmx ;RC:3f25a425-c3b3-4aeb-baf2-cadbd0d584b6;Init>>Conn:0,HangingConn:0,AD:30000/30000/0%,CAS:54000/52911/2%,AB:30000/30000/0%,RPC:36000/35894/1%,FC:1000/0,Policy:DefaultThrottlingPolicy_7f57033f-58bb-4645-bfe6-a987bbd75369,Norm,Sub:5000/0;[C]Queues:0msec/Execute:0msec;SoapAction=m:ConvertId;Version=4;RpcC=0;RpcL=0;LdapC=0;LdapL=0;End(15.6254ms)>>Conn:1,HangingConn:0,AD:30000/30000/0%,CAS:54000/52896/2%,AB:30000/30000/0%,RPC:36000/35894/1%,FC:1000/0,Policy:DefaultThrottlingPolicy_7f57033f-58bb-4645-bfe6-a987bbd75369,Norm,Sub:5000/0; 443 DOM\letest2010 ::1 ExchangeServicesClient/14.01.0218.002 200 0 0 15
 2012-01-20 09:33:13 ::1 POST /ews/exchange.asmx - 443 - ::1 ExchangeServicesClient/14.01.0218.002 401 0 0 0
 2012-01-20 09:33:13 ::1 POST /ews/exchange.asmx ;RC:7a5fda25-e4d4-4557-adcc-aa66b68e2de4;Init>>Conn:0,HangingConn:0,AD:30000/30000/0%,CAS:54000/52896/2%,AB:30000/30000/0%,RPC:36000/35894/1%,FC:1000/0,Policy:DefaultThrottlingPolicy_7f57033f-58bb-4645-bfe6-a987bbd75369,Norm,Sub:5000/0;[C]Queues:0msec/Execute:0msec;SoapAction=m:GetItem;Version=4;RpcC=3;RpcL=15;LdapC=0;LdapL=0;End(31.2508ms)>>Conn:1,HangingConn:0,AD:30000/30000/0%,CAS:54000/52865/2%,AB:30000/30000/0%,RPC:36000/35879/1%,FC:1000/0,Policy:DefaultThrottlingPolicy_7f57033f-58bb-4645-bfe6-a987bbd75369,Norm[Resources:(Mdb)DB2(Health:-1%,HistLoad:0),],Sub:5000/0; 443 DOM\letest2010 ::1 ExchangeServicesClient/14.01.0218.002 200 0 0 437
 2012-01-20 09:33:14 10.100.16.202 GET /owa/forms/premium/SubPageEventHandler.aspx ae=Item&a=Preview&t=IPM.Note.EnterpriseVault.Shortcut&id=RgAAAAA7m1FM8e3zR47LnvEPcjkcBwA%2fHxm2ychHS7klpl4hMjaGAAAA4p%2blAAA%2fHxm2ychHS7klpl4hMjaGAAAA4scOAAAJ&calist=05051005050505051616&canary=b89d4de1cc104d46811c5d53a2e6b5e7&SP=1&pfmk=M33:1327051916022;M46:1327051916030&Initial+Budget>>Conn:1,HangingConn:0,AD:18000/18000/0%,CAS:90000/77064/22%,AB:18000/18000/0%,RPC:90000/89830/1%,FC:1000/0,Policy:DefaultThrottlingPolicy_7f57033f-58bb-4645-bfe6-a987bbd75369,Norm&v=14.1.218.13&mbx=DOM-EX-MAIL01.mycompany.co.uk&sessionId=b89d4de1cc104d46811c5d53a2e6b5e7&prfltncy=551&prfrpccnt=2&prfrpcltncy=15&prfldpcnt=0&prfldpltncy=0&prfavlcnt=0&prfavlltncy=0&End+Budget>>Conn:1,HangingConn:0,AD:18000/18000/0%,CAS:90000/76518/23%,AB:18000/18000/0%,RPC:90000/89815/1%,FC:1000/0,Policy:DefaultThrottlingPolicy_7f57033f-58bb-4645-bfe6-a987bbd75369,Norm[Resources:(Mdb)DB2(Health:-1%,HistLoad:0),] 443 DOM\letest2010 10.112.7.244 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+6.1;+Trident/5.0;+SLCC2;+.NET+CLR+2.0.50727;+.NET+CLR+3.5.30729;+.NET+CLR+3.0.30729;+Media+Center+PC+6.0;+MDDR;+InfoPath.3) 200 0 0 765 

[Firewall1976]

2012-01-20 09:32:00 ::1 POST /ews/exchange.asmx - 443 - ::1 ExchangeServicesClient/14.01.0218.002 401 0 0 0
2012-01-20 09:32:00 ::1 POST /ews/exchange.asmx ;RC:49457a71-bacb-4c21-bdb8-1d17833fb40e;Init>>Conn:0,HangingConn:0,AD:30000/30000/0%,CAS:54000/51036/5%,AB:30000/30000/0%,RPC:36000/35865/1%,FC:1000/0,Policy:DefaultThrottlingPolicy_7f57033f-58bb-4645-bfe6-a987bbd75369,Norm,Sub:5000/0;[C]Queues:0msec/Execute:62.5008msec;SoapAction=m:GetFolder;Version=4;RpcC=1;RpcL=0;LdapC=0;LdapL=0;End(140.6268ms)>>Conn:1,HangingConn:0,AD:30000/30000/0%,CAS:54000/51237/5%,AB:30000/30000/0%,RPC:36000/35865/1%,FC:1000/0,Policy:DefaultThrottlingPolicy_7f57033f-58bb-4645-bfe6-a987bbd75369,Norm[Resources:(Mdb)DB2(Health:-1%,HistLoad:0),],Sub:5000/0; 443 DOM\letest2010 ::1 ExchangeServicesClient/14.01.0218.002 200 0 0 156

[LCT]

2012-01-20 09:32:00 ::1 POST /ews/exchange.asmx - 443 - ::1 ExchangeServicesClient/14.01.0218.002 401 0 0 0
 

Have you got this line in your web.config file on the CAS server?

<add key="EnterpriseVault_ExchangeWebServicesUrl" value="https://localhost/ews/exchange.asmx"/>
 

http://www.symantec.com/business/support/index?page=content&id=TECH141519

Not much different between EV9 and EV10 regarding this. I suspect this is where your problem is. You need to change the localhost appropriately to your environment for exchange 2010.

When you put the https://localhost/ews/exchange.asmx in IE on your CAS server you should not get any problems, and you should get to an xml page.

[LCT]

2012-01-20 09:32:00 ::1 POST /ews/exchange.asmx - 443 - ::1 ExchangeServicesClient/14.01.0218.002 401 0 0 0
 

Have you got this line in your web.config file on the CAS server?

<add key="EnterpriseVault_ExchangeWebServicesUrl" value="https://localhost/ews/exchange.asmx"/>
 

http://www.symantec.com/business/support/index?page=content&id=TECH141519

Not much different between EV9 and EV10 regarding this. I suspect this is where your problem is. You need to change the localhost appropriately to your environment for exchange 2010.

When you put the https://localhost/ews/exchange.asmx in IE on your CAS server you should not get any problems, and you should get to an xml page.

[Firewall1976]

but we've added it and still no change?

[Firewall1976]

if that helps?

[Firewall1976]

to the web.config file and running the cscript user script is that I can now archive a message or folder from OWA which was not possible before that.

Previously there were no vaults in the drop down field when the archive box opened.

We're getting there slowly but surely!

I would like to have a look at a working web.config file from an Ex2010 OWA box with EV10 integration if anyone can post a one...

[LCT]

OK lets start from the beginning.

Currently if you connect directly to your CAS server locally via https://caserver.domain.local/owa can you perform the following?

1. Can you retrieve the message by double-clicking on the shortcut?

2. Can you see the EV icon and tool bar?

3. Can you archive an email item?

4. Can you restore an archived item?

If you can enable the EV OWA log for each of the above then we can work out where the error is occuring.

Are you still getting

2012-01-20 09:32:00 ::1 POST /ews/exchange.asmx - 443 - ::1 ExchangeServicesClient/14.01.0218.002 401 0 0 0
 

If you are still getting this then there may be an issue with the permissions on the EWS virtual directory. What did you replace with localhost?

[Firewall1976]

1. See attached 1.jpeg

2. No

3. Yes (previously couldn't)

4. No

We placed the actual server name into the web.config not the virtual loadbalanced name.

I can't see the previous error you mentioned in the log output. I've attached this as a txt file as wordwrap doesn't appear to be an option on this forum..

[LCT]

OK. Can you upload a full EV OWA logs so that I can take a look. feel free to take out private info etc. Also a copy of your web.config too.