EWS The server cannot service this request right now. Try again later.

html,body{padding:0;margin:0;font-family:Verdana,Geneva,sans-serif;background:#fff;}html{font-size:100%}body{font-size:.75em;line-height:1.5;padding-top:1px;margin-top:-1px;}h1{font-size:2em;margin:.67em 0}h2{font-size:1.5em}h3{font-size:1.16em}h4{font-size:1em}h5{font-size:.83em}h6{font-size:.7em}p{margin:0
0 1em;padding:0 .2em}.t-marker{display:none;}.t-paste-container{;left:-10000px;width:1px;height:1px;overflow:hidden}ul,ol{padding-left:2.5em}a{color:#00a}code, pre{font-size:1.23em}
Hi,
I do have a problem that Exchange 2013 CU7 is giving mit a "The server cannot service this request right now. Try again later." when trying to access some accounts using EWS and impersonation.
I know there might be throttling involved and for that I did make an separate policy and assigned it to the users (EWS andthe mailbox - just in case...)
Here is what I got from the EWS logs:
.007Z,f973ffeb-b1fa-4946-a9b4-acb047ea1b37,15,0,1044,21,,NTLM,true,[email protected],domain,ExchangeServicesClient/0.0.0.0,Target=None;Req=Exchange2007_SP1/Exchange2007_SP1;,192.168.0.100,EWS15MB1,EWS15MB3.domain,FindItem,200,1041,,ErrorServerBusy,[email protected],,,cc91dc21f4c542acb64f196ec47ae727,c314fd38-a24e-4bcb-992e-e009c7adcb4e,PrimaryServer,LocalTask,0,1,0,1,0,0,1,0,0,,,,,,,,,0
Max,0 Max,,,,EWS_BO,0.1067,[C],0,0,10,390,,,5,0,,6,15,695,713,,,BackEndAuthenticator=WindowsAuthenticator;TotalBERehydrationModuleLatency=0;AuthzFlags=AuthzSkipTokenGroups;FindItemQueryFilter=(True);AQS=False;MailboxTypeCacheSize=2039;S:WLM.Cl=InternalMaintenance;S:ServiceTaskMetadata.ADCount=0;S:WLM.Type=Ews;S:FCI.MBXT=Primary;S:ServiceTaskMetadata.ADLatency=0;S:WLM.Int=True;S:FCI.QS=;S:ServiceTaskMetadata.RpcCount=10;S:ServiceTaskMetadata.RpcLatency=420;S:WLM.SvcA=False;S:FCI.VF=All;S:ServiceTaskMetadata.WatsonReportCount=0;S:ServiceTaskMetadata.ServiceCommandBegin=16;S:ServiceTaskMetadata.ServiceCommandEnd=711;S:ActivityStandardMetadata.Component=Ews;S:WLM.BT=Ews;S:BudgetMetadata.MaxConn=Unlimited;S:BudgetMetadata.MaxBurst=Unlimited;S:BudgetMetadata.BeginBalance=$null;S:BudgetMetadata.Cutoff=Unlimited;S:BudgetMetadata.RechargeRate=Unlimited;S:BudgetMetadata.IsServiceAct=False;S:BudgetMetadata.LiveTime=00:00:00.2343945;S:BudgetMetadata.EndBalance=$null;S:FCI.CVT=689;S:FCI.CSIT=70;S:FCI.CSIC=0;S:FCI.CSIQ=2;S:FCI.CSISTC=2;S:FCI.CSIG=54;S:FCI.CRIT=613;S:FCI.CRIC=340;S:FCI.CRIQ=2;S:FCI.CRIG=381;S:FCI.CRIET=0;S:FCI.CRINI=160;S:FCI.CRIMBT=0;S:FCI.CRIMET=7;S:FCI.CRIMP=0;S:FCI.CRIMAR=37;S:FCI.CVU=False;Dbl:WLM.TS=713;Dbl:BudgUse.T[]=715.151611328125;I32:ADR.C[dc1]=1;F:ADR.AL[dc1]=3.1106;Dbl:CCpu.T[CMD]=312.5;I32:RPC.C[EWS15mb1.fb00df0b-8bdd-4dee-81a3-1696ea8bd747]=10;Dbl:RPC.T[EWS15mb1.fb00df0b-8bdd-4dee-81a3-1696ea8bd747]=420;I32:ROP.C[EWS15mb1.fb00df0b-8bdd-4dee-81a3-1696ea8bd747]=80768493;I32:MAPI.C[EWS15mb1.fb00df0b-8bdd-4dee-81a3-1696ea8bd747]=23;Dbl:MAPI.T[EWS15mb1.fb00df0b-8bdd-4dee-81a3-1696ea8bd747]=420;I32:MB.C[EWS15mb1.fb00df0b-8bdd-4dee-81a3-1696ea8bd747]=10;F:MB.AL[EWS15mb1.fb00df0b-8bdd-4dee-81a3-1696ea8bd747]=42;Dbl:ST.T[EWS15mb1.fb00df0b-8bdd-4dee-81a3-1696ea8bd747]=59;I32:ATE.C[dc1.domain-]=1;F:ATE.AL[dc1.domain-]=0;Dbl:STCPU.T[EWS15mb1.fb00df0b-8bdd-4dee-81a3-1696ea8bd747]=46,,ExceptionHandler_Execute=Microsoft.Exchange.Services.Core.Types.ServerBusyException:
The server cannot service this request right now. Try again later.    at Microsoft.Exchange.Services.Core.Search.NormalQueryView.ThrowIfFindCountLimitExceeded(UInt32 viewLength)    at Microsoft.Exchange.Services.Core.Search.NormalQueryView.RetrieveCalendarViewData(Object[][]
view Int32 rowsToGet)    at Microsoft.Exchange.Services.Core.Search.CalendarPageView.ApplyPostQueryPaging(Object[][] view)    at Microsoft.Exchange.Services.Core.Search.NoGrouping.IssueQuery(QueryFilter query Folder
folder SortBy[] sortBy BasePagingType paging ItemQueryTraversal traversal PropertyDefinition[] propsToFetch RequestDetailsLogger logger)    at Microsoft.Exchange.Services.Core.FindItem.FindItemsInParent(IdAndSession
folderIdAndSession)    at Microsoft.Exchange.Services.Core.FindItem.Execute()    at Microsoft.Exchange.Services.Core.ExceptionHandler`1.Execute(CreateServiceResult createServiceResult Int32 index GenerateMessageXmlForServiceError
generateErrorXml);,
And here is the throttling policy I'm using for those users.
ThrottlingPolicyScope                       : Regular
IsServiceAccount                            : False
AnonymousMaxConcurrency                     : 1
AnonymousMaxBurst                           : 120000
AnonymousRechargeRate                       :420000
AnonymousCutoffBalance                      : 720000
EasMaxConcurrency                           : 10
EasMaxBurst                                 : 480000
EasRechargeRate                             : 1800000
EasCutoffBalance                            : 600000
EasMaxDevices                               : 100
EasMaxDeviceDeletesPerMonth                 : Unlimited
EasMaxInactivityForDeviceCleanup            : Unlimited
EwsMaxConcurrency                           : Unlimited
EwsMaxBurst                                 : Unlimited
EwsRechargeRate                             : Unlimited
EwsCutoffBalance                            : Unlimited
EwsMaxSubscriptions                         : Unlimited
ImapMaxConcurrency                          : Unlimited
ImapMaxBurst                                : 3600000
ImapRechargeRate                            : 600000
ImapCutoffBalance                           : Unlimited
OutlookServiceMaxConcurrency                : 27
OutlookServiceMaxBurst                      : 300000
OutlookServiceRechargeRate                  : 900000
OutlookServiceCutoffBalance                 : 3000000
OutlookServiceMaxSubscriptions              : 5000
OutlookServiceMaxSocketConnectionsPerDevice : 4
OutlookServiceMaxSocketConnectionsPerUser   : 12
OwaMaxConcurrency                           : 20
OwaMaxBurst                                 : 480000
OwaRechargeRate                             : 1800000
OwaCutoffBalance                            : Unlimited
OwaVoiceMaxConcurrency                      : 3
OwaVoiceMaxBurst                            : 75000
OwaVoiceRechargeRate                        : 375000
OwaVoiceCutoffBalance                       : 525000
PopMaxConcurrency                           : 20
PopMaxBurst                                 : 3600000
PopRechargeRate                             : 600000
PopCutoffBalance                            : Unlimited
PowerShellMaxConcurrency                    : 18
PowerShellMaxBurst                          : Unlimited
PowerShellRechargeRate                      : Unlimited
PowerShellCutoffBalance                     : Unlimited
PowerShellMaxTenantConcurrency              :
PowerShellMaxOperations                     : Unlimited
PowerShellMaxCmdletsTimePeriod              : Unlimited
ExchangeMaxCmdlets                          : Unlimited
PowerShellMaxCmdletQueueDepth               : Unlimited
PowerShellMaxDestructiveCmdlets             : Unlimited
PowerShellMaxDestructiveCmdletsTimePeriod   : Unlimited
PowerShellMaxCmdlets                       : Unlimited
PowerShellMaxRunspaces                      : Unlimited
PowerShellMaxTenantRunspaces                :
PowerShellMaxRunspacesTimePeriod            : Unlimited
PswsMaxConcurrency                          : 18
PswsMaxRequest                              : Unlimited
PswsMaxRequestTimePeriod                    : Unlimited
RcaMaxConcurrency                           : Unlimited
RcaMaxBurst                                 : 150000
RcaRechargeRate                             : 900000
RcaCutoffBalance                            : Unlimited
CpaMaxConcurrency                           : Unlimited
CpaMaxBurst                                 : Unlimited
CpaRechargeRate                             : Unlimited
CpaCutoffBalance                            : Unlimited
MessageRateLimit                            : Unlimited
RecipientRateLimit                          : Unlimited
ForwardeeLimit                              : Unlimited
DiscoveryMaxConcurrency                     : 15
DiscoveryMaxMailboxes                       : 20000
DiscoveryMaxKeywords                        :2000
DiscoveryMaxPreviewSearchMailboxes          : 5000
DiscoveryMaxStatsSearchMailboxes            : 1000
DiscoveryPreviewSearchResultsPageSize       : 2000
DiscoveryMaxKeywordsPerPage                 : 500
DiscoveryMaxRefinerResults                  : 500
DiscoveryMaxSearchQueueDepth                : 128
DiscoverySearchTimeoutPeriod                : 30
PushNotificationMaxConcurrency              : 20
PushNotificationMaxBurst                    : Unlimited
PushNotificationRechargeRate                : Unlimited
PushNotificationCutoffBalance               : Unlimited
PushNotificationMaxBurstPerDevice           : 10
PushNotificationRechargeRatePerDevice       : 6
PushNotificationSamplingPeriodPerDevice     : 600000
EncryptionSenderMaxConcurrency             : 200
EncryptionSenderMaxBurst                    : 4800000
EncryptionSenderRechargeRate                : 18000000
EncryptionSenderCutoffBalance               : Unlimited
EncryptionRecipientMaxConcurrency           : 20
EncryptionRecipientMaxBurst                 : 480000
EncryptionRecipientRechargeRate             : 1800000
EncryptionRecipientCutoffBalance            : Unlimited
ComplianceMaxExpansionDGRecipients          : 10000
ComplianceMaxExpansionNestedDGs             : 25
IsLegacyDefault                             : False
Diagnostics                                 :
Do you have an idea how to get rid of this?
Thank you.
Regards
Carsten

Hi,
This issue occurs because the EWS monitoring detects that the limit for the requests that are from a Client Access server to a Mailbox server was reached. Therefore, the Client Access server returns an ErrorServerBusy response code to all EWS requests to
the Mailbox server.
To work around this issue, make the following changes in the Web.config file on the Client Access server, The Web.Config file is located in the following path: Drive\Program Files\Microsoft\Exchange Server\V15\ClientAccess\exchweb\ews
1.        Find the following code in the Web.config file:
<add key="MbxServerEnableConcurrencyControl" value="true" />
Change the MbxServerEnableConcurrencyControl value from true to
false.
2.        Add the following line of code into the Web.config file:
<add key="DefaultFindCountLimit" value="2000" />
<add key="MdbFairUnhealthyLatencyThreshold" value="500" />
3.        Reset IIS to check this issue.
If this issue persists, I suggest to create a new throttling policy with unlimited settings and applying the policy to those users.
New-ThrottlingPolicy EWSRCAunlimited
Get-ThrottlingPolicy EWSRCAunlimited | Set-ThrottlingPolicy -EWSPercentTimeInAD:$null -EWSFindCountLimit:$null -EWSPercentTimeInMailboxRPC:$null -EWSMaxConcurrency:$null -EWSFastSearchTimeoutInSeconds:$null -EWSMaxSubscriptions:$null -EWSPercentTimeInCAS:$null
-RCAPercentTimeInCAS:$null -RCAPercentTimeInMailboxRPC:$null -RCAMaxConcurrency:$null -RCAPercentTimeInAD:$null
Set-Mailbox username -ThrottlingPolicy EWSRCAunlimited
Best Regards.

Similar Messages

Why am I getting ExchangeWebServices Inbox Error: Error, ErrorServerBusy. The server cannot service this request right now. Try again later

I recently switched my application that uses EWS from an on-premise Exchange Server to Exchage Online through Office356.
The process worked just fine for several days, then I started getting the following errors;
Error accessing [USERNAME] email account.; ExchangeWebServices Inbox Error: Error, ErrorServerBusy, The server cannot service this request right now. Try again later. -->
This has been happening for the past 14 hours now.
I contacted my Office365 support team and they acted like they had never heard of the Exchange Web Services API, so no help there.
I can access the mailbox using the O365 web portal and I can access the mailbox account using the Outlook 2013 desktop client. The issue seems specific to EWS
My program is a Windows service, written in VB.Net. It connects to EWS, goes to the user account inbox, iterates through the inbox extracting attachments from messages, then moves the messages to a saved folder below the inbox.
I created the wrapper for EWS that I can reference in my project code using the following, run from an elevated VS2012 command prompt;
wsdl.exe /namespace:ExchangeWebServices /out:EWS.cs https://outlook.office365.com/ews/services.wsdl /username:[email protected] /password:p@ssw0rd
csc /out:EWS_E2K13_release /target:library EWS.cs
I bind to EWS in my class, using the following code;
Imports System.Net
Imports ExchangeWebServices
Public Class Exchange2013WebServiceClass
Private ExchangeBinding As New ExchangeServiceBinding
Public Sub New(ByVal userEmail As String, ByVal userPassword As String, ByVal URL As String)
ExchangeBinding.Credentials = New NetworkCredential(userEmail, userPassword)
ExchangeBinding.Url = URL
End Sub
The error that is logged gets triggered when my code makes a call to the following method;
Public Function GetInboxMessageIDs() As ArrayOfRealItemsType
Dim returnInboxMessageIds As ArrayOfRealItemsType = Nothing
Dim errMsg As String = String.Empty
'Create the request and specify the travesal type.
Dim FindItemRequest As FindItemType
FindItemRequest = New FindItemType
FindItemRequest.Traversal = ItemQueryTraversalType.Shallow
'Define which item properties are returned in the response.
Dim ItemProperties As ItemResponseShapeType
ItemProperties = New ItemResponseShapeType
ItemProperties.BaseShape = DefaultShapeNamesType.IdOnly
'Add properties shape to the request.
FindItemRequest.ItemShape = ItemProperties
'Identify which folders to search to find items.
Dim FolderIDArray(0) As DistinguishedFolderIdType
FolderIDArray(0) = New DistinguishedFolderIdType
FolderIDArray(0).Id = DistinguishedFolderIdNameType.inbox
'Add folders to the request.
FindItemRequest.ParentFolderIds = FolderIDArray
Try
'Send the request and get the response.
Dim FindItemResponse As FindItemResponseType
FindItemResponse = ExchangeBinding.FindItem(FindItemRequest)
'Get the response messages.
Dim ResponseMessage As ResponseMessageType()
ResponseMessage = FindItemResponse.ResponseMessages.Items
Dim FindItemResponseMessage As FindItemResponseMessageType
If ResponseMessage(0).ResponseClass = ResponseClassType.Success Then
FindItemResponseMessage = ResponseMessage(0)
returnInboxMessageIds = FindItemResponseMessage.RootFolder.Item
Else
'' Server error
Dim responseClassStr As String = [Enum].GetName(GetType(ExchangeWebServices.ResponseClassType), ResponseMessage(0).ResponseClass).ToString
Dim responseCodeStr As String = [Enum].GetName(GetType(ExchangeWebServices.ResponseCodeType), ResponseMessage(0).ResponseCode).ToString
Dim messageTextStr As String = ResponseMessage(0).MessageText.ToString
Dim thisErrMsg As String = String.Format("ExchangeWebServices Inbox Error: {0}, {1}, {2}", responseClassStr, responseCodeStr, messageTextStr)
errMsg = If(errMsg.Equals(String.Empty), String.Empty, errMsg & "; ") & thisErrMsg
End If
Catch ex As Exception
'errMsg = String.Join("; ", errMsg, ex.Message)
errMsg = If(errMsg.Equals(String.Empty), String.Empty, errMsg & "; ") & ex.Message
End Try
If Not errMsg.Equals(String.Empty) Then
returnInboxMessageIds = Nothing
Throw New System.Exception(errMsg)
End If
Return returnInboxMessageIds
End Function
Since the code worked just fine for several days and then suddenly stopped working with a server busy error, I have to think that this is some type of limit or throttling by EWS on the account. I process several thousand emails per day, in chunks of 300
at a time.
But I have no idea how to check for any limits exceeded. I am nowhere close to my O365 mailbox size limit. Right now, there are over 4,000 messages in my inbox, and growing.
Thanks in advance for any ideas you can offer.
Dave

All the API's EWS, MAPI, ActiveSync,Remote powershell are throttled on Office365 (based around what 1 particular user could resonably do). If you have had a read of this already i would recommend
http://msdn.microsoft.com/en-us/library/office/jj945066(v=exchg.150).aspx
You can't adjust or even find your current throttle usage so you have to try to design your code around living inside the default limits. If your using One Service Account to access multiple Mailboxes (or if that account is because used across multiple
applications) that can cause problems. In this case using EWS Impersonation is good solution as described in
http://blogs.msdn.com/b/exchangedev/archive/2012/04/19/more-throttling-changes-for-exchange-online.aspx (this basically means the Target Mailbox is charged instead of the Service Account).
Looking at the code one thing I notice missing is your don't appear to be paging the results of FindItems, also have versioned your requests to Exchagne2013. eg ". When the value of the
RequestServerVersion element indicates Exchange 2010 or an earlier version of Exchange, the server sends a failure response with error code
ErrorServerBusy. If the value of the RequestServerVersion
element indicates a version of Exchange starting with Exchange 2010 SP1
or Exchange Online, and the client is using paging, EWS may return a
partial result set instead of an error"
To Page FindItems Correctly you should use the IndexedPageViewType class and page the Items at no more the 1000 at a time eg something like
IndexedPageViewType indexedPageView = new IndexedPageViewType();
indexedPageView.BasePoint = IndexBasePointType.Beginning;
indexedPageView.Offset = 0;
indexedPageView.MaxEntriesReturned = 1000;
indexedPageView.MaxEntriesReturnedSpecified = true;
FindItemType findItemrequest = new FindItemType();
findItemrequest.Item = indexedPageView;
findItemrequest.ItemShape = new ItemResponseShapeType();
findItemrequest.ItemShape.BaseShape = DefaultShapeNamesType.IdOnly;
BasePathToElementType[] beAdditionproperties = new BasePathToElementType[3];
PathToUnindexedFieldType SubjectField = new PathToUnindexedFieldType();
SubjectField.FieldURI = UnindexedFieldURIType.itemSubject;
beAdditionproperties[0] = SubjectField;
PathToUnindexedFieldType RcvdTime = new PathToUnindexedFieldType();
RcvdTime.FieldURI = UnindexedFieldURIType.itemDateTimeReceived;
beAdditionproperties[1] = RcvdTime;
PathToUnindexedFieldType ReadStatus = new PathToUnindexedFieldType();
ReadStatus.FieldURI = UnindexedFieldURIType.messageIsRead;
beAdditionproperties[2] = ReadStatus;
findItemrequest.ItemShape.AdditionalProperties = beAdditionproperties;
DistinguishedFolderIdType[] faFolderIDArray = new DistinguishedFolderIdType[1];
faFolderIDArray[0] = new DistinguishedFolderIdType();
faFolderIDArray[0].Mailbox = new EmailAddressType();
faFolderIDArray[0].Mailbox.EmailAddress = "[email protected]";
faFolderIDArray[0].Id = DistinguishedFolderIdNameType.inbox;
bool moreAvailible = false;
findItemrequest.ParentFolderIds = faFolderIDArray;
int loopCount = 0;
do
FindItemResponseType frFindItemResponse = esb.FindItem(findItemrequest);
if (frFindItemResponse.ResponseMessages.Items[0].ResponseClass == ResponseClassType.Success)
foreach (FindItemResponseMessageType firmtMessage in frFindItemResponse.ResponseMessages.Items)
Console.WriteLine("Number of Items retreived : " + ((ArrayOfRealItemsType)firmtMessage.RootFolder.Item).Items.Length);
if (firmtMessage.RootFolder.IncludesLastItemInRange == false)
moreAvailible = true;
else
moreAvailible = false;
((IndexedPageViewType)findItemrequest.Item).Offset += ((ArrayOfRealItemsType)firmtMessage.RootFolder.Item).Items.Length;
Console.WriteLine("Offset : " + ((IndexedPageViewType)findItemrequest.Item).Offset);
if (firmtMessage.RootFolder.TotalItemsInView > 0)
foreach (ItemType miMailboxItem in ((ArrayOfRealItemsType)firmtMessage.RootFolder.Item).Items)
Console.WriteLine(miMailboxItem.Subject);
else
throw new Exception("error " + frFindItemResponse.ResponseMessages.Items[0].MessageText);
} while (moreAvailible);
The support people should be able to help you as long as you can get past the first level. The EWS Managed API has a RequestId header that gets submitted with requests
http://blogs.msdn.com/b/exchangedev/archive/2012/06/18/exchange-web-services-managed-api-1-2-1-now-released.aspx . In theory they should be able to take this and then from the Logs tell more information about why your request failed etc.
Cheers
Glen

I am getting the error "We're sorry we cannot complete your request on the iTunes store at this time. Please try again later." on both my iPhone and iTunes on my computer. What is wrong with iTunes? Is the server down???

I am getting the error "We're sorry we cannot complete your request on the iTunes store at this time. Please try again later." on both my iPhone and iTunes on my computer. What is wrong with iTunes? Is the server down or what? I need to download some things and update some apps...

I've been getting the same message for like an hour now. Since everything was working fine a few hours ago, and nothing changed on my end before it stopped working, I'm guessing it's something on Apple's end. They probably already know about it by now, and are hopefully working on fixing it, so there's probably not much we can do but wait for them to fix it.

I keep gettign an error that says: We're sorry, we cannot complete your request on the itunes store at this time. Please try again later. Is this a common error? is there a fix?

When I try to access itunes, I get this error: We're sorry, we cannot complete your request on the itunes store at this time. Please try again later. Is this a common error? Is there a fix?

Sorry, I don't have any suggestions at this time. You can try running the Network Diagnostics in iTunes:
http://support.apple.com/kb/HT3204
and post the results here. That may provide some clues that someone can use to diagnose the problem and offer suggestions.
Regards.

MSDN Internet Server error: Sorry, we were unable to service your request. Please try again later.

I have been experiencing a high rate (maybe 1 in 5 page renders) errors from the MSDN servers in the last 4-6 weeks.
It reports in the breadcrumb "Internal Server error"
And then writes below: Sorry, we were unable to service your request. Please try again later.
Is Microsoft aware of this ongoing and high rate issues?
--Dale

There are many who are facing this issue.
https://social.msdn.microsoft.com/Forums/en-US/098dc7d7-b12a-4a6d-ae74-47e612531e68/internal-server-error-coming-when-accessing-msdn-forum?forum=reportabug
-Vaibhav Chaudhari

From the past 3days,i can't install apps from the appstore,it says "this items can't be purchased right now,try again later", please help me,thank you

From the past 3days,i can't install apps from the appstore,it says "this items can't be purchased right now,try again later", please help me,thank you

Hey Kay97,
These are some troubleshooting steps that might be relevant to your issue:
Can't connect to the iTunes Store
http://support.apple.com/kb/TS1368
Welcome to Apple Support Communities!
Have a good one,
Delgadoh

I get this when try to verify my id on FaceTime: the server rencountered an error processing registration please try again later.

I get this when try to verify my id on FaceTime: the server rencountered an error processing registration please try again later.

While we all have MacBooks in this forum not all of us use FaceTime. There's a FaceTime Support Community where everybody uses FaceTime. You should also post this question there to increase your chances of getting an answer. https://discussions.apple.com/community/mac_app_store/facetime_for_mac

TS4268 i am trying to log into facetime through my Macbook Pro and it shows me this message "the server encountered an error processing registration please try again later". what does this mean and what should i do?

i am trying to log into facetime through my Macbook Pro and it shows me this message "the server encountered an error processing registration please try again later". what does this mean and what should i do? also on my iphone 5 i am trying to log in with my apple ID but everytime i try it sayd incorrect password! please help!!

Wait until Apple fix it. See: http://www.apple.com/support/icloud/systemstatus/

I have a MacBook Pro and I seem to have problems with my FaceTime. It want me to enter my apple ID, but when I do it comes up with a msg that says, "The server encountered an error processing registration. Try again later." What do I need to do?

I have a MacBook Pro and have problems using my Facetime. Last time I used it without problems. Now I am trying to use it, and it is asking that I enter my Apple ID. When doing so, it comes up with a message that says, "The server encountered an error processing registrion. Try again later." What does this mean, and how do I fix it? Thanks.

I had the same problem and found the solution here:
https://discussions.apple.com/thread/3189272

When I try to activate my FaceTime from my iMac is says the server encountered an errorprocessing registration. Please try again later. Please help

When I try to activate my FaceTime from my iMac is says," the server encountered an errorprocessing registration. Please try again later." Please help. Any ideas

Back up all data.
Take the steps suggested in this support article:
FaceTime, Game Center, Messages: "There was an error processing registration" when signing in
Sign out of iMessage:
Messages ▹ Preferences ▹ Accounts ▹ Sign out
Then sign back in with your verified credentials. Note that the password of some Apple ID's will expire periodically.
If you get the same error, try resetting the NVRAM.

Unable to log into FaceTime it says "the server encountered an error processing registration please try again later. Apple ID is verified ok but could not login. Please help. Thanks

Unable to log into FaceTime it says "the server encountered an error processing registration please try again later. Apple ID is verified ok but could not login. Please help. Thanks

I had the same problem and found the solution here:
https://discussions.apple.com/thread/3189272

My macbook pro says "the server encountered an error processing registration.please try again later." What does it mean ? i tried since the previous day. help me.

my macbook pro says "the server encountered an error processing registered.please try again later."in facetime .what does it mean?

Direct you to the proper forum for MacBook :
MacBook Series Forums
https://discussions.apple.com/community/notebooks?view=discussions

I can't sign in FaceTime and when i sign in, it's said: The Server Encountered An Error Processing Registration.Please Try Again Later... Plzz somebody help me!!

I can't sign in FaceTime and when i sign in, it's said: The Server Encountered An Error Processing Registration.Please Try Again Later... Plzz somebody help me!!

Hi,
As the Other threads suggests I would check the Date and Time settings on the Mac and compare that with the settings in the router.
Messages (and iChat before that) send Time stamped info to Login and to send IMs.
Obviously most people set their Macs to their Time Zone and nearest city/town.
What people sometimes forget is that their Router/Modem device(s) have to be set correctly as well.
EDIT
Also Add a Public DNS server to your System Preferences> Network > Advanced Button > DNS tab
A Google one such as 8.8.4.4 or 8.8.8.8 seem to work well for most people
10:15 PM Saturday; March 17, 2012
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
 iMac 2.5Ghz 5i 2011 (Lion 10.7.3)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
"Limit the Logs to the Bits above Binary Images."  No, Seriously
Message was edited by: Ralph Johns (UK)

TS4185 please help with message: "Could not sign in. The server encountered an error processing registration. please try again later."

any suggestions? could not sign in. The server encountered an error processing regisgtration. PLease try again later."
Any thoughts?

Try this: http://conpartior.wordpress.com/2012/08/22/imessage-could-not-sign-in-imessage-t he-server-encountered-an-error-processing-registration-please-try-again-later-so lve/

I down loaded iMessage for mac, but when i try to register it it say the server encountered an error processing registration. please try again later, it has been doing this all night,

I down loaded the new imessage for mac from the mountain lion, free trial, but when i try to sign in it says the server encountered an error processing registration. Please try again later. I have put it on my other mac, and no problems with it, i have only brought this mac today, and just want to get it all set up

Try this:
https://discussions.apple.com/thread/3801516?tstart=0

EWS The server cannot service this request right now. Try again later.

Similar Messages

Maybe you are looking for