The following is seen in the Job Status log:
MM/DD/YYY HH:HH:MM [RedirectingJob] Redirecting job execution to 0.2.1.0
MM/DD/YYY HH:HH:MM Job started in system component running at SERVER:2595
MM/DD/YYY HH:HH:MM Attempting to lock TagFolder Batch Lock
MM/DD/YYY HH:HH:MM Successfully locked TagFolder Batch Lock
MM/DD/YYY HH:HH:MM Starting tag operation. addPtags:[PID:25 TIDs:] rmvPtags:[] Comment:null EstimatedSize:4,359 (event id: 35)
MM/DD/YYY HH:HH:MM Successfully unlocked TagFolder Batch Lock
MM/DD/YYY HH:HH:MM Exception while tagging
MM/DD/YYY HH:HH:MM Exception while tagging com.teneo.esa.tag.TaggingException:
[#124006] Tagger - Persistence Exception - While updating doc tagging data
com.teneo.esa.tag.TaggingTagImpl.updateDocTagging(TaggingTagImpl.java:2090)
com.teneo.esa.tag.TaggingTagImpl.updateDocTaggingForOp(TaggingTagImpl.java:1917)
com.teneo.esa.tag.TaggingTagImpl.tagNext(TaggingTagImpl.java:981)
com.teneo.esa.tag.TaggingTagImpl.tagFamilyORItemTags(TaggingTagImpl.java:618)
com.teneo.esa.tag.TaggingTagImpl.applyTags(TaggingTagImpl.java:407)
com.teneo.esa.tag.TaggingTagImpl.tagMessagesInternal(TaggingTagImpl.java:350)
com.teneo.esa.tag.TaggingTagImpl.tagMessages(TaggingTagImpl.java:180)
com.teneo.esa.tag.Tagger.tagMessages(Tagger.java:466)
com.teneo.esa.tag.AutomationRules.FolderRule.tagAndFolder(FolderRule.java:140)
com.teneo.esa.tag.AutomationRules.FolderRule.call(FolderRule.java:78)
com.teneo.esa.tag.AutomationRules.FolderRule.call(FolderRule.java:40)
com.teneo.esa.tag.job.TaggingJob.tag(TaggingJob.java:201)
com.teneo.esa.tag.job.TaggingJob.run(TaggingJob.java:82)
com.teneo.esa.jobmanager.remote.ThrottledJob.run(ThrottledJob.java:70)
com.teneo.esa.jobmanager.remote.RemoteJobCapsule.call(RemoteJobCapsule.java:73) c
om.teneo.esa.jobmanager.remote.RemoteJobCapsule.call(RemoteJobCapsule.java:26)
com.teneo.esa.common.remote.ServerSideRemoteExecutor$CancelHandler.callNested(ServerSideRemoteExecutor.java:559)
com.teneo.esa.common.remote.ServerSideRemoteExecutor$CancelHandler.call(ServerSideRemoteExecutor.java:535)
java.util.concurrent.FutureTask.run(FutureTask.java:266)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
java.lang.Thread.run(Thread.java:745)
Caused by: com.teneo.esa.common.persistentmap.esent.EsaEsentException: [#71000]
Admin Services Error : Esent Error - Esent error: JET_errColumnTooBig,
Field length is greater than maximum while calling JetSetColumn in function EsaEsentCursor::simplePut at line # 695
From the server.yyyy-mm-dd.log:
ERROR [tag.manager.TaggingManager] (http-bio-80-exec-23-user:) CaseName:[
com.teneo.esa.tag.TaggingException: [#124006] Tagger - Persistence Exception - While updating doc tagging data
.
Caused by: com.teneo.esa.common.persistentmap.esent.EsaEsentException: [#71000] Admin Services Error : Esent Error - Esent error: JET_errColumnTooBig, Field length is greater than maximum while calling JetSetColumn in function EsaEsentCursor::simplePut at line # 721
Cases created in eDiscovery Platform 8.2.5 and below had an Esent Tagging database size of 64Kb to store item tagging information and tag comments. Multiple long tag comments in a case can quickly fill this 64Kb size limit.
The size of this database was increased to 16Mb for cases created in version 8.2.6 and above.
To resolve this issue, a new tool, Esent Cache Management, was introduced in eDiscovery Platform versions 8.3.4, 9.0.1 and 9.1.0 as an Advanced Support Feature.
Please contact support for assistance in running this tool.