It looks like the issue is with the Archive Server. On the Content Server side, there is a log file called easp_dsh.l...
Asked 1 year ago
Modified 2 days ago
Viewed 252
times
Asked By Sirisha Angadala
0
It looks like the issue is with the Archive Server. On the Content Server side, there is a log file called easp_dsh.log that is related to archiving. If you enable it and then replicate the issue, you should be able to capture more details in that log. Also, have you tried restarting the Archive Server services and checking again?
Answers
0
Job Description – Documentum Developer
Answered by Srinath B Goud 1 year ago
Your Answer
Please login to join the live discussion.
Latest Topics
💬 0 Answers • 👁️
1508 Views
💬 0 Answers • 👁️
136 Views
💬 0 Answers • 👁️
169 Views
💬 0 Answers • 👁️
214 Views
💬 0 Answers • 👁️
184 Views
