How can the following TrueSight Presentation Server (TSPS) event related symptoms be resolved?

Events missing in TSPS compared to TrueSight Infrastructure Management (TSIM).
Events cannot be closed in TSPS.
Deleted events still visible in TSPS.
Event status incorrect. For example, event shows closed in TSIM but open in TSPS.
Event group with custom slot not working.
Unable to see any events in monitor details view.
Non-synthetic Application created in TSPS doesn't reflect actual severity based on events associated with it. 

Log in to the TrueSight Presentation  console, and select Administration > Components. Ensure that all the connected Infrastructure Management servers are up and running before you execute following procedure

Note: If you execute following steps when the Infrastructure Management servers are not up and running, the events are not reinitialized.
 

For TSPS 10.0 and 10.1:

Stop the TSPS server.

Rename the elasticsearch data folder <installdir>\truesightpserver\modules\elasticsearch\data to <installdir>\truesightpserver\modules\elasticsearch\data_backup

Start the TSPS server and once connected to TSIM it will sync all the events.

For TSPS 10.5, 10.7, 11.0 (except FP3 or later), 11.3.01:

1. From a command window, go to the <installdir>\truesightpserver\bin directory and stop the Core server process with command:

tssh process stop csr

2. Verify that the database service is running with command:

tssh server status

3. Execute:

tssh properties list | findstr EVENT_TIME_TRACKED ( Windows )
or  
tssh properties list | grep EVENT_TIME_TRACKED  (Linux)

It will output a list similar to the example below. For each TSIM it will list one row.
For example; If there are 2 TSIMs, then there will be two rows of output.

EVENT_TIME_TRACKED_1                                      1471849890
EVENT_TIME_TRACKED_2                                      1471849891

Where EVENT_TIME_TRACKED_#  is the component id of a TSIM and 1471849890 is the epoch timestamp for the last event updated for that TSIM.​

For each row, execute below commands:

tssh properties set EVENT_TIME_TRACKED_1 0
tssh properties set EVENT_TIME_TRACKED_2 0

Make sure the value for the above property is 0 before restart.

4. Stop the TSPS server. Execute 'tssh server status' to verify it is completely stopped. If the Index Server and Database Server processes still show as running then stop them manually by executing 'tssh process stop indexserver' and 'tssh process stop database'.

5. Rename the elasticsearch data folder <installdir>\truesightpserver\modules\elasticsearch\data to <installdir>\truesightpserver\modules\elasticsearch\data_backup

6. Start the TSPS server and once connected to TSIM it will sync all the events.

For TSPS in HA 10.5, 10.7, 11.0 (except FP3 or later), 11.3.01:

1. Stop the secondary TSPS and execute 'tssh server status' to verify it is completely stopped. If the Index Server and Database Server processes still show as running then stop them manually by executing 'tssh process stop indexserver' and 'tssh process stop database'.

2.  On the primary TSPS, from a command window, go to the <installdir>\truesightpserver\bin directory and stop the Core server process with command:

tssh process stop csr

Verify that the database service is running with command:

tssh server status

Execute:

tssh properties list | findstr EVENT_TIME_TRACKED ( Windows ) or  tssh properties list | grep EVENT_TIME_TRACKED  (Linux)

It will output a list similar to the example below. For each TSIM it will list one row.
For example; If there are 2 TSIMs, then there will be two rows of output.

EVENT_TIME_TRACKED_1                                      1471849890
EVENT_TIME_TRACKED_2                                      1471849891

Where EVENT_TIME_TRACKED_#  is the component id of a TSIM and 1471849890 is the epoch timestamp for the last event updated for that TSIM.​

**If the TSIM has been re-registered several times with TSPS there will be multiple EVENT_TIME_TRACKED entries, one created for each re-registration. **

3. For each row, execute below commands:

tssh properties set EVENT_TIME_TRACKED_1 0
tssh properties set EVENT_TIME_TRACKED_2 0

Make sure the value for the above property is 0 before restart.

4. On the secondary TSPS rename the elasticsearch data folder <installdir>\truesightpserver\modules\elasticsearch\data to <installdir>\truesightpserver\modules\elasticsearch\data_backup

5. Stop the primary TSPS and execute 'tssh server status' to verify it is completely stopped. If the Index Server and Database Server processes still show as running then stop them manually by executing 'tssh process stop indexserver' and 'tssh process stop database'.

6. On the primary TSPS rename the elasticsearch data folder <installdir>\truesightpserver\modules\elasticsearch\data to <installdir>\truesightpserver\modules\elasticsearch\data_backup

7. Start the primary TSPS server and once connected to TSIM it will sync all the events.

8. Start the secondary TSPS server 

Note : Best practice recommends closing the events to allow propagation to clear the events after the defined pruning period.

For TSPS 11.0 FP3 and 11.3.02 or later:

1. With TSPS running, execute command:

tssh event reinitialize

2. Enter Y when prompted to continue. The TSPS will then be automatically restarted and once connected to TSIM it will sync all the events.

For TSPS in HA 11.0 FP3 and 11.3.02 or later:

1. On the secondary TSPS execute command:

tssh event reinitialize

2. Enter Y when prompted to continue. The secondary TSPS will then be stopped.

3. On the primary TSPS execute command:

tssh event reinitialize

4. Enter Y when prompted to continue. The primary TSPS will then be automatically restarted and once connected to TSIM it will sync all the events.

5. Once the primary TSPS is active (confirmed with 'tssh ha status' command), start the secondary TSPS.