Getting "Sorry! We're having trouble processing your request right now. Please try again in a few minutes." when trying to set auto-replies in OWA

Hi,
I have an SBS 2011 box with Exchange 2010 on it. All updates are installed. Whenever a user tries to use Outlook Web Access to set an Auto-Reply the error "Sorry! We're having trouble processing your request right now. Please try again
in a few minutes." pops up.
I have reset the OWA and ECP virtual directories.
I have verified the that anonymous authentication is enabled for ECP in IIS
I have verified that ECP is using .NET V2.0 for the Application pool.
What else could it be?

Hi JGolds,
Except above suggestion, I also recommend you refer to the following article to compare with the default auth settings for :
Default Authentication Settings for Exchange-related Virtual Directories
In addition, Is there only one user have this issue? or all users have this issue?
If just one user have this issue, you can try to move mailbox to other DB and check if any helps.
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Niko Cheng
TechNet Community Support

Similar Messages

TS4079 Why does Siri say "I'm really sorry about this but I can't take any requests right now Please try again in a little while" ? Is she broke? How do I reset? Thanks

Why does Siri say "I'm really sorry about this but I can't take any requests right now Please try again later"?
I haven't had any trouble up to this morning. Is there a reset?
Thanks for your help.

Thanks James, I just tried Siri again and it worked fine on two tests.
Does this Problem happen often? I have had my Iphone5 for about two weeks and this is the first time I have
had the problem. My 3gs used Siri to dial phone numbers or use the address book to dial and I never had a problem with it.
Thanks for posting the system status page.

TS4079 siri say ( i'm really sorry about this , but i can't take any request right now , please try again in a little while )

siri say ( i'm really sorry about this , but i can't take any request right now , please try again in a little while )
please help me >>>>

Thanks James, I just tried Siri again and it worked fine on two tests.
Does this Problem happen often? I have had my Iphone5 for about two weeks and this is the first time I have
had the problem. My 3gs used Siri to dial phone numbers or use the address book to dial and I never had a problem with it.
Thanks for posting the system status page.

HT204389 Whenever I wanna use Siri, it says : sorry, I can't take any request right now please try again in a while. What can I do?

Whenever I wanna use Siri, it says : sorry, I can't take any request right now please try again in a while. What can I do?

http://support.apple.com/kb/TS4079
Read "Ensure that iPhone 4S is connected to the Internet"

About siri siri say im really sorry about this but i can not take any requests right now please try again a little while.      this more 1 month

about siri siri say im really sorry about this but i can not take any requests right now please try again a little while.      this more 1 month

Re: about siri siri say im really sorry about this but i can not take any requests right now please try again a little while.      this more 1 month
Aug 7, 2012 8:17 PM (in response to paulcb)
Im try and try restore but like the problem and
Like (0) Reply

TS4079 i'm really sorry, i can't take any requests right now, please try again in a little while

i'm really sorry, i can't take any requests right now, please try again in a little while
Why is happening? And this as been going for two week now

This type of response means that Siri can't connect to Apple's servers, so this means Apple's severs are down. if this continues over a long amount of time ask someone at an Apple store.

We're sorry, but we are unable to complete your request at this time. Please try again in a few minutes or start over now.

Trying to send my iPhone 5 in for repair, keep getting this error:
"We're sorry, but we are unable to complete your request at this time.
Please try again in a few minutes or start over now.
(system.99)"
Tried using different browsers, and waiting few minutes, no joy : (
Any Ideas?

Yeah, it kept doing it when I was trying to change the delivery address, changed it on my apple main apple profile adress and then it worked on the repair page.

Error occurred in deployment step 'Install app for SharePoint': We're sorry, we weren't able to complete the operation, please try again in a few minutes. If you see this message repeatedly, contact your administrator.

While deploying sharepoint hosted app i am getting error "Error occurred in deployment step 'Install app for SharePoint': We're sorry, we weren't able to complete the operation, please try again in a few minutes. If you see this message repeatedly, contact
your administrator.". From the developer site i remove the app manually and after deploying i am getting the same error again.
Harminder singh

I was trying to install SharePoint 2013 on premise development environment and encountered the following issues while deploying the app using Visual studio 2013.
Please refer these articles for configuration settings.
http://blogs.msdn.com/b/how24/archive/2013/06/14/prepare-your-sharepoint-2013-farm-for-app-development-and-debugging.aspx
http://www.codeproject.com/Articles/515677/MyplusFirstplusSharepoint-HostedplusAppplusinplus2
http://blogs.technet.com/b/mspfe/archive/2013/01/31/configuring-sharepoint-on-premise-deployments-for-apps.aspx
http://aanuwizard.com/2012/12/07/article-14-from-30-system-account-can-not-deploy-or-purchase-an-app-in-sharepoint-2013-rtm/
Error 1:
Error occurred in deployment step 'Install app for SharePoint': The System Account cannot perform this action.
Error 2:
The local SharePoint server is not available. Check that the server is running and connected to the SharePoint farm.
Error 3:
Error occurred in deployment step 'Install app for SharePoint': We're sorry, we weren't able to complete the operation, please try again in a few minutes. If you see this message repeatedly, contact your administrator.
Solution:
For error 1, follow these instructions:
a. Create a new domain account DOMAIN\myApp_Admin
b. add DOMAIN\myApp_Admin to local admin group
c. add DOMAIN\myApp_Admin to Farm Administrators group
   Central Admin site --> Site Settings --> People and groups
   Add DOMAIN\myApp_Admin
For error 2 & 3, follow these instructions:
1. Grant DOMAIN\myApp_Admin accont a sysadmin server role on SQL server
2. Open SharePoint Power Shell and execute Add-SPShellAdmin <DOMAIN\myApp_Admin> command.
3. Grant DOMAIN\myApp_Admin a db_owner rights to web application Content database that you would like to use for debugging SharePoint 2013 app.
4. Make sure following roles are assigned for SharePoint_Config database
   SharePoint_Shell_Access
   SPDDataAccess
   public
5. Make sure following roles are assigned for SharePoint_Content database
   db_owner
5. Make sure following roles are assigned for SharePoint_AdminContent database
   public

I keep having " Purchase processing is temporarily unavailable. Please try again later " How to solve it?

I keep having " Purchase processing is temporarily unavailable. Please try again later " How to solve it?

We are users like you. We can't make Apple's servers come back if they are currently down. So you'll have to wait or you can call them to complain. We cannot fix it for you.
Apple Store Customer Service at 1-800-676-2775 or visit online Help for more information.
To contact product and tech support: Apple - Support - Contact Apple Support.
For Mac App Store: Apple - Support - Mac App Store.
For iTunes: Apple - Support - iTunes.

ECP error "Your request couldn't be completed. Please try again in a few minutes."

Hi,
I'm having a problem with Exchange 2013 ECP which started with no apparent reason.
Anywhere i click i get error "Your request couldn't be completed. Please try again in a few minutes."
Other than that, everything seems to be working ok. I can even use ECP after i click OK on that error a few times.
Error log shows this message:
Current user: 'domain/user/removed'
Web service call 'https://server.domain:444/ecp/DDI/DDIService.svc/GetObject?workflow=GetForSDO&schema=ViewUserMailboxDetails&msExchEcpCanary=5bmUXzKmjk2N6Ey64H-cH7kIfLga_NAIZJxzV9Hvu71iCQWRHLXhQ3M_vw5KeOEMy-bhuKB4YlE.(https://mail.publicdomain.com/ecp/DDI/DDIService.svc/GetObject?workflow=GetForSDO&schema=ViewUserMailboxDetails&msExchEcpCanary=5bmUXzKmjk2N6Ey64H-cH7kIfLga_NAIZJxzV9Hvu71iCQWRHLXhQ3M_vw5KeOEMy-bhuKB4YlE.)'
failed with the following error:
System.ServiceModel.Dispatcher.NetDispatcherFaultException: The formatter threw an exception while trying to deserialize the message: There was an error while trying to deserialize parameter ECP:identity. The InnerException message was 'There was an error deserializing
the object of type Microsoft.Exchange.Management.ControlPanel.Identity. End element 'RawIdentity' from namespace '' expected. Found element 'IMGS_message_CMD' from namespace ''.'. Please see InnerException for more details. ---> System.Runtime.Serialization.SerializationException:
There was an error deserializing the object of type Microsoft.Exchange.Management.ControlPanel.Identity. End element 'RawIdentity' from namespace '' expected. Found element 'IMGS_message_CMD' from namespace ''. ---> System.Xml.XmlException: End element
'RawIdentity' from namespace '' expected. Found element 'IMGS_message_CMD' from namespace ''.
at System.Xml.XmlExceptionHelper.ThrowXmlException(XmlDictionaryReader reader, String res, String arg1, String arg2, String arg3)
at System.Xml.XmlBaseReader.ReadEndElement()
at System.Xml.XmlBaseReader.ReadElementContentAsString()
at ReadIdentityFromJson(XmlReaderDelegator , XmlObjectSerializerReadContextComplexJson , XmlDictionaryString , XmlDictionaryString[] )
at System.Runtime.Serialization.Json.JsonClassDataContract.ReadJsonValueCore(XmlReaderDelegator jsonReader, XmlObjectSerializerReadContextComplexJson context)
at System.Runtime.Serialization.Json.JsonDataContract.ReadJsonValue(XmlReaderDelegator jsonReader, XmlObjectSerializerReadContextComplexJson context)
at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator reader, String name, String ns, Type declaredType, DataContract& dataContract)
at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator xmlReader, Type declaredType, DataContract dataContract, String name, String ns)
at System.Runtime.Serialization.Json.DataContractJsonSerializer.InternalReadObject(XmlReaderDelegator xmlReader, Boolean verifyObjectName)
at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
--- End of inner exception stack trace ---
at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
at System.Runtime.Serialization.Json.DataContractJsonSerializer.ReadObject(XmlDictionaryReader reader, Boolean verifyObjectName)
at System.ServiceModel.Dispatcher.DataContractSerializerOperationFormatter.PartInfo.ReadObject(XmlDictionaryReader reader, XmlObjectSerializer serializer)
at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeParameterPart(XmlDictionaryReader reader, PartInfo part)
--- End of inner exception stack trace ---
at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeParameterPart(XmlDictionaryReader reader, PartInfo part)
at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeParameters(XmlDictionaryReader reader, PartInfo[] parts, Object[] parameters, PartInfo returnInfo, Object& returnValue)
at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeBodyCore(XmlDictionaryReader reader, Object[] parameters, Boolean isRequest)
at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeBody(XmlDictionaryReader reader, MessageVersion version, String action, MessageDescription messageDescription, Object[] parameters, Boolean isRequest)
at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeBodyContents(Message message, Object[] parameters, Boolean isRequest)
at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeRequest(Message message, Object[] parameters)
at System.ServiceModel.Dispatcher.DemultiplexingDispatchMessageFormatter.DeserializeRequest(Message message, Object[] parameters)
at System.ServiceModel.Dispatcher.UriTemplateDispatchFormatter.DeserializeRequest(Message message, Object[] parameters)
at Microsoft.Exchange.Management.ControlPanel.DiagnosticsBehavior.SerializationPerformanceTracker.DeserializeRequest(Message message, Object[] parameters)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.DeserializeInputs(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeParameterPart(XmlDictionaryReader reader, PartInfo part)
at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeParameters(XmlDictionaryReader reader, PartInfo[] parts, Object[] parameters, PartInfo returnInfo, Object& returnValue)
at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeBodyCore(XmlDictionaryReader reader, Object[] parameters, Boolean isRequest)
at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeBody(XmlDictionaryReader reader, MessageVersion version, String action, MessageDescription messageDescription, Object[] parameters, Boolean isRequest)
at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeBodyContents(Message message, Object[] parameters, Boolean isRequest)
at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeRequest(Message message, Object[] parameters)
at System.ServiceModel.Dispatcher.DemultiplexingDispatchMessageFormatter.DeserializeRequest(Message message, Object[] parameters)
at System.ServiceModel.Dispatcher.UriTemplateDispatchFormatter.DeserializeRequest(Message message, Object[] parameters)
at Microsoft.Exchange.Management.ControlPanel.DiagnosticsBehavior.SerializationPerformanceTracker.DeserializeRequest(Message message, Object[] parameters)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.DeserializeInputs(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
System.Runtime.Serialization.SerializationException: There was an error deserializing the object of type Microsoft.Exchange.Management.ControlPanel.Identity. End element 'RawIdentity' from namespace '' expected. Found element 'IMGS_message_CMD' from namespace
''. ---> System.Xml.XmlException: End element 'RawIdentity' from namespace '' expected. Found element 'IMGS_message_CMD' from namespace ''.
at System.Xml.XmlExceptionHelper.ThrowXmlException(XmlDictionaryReader reader, String res, String arg1, String arg2, String arg3)
at System.Xml.XmlBaseReader.ReadEndElement()
at System.Xml.XmlBaseReader.ReadElementContentAsString()
at ReadIdentityFromJson(XmlReaderDelegator , XmlObjectSerializerReadContextComplexJson , XmlDictionaryString , XmlDictionaryString[] )
at System.Runtime.Serialization.Json.JsonClassDataContract.ReadJsonValueCore(XmlReaderDelegator jsonReader, XmlObjectSerializerReadContextComplexJson context)
at System.Runtime.Serialization.Json.JsonDataContract.ReadJsonValue(XmlReaderDelegator jsonReader, XmlObjectSerializerReadContextComplexJson context)
at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator reader, String name, String ns, Type declaredType, DataContract& dataContract)
at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator xmlReader, Type declaredType, DataContract dataContract, String name, String ns)
at System.Runtime.Serialization.Json.DataContractJsonSerializer.InternalReadObject(XmlReaderDelegator xmlReader, Boolean verifyObjectName)
at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
--- End of inner exception stack trace ---
at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
at System.Runtime.Serialization.Json.DataContractJsonSerializer.ReadObject(XmlDictionaryReader reader, Boolean verifyObjectName)
at System.ServiceModel.Dispatcher.DataContractSerializerOperationFormatter.PartInfo.ReadObject(XmlDictionaryReader reader, XmlObjectSerializer serializer)
at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeParameterPart(XmlDictionaryReader reader, PartInfo part)
at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
at System.Runtime.Serialization.Json.DataContractJsonSerializer.ReadObject(XmlDictionaryReader reader, Boolean verifyObjectName)
at System.ServiceModel.Dispatcher.DataContractSerializerOperationFormatter.PartInfo.ReadObject(XmlDictionaryReader reader, XmlObjectSerializer serializer)
at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeParameterPart(XmlDictionaryReader reader, PartInfo part)
System.Xml.XmlException: End element 'RawIdentity' from namespace '' expected. Found element 'IMGS_message_CMD' from namespace ''.
at System.Xml.XmlExceptionHelper.ThrowXmlException(XmlDictionaryReader reader, String res, String arg1, String arg2, String arg3)
at System.Xml.XmlBaseReader.ReadEndElement()
at System.Xml.XmlBaseReader.ReadElementContentAsString()
at ReadIdentityFromJson(XmlReaderDelegator , XmlObjectSerializerReadContextComplexJson , XmlDictionaryString , XmlDictionaryString[] )
at System.Runtime.Serialization.Json.JsonClassDataContract.ReadJsonValueCore(XmlReaderDelegator jsonReader, XmlObjectSerializerReadContextComplexJson context)
at System.Runtime.Serialization.Json.JsonDataContract.ReadJsonValue(XmlReaderDelegator jsonReader, XmlObjectSerializerReadContextComplexJson context)
at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator reader, String name, String ns, Type declaredType, DataContract& dataContract)
at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator xmlReader, Type declaredType, DataContract dataContract, String name, String ns)
at System.Runtime.Serialization.Json.DataContractJsonSerializer.InternalReadObject(XmlReaderDelegator xmlReader, Boolean verifyObjectName)
at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
at System.Xml.XmlExceptionHelper.ThrowXmlException(XmlDictionaryReader reader, String res, String arg1, String arg2, String arg3)
at System.Xml.XmlBaseReader.ReadEndElement()
at System.Xml.XmlBaseReader.ReadElementContentAsString()
at ReadIdentityFromJson(XmlReaderDelegator , XmlObjectSerializerReadContextComplexJson , XmlDictionaryString , XmlDictionaryString[] )
at System.Runtime.Serialization.Json.JsonClassDataContract.ReadJsonValueCore(XmlReaderDelegator jsonReader, XmlObjectSerializerReadContextComplexJson context)
at System.Runtime.Serialization.Json.JsonDataContract.ReadJsonValue(XmlReaderDelegator jsonReader, XmlObjectSerializerReadContextComplexJson context)
at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator reader, String name, String ns, Type declaredType, DataContract& dataContract)
at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator xmlReader, Type declaredType, DataContract dataContract, String name, String ns)
at System.Runtime.Serialization.Json.DataContractJsonSerializer.InternalReadObject(XmlReaderDelegator xmlReader, Boolean verifyObjectName)
at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)

Hi,
Compatibility problem. Glad to know that we found the solution.
Have a nice day : )
Thanks
Mavis
Mavis Huang
TechNet Community Support

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

Your request couldn't be completed. Please try again in a few minutes

Hello everyone,
I recovered the exchange 2013 C7 and now I'm receiving a message error when I try to open the admin ECP page, Mail flow, Rules.
I get the message error: "Your request couldn't be completed. Please try again in a few minutes." If I try to create a new rule, I get an error message "access denied".
However, I'm able to created a new transportule through powershell.
I'm accessing ECP from IE. All services are started and running.Im also accessing Exchange server with Domain\Administrator account and the administrator have the following group membership:
Domain Admins
Schema Admins
Enterprise Admins
Organization Management
below is what I get on the file log:
Current user: 'mydomain.local/MyBusiness/Users/Admin'
Web service call 'https://exchangeserver.mydomain.local:444/ecp/RulesEditor/TransportRules.svc/GetList?msExchEcpCanary=p2Zp1y_1kESsrueBkDB6T1r0z46NLdII4Q_D6294gRCkKBixfp0OnWr9OfSQ9SO205BuS7NQnns.(https://remote.mydomain.com/ecp/RulesEditor/TransportRules.svc/GetList?msExchEcpCanary=p2Zp1y_1kESsrueBkDB6T1r0z46NLdII4Q_D6294gRCkKBixfp0OnWr9OfSQ9SO205BuS7NQnns.)'
failed with the following error:
System.Security.SecurityException: Request for principal permission failed.
at System.Security.Permissions.PrincipalPermission.ThrowSecurityException()
at System.Security.Permissions.PrincipalPermission.Demand()
at Microsoft.Exchange.Management.ControlPanel.WebServiceParameters.set_Item(String cmdletParameterName, Object value)
at Microsoft.Exchange.Management.ControlPanel.ResultSizeFilter.set_ResultSize(Int32 value)
at ReadTransportRuleFilterFromJson(XmlReaderDelegator , XmlObjectSerializerReadContextComplexJson , XmlDictionaryString , XmlDictionaryString[] )
at System.Runtime.Serialization.Json.JsonClassDataContract.ReadJsonValueCore(XmlReaderDelegator jsonReader, XmlObjectSerializerReadContextComplexJson context)
at System.Runtime.Serialization.Json.JsonDataContract.ReadJsonValue(XmlReaderDelegator jsonReader, XmlObjectSerializerReadContextComplexJson context)
at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator reader, String name, String ns, Type declaredType, DataContract& dataContract)
at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator xmlReader, Type declaredType, DataContract dataContract, String name,
String ns)
at System.Runtime.Serialization.Json.DataContractJsonSerializer.InternalReadObject(XmlReaderDelegator xmlReader, Boolean verifyObjectName)
at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
at System.Runtime.Serialization.Json.DataContractJsonSerializer.ReadObject(XmlDictionaryReader reader, Boolean verifyObjectName)
at System.ServiceModel.Dispatcher.DataContractSerializerOperationFormatter.PartInfo.ReadObject(XmlDictionaryReader reader, XmlObjectSerializer serializer)
at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeParameterPart(XmlDictionaryReader reader, PartInfo part)
at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeParameters(XmlDictionaryReader reader, PartInfo[] parts, Object[] parameters, PartInfo
returnInfo, Object& returnValue)
at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeBodyCore(XmlDictionaryReader reader, Object[] parameters, Boolean isRequest)
at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeBody(XmlDictionaryReader reader, MessageVersion version, String action, MessageDescription
messageDescription, Object[] parameters, Boolean isRequest)
at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeBodyContents(Message message, Object[] parameters, Boolean isRequest)
at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeRequest(Message message, Object[] parameters)
at System.ServiceModel.Dispatcher.DemultiplexingDispatchMessageFormatter.DeserializeRequest(Message message, Object[] parameters)
at System.ServiceModel.Dispatcher.UriTemplateDispatchFormatter.DeserializeRequest(Message message, Object[] parameters)
at Microsoft.Exchange.Management.ControlPanel.DiagnosticsBehavior.SerializationPerformanceTracker.DeserializeRequest(Message message, Object[] parameters)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.DeserializeInputs(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
The action that failed was:
Demand
The type of the first permission that failed was:
System.Security.Permissions.PrincipalPermission
The first permission that failed was:
<IPermission mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
version="1">
<Identity Authenticated="true"
Role="Get-TransportRule?ResultSize@R:Organization"/>
</IPermission>
The demand was for:
<IPermission mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
version="1">
<Identity Authenticated="true"
Role="Get-TransportRule?ResultSize@R:Organization"/>
</IPermission>
The assembly or AppDomain that failed was:
mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
at System.Security.Permissions.PrincipalPermission.ThrowSecurityException()
at System.Security.Permissions.PrincipalPermission.Demand()
at Microsoft.Exchange.Management.ControlPanel.WebServiceParameters.set_Item(String cmdletParameterName, Object value)
at Microsoft.Exchange.Management.ControlPanel.ResultSizeFilter.set_ResultSize(Int32 value)
at ReadTransportRuleFilterFromJson(XmlReaderDelegator , XmlObjectSerializerReadContextComplexJson , XmlDictionaryString , XmlDictionaryString[] )
at System.Runtime.Serialization.Json.JsonClassDataContract.ReadJsonValueCore(XmlReaderDelegator jsonReader, XmlObjectSerializerReadContextComplexJson context)
at System.Runtime.Serialization.Json.JsonDataContract.ReadJsonValue(XmlReaderDelegator jsonReader, XmlObjectSerializerReadContextComplexJson context)
at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator reader, String name, String ns, Type declaredType, DataContract& dataContract)
at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator xmlReader, Type declaredType, DataContract dataContract, String name,
String ns)
at System.Runtime.Serialization.Json.DataContractJsonSerializer.InternalReadObject(XmlReaderDelegator xmlReader, Boolean verifyObjectName)
at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
at System.Runtime.Serialization.Json.DataContractJsonSerializer.ReadObject(XmlDictionaryReader reader, Boolean verifyObjectName)
at System.ServiceModel.Dispatcher.DataContractSerializerOperationFormatter.PartInfo.ReadObject(XmlDictionaryReader reader, XmlObjectSerializer serializer)
at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeParameterPart(XmlDictionaryReader reader, PartInfo part)
at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeParameters(XmlDictionaryReader reader, PartInfo[] parts, Object[] parameters, PartInfo
returnInfo, Object& returnValue)
at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeBodyCore(XmlDictionaryReader reader, Object[] parameters, Boolean isRequest)
at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeBody(XmlDictionaryReader reader, MessageVersion version, String action, MessageDescription
messageDescription, Object[] parameters, Boolean isRequest)
at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeBodyContents(Message message, Object[] parameters, Boolean isRequest)
at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeRequest(Message message, Object[] parameters)
at System.ServiceModel.Dispatcher.DemultiplexingDispatchMessageFormatter.DeserializeRequest(Message message, Object[] parameters)
at System.ServiceModel.Dispatcher.UriTemplateDispatchFormatter.DeserializeRequest(Message message, Object[] parameters)
at Microsoft.Exchange.Management.ControlPanel.DiagnosticsBehavior.SerializationPerformanceTracker.DeserializeRequest(Message message, Object[] parameters)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.DeserializeInputs(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
Demand: <IPermission mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
version="1">
<Identity Authenticated="true"
Role="Get-TransportRule?ResultSize@R:Organization"/>
</IPermission>
First Failed Demand: <IPermission mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
version="1">
<Identity Authenticated="true"
Role="Get-TransportRule?ResultSize@R:Organization"/>
</IPermission>
Url: https://exchangeserver.mydomain.local:444/ecp/RulesEditor/TransportRules.svc/GetList?msExchEcpCanary=p2Zp1y_1kESsrueBkDB6T1r0z46NLdII4Q_D6294gRCkKBixfp0OnWr9OfSQ9SO205BuS7NQnns.(https://remote.mydomain.com/ecp/RulesEditor/TransportRules.svc/GetList?msExchEcpCanary=p2Zp1y_1kESsrueBkDB6T1r0z46NLdII4Q_D6294gRCkKBixfp0OnWr9OfSQ9SO205BuS7NQnns.)
Flight info: Features:[[Global.DistributedKeyManagement, False],[Global.GlobalCriminalCompliance, False],[Global.MultiTenancy, False],[Global.WindowsLiveID, False],[Eac.AllowMailboxArchiveOnlyMigration,
True],[Eac.AllowRemoteOnboardingMovesOnly, False],[Eac.BulkPermissionAddRemove, True],[Eac.CmdletLogging, True],[Eac.CrossPremiseMigration, False],[Eac.DevicePolicyMgmtUI, False],[Eac.DiscoveryDocIdHint, False],[Eac.DiscoveryPFSearch, False],[Eac.DiscoverySearchStats,
False],[Eac.DlpFingerprint, False],[Eac.EACClientAccessRulesEnabled, False],[Eac.GeminiShell, False],[Eac.ManageMailboxAuditing, False],[Eac.ModernGroups, False],[Eac.Office365DIcon, False],[Eac.OrgIdADSeverSettings, False],[Eac.RemoteDomain, False],[Eac.UCCAuditReports,
False],[Eac.UCCPermissions, False],[Eac.UnifiedAuditPolicy, False],[Eac.UnifiedComplianceCenter, False],[Eac.UnifiedPolicy, False],[Eac.UnlistedServices, False],], Flights:[], Constraints:[[LOC, EN-US],[MACHINE, EXCHANGESERVER],[MODE, ENTERPRISE],[PROCESS,
W3WP],[USER, TECHSUPPORT@],[USERTYPE, BUSINESS],], IsGlobalSnapshot: False
flavio

My server is running Exchange 2013 C7 Version 15.0 ‎(Build 913.22)‎.
How can I update the ExchangeVersion and
RBACConfigurationVersion?
PS] C:\Windows\system32>Get-transportrule test | fl *version
RuleVersion : 14.0.0.0
ExchangeVersion : 0.1 (8.0.535.0)
[PS] C:\Windows\system32>get-organizationconfig | fl *rba*
RBACConfigurationVersion : 0.1 (15.0.913.18)
flavio

ECP could not save UM Auto Attendant "Your request couldn`t be completed. Please try again in a few minutes"

Good Day.
I have Exchange 2013 SP1 CU5, everything works fine except only one thing:
1. ECP/UM/UM dial plan/UM Auto Attendant
2. I am receiving error only when i am adding Prompt in Menu Navigation. In "Menu Navigation Entry" i could press "OK" button successfully, in "UM Auto Attendant" when i am pressing "Save" - "error. Your request
couldn`t be completed. Please try again in a few minutes"
I`ve already done:
1. Checked IIS bindings
2. Recycle ApplicationPools
3. Restart IIS
Nothing helps...

Problem solved, in the prompt you shoudn`t use special charactes ^) ' " , / ' After i`1ve removed it from prompt everething saves ok.

Your request has failed. please try again later for messaging and web app my verizon

>> Duplicate post removed to comply with the Verizon Wireless Terms of Service Please see Cannot view messaging on computer at my verizon all of a sudden. using messages <<
Message was edited by: Verizon Moderator

I am having the same problem. It started on August 11, 2014. I get the "Your request has failed. Please try again later." message when logging into the Verizon Messaging web application.
Here is what I did to troubleshoot it:
I verified that I can log into the MyVerizon account successfully.
Verified that the feature was set up correctly.
Cleared cache and history on my browser.
Tried two different browsers - same result.
Tried a different computer - same result.
Tried from a mobile device - same result.
It is definitely on the Verizon end. I called their tech support and of course, got no results as usual.
Verizon creates and promotes all these features, you get dependent on using them, and they stop working. Then, of course Verizon can't resolve the issue. I'm shopping around when my contracts are up. For the premium price we pay for Verizon I would expect better stability and support in their service.

We're sorry, but we are unable to complete your request at this time. Please try again in a few minutes.

How can i remove old device's from My Support Profile.
When i try to remove a device, then i see this.
We're sorry............................
It is not possible te remove.
Any one with a fix for this.
Thanks.

Yeah, it kept doing it when I was trying to change the delivery address, changed it on my apple main apple profile adress and then it worked on the repair page.

Getting "Sorry! We're having trouble processing your request right now. Please try again in a few minutes." when trying to set auto-replies in OWA

Similar Messages

Maybe you are looking for