Now Filespace.com Is Not Supported. Please Try Again Later.

Before I brainstorm, let me state that I doubt many others will experienced the same effect I had even though the error message:

Fault: Your asking can't be completed right now. Please try again later.

… appears quite frequent when searched just none of the solutions fixed my issue.  To save others from going through all of the troubleshooting steps I went through myself too as with a Microsoft support engineer, what ended upwards fixing my issue was to treat the server equally if I've lost information technology and had to perform a recovery install with the:

Setup /m:RecoverServer /IAcceptExchangeServerLicenseTerms

… command.  In that location are many articles and weblog posts out in that location demonstrating a recovery install and so I'll just list out the bones steps that I did:

1. Deploy a new Windows Server 2012 server and don't join it to the domain
2. Configure the same drives and messages as the existing Exchange Server 2013
3. Copy the Substitution databases over to the new server maintaining the same drive and path
4. Re-create the prerequisites required for Exchange over to the new server
5. Copy the installed Exchange Server 2013 Cumulative Update package (in my case CU2) to the new server
6. Export the public certificate used for OWA and other services to a new server
7. Document where Exchange is installed (this information tin can exist found via ADSIEdit by navigating to CN=Ex-fifteen,CN=Servers,CN=Showtime Administrative Grouping,CN=Authoritative Groups,CN=Offset Organization,CN=Microsoft Substitution,CN=Services,CN=Configuration,DC=Contoso,CN=Local and opening the CN=EX-15 object and so viewing the backdrop of the msExchInstallPath aspect.
8. Shutdown the existing Substitution Server 2013 server (nosotros will not start this server back up again and then brand sure yous've copied what yous need off of it)
9. Reset the former Substitution server's reckoner account
10. Assign the new Commutation server'southward IP to exist the same equally the problematic one
11. Change the name of the new server to the problematic Substitution server'southward proper name and restart
12. Bring together the new renamed server to the domain
13. Install the prerequisites for Exchange Server 2013 (the downloaded packages and Roles and Features via PowerShell)
14. Using the same CU2 parcel, run the command Setup /m:RecoverServer /IAcceptExchangeServerLicenseTerms

One time the install is consummate, restart the server, log into ECP, mount the IS store, reconfigure the virtual directories (i.e. OWA, OAB, etc), review the issue logs, then test the services.  This fixed the issue I had as the Microsoft engineer suspected that here was some file, handler mapping, or a component that wasn't functioning properly.

With the solution out of the mode, I'm going to include the troubleshooting steps beneath:

Problem

Y'all take a new Substitution Server 2013 deployment (all roles on the aforementioned server) with CU2 installed in the surround and while testing OWA, you notice the following error when y'all effort to read the content of an e-mail:

Error: Your asking tin't be completed correct at present. Please try again later.

Composing new emails and sending it outbound appears to work properly:

However, browsing the contents of the sent email exhibits the same error:

Clicking on the Drafts node display the following:

Your request can't be completed right now. Please attempt again after.

There are no items to show in this view.

Troubleshooting Steps Performed

The issue logs do not show whatever relevant mistake messages.

Attempting to remove the net.pipage binding on the Site Bindings of Exchange Back End site in IIS:

… as per the following web log post:

http://gaurang-microsofttechnology.blogspot.com/2013/08/fault-your-request-cant-be-completed.html

… does non right the issue.  Note that I've confirmed with with a Microsoft engineer that there is no damage in removing this equally information technology'south not used past OWA.

Checking the Port 444 document binding shows the default cocky signed document which was confirmed by Microsoft that it is ok for the Substitution Back End site in IIS.

Checking all of the IIS permissions as per the following KB:

Default Settings for Exchange Virtual Directories
http://technet.microsoft.com/en-us/library/gg247612.aspx

… appear to be fine.

Reinstalling the:

Windows Procedure Activation Service

• Process Model
• Configuration APIs

… does non fix the event.

Trying to rerun the CU2 update does not piece of work equally yous won't be able to click the Adjacent button to outset the upgrade.  Running CU2 with setup /m:upgrade works simply does not fix the outcome.

Browsing the IIS logs in the folder:

C:\Program Files\Microsoft\Exchange Server\V15\Logging\HttpProxy\Owa

… and opening the latest log after mimiking the issue in OWA you noticed the following lines created:

2013-10-23T02:04:42.337Z,ebcea5c9-fff5-421b-a200-aaef3c04090a,15,0,712,12,,Owa,webmail.contoso.bm,/owa/ev.owa2,,FBA,True,contoso\hugh.nevile,,Sid~Due south-1-5-21-788572559-3134175131-1749204635-1116,Mozilla/5.0 (compatible; MSIE 9.0; Windows NT vi.one; WOW64; Trident/5.0; chromeframe/30.0.1599.101),199.172.202.68,BM1-AZIM-40-001,200,200,,Become,Proxy,bm1-azim-40-001.contoso.local,15.00.0712.000,IntraForest,WindowsIdentity,Database~2ea1e285-a27c-4183-9931-dad6075ed100~~ten/23/2013 2:13:42 AM,,,0,810,1,,i,0,,0,,0,,0,0,59951.0693,0,,,,3,ane,59951,1,59958,0,59956,2,iii,4,59959,?ns=PendingRequest&ev=PendingNotificationRequest&UA=0&cid=23bef3f4-905a-4782-b4ce-b1e3284f5d96&X-OWA-CANARY=1Rm53J0O10qf83-QL8VTQJ4jmRqnndAIvI239N21LeirqJbvhalTBvn7ONLGfv5yrj94xD4axCg.,,OnBeginRequest=0;,HttpException=ClientDisconnect;
2013-ten-23T02:04:42.384Z,a1aefcad-d10a-43e0-8b66-301e1100eaaa,xv,0,712,12,,Owa,webmail.contoso.bm,/owa/service.svc,FindConversation,FBA,True,contoso\hugh.nevile,,Sid~S-1-5-21-788572559-3134175131-1749204635-1116,Mozilla/five.0 (compatible; MSIE 9.0; Windows NT 6.i; WOW64; Trident/v.0),199.172.202.68,BM1-AZIM-xl-001,405,405,,POST,Proxy,bm1-azim-40-001.contoso.local,15.00.0712.000,IntraForest,WindowsIdentity,Database~2ea1e285-a27c-4183-9931-dad6075ed100~~10/23/2013 ii:14:42 AM,,,875,1293,i,,five,0,,0,,0,,0,0,fifteen.5942,0,i,0,2,0,0,0,0,6,0,i,three,3,8,11,?action=FindConversation&UA=0,,OnBeginRequest=five;,WebExceptionStatus=ProtocolError;ResponseStatusCode=405;WebException=Organisation.Net.WebException: The remote server returned an error: (405) Method Not Allowed.    at Organization.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)    at Microsoft.Substitution.HttpProxy.ProxyRequestHandler.<>c__DisplayClass20.<OnResponseReady>b__1e();
2013-x-23T02:05:31.649Z,c2614a6e-8846-4b55-9dc8-139e1cc9601e,15,0,712,12,,,,,,,,,,,,,BM1-AZIM-40-001,,,,,,,,,,,,,,,,,,,,,,,,,,600038.8438,,,,,,,,,,,,,,,,,,S:ActivityStandardMetadata.Action=GlobalActivity;I32:ADS.C[UNINSTR]=1;F:ADS.AL[UNINSTR]=iv.7919,
2013-x-23T02:05:43.006Z,44349282-87e7-4520-92ad-aeca244490f8,15,0,712,12,,Owa,webmail.contoso.bm,/owa/ev.owa2,,FBA,True,contoso\hugh.nevile,,Sid~Due south-1-five-21-788572559-3134175131-1749204635-1116,Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.i; WOW64; Trident/5.0; chromeframe/30.0.1599.101),199.172.202.68,BM1-AZIM-40-001,200,200,,GET,Proxy,bm1-azim-xl-001.contoso.local,15.00.0712.000,IntraForest,WindowsIdentity,Database~2ea1e285-a27c-4183-9931-dad6075ed100~~10/23/2013 2:xiv:42 AM,,,0,810,ane,,one,0,,0,,0,,0,0,60606.254,0,,,,vii,1,60581,three,60595,1,60593,4,5,half-dozen,60597,?ns=PendingRequest&ev=PendingNotificationRequest&UA=0&cid=23bef3f4-905a-4782-b4ce-b1e3284f5d96&Ten-OWA-CANARY=1Rm53J0O10qf83-QL8VTQJ4jmRqnndAIvI239N21LeirqJbvhalTBvn7ONLGfv5yrj94xD4axCg.,,OnBeginRequest=0;,HttpException=ClientDisconnect;
2013-10-23T02:06:09.245Z,2d027367-cd3a-40b0-8634-5c74a033db5b,15,0,712,12,,Owa,webmail.contoso.bm,/owa/ev.owa2,,FBA,True,contoso\torgeir.dagsleth,,Sid~S-1-5-21-788572559-3134175131-1749204635-1113,Mozilla/5.0 (Macintosh; Intel Mac Bone X 10_8_5) AppleWebKit/536.30.1 (KHTML  like Gecko) Version/vi.0.5 Safari/536.thirty.one,199.172.240.98,BM1-AZIM-40-001,200,200,,Become,Proxy,bm1-azim-xl-001.contoso.local,15.00.0712.000,IntraForest,WindowsIdentity,Database~2ea1e285-a27c-4183-9931-dad6075ed100~~10/23/2013 2:10:49 AM,,,0,1140,1,,1,0,,0,,0,,0,0,319723.4178,0,,,,iv,0,319712,1,319719,0,319717,2,two,iii,319720,?ns=PendingRequest&ev=PendingNotificationRequest&UA=0&cid=ab24e4be-32f9-48f2-877c-cdaf1dd7c816&Ten-OWA-CANARY=KbqlV02F5EObilbXWME5wiHF9AOHndAIHbXU9aRJUWoCtt2QdtBS3st9SK8UzEhXxw_QjQWdkDo.&n=hn3x0v2p,,OnBeginRequest=0;,
2013-10-23T02:06:30.243Z,66e7d747-37a5-4909-acf4-a8afbf440e7a,15,0,712,12,,Owa,webmail.contoso.bm,/owa/ev.owa2,,FBA,True,contoso\torgeir.dagsleth,,Sid~S-1-5-21-788572559-3134175131-1749204635-1113,Mozilla/5.0 (compatible; MSIE x.0; Windows NT 6.ii; WOW64; Trident/6.0; Touch),199.172.240.98,BM1-AZIM-40-001,200,200,,GET,Proxy,bm1-azim-twoscore-001.contoso.local,15.00.0712.000,IntraForest,WindowsIdentity,Database~2ea1e285-a27c-4183-9931-dad6075ed100~~10/23/2013 ii:eleven:09 AM,,,0,1706,i,,1,0,,0,,0,,0,0,320128.994,0,,,,iii,1,320115,4,320124,0,320123,1,ii,3,320125,?ns=PendingRequest&ev=PendingNotificationRequest&UA=0&cid=d346ff16-b3cd-4655-9a88-705154896893&X-OWA-CANARY=HQjKAb7cQUqZYxo77UNQ2sZzVEyGndAIaL8fK3fa16q8-KVMLXheqc4LBrRis4iMT7u7NPQS2Zc.,,OnBeginRequest=0;,

**Sorry well-nigh the word wrap merely the lines are supposed to look similar what is shown in the screenshot.

The output we're interested in is actually the following:

WebExceptionStatus=ProtocolError;ResponseStatusCode=405;WebException=Organization.Net.WebException: The remote server returned an mistake: (405) Method Not Allowed.    at Organisation.Cyberspace.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)    at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.<>c__DisplayClass20.<OnResponseReady>b__1e();

To ready the error in the logs, perform the following:

Prior to making any changes to IIS, it is recommended to employ the following command to backup the site settings offset:

%windir%\system32\inetsrv\appcmd.exe add fill-in "My Backup Proper noun"

The following is an instance:

%windir%\system32\inetsrv\appcmd.exe add backup "IIS-Backup-ten-22-2013"

The above command will create a folder in the following folder:

C:\Windows\system32\inetsrv\fill-in

Later on reviewing all the settings with the Microsoft engineer I was working with noticed that the environment with the outcome was missing some Handler Mappings for the Default Website:

The post-obit is some other environment I have admission to and annotation that the post-obit 3 Handler Mappings is missing:

1. svc-Integrated-4.0
2. svc-ISAPI-4.0_32bit
3. svc-ISAPI-four.0_64bit

… are missing:

What ended up bringing the missing handler back was rerunning the prerequsites PowerShell cmdlet (this is for a server with all the roles installed, go to the following URL to observe the cmdlets for other configurations http://technet.microsoft.com/en-us/library/bb691354(five=exchg.150).aspx#WS2012MBX):

Install-WindowsFeature Equally-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Spider web-Mgmt-Console, WAS-Procedure-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Spider web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Spider web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Spider web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Asking-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation

… shut the IIS managing director then execute iisreset command.  This did non set up my outcome merely probably overnice to know for other environments.

Nosotros went on to endeavor and recreate the web services directories with the post-obit cmdlets:

Remove-WebServicesVirtualDirectory -Identity "ServerName\EWS (Default Spider web Site)"

Remove-WebServicesVirtualDirectory -Identity "ServerName\EWS (Exchange Back End)"

New-WebServicesVirtualDirectory -Server "ServerName" -WebSite "Default Web Site"

New-WebServicesVirtualDirectory -Server "ServerName" -WebSiteName "Exchange Back End" -role:mailbox

This did non gear up the upshot so we and then tried to recreate the OWA virtual directories with the post-obit cmdlets:

Remove-owavirtualdirectory -Identity "ServerName\owa (Default Web Site)"

Remove-owavirtualdirectory -Identity "ServerName\owa (Exchange Dorsum End)"

New-owavirtualdirectory -SERVER "ServerName" -WebSite "Default Web Site"

New-owavirtualdirectory -SERVER "ServerName" -WebSiteName "Commutation Back End" -office:mailbox

Nosotros also went ahead to check the server component's state with the cmdlet:

Get-ServerComponentState

… and all of them checked out ok.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------

Information technology was unfortunate that later 6 hours on a call with Microsoft, the engineer wasn't able to fix it but I did appreciate the endeavor he put in.  Hope this helps anyone out there who may come across such an upshot.

schickemse1939.blogspot.com

Source: https://terenceluk.blogspot.com/2013/10/exchange-server-2013-owa-throws-error.html