资源CiAgeOfLastNotification 是不健康的错误

有些邮箱正在移动和完成，有些则失败。在检查失败邮箱的报告时，它重复显示错误：Resource CiAgeOfLastNotification is unhealthy and Should not be access.发生了什么？在本文中，您将了解移动邮箱时出现 CiAgeOfLastNotification 错误的解决方案。

资源 CiAgeOfLastNotification 错误

我们正在移动邮箱，当我们检查移动请求状态时，邮箱显示状态：

• 瞬态故障源

• 失败其他

[PS] C:\>Get-MoveRequest -ResultSize Unlimited | Get-MoveRequestStatistics

DisplayName    StatusDetail           TotalMailboxSize               TotalArchiveSize PercentComplete
-----------    ------------           ----------------               ---------------- ---------------
Boris CampBell TransientFailureSource 5.319 GB (5,711,321,836 bytes)                  21

让我们排查邮箱移动失败的原因，并运行下面的两个命令来获取邮箱移动报告。

[PS] C:\>$stats = Get-MoveRequestStatistics "[email protected]" -IncludeReport

[PS] C:\>$stats.report.Failures | group FailureType | fl

Name   : ResourceUnhealthyException
Count  : 962
Group  : {ResourceUnhealthyException: The remote server is unhealthy due to 'Resource 'CiAgeOfLastNotification(DB01-2016)' is unhealthy and shouldn't 
         be accessed.'., ResourceUnhealthyException: The remote server is unhealthy due to 'Resource 'CiAgeOfLastNotification(DB01-2016)' is unhealthy 
         and shouldn't be accessed.'., ResourceUnhealthyException: The remote server is unhealthy due to 'Resource 
         'CiAgeOfLastNotification(DB01-2016)' is unhealthy and shouldn't be accessed.'., ResourceUnhealthyException: The remote server is unhealthy 
         due to 'Resource 'CiAgeOfLastNotification(DB01-2016)' is unhealthy and shouldn't be accessed.'....}
Values : {ResourceUnhealthyException}

错误：MigrationPermanentException：错误：资源“CiAgeOfLastNotification（系统）”不健康，不应访问

为什么会出现此错误？错误 Resource ’CiAgeOfLastNotification 的解决方案是什么？

资源 CiAgeOfLastNotification 不健康的解决方案

问题是 Exchange Server 邮箱数据库上的索引已损坏，您必须重建 Exchange 搜索索引。

注意：Exchange Server 2019 邮箱数据库的 ContentIndexState 将显示为 NotApplicable，因为它使用不同的索引方式。

1.检查内容索引目录状态

这是重建邮箱数据库搜索索引之前的样子。

对于 Exchange Server 2016 上的所有邮箱数据库，ContentIndexState 显示为 FailedAndSuspished。

[PS] C:\>Get-MailboxDatabaseCopyStatus * | ft -AutoSize

Name                Status  CopyQueueLength ReplayQueueLength LastInspectedLogTime  ContentIndexState
----                ------  --------------- ----------------- --------------------  -----------------
DB01-2016\EX01-2016 Mounted 0               0                                       Healthy
DB02-2016\EX01-2016 Mounted 0               0                                       Healthy
DB03-2016\EX01-2016 Mounted 0               0                                       Healthy
DB01-2016\EX02-2016 Healthy 0               0                 3/21/2023 12:26:40 PM FailedAndSuspended
DB02-2016\EX02-2016 Healthy 0               1                 3/21/2023 12:31:38 PM FailedAndSuspended
DB03-2016\EX02-2016 Healthy 0               0                 3/21/2023 12:31:21 PM FailedAndSuspended
DB01\EX01-2019      Mounted 0               0                                       NotApplicable
DB02\EX01-2019      Mounted 0               0                                       NotApplicable
DB03\EX01-2019      Mounted 0               0                                       NotApplicable
DB01\EX02-2019      Healthy 0               0                 3/21/2023 12:29:45 PM NotApplicable
DB02\EX02-2019      Healthy 0               0                 3/21/2023 12:24:24 PM NotApplicable
DB03\EX02-2019      Healthy 0               0                 3/21/2023 12:28:00 PM NotApplicable

2.重建内容索引目录

这是在完成文章中重建 Exchange 搜索索引的步骤之后的结果。邮箱数据库副本状态将 ContentIdexState 显示为播种。

[PS] C:\>Get-MailboxDatabaseCopyStatus * | ft -AutoSize

Name                Status  CopyQueueLength ReplayQueueLength LastInspectedLogTime  ContentIndexState
----                ------  --------------- ----------------- --------------------  -----------------
DB01-2016\EX01-2016 Mounted 0               0                                       Healthy
DB02-2016\EX01-2016 Mounted 0               0                                       Healthy
DB03-2016\EX01-2016 Mounted 0               0                                       Healthy
DB01-2016\EX02-2016 Healthy 0               0                 3/21/2023 12:45:18 PM Seeding
DB02-2016\EX02-2016 Healthy 0               1                 3/21/2023 12:46:03 PM Seeding
DB03-2016\EX02-2016 Healthy 0               0                 3/21/2023 12:45:37 PM Seeding
DB01\EX01-2019      Mounted 0               0                                       NotApplicable
DB02\EX01-2019      Mounted 0               0                                       NotApplicable
DB03\EX01-2019      Mounted 0               0                                       NotApplicable
DB01\EX02-2019      Healthy 0               0                 3/21/2023 12:32:08 PM NotApplicable
DB02\EX02-2019      Healthy 0               0                 3/21/2023 12:45:04 PM NotApplicable
DB03\EX02-2019      Healthy 0               0                 3/21/2023 12:44:56 PM NotApplicable

3.验证内容索引目录健康状态

你必须等到它完成播种。之后，验证 ContentIndexState 显示健康。

[PS] C:\>Get-MailboxDatabaseCopyStatus * | ft -AutoSize

Name                Status  CopyQueueLength ReplayQueueLength LastInspectedLogTime  ContentIndexState
----                ------  --------------- ----------------- --------------------  -----------------
DB01-2016\EX01-2016 Mounted 0               0                                       Healthy
DB02-2016\EX01-2016 Mounted 0               0                                       Healthy
DB03-2016\EX01-2016 Mounted 0               0                                       Healthy
DB01-2016\EX02-2016 Healthy 0               0                 3/21/2023 1:04:09 PM  Healthy
DB02-2016\EX02-2016 Healthy 0               1                 3/21/2023 1:06:25 PM  Healthy
DB03-2016\EX02-2016 Healthy 0               0                 3/21/2023 1:05:59 PM  Healthy
DB01\EX01-2019      Mounted 0               0                                       NotApplicable
DB02\EX01-2019      Mounted 0               0                                       NotApplicable
DB03\EX01-2019      Mounted 0               0                                       NotApplicable
DB01\EX02-2019      Healthy 0               0                 3/21/2023 1:06:13 PM  NotApplicable
DB02\EX02-2019      Healthy 0               0                 3/21/2023 1:03:59 PM  NotApplicable
DB03\EX02-2019      Healthy 0               0                 3/21/2023 1:05:29 PM  NotApplicable

现在您可以再次启动邮箱移动，Resource CiAgeOfLastNotification is unhealthy 错误将不再出现。

了解更多：将 Exchange 数据库移至另一个驱动器 »

结论

您了解了为什么会出现Resource CiAgeOfLastNotification is unhealthy 错误。解决方案是在不健康的邮箱数据库上重建搜索索引。之后，您可以移动邮箱。

您喜欢这篇文章吗？您可能还喜欢邮箱大小超过目标配额（移动邮箱）。不要忘记关注我们并分享这篇文章。