资源CiAgeOfLastNotification 是不健康的错误
有些邮箱正在移动和完成，有些则失败。在检查失败邮箱的报告时，它重复显示错误：资源 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(System)”运行状况不佳，不应访问
为什么会出现此错误，该错误的解决方案是什么资源 'CiAgeOfLastNotification？
资源 CiAgeOfLastNotification 不健康的解决方案
问题是 Exchange Server 邮箱数据库上的索引已损坏，您必须重建 Exchange 搜索索引。
笔记：Exchange Server 2019 邮箱数据库的 ContentIndexState 将显示为 NotApplicable，因为它使用不同的索引方式。
1.检查内容索引目录状态
这是重建邮箱数据库搜索索引之前的样子。
这内容索引状态显示为失败并暂停对于 Exchange Server 2016 上的所有邮箱数据库。
更多阅读：在 Windows 10 中打开资源监视器的简单方法
[PS] C:>Get-MailboxDatabaseCopyStatus * | ft -AutoSize
Name Status CopyQueueLength ReplayQueueLength LastInspectedLogTime ContentIndexState
---- ------ --------------- ----------------- -------------------- -----------------
DB01-2016EX01-2016 Mounted 0 0 Healthy
DB02-2016EX01-2016 Mounted 0 0 Healthy
DB03-2016EX01-2016 Mounted 0 0 Healthy
DB01-2016EX02-2016 Healthy 0 0 3/21/2023 12:26:40 PM FailedAndSuspended
DB02-2016EX02-2016 Healthy 0 1 3/21/2023 12:31:38 PM FailedAndSuspended
DB03-2016EX02-2016 Healthy 0 0 3/21/2023 12:31:21 PM FailedAndSuspended
DB01EX01-2019 Mounted 0 0 NotApplicable
DB02EX01-2019 Mounted 0 0 NotApplicable
DB03EX01-2019 Mounted 0 0 NotApplicable
DB01EX02-2019 Healthy 0 0 3/21/2023 12:29:45 PM NotApplicable
DB02EX02-2019 Healthy 0 0 3/21/2023 12:24:24 PM NotApplicable
DB03EX02-2019 Healthy 0 0 3/21/2023 12:28:00 PM NotApplicable2.重建内容索引目录
这是在完成文章中重建 Exchange 搜索索引的步骤之后的结果。邮箱数据库副本状态显示内容索引状态作为播种。
[PS] C:>Get-MailboxDatabaseCopyStatus * | ft -AutoSize
Name Status CopyQueueLength ReplayQueueLength LastInspectedLogTime ContentIndexState
---- ------ --------------- ----------------- -------------------- -----------------
DB01-2016EX01-2016 Mounted 0 0 Healthy
DB02-2016EX01-2016 Mounted 0 0 Healthy
DB03-2016EX01-2016 Mounted 0 0 Healthy
DB01-2016EX02-2016 Healthy 0 0 3/21/2023 12:45:18 PM Seeding
DB02-2016EX02-2016 Healthy 0 1 3/21/2023 12:46:03 PM Seeding
DB03-2016EX02-2016 Healthy 0 0 3/21/2023 12:45:37 PM Seeding
DB01EX01-2019 Mounted 0 0 NotApplicable
DB02EX01-2019 Mounted 0 0 NotApplicable
DB03EX01-2019 Mounted 0 0 NotApplicable
DB01EX02-2019 Healthy 0 0 3/21/2023 12:32:08 PM NotApplicable
DB02EX02-2019 Healthy 0 0 3/21/2023 12:45:04 PM NotApplicable
DB03EX02-2019 Healthy 0 0 3/21/2023 12:44:56 PM NotApplicable3.验证内容索引目录健康状态
你必须等到它完成播种。之后，验证内容索引状态出现健康。
[PS] C:>Get-MailboxDatabaseCopyStatus * | ft -AutoSize
Name Status CopyQueueLength ReplayQueueLength LastInspectedLogTime ContentIndexState
---- ------ --------------- ----------------- -------------------- -----------------
DB01-2016EX01-2016 Mounted 0 0 Healthy
DB02-2016EX01-2016 Mounted 0 0 Healthy
DB03-2016EX01-2016 Mounted 0 0 Healthy
DB01-2016EX02-2016 Healthy 0 0 3/21/2023 1:04:09 PM Healthy
DB02-2016EX02-2016 Healthy 0 1 3/21/2023 1:06:25 PM Healthy
DB03-2016EX02-2016 Healthy 0 0 3/21/2023 1:05:59 PM Healthy
DB01EX01-2019 Mounted 0 0 NotApplicable
DB02EX01-2019 Mounted 0 0 NotApplicable
DB03EX01-2019 Mounted 0 0 NotApplicable
DB01EX02-2019 Healthy 0 0 3/21/2023 1:06:13 PM NotApplicable
DB02EX02-2019 Healthy 0 0 3/21/2023 1:03:59 PM NotApplicable
DB03EX02-2019 Healthy 0 0 3/21/2023 1:05:29 PM NotApplicable现在您可以再次启动邮箱移动，并且不会再出现 Resource CiAgeOfLastNotification is unhealthy 错误。
结论
您了解了为什么会出现 Resource CiAgeOfLastNotification is unhealthy 错误。解决方案是在不健康的邮箱数据库上重建搜索索引。之后，您可以移动邮箱。
您喜欢这篇文章吗？您可能还喜欢邮箱大小超过目标配额（移动邮箱）。不要忘记关注我们并分享这篇文章。
