Exchange stops working!!!

Was getting my work email through Exchange perfectly and since yesterday I get nothing but a "connection to server failed" message. Nothing in the setting has changed, the password is correct, etc. I can still get email on my desktop via Mail 4.1. I can get my Gmail on my phone and surf the web. Tried a restore on my phone and that did nothing either. Tried my IT to no avail. Can someone help!?!
iPhone 3G
3.1.2

Yes I can access my email OWA and no my IT Admin has not blocked my iPhone. I was working before and all of a sudden now it doesn't. Very strange and frustrating since I need to get my email on the go. I have tried a complete restore and deleted/recreated the account, did not help either.

Similar Messages

Mail exchange stop working after the latest upgrade, how do you reboot it to restart again

Mail exchange stop working after the latest upgrade, how do you reboot it to restart again

Hmmm, here's the opposite problem/fix...
Gmail send but not receive...
Here are two steps that have come in handy in related situations
1) login to gmail on your computer or device via a web browser
2) once logged in successfully, go to this URL to unlock:
https://www.google.com/accounts/DisplayUnlockCaptch
Is your gMail POP or IMAP?
If IMAP...
Is the Outgoing server smtp.gmail.com, port 25, SSL on, & Authentication = Password

Mail for Exchange stopped working after installing...

I downloaded the software updater and duly connected and updated the firmware in my X6. It now has the latest version, although oddly the updater said that it needed updating with a new version from Sunday 2nd May. I now have the 4th May version.
Anyway since updating the firmware, Mail for exchange doesn't work, it is in the program list and starts to react when touched but then stops. It offers no error message but simply refuses to start.
I have tried the windows classics (off and on again) and even tried to update the firmware with the latest version of the updater, which it told me that the firmware was up to date but I could update it again if I wanted, so I did.
Anyway, No email etc on the phone and M4e is not working, I have emailed Nokia technical and thought I'd try this as well.
Any help would be gratefully recieved.
Paul

I have a similar ongoing problem with MfE and my E63, in that after a period of time ranging anywhere between 1 and 3 months, I start getting system errors and "try again later" messages in the MfE log when trying to synchronize my email (no contacts or calendar sync, email only from my company's exchange webmail server, MfE installed on phone memory). I typically could get it to sync if I forced it two or three times in a row, but it generally completely stopped syncing on the schedule I had put in, regardless of whether "always on" or a time interval was selected.
I get the feeling there is something in memory or a log file someplace that builds up and starts causing these errors - so far I have been able to fix the problem every time by simply reinstalling the same version of MfE. When asked if you want to overwrite the existing version, choose yes. You shouldn't have to re-enter any setup or credential information.

Mail for Exchange Stopped Working

After a Successfull migration from Exch 2003 to 2007
RPCOverHTTPS Works
OWA Works
ActiveSync over a PPC5.0 Device Works
Only Mail for Exchange 2.1 on my Nokia E65 (Which i use the most) stopped Connecting
Address\Security hasen't changed
Did anyone else encounter this ?
Or

Does this work for E50? Please, let me know.

Exchange OWA stopped Working.

Our Exchange stopped working after I made some changes to the Remote access and the VPN Connection.
When i try to Open exchange management console I get his error:
[<var style="color:#333333;font-family:'Segoe UI', Arial, Verdana, Tahoma, sans-serif;font-size:13px;line-height:normal;background-color:#f5f5f5;"><server
name></var>] Connecting to remote server failed with the following error message : The WinRM client received
an HTTP status code of 403 from the remote WS-Management service.
I have had problems with my
exchange bindings disappearing after the server was rebooted, and I did reboot the server when making changes to the VPN setup.
MY bindings for Exchange back end are:
http port 80
ip address *
https Port 443
ip address *
Yes SSL and ignore
My MY bindings for Default web site are:
http port 80
ip address 192.168.0.19 (Servers IP address)
https Port 443
ip address 192.168.0.19 (Servers IP address)
Yes SSL and ignore
I have tryed this but it did not help and I turned SSL back on. With SSL turned off I get this error.
http://www.exchangedictionary.com/articles/winrm-client-received-an-http-status-code-of-403-when-opening-emc-ems
The WinRM client tried to use Kerberos authentication mechanism, but the destination
computer (ServerName.domain.local:80)
I have turned SSL back on for PowerShell
I can't access OWA or exchange management console.
Help ?

Yes, I have check the certificate for https. I have a certificate
from go daddy I used and its bound to both Default
web and Exchange back end.
Does what I have for bindings
look correct ?
My outlook is working to received email and sending it mostly working.
I can't access OWA or exchange management console though.
sometimes I get this error:
Delivery is delayed to these recipients or groups:
This message hasn't been delivered yet. Delivery will continue to be attempted.
The server will keep trying to deliver this message for the next 1 days, 22 hours and 59 minutes. You'll be notified if the message can't be delivered by that time.
I am not sure if this is the same problem or another problem I am having ..... :(
Email to the phone stopped working today when I was trying to fixed the bindings.

ActiveSync stops working after migrating from Exchange 2007 to Exchange 2013

We have started the migration from Exchange 2007 to Exchange 2013. We've followed best practices and everything is working great except ActiveSync. I've performed Exchange migrations in the past so this is nothing new for me. I've also been referring to
a great guide which has been a big help,
http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/planning-and-migrating-small-organization-exchange-2007-2013-part1.html.
Once a user is migrated from Exchange 2007 to 2013, ActiveSync stops working properly. Email can be pulled to the device (Nokia Lumia 625 running Windows Phone 8) by performing a manual sync. But DirectPush is not working. The strange part is it's not affecting
everyone who's been migrated. Anyone who is still on Exchange 2007 is not affected.
At first I thought it was our wildcard certificate. 99% of our users are running Outlook 2013 on Windows 7 or higher but we do have a few terminal servers still running Outlook 2010. Outlook 2010 was giving us certificate errors. I realized it was the wildcard
certificate. Rather than making changes to the OutlookProvider I simply obtained a new SAN certificate. Although that resolved the issues for Outlook 2010 users, ActiveSync was still a problem.
Rebooting the phones and removing the email account from the user's device and re-adding it didn't resolve the issue either.
Then I performed an iisreset on the CAS server. This didn't help either. I didn't know it at the time, but I was getting closer...
I tried using the cmdlet Test-ActiveSyncConnectivity but it gave me the following error:
WARNING: Test user 'extest_0d9a45b025374' isn't accessible, so this cmdlet won't be able to test Client Access server
connectivity.
Could not find or sign in with user DOMAIN.com\extest_0d9a45b025374. If this task is being run without
credentials, sign in as a Domain Administrator, and then run Scripts\new-TestCasConnectivityUser.ps1 to verify that
the user exists on Mailbox server EX02.DOMAIN.COM
I started reviewing how Exchange 2013 proxied information from the CAS to the mailbox server and realized the issue may in fact be on the mailbox server.
I performed an iisreset on the mailbox server and all of a sudden ActiveSync started working again. Awesome!
I can't explain why. The only thing I can assume is when some users were migrated from 2007 to 2013 something wasn't being triggered on the Exchange 2013 side. Resetting IIS resolved the issue. I guess I'll have to do an IIS reset after I perform a batch
of migrations. Disabling ActiveSync and re-enabling it for the affected users didn't help - only the IISRESET resolved the issue.
If anyone has any information as to why this happens, please chime in. Also, if anyone knows why I can't run the Test-ActiveSyncConnectivity cmdlet, I'd appreciate the help.
Thanks.

Hi,
In Exchange 2013, the Public Folder is changed to Public Folder mailbox instead of Public Folder in Exchange 2007 database.
Due to the changes in how public folders are stored, legacy Exchange mailboxes are unable to access the public folder hierarchy on Exchange 2013 servers. However, user mailboxes on Exchange 2013 servers or Exchange Online can connect to legacy
public folders. Exchange 2013 public folders and legacy public folders can’t exist in your Exchange organization simultaneously. This effectively means that
there’s no coexistence between versions.
For this reason, it’s recommended that prior to migrating your public folders, you should
first migrate your all legacy mailboxes to Exchange 2013. For more information about migrating public folder from previous versions, please refer to:
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
(Please note the What do you need to know before you begin part in this link)
Regards,
Winnie Liang
TechNet Community Support

Mail.app stopped working over IMAP to exchange 2003 server

Hi Peoples,
I'm posting this as a problem with the solution simply because of the absolute bizarre behavior that I observed....
PROBLEM
On Thursday night, without me having made any changes to either my mac or my exchange server, mail.app just stopped working. The problem was like many I've read about on various forums including this one but none of the solutions worked. Basically the problem was that the server would no longer authenticate mail.app's connection attempts. It failed both plain text and SSL with both NTLM and password style authentication. IMAP from a PC was still working OK (I keep this around for testing). So I tried the following...
Removed all the relevant keychain entries - no go
Removed the entire login keychain - no go
Removed & reconfigured the exchange account config from mail.app - no go
Removed the entire config from mail.app (i.e. removed ~/Library/Preferences/com.apple.mail.plist ) - bop-bong still no go
created a new IMAP service in exchange in case something was screwed there - no go
created a new user in exchange and tried that user - still no go
sledge hammer approach - reinstalled OS X - no go
48+ hours later... Getting very frustrated by now... scratching head...
SOLUTION
OK (should have done this much earlier and saved much pain), time to install another IMAP client on the mac and see what happens.... installed Thunderbird and low and behold it worked first go with and without SSL - hmmm
Restarted mail.app and reconfigured to use same settings as thunderbird (SSL with password authentication - no NTLM)
What the????? Now it all works again....
I cannot for the life of me figure out why this happened, and why only mail.app was affected. Obviously, something went screwy on the Exchange server and caused mail.app to have a coronary. Whatever it was, other IMAP clients seemed to be able to handle it. Was it the install and subsequent use of thunderbird that fixed it - I hope not but who knows...
Think I'll be keep thunderbird installed in case it happens again... very, very, very strange.
Anyways... hope this helps if anyone else experiences such unexplainable weirdness.
Cheers - I'm going to have Chardy on the balcony and think about something else.

Just thought I'd update with the latest... This problem happened again this morning and again, the only way to fix it was to connect from the mac with another IMAP client (I used Thunderbird again) and immediately the problem was fixed.
Need to do some detailed network analysis here to see exactly what's going on but it's definitely a case of mail.app not playing nicely with Exchange (or vice versa).
Cheers, time for a JD

Receive Connector stopped working after Update Rollout 2 for Exchange 2007 SP2

One of the Exchange 2007 servers receive connector has stopped working since installing the latest rollout update for Exchange 2007 SP2 - for some reason the following error is received (when troubleshooting on the adjacent server) :
"Remote server server.domain.co.uk failed the mail acceptance test. MAIL FROM command: Respond = 530 5.7.1 Client was not authenticated."
Most admins will know you usually get this when first setting up Exchange and the receive connector not allowing anonymous connections. But our setup has been working for well over a year with no problems. Even enabling anonymous connections still doesn't fix the problem.
Our setup is 2 exchange servers across 2 sites, with the problematic server never receiving email from the internet, only from the other Exchange server (which is internet facing). The above error is received when the internet facing server is relaying email over to the problematic server. Though in the message queue the following error is received:
"SMTPSEND.DNS.NonExistantDomain; nonecistant domain"
After testing DNS that all seems fine, so I don't believe it's a DNS problem.
Any ideas why this would happen?
Thanks,
Matt

Hi Matt....
To receive e-mails from the external servers or domains or clients, you can setup a new receive connector on Hub Transport Server. To do this task, you can go through the steps mentioned in this blog....
https://mailsolutions.wordpress.com/2015/02/06/resolving-error-530-5-7-1-client-was-not-authenticated-with-receiver-connector/
Hope this will work
Thanks

"OutlookSyncClient has stopped working" when Exchange Cached Mode is On.

Hi,
I have an iPhone 3G which originally didn't sync with outlook 2003 in Vista. Sync is being perform via USB. I initially tried reinstalling iTunes, Reset sync history, Syncing with new windows user but could not get it to sync without an error. Vista displays an "OutlookSyncClient has stopped working" error when it tries to sync the calendar. Finally figured out that if you untick "Exchange Cached Mode", it will sucessfully sync with Outlook. However, this is not a workable solution as the computer is a notebook and needs to be able to access their Outlook email while away from the office (and hence needs to be working in Exchange Cached Mode).
After this, I tried rebuilding the Outlook OST file. I also tried deleting the exchange connection and re-adding the exchange connection to the user profile from scratch. I was not able to get it to sync without the error.
Does anyone know of a solution to this problem? or anything else to try? The only workaround at this point is to disable cached mode while in the office, sync the phone and then re-enable cached mode after the sync is complete. This is proving to be quite a pain, surely there must be a way to solve this problem!

Well, your tip helped me to not get this error only by acessing the "Info"-Tab as happened before, thank you!
I was really happy, but then starting the synchronisation itself crashed again with the same error...
So I am still clueless... It must have something to do with outlook being used with Exchange. At home, where I use it locally, synchronisation did work...
sigh
Message was edited by: adeptus
Message was edited by: adeptus

PC Exchange has stopped working

The PC exchange function of my iMac (9.2.2) has stopped working. I can open PC files directly from the appropriate application, but double clicking on the PC file results in an error message that the application that created it is not on this computer. Also the File Translation box won't let me create any new translation mappings. I wonder if I have thrown away any important in an ill advised cleanup?
Robin Helmond

Hi, Robin -
Can't think of anything else that might directly affect the File Exchange control panel, other than throwing away its preference file and restarting. Note, though, that by doing that all settings in both File Translation and PC Exchange will probably return to default.
One other item to consider - when OS 9.1 first came out, many folk found that the new File Exchange control panel, v. 3.0.4, did not work as it should. The solution for that was to replace it with the one that came with OS 9.0.4, v. 3.0.3.
If you want to experiment with using different versions of that control panel, you can use the utility TomeViewer to extract (expand) any files you want from an Installation Tome on an OS Install CD or download disk image, without running the installer.
How to use TomeViewer

Exchange 2013- Outlook will stop working intermittently but OWA works that time

Hello everyone. Hope someone can help me with this issue. We are experiencing a strange issue with our exchange 2013 server. We only have one exchange 2013 server and it is up to the CU2 level. The issue is sometimes the outlook clients
will stop working and the only way to fix this issue is by restarting the server . I tried restarting the exchange services but it didn't fix the issue. The outlook web access will work without any issue during this time. My research indicates
that the exchange server is getting some kind of disconnection/timeout from the Active directory. I can see the following event logs on the exchange server:
Log Name:      Microsoft-Exchange-MailboxDatabaseFailureItems/Operational
Source:        Microsoft-Exchange-MailboxDatabaseFailureItems
Date:          13/03/2014 1:12:20 PM
Event ID:      1
Task Category: Store
Level:         Information
Keywords:
User:          SYSTEM
Computer:      xxEXCHSVR.xxxx.local
Description:
Failure Item (Namespace=Store, Tag=HungStoreWorker, Database=CN=Mailbox Database 0572517180,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=xxxxxxxxx,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=xx,DC=local,
Instance=Mailbox Database 0572517180)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Microsoft-Exchange-MailboxDatabaseFailureItems" Guid="{08E893EA-4C11-4FFF-A737-99B9EEDEE4F4}" />
    <EventID>1</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>1</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2014-03-13T02:42:20.026303800Z" />
    <EventRecordID>8180</EventRecordID>
    <Correlation />
    <Execution ProcessID="5980" ThreadID="14380" />
    <Channel>Microsoft-Exchange-MailboxDatabaseFailureItems/Operational</Channel>
    <Computer>xxEXCHSVR.xxxxxx.local</Computer>
    <Security UserID="S-1-5-18" />
</System>
<UserData>
    <EventXML xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="myNs">
      <Version>1</Version>
      <Namespace>1</Namespace>
      <Tag>38</Tag>
      <DatabaseGuid>{D789BB55-9D2A-445C-B29E-E7EA510E89D6}</DatabaseGuid>
      <DatabaseInstanceName>Mailbox Database 0572517180</DatabaseInstanceName>
      <Component>StoreService</Component>
      <IOErrorIsSpecified>false</IOErrorIsSpecified>
      <NotificationEventIsSpecified>false</NotificationEventIsSpecified>
      <IOError>
        <Category>0</Category>
        <FileName>
        </FileName>
        <Offset>0</Offset>
        <Size>0</Size>
      </IOError>
      <NotificationEvent>
        <EventID>0</EventID>
        <ParameterBufferSize>0</ParameterBufferSize>
        <ParameterBuffer>
        </ParameterBuffer>
      </NotificationEvent>
    </EventXML>
</UserData>
</Event>
Log Name:      Microsoft-Exchange-HighAvailability/Operational
Source:        Microsoft-Exchange-HighAvailability
Date:          3/03/2014 1:43:53 PM
Event ID:      841
Task Category: Database Action
Level:         Error
Keywords:
User:          SYSTEM
Computer:      xxEXCHSVR.xxxx.local
Description:
ListMdbStatus failed to server 'xxexchsvr': Microsoft.Mapi.MapiExceptionTimeout: MapiExceptionTimeout: RPC operation (ExRpcAdmin.Create) to the Microsoft Exchange Information Store service timed out. Operation did not complete within the given timeout of 00:00:05.
(hr=0x80040401, ec=0) ---> System.TimeoutException: Operation did not complete within the given timeout of 00:00:05.
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.InternalInvoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.Invoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
   --- End of inner exception stack trace ---
Server stack trace:
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
   at Microsoft.Exchange.Cluster.Replay.StoreRpcController.get_ExRpcAdmin()
   at Microsoft.Exchange.Cluster.Replay.StoreRpcController.<>c__DisplayClass19.<ListMdbStatus>b__18()
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.<>c__DisplayClass2.<ProtectedCallWithTimeout>b__0()
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
   at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
   at System.Action.EndInvoke(IAsyncResult result)
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.InternalInvoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.Invoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
   at Microsoft.Exchange.Cluster.Replay.StoreRpcController.ListMdbStatus(Boolean isBasicInformation)
   at Microsoft.Exchange.Cluster.ActiveManagerServer.AmStoreHelper.GetAllDatabaseStatuses(AmServerName serverName, Boolean isBasicInformation, MdbStatus[]& mdbStatuses, Exception& exception)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Microsoft-Exchange-HighAvailability" Guid="{455E3D31-77EF-4853-94A1-032A399567EC}" />
    <EventID>841</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>1</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2014-03-03T03:13:53.421449100Z" />
    <EventRecordID>15370</EventRecordID>
    <Correlation />
    <Execution ProcessID="7264" ThreadID="5188" />
    <Channel>Microsoft-Exchange-HighAvailability/Operational</Channel>
    <Computer>xxEXCHSVR.xxxxx.local</Computer>
    <Security UserID="S-1-5-18" />
</System>
<UserData>
    <EventXML xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="myNs">
      <NodeName>xxexchsvr</NodeName>
      <Message>Microsoft.Mapi.MapiExceptionTimeout: MapiExceptionTimeout: RPC operation (ExRpcAdmin.Create) to the Microsoft Exchange Information Store service timed out. Operation did not complete within the given timeout of
00:00:05. (hr=0x80040401, ec=0) ---> System.TimeoutException: Operation did not complete within the given timeout of 00:00:05.
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.InternalInvoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.Invoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
   --- End of inner exception stack trace ---
Server stack trace:
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
   at Microsoft.Exchange.Cluster.Replay.StoreRpcController.get_ExRpcAdmin()
   at Microsoft.Exchange.Cluster.Replay.StoreRpcController.<>c__DisplayClass19.<ListMdbStatus>b__18()
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.<>c__DisplayClass2.<ProtectedCallWithTimeout>b__0()
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
   at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
   at System.Action.EndInvoke(IAsyncResult result)
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.InternalInvoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.Invoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
   at Microsoft.Exchange.Cluster.Replay.StoreRpcController.ListMdbStatus(Boolean isBasicInformation)
   at Microsoft.Exchange.Cluster.ActiveManagerServer.AmStoreHelper.GetAllDatabaseStatuses(AmServerName serverName, Boolean isBasicInformation, MdbStatus[]& mdbStatuses, Exception& exception)</Message>
    </EventXML>
</UserData>
</Event>
Can anyone please tell me what causing this issue?
Thanks in advance.

Hi,
According to your description, your Outlook client intermittently cannot work. I recommend you try to use RPC trace log to find the root cause.
Additionally, I recommend you update to Exchange 2013 sp1 and then check if the issue still can be reproduced.
http://blogs.technet.com/b/rmilne/archive/2014/02/25/exchange-2013-sp1-released.aspx
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

ISync (and BT File Exchange) Mysteriously Stop Working...

Hi there. I've been very happily syncing my Sony Ericsson Z520a with my Powerbook G4 for a while. Almost a year in fact. Now, suddenly, isync stopped being able to connect to my phone. I have checked everything I know how to check; bluetooth is enabled on both my phone and my computer and the two are able to see each other, and all the settings on my phone and my computer are the same as they were before this stopped working.
I'm getting this error:
[Z520a] Connection to the phone failed.
Please make sure that your phone is turned on. If this error occurs again, please restart your phone.
Device "Z520a" synchronization failed
At first my computer couldn't see my phone, and my phone couldn't see my computer. When this first happened and I was trying to figure out what was wrong, I noticed that the "Computer Name" in the Bluetooth System Preference pane had gone to "Not Available". Initially I tried changing the name of my computer under Sharing, but that didn't help, so I restarted the computer and the phone. Then I re-paired the two devices. They saw each other just fine after that, and when I hit sync in iSync my phone is definitely communicating with my computer (its bluetooth activity indicator says it's communicating) but I still get the above error, and nothing is being transfered between my phone and computer. When I try to Browse my phone with Bluetooth File Exchange, it tells me "The connection Failed or Closed."
So, can anyone help me? Synchronizing my phone's calendar with my iCal is a big thing for me, and I really need to find a way to make it work again.
Thanks!

Hi- I'm a Verizon customer, not Cingular but I know that Verizon purposefully cripples their phones to not allow BT file transfer... forcing you to email your pics, etc... which costs money. I would guess that maybe Cingular does the same?
As you've noticed... the Razor IS compatible with iSync... and there aren't a ton of phones that even do that, so that's a positive. I have a Motorola e815 and there ARE ways on the net to hack it to enable BT file transfer, though I'm not going to try them. Does the Razor have a memory card? I bought a memory card for my phone and I do transfers that way.
Anyway... like I said, I'm not sure that this is a Cingular issue, I'm just offering a thought since that's what I'm dealing with. You might try browsing the iSync part of the forums to find more info!

HT2480 Ipad mini - exchange email stopped working randomly Error: "Cannot get mail. The connection to the server failed."

I got an iPad mini over Christmas and have had no issues setting up/managing my email until yesterday. I've had my Exchange email working for almost a month, and yesterday I stopped getting emails and getting the error: "Cannot Get Mail. The connection to the server failed."
I tried resetting the device (multiple times) and deleting and recreating the Exchange account (multiple times). This is getting annoying because it worked fine up until yesterday. I'm not aware of any updates to the device, or any changes that have occurred since yesterday.

Due to a screen issue, I had my iPhone 5 replaced two days ago. I repeated deleted the mail account and kept adding it but this did not make any difference. When I attempted to setup the new phone with my Google (Gmail via exchange active sync) accounts I was receiving this same "Cannot Get Mail" error. From what I was able to gather, this problem should be affecting Gmail accounts set up via Exchange. When originally purchasing the phone I was assisted and directed to set up my Gmail account through Exchange because it had the ability to use "ActiveSync" and push not only mail and calendars, but all of my contacts as well. I found this article regarding the subject.
http://www.pcmag.com/article2/0,2817,2413283,00.asp
What it came down to was having to delete my Gmail via Exchange account and separate it into two different accounts, a regular gmail account for my mail and a CardDAV account for my contacts.
Here is what I did. Google is changing their system and for new registrars Exchange ActiveSync will not work so you will be unable to register your account via Exchange and have your mail, calenders, and contacts all pushed together. I find this change really annoying. If you are having problems accessing your contacts after deleting the mail account, like I was, here is the work around.
To circumvent this issue go to Setting > Mail, Contacts, Calendars > Add Account > Other > Add CardDAV Account: Under server ender google.com, then your email user name and password, then click next to verify the information.
I hope this helps.

Exchange connector stops working after patching?

our service manager exchange connector stopped working after patching that we performed on wed.
When starting or stopping the exchange connector we get this info in the Operations manager log file.
Error importing solutions. Error message:Management Pack [Microsoft.EnterpriseManagement.ServiceManager.Connector.AD,d43c3091-62c2-6404-607d-4376e592a89b] already imported.
Management Pack [Microsoft.EnterpriseManagement.ServiceManager.Connector.Sms,f772aa89-b934-2fac-4f37-5e0165d390ec] already imported.
Management Pack [Microsoft.SystemCenter.ConfigurationManager.Connector.PowerManagement,a070249c-6b56-37b8-d52c-a2906a63f9fc] already imported.
Management Pack [Microsoft.EnterpriseManagement.ServiceManager.Connector.Sms2011,fbea6f5a-838d-25a2-20af-fc21eb0b6706] already imported.
Management Pack [Microsoft.SystemCenter.ConfigurationManager2011.Connector.PowerManagement,bc23ed54-a33a-f608-05a9-c1f292140d2e] already imported.
Has anybody else seen this? Any suggestions?
Thanks Lance

Hi,
Did you try to restart SCSM's services?
If this doesn't help, I would try to delete and recreate the connectors.
More info:
System Center Service Manager Connector 3.0 for Exchange
http://www.microsoft.com/en-us/download/details.aspx?id=38791
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Sync with exchange has stopped working, help!

I purchased my iPhone last week, and set it up to sync with my exchange server at work with no problems.
Yesterday at about noon, the sync stopped working. In my mail account, I get a "checking for email" status with the spinning disc at the bottom of the screen. But it just sits there.
About that time, I also installed izymail, so I could sync my hotmail. Not sure if this may have anything to do with my exchange problem, but izymail sync'ed once and then stopped working as well.
I've since removed the izymail/hotmail account, and also removed and re-added my exchange account.
But exchange still won't sync.
Ideas?

I am running in cached mode when I access my account from a windows machine and outlook. How is that set up in mac mail? I have a setting in mac mail called "Keep copies of messages for offline viewing" and it's set to "All messages and their attachments." Is there a separate setting for cached mode?

Exchange stops working!!!

Similar Messages

Maybe you are looking for