Error: An exception occurred during replication, job will be restarted from the last check point when possible. The file or directory is corrupted and unreadable.

Products

• Client Management Suite

Issue/Introduction

Replication between the Parent SMP and Child SMP is not working.

During a Differential Hierarchy or Complete Hierarchy replication from the Parent to Child SMP, you may see that it seems to be stuck at 0% complete, and the retries are increasing as time goes by.  In reviewing the SMP logs you may notice an error stating the following:

<![CDATA[An exception occurred during replication, job will be restarted from the last check point when possible, JobID: {30ebc4f9-d96d-4f6f-b409-a9c1b6c148d1}

The file or directory is corrupted and unreadable.
 ---> The file or directory is corrupted and unreadable.

SOAP Exception detail:
Unable to begin an asynchronous task to obtain the specified item hashes (Exception : The file or directory is corrupted and unreadable.

You may also notice that other hierarchy replication jobs are completing without a problem.

Environment

ITMS 8.6

Cause

The main volume on the destination server (Child SMP) is damaged or something is wrong with it.  The error indicates that the replication process is trying to post data to the Child SMP server's replication directory under C:\ProgramData\Symantec\SMP\Replication\Temp and during this process it has encountered a problem writing to the disk.

In order to test this, simply try creating a new folder on the desktop of the server, which by default is usually on the C drive.  If this works then delete it and keep trying every 30 seconds or so.  Eventually you will see the following error:

Error 0x80070570: The file or directory is corrupted and unreadable.

You also could even get a similar error when trying to delete the newly created folder.

Smaller replication jobs will complete as expected because those jobs can quickly post files to the C:\ProgramData\Symantec\SMP\Replication\Temp directory and complete the process before this issue presents itself.

Resolution

This is an environmental problem with the server and should be investigated by your server administrators to resolve a possible corrupted disk.

There is a way to change the location that these temporary replication files are processed to a different drive as documented in this KB How to change the path for replication's temp folders from the default location?