ExchCollection_output.log:
2017-12-27 19:07:32,643 INFO [CRedirector] (12852:pid:13780:0fc12b3f106b4ac7bc53b5ecb4d106df-Administrato) Started 7z.exe with process id:6216
2017-12-27 19:07:32,705 INFO [ExchangeCollection] (12852:pid:13780:0fc12b3f106b4ac7bc53b5ecb4d106df-Administrato) Compressing file:D:\Destination\0.27.6.33-20171227-180618-294\content\4503603922337798\0fc12b3f106b4ac7bc53b5ecb4d106df-Administrato.pst ...
2017-12-27 19:13:43,389 INFO [ExchangeCollection] (12852:pid:13780:0fc12b3f106b4ac7bc53b5ecb4d106df-Administrato) Compressing file:D:\Destination\0.27.6.33-20171227-180618-294\content\4503603922337798\0fc12b3f106b4ac7bc53b5ecb4d106df-Administrato1.pst ...
2017-12-27 19:13:44,834 ERROR [ExchangeCollection] (5456:pid:13780:Monitor) Mailbox:0fc12b3f106b4ac7bc53b5ecb4d106df-Administrato had inactivity timeout out after seconds:374. Exiting the Collection process with error code (-100)
After the Exchange collection has collected all PSTs it will proceed to compress them using 7zip. During this time the Exchange Collection Agent is considered to be inactive as 7zip is compressing the data.
In order to correct the issue the inactivity timeout must be increased to allow the compression to complete.
The following instructions will adjust the inactivity timeout to be 14400 seconds (4 hours):
In Property Browser (System >> Support Features >> Property Browser):
Under "Name of Property to change":
esa.icp.collection.exchange.AbortOnInactivityTimeSec
Under "New Value":
14400
Check the box for "Confirm Change Are you Sure?"
Then hit Submit.