01-01-2014 04:39 PM
We are running TRIM Workgroup 184.108.40.2067
Under TES / MEP we are receiving content Indexing "continually blocked by error" even after identifying and deleting the uri's in question (there are about 10,000 documents in the queue).
Select * from TSEVENTDAT
Where uri = xxxxxxx
Delete From TSEVENTDAT where uri = xxxxxxx
We then stop the Content Indexing through Event processing / Configure, then save and deploy the change, then enable Content Indexing, save and deploy. Then look at Event processing / Monitor.
The status will change from Running to Blocked by Error.
Any suggestions please advise.
01-01-2014 05:45 PM
I think your best avenue here would be to log a case with suppot to have it looked into. We will require the windows app logs, TRIM DCI logs etc.
01-02-2014 10:43 AM
With CI suspended, you could delete all queued CI Events.
Then run a re-index from within TRIM Enterprise Studio (TES). The Date Registered should match the time frame when this issue started. (i.e. Dec 15-31.)
Then you should reindex edocs with Date Modified with those same dates. That will ensure you capture recs which were created earlier but that have been edited during your issue window.
If you run search in TRIM, avoid double indexing by matching search shown below:
Date Modified = Dec 15-31
NOT Date Registered = Dec 15-31
Filter for record types as appropriate, if you want to push through certain ones as priority.
01-06-2014 04:06 PM
We are looking at performing the re-index etc within an out-of-hours time frame over the next week.
Shall update the blog with the how things went.