Hi all

I have just finished installing a production exchange 2013 install with one CAS and one MBX. All functions are working well OWA works internally and externally and users that are still on exchange 2007 are being transferred over to the old OWA when they log in. The problem that I have now is that the Outlook apps are not working in outlook 2013 or OWA.

Bing maps and Action item either fail to load or I get Navigation to this webpage was canceled. If I hit the refresh the page link I get there was a problem with this websites security cert. If I then click continue I get a 404 cant find page.

This happens to all users that have been moved over the the ex2013 server.

I have a feeling this is an internal url problem as I think the cert being sent is for the private cert and not the public cert

Has anyone seen this before?

Thanks in a

Hi,

Try creating a new user on Exchange 2013 and check whether the Bing Maps works? If it works, the issue may occur because the backend is till on Exchange 2007

Thanks,

If you have feedback for TechNet Subscriber Support, contact tnsfl@microsoft.com

This problem happens with 2007 and 2013 users. I tried a new mailbox and still have the same problem

I think it might have something to do with outlook anywhere requiring a cert internally as well as externally. The command required to set intern cert required does not work

Set-OutlookAnywhere -InternalClientRequireSSL $False
A positional parameter cannot be found that accepts argument 'False'.
This is probably not the problem but its something to look at

for the error message "A positional parameter cannot be found that accepts argument 'False'." Try this..

Set-OutlookAnywhere -InternalClientRequireSSL:$False

I still get this error

A parameter cannot be found that matches parameter name 'InternalClientRequireSSL'

Thanks for the help so far

To add to this I am using a single wildcard cert for our domain.

I have now changed the certs on both exchange 2007 and exchange 2013 to standard certs with the correct SANS.

I am still getting the error but I have found a new erro message when using firefox

This Connection is Untrusted

You have asked Firefox to connect securely to ex2013.server.co.uk but we can't confirm that your connection is secure.

So it looks like exchange is sending out the wrong cert to outlook and OWA.

I think this is a configuration problem but I don't know where

Any more help?

Can anyone offer any help?

I also get this error in ie when I try the app

Key    Value
Request    GET /owa/auth/errorFE.aspx?httpCode=404 HTTP/1.1

Baffled a bit now

Hi,

Have you checked the EAC, does Bing Maps are enabled for everyone?

Thanks,

If you have feedback for TechNet Subscriber Support, contact tnsfl@microsoft.com

Hi Simon

thanks for the resposne I have checked and double checked the options and yes they are set to enabled for all users

I'm still stumbling around in the dark over this one

Can Anyone Help?

We've got the same problem. Brand new Exchange 2013 install, new user with mailbox on 2013, all apps fail to load. Also tried migrating a mailbox from 2010, same problem...

Glad to see someone else is having this issue and its not just me. Can anyone from MS help with this before I open a ticket?

Hi

Exchange 2007 has been removed from the domain now and we still have this problem!

I am also having the same issue, has anyone been able to solve this? Newly installed Exchange 2013, our old Exchange 2007 server has been decommissioned and removed from the network. It appears none of our apps are working in Outlook. Bing Maps, Action Items, and Unsubscribe all report an error in Outlook and OWA:

Outlook error:

404
can't find page :-(
The page you're looking for couldn't be found on the server.

OWA error:

App Error Something went wrong and we couldn't start this app. Please try again later or contact your system administrator.

All users new and old are experiencing the same error.

I still have no fix for this and am loathed to open a MS case for something that should just work as described.

I am installing CU3 tonight, lets see if that helps!

CU3 did not fix it for us, we installed CU3 on New Years Day. I was thinking it might be a permissions issues but I have the proper permissions. The only thing I haven't tried yet is to remove myself from Domain Admins group in AD since DA's have weird issues in Exchange 2013.

Yep CU3 did nothing to help this problem. The 404 appears on normal users AND DA's Permissions seems the logical place to look BUT I am pretty sure our permissions are correct as required by MS.

This is getting beyond a joke.

I removed myself from being a domain admin and still getting the same error. I didn't think it would make a difference but we've been wanting to get rid of Domain Admin for regular use for a while now so made the changes this afternoon.

Andrew, in EAC, when you click on Organization then Apps, then click on an App, does yours show no logo for them on the right side? Ours has the logos missing from each app, here's a screen capture:

I added another app from the Microsoft Outlook App Store, and I can use that no problem. Wonder if there is an install someplace we missed???

Andrew, in EAC, when you click on Organization then Apps, then click on an App, does yours show no logo for them on the right side? Ours has the logos missing from each app, here's a screen capture:

I have the same issue with 404 errors  and missing logos. When I look at the image path for the logo on the EAC Apps page, it is https://<serveraddress>/owa/<guid>%40<domain>/.../icon.png. %40 is the @ sign URL encoded, and if I replace it with @, the image loads and I get the flag logo. After playing around, I've managed to load an action item by replacing the same @ sign. So it would appear that Exchange is emitting the URL in a format that it can't subsequently interpret. Unfortunately, I have no idea how to fix this or work around it - does anyone have any idea?

• Edited by steviep Friday, January 10, 2014 4:24 PM

Hi all,

I think I have the same problem. Only if I install my own apps I can see the logo's. For the default apps I have the %40 issue as well.

For each app, be it preinstalled with the Exchange 2013 install, or be it downloaded from Office.com or be it my own app that is installed, in OWA I get the error "App Error We couldn't connect to the catalog server for this app". On mobile access I get the error that others describe in this thread: "404 page not found".

I tried reinstalling the pre-reqs (including roles and features), I tried checking all the internal URLs for the Exchange Virtual Directories and pointing them to externally resolvable FQDNs. Nothing changes.

Does anyone know what the URL is to the Catalog Server that is mentioned in the error? I'd love to troubleshoot this..

Cheers

Arjan

Out of curiosity, which server OS are you using?

My non working system is built on Windows Server 2012 R2, and I have a demo install that is working, and that is built on Windows Server 2012...

Cheers

Arjan

My Exchange is on 2012 R2 (which is not supported by Microsoft until SP1) but we didn't find about R2 not being supported until after our install and migration. It would have been nice had the preinstall check pop up and say it was an unsupported OS.

I can confirm that now.

Update:

Installed a clean Windows 2012R2 + Exchange 2013 in a lab: No apps working, same errors

Installed a clean Windows 2012 + Exchange 2013 in a lab: ALL APPS working.

Conclusion: IIS in 2012R2 is handling the apps differently then IIS in 2012.

Cheers

Arjan

Well I guess we'll have to wait until SP1, no date as of yet.

http://danblee.com/microsoft-to-release-outlook-sharepoint-and-exchange-2013-sp1-in-early-2014/

http://blogs.technet.com/b/exchange/archive/2013/11/20/exchange-server-2013-service-pack-1-coming-in-early-2014.aspx

I'm also having this problem,

My setup is Server 2012 R2
Just updated from CU3 to SP1,

The apps still don't work, i have the same issue that you have.

Same for me :( no apps still after SP1 on 2012R2.

Anyone got any ideas?

This is has been going on for some time, and we would like to get it working.

I also upgraded to SP1 and still no apps are working.  None of the built-in ones or any new ones I install from the store.  404 error in Outlook 2013 and OWA: App ErrorSomething went wrong and we couldn't start this app. Please try again later or contact your system administrator

The 404 error can occur if the app can not contact the office.com license server also.

I found a few issues with the apps after the SP1 upgrade.  The manifest.xml had the wrong URL in it which I realized was due to the OWA virtual directory.  I recreated this directory and it created an new oma virtual directory and fixed the URL's.

I then testing access the URL listed in the manifest directly after authenticating to OWA (Bing Maps icon.png).  The files exist on the Exchange server but there is no virtual directory under OWA that would point to the icon.png file (e.g. https://mail.......07fb4824019b/images/icon.png).  

The IIS logs show a 302 error when the path is explicitly attempted in a browser.

So I'm wondering if there is a way to force a reinstall of the apps to see if the virtual directory is created in IIS.  I don't see any other way that the app could be used if there is no virtual directory listing in IIS?

If the bug is Microsoft's they will comp the case back.  Sometimes you have to pull the plug and open a case as forum support won't cut it (you know what I mean?)

I have two setups.

1 is a single server install, which holds all roles.
1 is a multi server install, which has CAS separated.

The multi server install has working apps, the single server does not.

For the guys who also have failing apps: multi or single server installs?

My install is a single server (apps not working).  I was wondering if maybe this is related to the CAS (Default Web Site) and "Exchange Back End" IIS sites running on the same machine?  They use different ports (443 and 444) so maybe there is some issue there with the proxy behavior?

Same here, no logos on the built-in apps but third-party apps work fine. Also Exchange 2013 SP1 on Windows Server 2012 R2. Real-world SSL cert in place. Everything else works well.

Same issue here as well with a new multi-role Exchange 2013 SP1 on 2012 R2 server. No issues with Exchange 2013 SP1 on Win 2012 (non-R2) with the same configuration

I have a multi server setup, x1 CAS, x2 Mailbox.

Is there anyware to reinstall the builtin apps?

I've laos notices some of the image previews in OWA, have the same isse.

This is the IIS log.

2014-03-01 09:19:01 172.18.1.206 GET /owa/08226717-a8f5-4add-a650-00d6df7ec502@emaildomain.com/prem/15.0.847.32/ext/def/bc13b9d0-5ba2-446a-956b-c583bdc94d5e/images/icon.png httpCode=404&404;https://mbx1.internaldomain.com:444/owa/08226717-a8f5-4add-a650-00d6df7ec502@emaildomain.com/prem/15.0.847.32/ext/def/bc13b9d0-5ba2-446a-956b-c583bdc94d5e/images/icon.png&ActID=3d16d009-e847-4ed0-8eba-40e026a04e5b&CorrelationID=<empty>&ex=E409 444 - 172.18.1.205 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko https://owa.remotedomain.uk/ecp/Extension/OrgViewExtensionDetails.aspx?isNarrow=t&id=490a0f0e-5c00-4e41-a17e-a081d19a78f3%5Cbc13b9d0-5ba2-446a-956b-c583bdc94d5e 302 0 0 31

On the bottom of the EHLO blog: ADBL

ADBL

10 Points200 Recent Achievements New Blog CommentatorFirst Marked Answer View Profile 1 Mar 2014 11:33 AM #

Hi Exchange Team: Congrats on getting SP1 out! The product tests fine in our lab apart from one issue:

OWA Apps do not work as they have previously on Windows Server 2012 (non R2).

With Server 2012 R2, some of the App specific URLs that are present in the OWA pages are escaped, e.g. the @ symbol is replaced by '%40'. The referenced resources then do not load properly. This appears to be new behaviour with IIS8.5 & .NET Framework 4.5.1 vs IIS8 &.NET Framework 4.5 on 2012.

http://programmaticallyspeaking.com/the-mysteriously-escaped-request-path-in-aspnet.html has more detail about the issue.

A possible work around may be to edit the web.config to include (aspnet:UseLegacyRequestUrlGeneration" value="true") but we'd rather not mess around with these things ourselves.

We've disabled app functionality for our pilot users but we'd appreciate if you could comment on this ASAP.

Regards

Brent Alinger [MSFT]

1 Mar 2014 8:54 PM

#

@ABDL - Regarding OWA Apps on 2012 R2, yes there is a change in behavior in Windows 2012 R2 which requires a Web.Config change for many OWA Apps.  We are working on a KB article for this issue and will have this guidance posted within the next week.  Unfortunately the article was not ready for publishing prior to the launch of SP1.  It is never our preference to force customer changes to Web.Config and we are working with the Windows team to make this seamless for those who want to deploy Windows Server 2012 R2.

I can confirm this is the issue.  When I added the key <add key="aspnet:UseLegacyRequestUrlGeneration" value="true" /> to the <appSettings> in the web.config located in the frontend\httpproxy\owa\web.config file, the web apps work in owa and Outlook 2013.  Great find!  

I look forward to the KB article that will document how to address it rather than my manual edit.

Thanks Rob, this worked for me as well (Exchange 2013 SP1 on Windows Server 2012 R2). I wonder what, if any, repercussions it has with this setting enabled otherwise?

It would be wise to wait for the official documentation/KB.  This will give you the official supported info.  It may be the same, but to be safe in production environments, I'd wait to be sure.

Bottom line, this still feels a bit too early/untested to be rolling out production until some of these follow up KBs come out.

@Susan:
Good idea, in the meantime I've put this in place and works perfectly.

Thanks!

Adding the <add key="aspnet:UseLegacyRequestUrlGeneration" value="true" /> to my web.config file fixed it for me! Thank you!

Thanks, fixed it for my OWA, but Outlook 2013 SP1 still fails with "APP ERROR This app could not be started..."

In OWA the Action Items shows asomething to action, but no follow up button.

• Edited by Mattbisme123 Monday, March 10, 2014 8:40 AM extra info

Hey Mattbisme,

I don't see any of my OWA web apps in Outlook 2013 SP1? Did you do anything special to make those show up?

T

I have a similar problem with Outlook apps not working in OWA and Outlook 2013 with Exchange 2013 SP1, however it's on Windows Server 2012 (not R2)... AND, the Outlook apps do work in Apple's Safari browser on Mac OS X.  They do not work on any Windows PC browser.  Has anyone tried OWA on a Mac and noticed the OWA apps working?

See screenshots in this other thread here.

Adding the key <add key="aspnet:UseLegacyRequestUrlGeneration" value="true" /> to the <appSettings> in the web.config located in the frontend\httpproxy\owa\web.config file and restarting IIS didn't fix it for me.

Hey AdamZ1977,

Before I added the appSetting I noticed I could open the apps without errors if I added my OWA urk to the trusted sites zone in IE.

You could try that as a workaround?

Cheers

Arjan

Before I added the appSetting I noticed I could open the apps without errors if I added my OWA urk to the trusted sites zone in IE.

Tried adding to a trusted zone and intranet zone in IE, but neither of those worked.  Thanks for the attempt though.  Not sure what Mac OS X's Safari is doing differently.

Default apps in Outlook Web App do not work if Exchange is installed in
Window Server 2012 R2:

http://support.microsoft.com/kb/2938292/en-us?sd=rss&spid=730

This issue occurs because the logic to load app resources is broken in
Windows Server 2012 R2.

This issue will be fixed in Exchange Server 2013 Cumulative

I've installed CU5 and CU6 and I still cannot get Bings Maps to work in OWA or Outlook 2013. They just don't appear at all. I've confirmed that they're enabled for all users.

I can confirm, that Exchange 2013 CU5 or CU6 on Windows Server 2012 R2 did not fix the problem.

CU6 and the mentioned change in \frontend\httpproxy\owa\web.config did not fix the issue too.

<add key="aspnet:UseLegacyRequestUrlGeneration" value="true" /> to the <appSettings>

Any idee?

I'm still having the same problem... all updates installed, including CU6, and the web.config modification did not fix it for me. The error I'm getting now is "There was an error contacting Bing Maps. Please try again later." All other apps work correctly.

I put more info in a separate thread, at:

https://social.technet.microsoft.com/Forums/en-US/4612f7af-a7dd-4d34-a067-6401fa0524ac/bing-maps-not-working?forum=exchangesvradmin

• Edited by Omatsei Tuesday, November 18, 2014 7:51 PM

Thanks Winnie - just to confirm, we upgraded to CU7 over the weekend and the issue persists.  Adding the key recommended above to the web.config file did not help us.

Hi any news here?

CU9 and not working!