Exchange 2010 Owa Options Unexpected Error
Contents |
Sales & Marketing Manager GROUP SPONSORED BY EXCLAIMER See more RELATED PROJECTS Company Move Moved due to sale of the business to a private company Distributed Simulations Capability Provide network connectivity to conduct simulation exercises between owa 2010 options unexpected error occurred multiple CONUS/OCONUS sites. Lotus Notes to Exchange Migration Migrated all email from Lotus Notes/Domino
Owa An Unexpected Error Has Occurred
to Microsoft Exchange 2010 and Outlook 2010. This included mailboxes, contacts, shared account, and distribution lists. TECHNOLOGY IN THIS DISCUSSION Join the outlook web app an unexpected error occurred Community! Creating your account only takes a few minutes. Join Now Greetings Spiceheads, I originally posted about this in the Networking forum thinking the issue may be tied to my recent VLAN and wireless deployment, I'm not so owa 2010 options not working sure of that anymore. I believe it started sometime last week. A user logs in to OWA (inside or outside the school) , when they try to complete an action they get a popup "An unexpected error occurred and your request couldn't be handled." (A screen shot of the full message is below). I checked the windows event log on the server and my computer and I see nothing. I also checked the accepted domain names
Exchange 2010 Owa Redirect
and they appear to be fine, I haven't changed them since I installed the server a year ago. I checked the default website bindings and there is no host name, some have suggested having a host name in the bindings could cause this error. I also checked the authentication for the ecp, EWS, and owa folders in IIS as was suggested on a MS forum. Just in case it was my VLAN project I took the Exchange server and DCs out of the VLAN and nothing changed. Still no luck. Does anyone here have any ideas? Reply Subscribe View Best Answer RELATED TOPICS: OWA problems with 2010 OWA suddenly not working Which OWA will the user see?   10 Replies Mace OP Helpful Post Jay6111 Jul 1, 2011 at 8:29 UTC Are you up to date? Have you installed the latest roll-up? http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=165
-Jay 0 Anaheim OP JMPerry Jul 1, 2011 at 9:00 UTC 1st Post Can you paste the full error report here? 0 Thai Pepper OP Nate@127001 Jul 1, 2011 at 9:09 UTC @Jay6111 I did not have the latest roll up. Installed it and I'm still getting the error. @JMPerry That screen shot contains the entire error report. If there's another place it's hiding please let me know. I'll go look for i1, 2011 jaxelos Leave a comment Go to comments Many of you might have encountered this error "An unexpected error occurred and your request couldn't be handled" after applying Exchange 2010 SP1. This error will start showing up exchange 2010 owa redirect to exchange 2003 in OWA 2010 when you are trying to delete some messages or try to move exchange 2010 owa redirect loop them to another folders. So basically the Exchange it is fully functional but you can not delete any messages in OWA. This
Exchange 2010 Owa Redirect 403 - Forbidden Access Is Denied
error comes only after applying SP1 to the Exchange 2010. There are many discussions on the web regarding this error and many solutions are also provided. Some of the people report this problem because of permissions on the https://community.spiceworks.com/topic/145946-owa-unexpected-errors folders or on the IIS directories, different permission sets on the IIS folders and so long. You can find some of the discussions and solution in this links below: http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/26f46cfb-4335-4dd4-999d-301e70f89607 http://forums.msexchange.org/m_1800538801/mpage_1/key_/tm.htm#1800544783 http://social.technet.microsoft.com/Forums/en-GB/exchange2010hosters/thread/e45d7277-b205-4791-a430-631b163a5072 Some of the posts blame Authentication method or even editing the web.config file and altering some of the values in there in order to make it work. You might also get an Event Error in the event log like : Event ID: 3 The https://jaxelos.wordpress.com/2011/12/01/owa-2010-an-unexpected-error-occurred-and-your-request-couldnt-be-handled/ service ‘/EWS/Exchange.asmx' cannot be activated due to an exception during compilation. OR Event ID: 108 Outlook Web App couldn't connect Exchange Web Services due to a configuration error. For me none of this solutions applied. I was fighting with this error for a few good hours then I decided that I am stupid and I made some mistake somewhere that it was impossible to detect. And since this was a newly installed server and admins with real balls never take backups of newly installed machines I decided to re-install. After re-installing the machine, I configured the Exchange, assured that everything works as intended and re-installed SP1. SAME ERROR ! After looking at the log files and all this articles one more time (a few hours later) it hit me. What could I have changed at the Exchange (the IIS part that is) to provoke the error. Then it hit me. The ONLY thing I changed in my IIS configuration was my HOST HEADERS on my default website. Went to IIS, removed ANY host headers I had there and then everything WORKED. So for all you out there, if you have this kind of error, first thing you want to try is to take a look at your host headers and remove any custom host headers then try all the other solutions. Like this:Like Loading... Rel
compose new emails in OWA/Webmail. Error Message: While user access the webmail/OWA user getting an error http://exchangeexpertscommunity.blogspot.com/2013/06/an-unexpected-error-occurred-and-your.html "An unexpected error occurred and your request couldn't be handled" Problem http://www.networksteve.com/exchange/topic.php/Exchange_OWA_ECP_error,_users_cannot_access_options._Event_viewe/?TopicId=32029&Posts=0 Statement:- Due to the above error message user not able to access mailbox, Calendar, Task and Contacts in webmail. Resolution: - 1. When I checked the IIS settings in Client access server I found HTTP Redirect option were enabled and unchecked/disabled the exchange 2010 option to resolve the issue. 2. Reset the IIS (iisreset /noforce). 3. Check the IIS binding option and make sure "All Assigned IP address" is selected. Now user able to access the mailbox successfully. Thanks. Posted by gengaiyan m at 12:40 PM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: exchange 2010 owa An unexpected error occurred and your request couldn't be handled. Newer Post Older Post Home Subscribe to: Post Comments (Atom) Pages Home Total Pageviews Feedjit Live Blog Stats There was an error in this gadget MCITP (Exchange Enterprise Administrator) gengaiyan m View my complete profile Blog Archive ► 2014 (7) ► January (7) ▼ 2013 (37) ► November (2) ► September (2) ► August (8) ► July (7) ▼ June (9) Error when you start Exchange Management Shell(EM... Installing Lync Server 2013 Persistent Chat Server... Unable to access Exchange 2013 EAC/ECP webpage Install and configure Exchange Server 2013 on Wind... How to Install Lync Server 2013 Std. Edition on Wi... The WinRM client received an HTTP server error sta... Your message wasn't sent to Administrator because ... Create a Dial tone Database in Exchange 2010 and P... An unexpected error occurred and your request coul... ► May (5) ► April (4) Blogspot Tutorial Simple template. Powered by Blogger.
Trying throws up the on screen message of "Unexpected error. An error occourred and your request couldn't be completed. Please try again." Searching event viewer on the exchange server has the following event for every time someone accesses (or tries to) ECP. Current user: ******* Request for URL 'http://exchange01/ecp/default.aspx?rfr=owa&p=Customize/Messaging.aspx' failed with the following error: System.Web.HttpUnhandledException: Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.ArgumentException: 'MobileDevices' is not a valid RBAC query. at Microsoft.Exchange.PowerShell.RbacHostingTools.RbacQuery..ctor(String rbacQuery) at Microsoft.Exchange.PowerShell.RbacHostingTools.RbacPrincipal.IsInRole(String rbacQuery, Boolean& canCache) at Microsoft.Exchange.PowerShell.RbacHostingTools.RbacPrincipal.IsInRole(String role) at System.Web.Configuration.AuthorizationRule.IsTheUserInAnyRole(StringCollection roles, IPrincipal principal) at System.Web.Configuration.AuthorizationRule.IsUserAllowed(IPrincipal user, String verb) at System.Web.Configuration.AuthorizationRuleCollection.IsUserAllowed(IPrincipal user, String verb) at System.Web.Security.UrlAuthorizationModule.IsUserAllowedToPath(HttpContext context, VirtualPath virtualPath) at System.Web.SiteMapProvider.IsAccessibleToUser(HttpContext context, SiteMapNode node) at System.Web.StaticSiteMapProvider.GetChildNodes(SiteMapNode node) at Microsoft.Exchange.Management.ControlPanel._Default.CreateDataContract(SiteMapNode sNode) at Microsoft.Exchange.Management.ControlPanel._Default.CreateDataContract(SiteMapNode sNode) at Microsoft.Exchange.Management.ControlPanel._Default.CreateDataContract(SiteMapNode sNode) at Microsoft.Exchange.Management.ControlPanel._Default.CreateNavTree() at Microsoft.Exchange.Management.ControlPanel._Default.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRe