- Remove From My Forums
-
Вопрос
-
Добрый день.
Имеются Exchange 2010 и Exchange 2013
В 2013 импорт PST в архивный ящик заканчивается failed:
В 2010 — всё ок.
Комманда на обоих была:
New-MailboxImportRequest -BatchName «d.medvedev» -Mailbox «d.medvedev» -FilePath \\VS-SBL01-XCH01\temp\archive.pst -IsArchive -BadItemLimit 50
Ребутить почтарь пробовал — без толку.
Пробовал на 2013 ещё так: add-MailboxPermission -Identity «d.medvedev» -User «NT Authority\SELF» -Accessright FullAccess
Лог с 2013 таков:
RunspaceId : 23df6890-00cd-4238-9041-669126de86f6 Name : MailboxImport4 Status : Failed StatusDetail : FailedMAPI SyncStage : None Flags : IntraOrg, Pull, Suspend RequestStyle : IntraOrg Direction : Pull Protect : False Priority : Normal WorkloadType : Local Suspend : True FilePath : \\VS-SBL01-XCH01\temp\archive.pst ContentCodePage : SourceRootFolder : TargetAlias : help TargetIsArchive : True TargetExchangeGuid : 0a6b2fb4-e36e-45f1-b745-c874d5fbf3da TargetRootFolder : RecipientTypeDetails : UserMailbox TargetVersion : Version 15.0 (Build 1236.0) TargetDatabase : ARCH01 TargetServer : VS-SBL01-XCH01.www.group.ru TargetMailboxIdentity : www.group.ru/CottonClub/dpt_IT/help IncludeFolders : {} ExcludeFolders : {} ExcludeDumpster : False ConflictResolutionOption : KeepSourceItem AssociatedMessagesCopyOption : Copy BatchName : BadItemLimit : 0 BadItemsEncountered : 0 LargeItemLimit : 0 LargeItemsEncountered : 0 QueuedTimestamp : 13.02.2017 21:34:27 StartTimestamp : LastUpdateTimestamp : 13.02.2017 22:12:04 CompletionTimestamp : SuspendedTimestamp : OverallDuration : 00:43:09.9807638 TotalSuspendedDuration : 00:00:00 TotalFailedDuration : 00:05:34.2294355 TotalQueuedDuration : 00:02:07.6547573 TotalInProgressDuration : 00:35:28.0965710 TotalStalledDueToCIDuration : 00:00:00 TotalStalledDueToHADuration : 00:00:00 TotalStalledDueToMailboxLockedDuration : 00:00:00 TotalStalledDueToReadThrottle : 00:00:00 TotalStalledDueToWriteThrottle : 00:00:00 TotalStalledDueToReadCpu : 00:00:00 TotalStalledDueToWriteCpu : 00:00:00.5781237 TotalStalledDueToReadUnknown : 00:00:00 TotalStalledDueToWriteUnknown : 00:00:00 TotalTransientFailureDuration : 00:35:25.2765196 TotalIdleDuration : 00:35:25.1107449 MRSServerName : EstimatedTransferSize : 0 B (0 bytes) EstimatedTransferItemCount : 0 BytesTransferred : 0 B (0 bytes) BytesTransferredPerMinute : 0 B (0 bytes) ItemsTransferred : 0 PercentComplete : 0 CompletedRequestAgeLimit : 30.00:00:00 PositionInQueue : InternalFlags : None FailureCode : -2146233088 FailureType : ConnectionFailedTransientException FailureSide : Target Message : Ошибка: Не удается открыть почтовый ящик /o=COTTONCLUB-GROUP/ou=Exchange Admin istrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=helpa64. --> MapiExceptionL ogonFailed: Unable to open message store. (hr=0x80040111, ec=-2147221231) Diagnostic context: Lid: 55847 EMSMDBPOOL.EcPoolSessionDoRpc called [length=285] Lid: 43559 EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=352][l atency=0] Lid: 52176 ClientVersion: 15.0.1236.3 Lid: 50032 ServerVersion: 15.0.1236.6003 Lid: 23226 --- ROP Parse Start --- Lid: 27962 ROP: ropLogon [254] Lid: 17082 ROP Error: 0x80040111 Lid: 26937 Lid: 21921 StoreEc: 0x80040111 Lid: 27962 ROP: ropExtendedError [250] Lid: 1494 ---- Remote Context Beg ---- Lid: 47536 Lid: 41232 Lid: 60208 Lid: 37136 Lid: 47920 Lid: 58951 Lid: 51472 Lid: 41232 Lid: 60208 Lid: 37136 Lid: 59184 Lid: 55056 Lid: 42768 Lid: 56319 Lid: 55336 Lid: 56296 Lid: 51944 StoreEc: 0x80040111 Lid: 56872 dwParam: 0xFE Lid: 42712 StoreEc: 0x80040111 Lid: 10786 dwParam: 0x0 Msg: 15.00.1236.000:VS-SBL01-XCH01 Lid: 1750 ---- Remote Context End ---- Lid: 26849 Lid: 21817 ROP Failure: 0x80040111 Lid: 26297 Lid: 16585 StoreEc: 0x80040111 Lid: 32441 Lid: 1706 StoreEc: 0x80040111 Lid: 24761 Lid: 20665 StoreEc: 0x80040111 Lid: 25785 Lid: 29881 StoreEc: 0x80040111 FailureTimestamp : 13.02.2017 22:12:03 IsValid : True ValidationMessage : OrganizationId : RequestGuid : f6ab0c52-3d6d-4d53-82d9-373da85e790a RequestQueue : ARCH01 Identity : 203324e6-11ee-4780-9c57-172ba30c2d38\f6ab0c52-3d6d-4d53-82d9-373da85e790a DiagnosticInfo : Report : 13.02.2017 21:34:27 [VS-SBL01-XCH02] Пользователь 'www.group.ru/IT-Infrastruct ure/Generic Accounts/Administrators/adm2kabanov' создал запрос. 13.02.2017 21:36:36 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:36:37 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (1/60). 13.02.2017 21:37:11 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:37:11 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (2/60). 13.02.2017 21:37:46 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:37:46 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (3/60). 13.02.2017 21:38:21 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:38:21 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (4/60). 13.02.2017 21:38:56 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:38:56 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (5/60). 13.02.2017 21:39:31 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:39:31 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (6/60). 13.02.2017 21:40:06 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:40:06 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (7/60). 13.02.2017 21:40:41 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:40:41 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (8/60). 13.02.2017 21:41:17 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:41:17 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (9/60). 13.02.2017 21:41:52 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:41:52 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (10/60). 13.02.2017 21:42:27 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:42:27 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (11/60). 13.02.2017 21:43:02 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:43:02 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (12/60). 13.02.2017 21:43:42 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:43:42 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (13/60). 13.02.2017 21:44:17 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:44:17 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (14/60). 13.02.2017 21:44:53 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:44:53 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (15/60). 13.02.2017 21:45:28 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:45:28 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (16/60). 13.02.2017 21:46:03 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:46:03 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (17/60). 13.02.2017 21:46:38 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:46:38 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (18/60). 13.02.2017 21:47:13 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:47:14 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (19/60). 13.02.2017 21:47:49 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:47:49 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (20/60). 13.02.2017 21:48:29 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:48:29 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (21/60). 13.02.2017 21:49:04 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:49:04 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (22/60). 13.02.2017 21:49:39 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:49:39 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (23/60). 13.02.2017 21:50:14 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:50:14 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (24/60). 13.02.2017 21:50:49 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:50:49 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (25/60). 13.02.2017 21:51:24 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:51:24 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (26/60). 13.02.2017 21:51:59 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:51:59 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (27/60). 13.02.2017 21:52:34 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:52:34 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (28/60). 13.02.2017 21:53:06 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:53:09 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (29/60). 13.02.2017 21:53:44 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:53:44 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (30/60). 13.02.2017 21:54:19 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:54:19 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (31/60). 13.02.2017 21:54:54 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:54:54 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (32/60). 13.02.2017 21:55:29 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:55:29 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (33/60). 13.02.2017 21:56:04 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:56:04 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (34/60). 13.02.2017 21:56:39 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:56:39 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (35/60). 13.02.2017 21:57:14 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:57:15 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (36/60). 13.02.2017 21:57:49 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:57:50 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (37/60). 13.02.2017 21:58:25 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:58:25 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (38/60). 13.02.2017 21:59:00 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:59:00 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (39/60). 13.02.2017 21:59:35 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 21:59:35 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (40/60). 13.02.2017 22:00:10 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 22:00:10 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (41/60). 13.02.2017 22:00:45 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 22:00:45 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (42/60). 13.02.2017 22:01:20 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 22:01:20 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (43/60). 13.02.2017 22:01:55 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 22:01:55 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (44/60). 13.02.2017 22:02:30 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 22:02:30 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (45/60). 13.02.2017 22:03:05 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 22:03:05 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (46/60). 13.02.2017 22:03:40 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 22:03:40 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (47/60). 13.02.2017 22:04:15 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 22:04:15 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (48/60). 13.02.2017 22:04:50 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 22:04:50 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (49/60). 13.02.2017 22:05:25 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 22:05:25 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (50/60). 13.02.2017 22:06:00 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 22:06:00 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (51/60). 13.02.2017 22:06:35 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 22:06:36 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (52/60). 13.02.2017 22:07:11 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 22:07:11 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (53/60). 13.02.2017 22:07:46 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 22:07:46 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (54/60). 13.02.2017 22:08:21 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 22:08:21 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (55/60). 13.02.2017 22:08:56 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 22:08:56 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (56/60). 13.02.2017 22:09:31 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 22:09:31 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (57/60). 13.02.2017 22:10:11 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 22:10:11 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (58/60). 13.02.2017 22:10:46 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 22:10:46 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (59/60). 13.02.2017 22:11:21 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 22:11:21 [VS-SBL01-XCH01] Произошла временная ошибка ConnectionFail edTransientException. Система повторит попытку (60/60). 13.02.2017 22:11:56 [VS-SBL01-XCH01] Служба репликации почтовых ящиков Microso ft Exchange 'VS-SBL01-XCH01.www.group.ru' (15.0.1236.0 caps:1FFF) проверяет за прос. 13.02.2017 22:12:03 [VS-SBL01-XCH01] При выполнении задания произошло слишком много временных ошибок (60), оно будет прекращено. 13.02.2017 22:12:03 [VS-SBL01-XCH01] Произошла неустранимая ошибка ConnectionF ailedTransientException. ObjectState : New
Ответы
-
Попробовать до cu15 обновиться. В 14 баг с индексом, может и с экспортом pst тоже траблы есть.
scientia potentia est
My blog-
Помечено в качестве ответа
27 февраля 2017 г. 7:41
-
Помечено в качестве ответа
-
Я нашёл причину и решение.
У меня винда русскоязычная была.
На тестовой англоязычной винде с Exchange Server2013 проблем нет.
Чуть позже хочу переключить язык системы и отпишусь о результате.
-
Помечено в качестве ответа
Dmitry Kabanov
12 декабря 2017 г. 12:08
-
Помечено в качестве ответа
- Remove From My Forums
-
Question
-
Recently I asked what preparation was needed to import .PST files into mailboxes already populated. Everyone said something like «No Problem».
When I said «populated» I meant mailboxes populated with messages, calendars etc. But now I find you can’t import .PST files into mailboxes already in use.
ALERTS: Import PST of mailbox «%Alias%» has failed . .I have no problem importing into mailboxes that are empty. So how to import .PST files into mailboxes already in use ? It works to delete the User Accounts and Mailbox, but I would rather
not.Thank You
Moving PST File in Exchange Environment becomes an easy task when the correct Powershell cmdlet is used. But while using the Microsoft Exchange Powershell command to import PST mailbox to Exchange 2013, 2016 Server & various other versions. A naive user of Exchange faces numerous issues. One of the frequently occurring error while using ‘new-mailboximportrequest failed’ message. This message prompt an issue during importing data from Outlook to Exchange Environment such as:
- Bad Item Limit
- Large Items Not Copied
Since it’s not necessary, every time a solution to these issues created due to the same reason, different reasons can be lead to the same error. Some user query is given below:
“I was having a PST file of 11GB. I wanted to import that PST to Exchange. When I ran the import without BadLimit it failed with the event 1100. Then I tried to run it with BadLimit then also it failed to import PST file to Exchange. I am not able to figure out what is the main issue. Please guide me how can I eliminate this issue and import my PST file to Exchange.”
“Recently, I used ‘New-MailboxImportRequest’ command to import one PST file to Exchange Server. But only 800 MB of data was imported and the mailboxImport failed. I do not know what to do. There is any method using which I can resolve it and import PST file to Exchange without any data loss.”
How to Resume New-mailboximportrequest Failed Command Management Console
Before using this command, an Exchange Administrator need to assign “Import Export Role” to use this command. If Command is used directly to import then user received the message.
So First, assigns the rights to himself/herself to import mailboxes:
New-ManagementRoleAssignment –Role "Mailbox Import Export" –User Administrator
After that Now use command “New-MailboxImportRequest” to import PST File
Command: New-MailboxImportRequest -Mailbox Peter -FilePath \exchangePSTarchiveoutlook.pst
Wait to start the process of importing, if Exchange user wants to know the status of given command then go for command:
Get-MailboxImportRequest
Note: To save the result of Import Request in Text File format, Try Command
Get-MailboxImportRequestStatistics PeterImport20120527 -IncludeReport | fl > c:importsreport.txt
And to save the result of the failed process in Text File format, Exchange user can go for command:
Get-MailboxImportRequest -Status Failed | Get-MailboxImportRequestStatistics -IncludeReport | fl > c:importsallfailedreport.txt
Solution to Fix New-MailboxImportRequest Failed Error
After getting failed message, a user need to find the root cause of the error first, and common issues are
Large Items: Since Message Size limit is changed according to different versions and this become common reason as the size of the emails which the user wants to import is larger than the specified size on the Exchange Transport components, connectors etc. Then it results in the failure of the import process and to fix, user command:
New-MailboxImportRequest [-Mailbox Name] <LargeItemLimit 100 AcceptLargeDataLoss > -FilePath <LongPath> -LargeItemLimit
Note: The AcceptLargeDataLoss parameter used when the value of large item limit higher than 51
Bad Items: Bad Items can be associated with the corruption in the PST file items you want to import. If the PST file you want to transfer to Exchange is corrupted. Then, the import process fails. Fix this issues by changing the parameter of bad-limit items, but to set the value of Parameter around 10 or low, but if you want to try to set the value greater then 50 then please use also another parameter know “AcceptLargeDataLoss switch”
New-MailboxImportRequest [-Mailbox Name] <MailboxOrMailUserIdParameter> -FilePath <LongPath>
New-MailboxImportRequest [-Mailbox Name] <BadItemLimit 1000 -AcceptLargeDataLoss> -FilePath <exchangePSTarchiveoutlook.pst>
How to Resolve Mailbox Import Failed Issue?
The user can adopt a smart and automated solution i.e. SysTools Exchange Import Tool to eliminate all the issues faced while importing PST files into Exchange Server. With this software, the user can easily move PST emails, calendars, contacts, tasks, journals, etc. to Exchange. Users can easily import PST into Exchange 2013, 2016 and many other Exchange Server versions such as: 2010, 2007 & 2003 in a simplified manner.
Download Now Free Purchase Now 100% Secure
The software is having an easy-to-use interface which makes it easy for the users to work with it. There is no data loss issue associated with the utility. Moreover, one can also transfer password-protected and inaccessible PST files to Exchange Server with the help of this software.
Steps to Import PST Files to Exchange via Automated Solution
1. First, download and install SysTools Exchange Import Tool on your local machine and then click on the Add File/Folder/Network Files to import numerous PST File into Exchange on the initial screen of the tool
Download Utility:
2. Now, insert the Admin SMTP Address, Password, Exchange Version etc. and all the other details also to start the import process.
3. After that, specify the Exchange mailbox name and then select categories such as emails, calendars, contacts, journals etc. as per your requirements.
4. Click on the Import Button and the move Outlook PST files to Exchange Server
Final Words
When a user tries to use command “new-mailboximportrequest failed” to migrate Outlook Data File, faces issues due to Bad Items limit or large mailbox size issues and to fix it, you need to check the pre-requisites and parameter used along with the command first. To avoid issues, Exchange User can go for SysTools Exchange Importer, an automated solution to import PST File to Live Exchange Server 2016, 2013, 2010, 2007, 2003 without any data loss and trouble-free way.
Are you trying to import PST files into Exchange mailbox? And you are stuck in between the migration process due to New-MailboxImportRequest failed. So, follow the solution briefed in this article to know how to deal with this situation.
The New-MailboxImportRequest Command can be used for on-premises as well as for Exchange Online also. It allows users to import .pst file to the Exchange 2016/13/10 and other below environment mailboxes.
To use this cmdlet, users need to take various permissions in Exchange as a pre-requisites. But ‘New-MailboxImportRequest’ get failed error occur s while transferring Outlook PST to Exchange mailbox. Therefore, in this article, we are going to discuss some handy solution to troubleshoot New-MailboxImportRequest: Status Failed or Access Denied Issues.
Well, let’s have a look at some scenario that will give a brief insight into the situation.
“I have been trying to import an 11 GB(Giga-Byte) PST file to Exchange 2013 using ‘New-MailboxImportRequest’ cmdlet. In beginning, the process went so smooth. But, after some time, it remains hung at Queued. After that, the request becomes failed. I have no idea about this situation. Also, I go through many forum and use ‘Get-MailboxImportRequest’. But, it just displayed the Name/Mailbox/ Import request status. Please guide me what step should I take to resolve New-MailboxImportRequest command failed status in Exchange 2013 and communicate with the database mailboxes without any data loss. Please help!”
Why New-MailboxImportRequest Failed Issues Arise– Know the Reasons
When the users execute import request in Management Shell in order to move the PST files into mailboxes, they hung up and the following error runs through the screen:
- New-MailboxImportRequest: Status Failed
- New-MailboxImportRequest: Access to the path is denied
- New-MailboxImportRequest: Failed to communicate with the mailbox database
There are some Common reasons by which this error occurs during the import process. Here, we discuss the three top-most causes due to which import request become failed or access denied issues.
- It might happen that before the process, the role like Organization Management Group Role Group should not be assigned properly. As a result, when users run the ‘New -MailboxImportRequest’ cmdlet, it becomes failed.
- When the corrupted items in a PST file are more than the specified limit then the following error is generated:
This can be resolved by placing the following Parameter value in New-MailboxImportRequest command before the execution in the shell.
[-BadItemLimit ]
- In this case, when the users PST file has lots of data and users try to move that file in Exchange. Then it results in the failure of import request. This situation can be overcome by using ‘LargeItemLimit ’ in the import cmdlet.
Note: Parameter value should be greater than 51.
After knowing the reasons, let us go through the troubleshooting methods to fix this error.
Note: After running the cmdlet, to view the status of the current request by piping below cmdlet can be used: Get-MailboxImportRequestStatistics.
Tips to Fix New-MailboxImportRequest Failed Status
Whenever import process stop or failed, most Exchange users try to resume the process to save the time and effort. For that few commands are available.
Technique 1: Resume Failed MailboxImport Request
- To start the process, it is mandatory to assign the role. For this, follow the below-mentioned PowerShell cmdlet:
New-ManagementRoleAssignment –Role “Mailbox Import Export” –User Administrator
- Next, to move an individual .pst file execute the below command:
New-MailboxImportRequest -Mailbox Name -FilePath\exchangePSTarchiveoutlook.pst
- If you want to move PST file into multiple mailboxes, then used below-mentioned cmdlet:
Dir \exchsvrPSTarchive*.pst | %{ New-MailboxImportRequest -Name Import20120527 -BatchName Import20120527 -Mailbox $_.BaseName -FilePath $_.FullName}
- After that, use the following command to check the status of mailbox import request:
Get-MailboxImportRequest
- Now, run the below cmdlet to again start the failed import request:
Get-MailboxImportRequest -Status Failed | Resume-MailboxImportRequest
Technique 2: Increase Get-Send/Receive Connector Limit
It is evident from the above New-MailboxImportRequest cmdlet failed and not communicate with target mailbox stored in the database due to file size limit. So, it is better to improve the limit and then run an import command. For this, use the below instructions carefully:
After that, wait for few minutes and then restart the following services:
- MS Exchange Mailbox Assistants
- MS Exchange Transport
- MS Exchange Mail Submission
Now, restart Exchange Server to start the import process.
Fix New-MailboxImportRequest Failed – Access Denied Error
This is also a common error arise while importing Outlook file. The reason for this error mostly due to permission of folder used a file path to import data stored in it.
To avoid this error, grant all the “Read / Write” Permissions to Group Exchange Subsystem to the share networked from where you want to import Outlook File. If permission is not granted properly then the connection could not establish between the server and the target folder.
Smart Way to Resolve Mailbox Import Failed Glitch
PowerShell method is a good option to resolve various complicated task. But moving data from one place to another mailbox, PowerShell cmdlet take lots of time. So, it is better to click on SysTools Exchange Import Tool. The software is able to successfully import PST file into Exchange mailboxes.
With this utility, one can easily move emails, contacts and other data items from PST file to Exchange. Above all, the software is capable to transfer secured .pst file to Exchange Server 2016, 2013, 2010, 2007, 2003 without any error.
Users can easily import multiple as well as a selective Outlook data file to the Microsoft Live Exchange Server. It provides date filter option which allows you to import PST to Exchange in a specified period of time. Also, when the import process is complete the software automatically creates the export report which store the status of notes, tasks, journals, contacts, calendars, mails from the Outlook PST file to the selected Exchange Server version.
Concluding Lines
Many Exchange admins have first priority is to use the PowerShell Exchange command for the Import/Export process. However, any single mistake in cmdlet leads to numerous errors One of the glitches is New-MailboxImportRequest failed status. That is why, in this post, we have covered manual ways to resume the ‘failed’ status situation. If you want a better path to import multiple PST into desired Exchange mailbox, then go for Exchange Import tool to save Time and Effort.
Posted by Ankit5841 2018-10-24T13:58:04Z
Hello,
i have tried to import a PST file into a mailbox through Exchange Admin Center.
The process has failed at 90%, all the data which i wanted from the PST are imported into the mailbox.
But during the import task Exchange asked me to add a mailadress which will get informed after the task is completed. Now the entered mailadress is getting Mails after every 2 minutes, that the import task has failed.
How can i shut off these messages?
Thanks
Ankit5841
This person is a verified professional.
sonora
New contributor
2 Replies
-
-
John3367
This person is a verified professional.
thai pepper
lock
This topic has been locked by an administrator and is no longer open for commenting.
To continue this discussion, please ask a new question.
Read these next…
Snap! — Space Submarines, Brain Waves, Chernobyl Wind Farm, Real-Life Asteroids
Spiceworks Originals
Your daily dose of tech news, in brief.
Welcome to the Snap!
Flashback: September 21, 1996: Programming Error May Have Contributed to Plane Crash (Read more HERE.)
Bonus Flashback: September 21, 2003: Galileo Completes Jupiter Mission (Re…
Large amount of spam recently getting around filters. How to stop these?
Security
Got a HUGE uptick in spam emails recently, and they are actually getting through. The spam is coming from gibberish@gibberish.onmicrosoft.com and coming from IPs 40.107.X.X which after a quick search is Microsoft IPs…I am not able to just filter the do…
Old invoicing / tracking software
Software
Hi wonderful people. I hope someone may be able to assist with a rather perplexing issue.We started working with a company a few years ago providing their IT support.They use a very old (20 years plus) software package which they had built from scratch. …
Receive 250 Spicepoints and $100 Amazon GC for your participation!
Hardware
Spiceworks is looking for a couple of Lenovo advocates from the community to participate in a case study! We’re looking for those who also have experience using Apple Laptops to draw on comparisons for the case study.
We’d be asking for 30 minutes of …
Spark! Pro series — 21st September 2023
Spiceworks Originals
Today in History: 1942 — The Superfortress bomber takes flight
On September 21, 1942, the U.S. B-29 Superfortress makes its debut flight in Seattle, Washington. It was the largest bomber used in the war by any nation.
The B-29 was conceived in 1939…