Error: 'There was an error writing to the pipe: The pipe is being closed. (232, 0xe8)' when using the RestoreOwners tool

Versions / Builds Affected

20140616, 20141117

Status

Open

TT / JIRAID

2891

How to Identify

When using the RestoreOwners tool it fails with the error: There was an error writing to the pipe: The pipe is being closed. (232, 0xe8) It happens always at the same batch of emails within the same database. The error occurs when a batch of 1000 items takes more than 10min to process Store debug logs look like: 2015-01-30,12:44:55,986,1,"#00000220","#00000006","info ","RestoreOwners","Batch of emails to process: 1000" 2015-01-30,12:50:44,701,1,"#00000220","#00000001","info ","RestoreOwners","TotalProgress: 0/1, Current AS: 2014 Jan - Dez, Progress: 580000/610632." * it took ~ 6min to process the batch above - this was successful* 2015-01-30,12:50:49,716,1,"#00000220","#00000006","info ","RestoreOwners","Batch of emails to process: 1000" 2015-01-30,13:05:31,056,1,"#00000220","#00000001","info ","RestoreOwners","TotalProgress: 0/1, Current AS: 2014 Jan - Dez, Progress: 581000/610632." 2015-01-30,13:05:31,212,1,"#00000220","#00000006","warning","WCFClientIEmailMessageRetrievalRestoreOwners","Warning: Service Faulted" 2015-01-30,13:05:31,212,1,"#00000220","#00000006","warning","WCFClientIEmailMessageRetrievalRestoreOwners","Warning: Service Faulted" 2015-01-30,13:05:31,353,1,"#00000220","#00000006","error ","WCFClientIEmailMessageRetrievalRestoreOwners","Error: Failed to dispose: Store.Core.IEmailMessageRetrieval. The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state." 2015-01-30,13:06:21,464,1,"#00000220","#00000001","error ","RestoreOwners","Error: There was an error writing to the pipe: Die Pipe wird gerade geschlossen. (232, 0xe8)." * it took ~15min to process the batch above - important being, that it is more than 10min - here it failed* IMPORTANT: These logs ordered by time, but mixed from different files! Please check the module column to see to which log it refers to!

Workaround / Fix Details

%

Required Actions

Collect a set of TS files and escalate.