Skip to main content

LỖI EMAIL KHÔNG LOAD TRÊN ĐIỆN THOẠI SAU KHI SỬA MAILBOX DATABASE

 

Cách khắc phục:



Tạo 1 mailbox database mới và move mailbox bị lỗi qua database mới đó


ActiveSync Fails to Deliver E-Mail to Phones after Database Repair – Event ID 1008

We ran into an issue where an exchange server was down due to a full VM crash. We had to restore the server from a backup. After the backup was all up and running emails started flowing again. However, we also were notified that people were no longer receiving emails on their mobile devices. We also noticed that what started to happen were critical and error events to the application log.  While most appeared to be transient and would likely cure themselves – they did – one did not.  Event ID 1008.  Here is an excerpt from the description:

Description:
An exception occurred and was handled by Exchange ActiveSync. This may have been caused by an outdated or corrupted Exchange ActiveSync device partnership. This can occur if a user tries to modify the same item from multiple computers. If this is the case, Exchange ActiveSync will re-create the partnership with the device. Items will be updated at the next synchronization.

URL=/Microsoft-Server-ActiveSync/default.eas?User=xxxxxx&DeviceId=Appl70111HXKA4S&DeviceType=iPhone&Cmd=SendMail
— Exception start —
Exception type: System.Web.HttpException
Exception message: An error occurred while communicating with the remote host. The error code is 0x800703E3.

Note in particular the line beginning with “URL=/”.  The user name of the mailbox owner appears and it is their phone that is not syncing properly.  In my particular case, the users could send email from their phones but not receive .  Of course in this instance, only two users were effected: the owners of the company!

What Didn’t Work

The first thing I had them do was to delete the Exchange email account from their iPhones and re-add it.  It was a real test to see if they could accomplish this on their own.  Happy to say they did, sad to say it re-added the account and folders but still didn’t allow the phones to receive email.

Time for harsher measures, so I opened Exchange Management Console and expanded the Recipient Configuration and select Mailbox.  Then I selected one of the users and from the Actions pane on the right, I selected Manage Mobile Phone.  The following wizard appeared:

EMC Recipient Mobile Phone

The wizard background didn’t appear pink, but you get the point.

Notice that the radio button “Remove mobile phone partnership” is selected.  I completed the wizard by clicking on the Remove button, and felt very pleased.  I allowed for about an hour to pass to have Exchange and ActiveSync re-establish the partnerships.  After three hours, I figured that trick was not going to happen.

What Did Work

The trick that did work was pretty straight forward.  Here’s what I did:

  • Open EMC and expand Organization Configuration.
  • In the right hand action pane, select New Mailbox Database.
  • Complete the wizard to create a new mailbox database and mount it.
  • In EMC, expand Recipient Configuration and select Mailbox.
  • Select the user(s) whose phones are not syncing.
  • In the right hand action pane, select New Local Move Request.
  • Complete the wizard to move the mailboxes to the new database created in the previous steps.
  • In the EMC navigation pane on the left, click on Move Request and follow the progress of the mailbox move(s).  NOTE: you can double-click on a mailbox and the properties will display the size of the mailbox and the percent complete.  It does not refresh so close it and re-display as needed.

Just as soon as the move(s) were complete, email flow to the phones was re-established.

Will ActiveSync Still Work if You Move Them Back?

Yes, after testing, it worked just fine.


Nguồn: http://www.stormbreaker.tech/?p=169

và: https://lhdinger.wordpress.com/2012/04/10/activesync-fails-to-deliver-e-mail-to-iphones-after-database-repair-event-id-1008/

Comments

Popular posts from this blog

[RAID] SWITCH FROM AHCI TO RAID WITH INTEL C600 CONTROLLER

I personally have used other ways to do this. Manipulating some registry settings in combination with a safe boot before booting normally does the trick as well. This works with both SATA SSD and M.2 NVMe drives and it enables relatively fast switching between back and forth between AHCI and RAID. I have described this method below.  I have also tried the same process used to switch from RAD to AHCI and that works as well. Switch to safe boot Reboot into BIOS Change from AHCI to RAID in the BIOS Boot into safe mode Turn off safe mode and reboot normally again Nothing else and that also did the trick, just like with moving from RAID to AHCI.  So the link above and my step by step below is here for completeness. You have options in case one of them doesn’t work! Step by step AHCI to RAID registry method This procedure I describe below works on Windows 10 1803/1809 and has been tested on Dell Latitude E6220 an XPS 13 9360. Editing the registry is...

[Hyper-V] - Lỗi không boot vào được sau khi convert máy vật lý sang máy ảo

XỬ LÝ LỖI KHÔNG BOOT ĐƯỢC VÀO MÁY ẢO SAU KHI CONVERT TỪ MÁY VẬT LÝ BẰNG DISK2VHD Sau khi convert server vật lý sang file VHD để import vào Hyper thì khi start máy ảo lên màn hình máy ảo chỉ nhấp nháy con trỏ chuột trên màn hình đen (blinking cursor) NGUYÊN NHÂN Do máy vật lý sử dụng ổ đĩa cài OS được format theo chuẩn GPT (thay vì MBR như truyền thống, tham khảo GPT và MBR ) XỬ LÝ Bước 1: chuyển ổ GPT thành MBR Copy file VHD của ổ đĩa chứa OS về 1 máy tính Windows 8 trở lên Trên máy Windows 8+ click phải chuột lên file VHD vừa copy, chọn lệnh Mount . Lúc này dùng 1 phần mềm miễn phí (vd: Mini Partition Wizard ) để convert ổ đĩa vừa mount từ GPT  -> MBR Sau đó Delete phần Partition dư ra ở phần đầu ổ đĩa được mount (khoảng vài trăm MB) Set " Active " cho ổ đĩa này để là ổ đĩa boot OS Nhấn Apply để phần mềm thực thi tác vụ Sau khi phần mềm làm xong, tắt phần mềm Mini Partition Wizard, vào My Computer chọn eject ổ đĩa đang mount . Copy file VHD vừa đư...

LỖI "The provided partition "Migration...." is not a valid Migration mailbox"

  Solution for a valid Migration mailbox could not be found for this organization To address this issue, we will: Delete Migration mailbox in Active Directory Users and Computers Recreate Migration mailbox with /PrepareAD command Enable Migration mailbox with Exchange Management Shell 1. Delete Migration mailbox in Active Directory Users and Computers We do see the mailbox in ADUC, let’s remove it. If you don’t see it, search for it. It might be in a different container than the default container  Users . We can always verify in Exchange Management Shell if the Migration mailbox is present. If it shows up in the output, it means that it’s present and enabled. The output should be empty. [PS] C:\> Set - ADServerSettings - ViewEntireForest $true ; Get - Mailbox - Identity "Migration.8f3e7716-2011-43e4-96b1-aba62d229136" - Arbitration | Format-Table Name , ServerName , Database , AdminDisplayVersion , ProhibitSendQuota Copy 2. Recreate Migration mailbox with /Prepare...