Archive completes with an Incremental1 folder and cannot be opened (4039342)

In very rare situations where an Archive runs with Erase completely selected as the Recycle action and the core looses connection to the Archive target location during Archive creation, you may have a successfully completed job, with an unusable archive.

Example of issue:

• To verify issue check target location. You will see an Incremental1 folder, when there should not be one. 

• The AABackup folder may not exist and if it does it will be missing critical files
• In AppRecovery logs you will see an error such as:

ERROR 2016-03-06T11:49:30 [703] - Replay.Common.Implementation.Utilities.DirectoryHelper ()
Failed to delete the directory: \\192.168.10.90\Public\AABackup\cc9eb848-1ee2-4503-8983-b74280f7dc66
System.IO.IOException depth 0: The specified network name is no longer available.
(0x80070040)
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) +0x23b 6004524
at System.IO.FileSystemEnumerableIterator`1.CommonInit() +0x58 6004748

This behavior has been identified as a defect.

If the core looses connection to the Archive target location when the Recycle Action set to Erase completely, it should either fail the job or prompt user for a new location.

Instead the core attempts to erase the current AABackup folder, creates the Incremental1 folder, and continues the Archive job to the Incremental1 folder. The end result, an incomplete archive.

Work Around:

1. It is suggested to not use Erase completely as your Recycle action if archiving to a location with a non stable network connection.
2. Otherwise, if you do experience this issue, you need to delete the exported archive and rerun the archive job.
3. As soon as the defect has been corrected in a future build this KB will be updated stating so.