A server error from two months ago keeps displaying in the Status & Updates page. I will click on the Reset button and it goes away; however, a little while later, it comes back.
The Server errors are stored in the t_dbinfoproperties table. Only one error is supposed to be listed in that table; however, in this case, two errors were listed: a new error message showing the current unix time and the old "ghost" message that has a unix time from a couple of months ago. The ghost message had a unique "server_id" value from all the other entries in the table.
Thus, anytime a new Server error would occur (indexer extraction errors), it would be recorded in the t_dbinfoproperties table; however, when the Status & Updates page would be refreshed, the old server error values would be displayed.
We ran a query to delete the four rows that contained that unique server_id value. After that, anytime a new error occurred, it now displayed in Status & Updates.
This article was originally published in the GWAVA knowledgebase as article ID 2522.