Troubleshooting Failed Objects in Teamcenter Active Workspace Indexing

It is a common scenario that we are not able to search the objects using global search in Active Workspace Client. If objects are failed to index, you can find number of failed objects in the “TcFtsIndexer.log” . But reason for failure is not mentioned in the log.  Below are some steps to troubleshoot such type of problems.

Example of entry in “TcFtsIndexer.log” is as below

2024-03-27 12:54:09,800 WARN - There are 20 failed objects which have to be fixed manually and "indexsyncfailures" flow has to be run to index these failures.

1. Run the “indexsyncfailures” to index these failed objects.
   Path: <TC_ROOT>/TcFTSIndexer/bin

2. Restart the indexing services and check the “TcFtsIndexer.log” and verify if failed objects exists if yes, number of failed objects are same or reduced.

3. To get the UID & Object type of the failed objects, use below command.
   Path: <TC_ROOT>/TcFTSIndexer/bin

4. Check the text files obtained in the previous step; One file will contain UID of failed objects (Refer image 3.1) and another file will contain the UID and object types of the failed objects (Refer image 3.2). Examine the data model for these objects and review the property values for those that are being indexed. Fix the issues if any and then reindex the data again.

Some examples of Issues observed:

• Property constant “Awp0SearchIsIndexed” is true for particular property but Business Object Constant “Awp0SearchIsIndexed “is false for the same object.

• Some special in value of property.

By following this approach, you'll be well-equipped to troubleshoot failure objects in Teamcenter AWS (Active Workspace) and ensure smooth indexing.