tag:blogger.com,1999:blog-2228947945609574437.post5895400493873894486..comments2024-03-17T16:23:31.499-04:00Comments on Terence Luk: Exchange Server 2013 OWA throws the error: “Error: Your request can't be completed right now. Please try again later.”Terence Lukhttp://www.blogger.com/profile/02612575579652280306noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-2228947945609574437.post-497079871828634262017-02-16T15:21:05.982-05:002017-02-16T15:21:05.982-05:00I had the same issue but only one user was impacte...I had the same issue but only one user was impacted. Turns out two AD accounts (one of which was disabled) shared the same LegacyExchangeDN attribute. I cleared the attribute from the disabled account and now the messages display correctly.Angus McLeannoreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-44035653692479581302017-01-20T01:58:16.348-05:002017-01-20T01:58:16.348-05:00I would suggest you to please change the location ...I would suggest you to please change the location of database and check if it helps you.Anonymoushttps://www.blogger.com/profile/11548063213101031617noreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-74935474138032177222016-02-05T11:34:41.501-05:002016-02-05T11:34:41.501-05:00Check the Exchange Back End on IIS, the OWA virtua...Check the Exchange Back End on IIS, the OWA virtual directory must have anonymous permissions enabled.Cristian Nobregahttps://www.blogger.com/profile/11187120194513176797noreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-30385089572116355952015-03-12T06:12:30.007-04:002015-03-12T06:12:30.007-04:00Fixed the issue using steps from below link:
http...Fixed the issue using steps from below link:<br /><br />http://www.techieshelp.com/exchange-2013-request-cant-completed-right-now/Faisalnoreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-76098205401597401842014-02-07T06:20:07.302-05:002014-02-07T06:20:07.302-05:00I had this problem as well and i did fix it withou...I had this problem as well and i did fix it without reinstall.<br /><br />The rights of the following files in "C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys" where fucked.<br /><br />Changed owner to administrator en reapply inherit security.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2228947945609574437.post-23056838372149508452014-01-09T07:10:25.509-05:002014-01-09T07:10:25.509-05:00Sorry , I do not speak English.
I had the same pro...Sorry , I do not speak English.<br />I had the same problem and it was related to . NET FRAMEWORK 3.5 installed on IIS during the investigation of a problem related to the integration with Exchange Online site. To resolve completely removed . . NET Framework 3.5 and 4.5 , I entered the Event Handler and deleted the mappings and then reinstalled and everything is working again .<br /><br />of course it was not so simple because when I removed the . NET Framework 3.5 and IIS 4.5 it also removed the framework of the machine and when the machine rebooted again only with the command prompt . To resolve follow the procedures this blog<br /><br />When the machine came back with the graphical interface almost nothing worked so I got a clean installation of Windows 2012 and performed these procedures to install all roles and features patterns ( http://chall32.blogspot.com.br/2012/10/clone- windows- 2008r2 - installed- roles.html ) , after installing the machine was normal and just installed the framework 4.5 and the dependencies for the exchange again.<br /><br />Visit our blog www.imago.com.br / blogAnonymoushttps://www.blogger.com/profile/16925807027636998359noreply@blogger.com