Asked 5 months ago
Modified yesterday
Viewed 167
times
Asked By Sai Kumar Sunkara
It seems the issue is originating from the Archive Server. On the Content Server side, you can enable the easp_dsh.log file, which is linked to archiving. After enabling it and reproducing the problem, you should be able to gather more detailed information in that log. Have you also tried restarting the Archive Server services to check if the issue persists?