Owa Unexpected Error 2010
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: OWA
Outlook Web Access An Unexpected Error Occurred And Your Request Couldn T Be Handled
- An unexpected error occurred and your request couldn't be an unexpected error occurred and your request couldn't be handled outlook handled. Previous Versions of Exchange > Exchange Server 2010 Question 0 Sign in to vote After
Owa Delete Email An Unexpected Error Occurred And Your Request Couldn't Be Handled
OWA login I get the following error message when I execute the following; Click on Options. Doesnt do anything after Click on a message an error occurred and your request couldn't be completed in inbox. loads the message Click on Public Folders. Doesnt do anything after. I also get this message when doing other things in OWA. Any ideas???Mark C Thursday, October 28, 2010 9:35 PM Reply | Quote Answers 7 Sign in to vote well I was able to figure this iis host headers out my by self.... I setup redirection using this article.... http://briandesmond.com/blog/redirecting-owa-urls-in-exchange-2010/ In the article is stated to leave the redirection of /Public alone.... Well in testing, I removed http redirection from the /Public website, restarted IIS and BAM!!!!! I've got an error free OWA... thus far.Mark C Marked as answer by Mark Chris Thursday, November 04, 2010 8:57 PM Thursday, November 04, 2010 8:56 PM Reply | Quote All replies 0 Sign in to vote I believe options comes from the /ecp virtual directory and public folders from the /public virtual directory, so I think you can narrow your diagnostics there. Are there any settings that appear to be wrong in IIS?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." Friday, October 29, 2010 5:15 AM Reply | Quote 0 Sign in to vote Ed, I did some research and I am trying to install t
1, 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 in OWA 2010 when you are trying to delete some messages or try to move them to another folders. So basically the Exchange it is fully functional but you can not delete any messages in OWA. This 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 https://social.technet.microsoft.com/Forums/exchange/en-US/ca5e5e1b-643c-47eb-8c05-1e90c91b08a3/owa-an-unexpected-error-occurred-and-your-request-couldnt-be-handled?forum=exchange2010 the 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: https://jaxelos.wordpress.com/2011/12/01/owa-2010-an-unexpected-error-occurred-and-your-request-couldnt-be-handled/ 3 The 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 solu
you might want to delete any custom bindings on yourDefault Web Sitein IIS. To do http://itowns.blogspot.com/2012/09/exchange-2010-owa-unexpected-error.html this openIIS Manager, expand your server->sitesand selectDefault Web Site, right click http://www.moh10ly.com/blog/exchange/owa-an-unexpected-error-occurred-and-your-request-couldn-t-be-handled it and chooseEdit Bindings...Remove any custom headers you added and it should work right away. Links: http://jaxelos.wordpress.com/2011/12/01/owa-2010-an-unexpected-error-occurred-and-your-request-couldnt-be-handled/ Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Followers Blog unexpected error Archive ► 2015 (2) ► January 2015 (2) ► 2014 (2) ► December 2014 (2) ► 2013 (2) ► May 2013 (1) ► March 2013 (1) ▼ 2012 (31) ► December 2012 (2) ► November 2012 (1) ► October 2012 (1) ▼ September 2012 (27) Shared folders on windows 7 can't be error occurred and accessed from... Task 'me@emaildomain.com Sending' reported error (... Configuring Exchange 2010 Autodiscover for interna... New-EdgeSubscription: You can't use the FileName p... MSCCM 2012 - Fail to create SQL Server Certificate... OraClient only administrator can connect to databa... Wordpress Warning: is_dir() [function.is-dir]: ope... Exchange 2010 change default OU for Mail Contacts.... Exchange 2010 change default OU for Distribution G... Exchange 2010 OWA: An unexpected error occurred an... Exchange 2010 OWA errors after SP2. Moodle: Disable confirmation email when enrolling ... Moodle: You can not enrol yourself in this course.... Exchange ActiveSync doesn't have sufficient permis... 550 5.7.1 Client does not have permissions to send... Inheritable permissions on AD users are automatica... Adding MSSQL Server in OpManager Samsung Galaxy S2 Exchange account on Android - ca... Exchange 2010 Organization Prerequisites Fail - Th... Moodle - change access URL Moodle - Configuring LDAP authentication plugin wi... Moodle - Fatal error: $CFG->dataroot is not writab... Black Logon Screen Windows S
2010 Performance counters for the Client access role is not installedExchange 2013 not installing due to pending restart on Windows 2012Exchange RPC over HTTP problem with TMGExtend MS Exchange Server's Certificate lifeNew Mailbox migration suspended or queued with the error below generatedOffline Address book Issue after migration from Exchange 2003 to Exchange 2010Outlook 2007 keeps prompting users for passwordOWA an unexpected error occurred and your request couldn't be handledOwa Redirection results in 401 Unauthorized access messageUpgrading Exchange 2013 RTM to Latest SP and CUInstalling "Only" Trend Micro 11.0 on Exchange 2013 serverPfsenseBlock Facebook on Pfsense using WPAD Autodiscover featureConfigure Pfsense SSH with RSA/KSA KeysConfiguring Snort on PfsenseCreate your own Nameserver using TinyDns on PfsenseFilter DNS traffic after blocking websites with SquidPackage installation issuePfsense and Active Directory IntegrationPublishing Exchange on PfsenseSetup Squid Guard (Proxy Server) on PfsenseContactAbout this website Blog > Exchange > OWA an unexpected error occurred and your request couldn't be handled OWA an unexpected error occurred and your request couldn't be handledResolution 1: The error happens due to a redirection of OWA has been configured. To fix the issue simply remove the redirect option. Resolution 2: Another resolution that works without turning Redirection off for default site is to turn off redirection from the Public folder. Disqus for Google SitesThe gadget spec URL could not be found ContentHomeCalendarCertification and AwardsConsultationDonate!BlogGoogle CloudDownload VM (VHD) from Azure and uploading it to Google cloud and get it working..AZUREAdd multiple endpoints or port range to an Azure Virtual MachineAZURE ACTIVE DIRECTORY SYNC EVENT ID 906 FAILED WHILE PURGING RUN HISTORY INVALID NAMESPACEDEPLOYING AZURE RMS WITH EXCHANGE 2010 AND EXCHANGE 2013 ON-PREMISES AND IN HYBRID ENVIRONMENT WITH EXCHANGE ONLINEAzure Tutorial: Predicting Gas Prices Using Azure Machine Learning StudioActive DirectoryActive Directory Useful ScriptActive Directory MigrationsActive Directory Migration 2008R2 to 2012R2AD Cross Forest MigrationDomain Controller Cross Forest migration Part 1Domain Controller Cross Forest migration Part 2Domain Controller Cross Forest migration Part 3 (ADMT Installation)Find out which user is logged in to which computerChange Password Policy for AD and domain usersCHANGING PROXY ADDRESS FOR LOCAL AD USERSReplication after tombstone life expiredPrepare Active Directory with powershellResetting Usernames and Passwords from text fileRestoring an Act