Timeline for Web indexes not updated upon publish
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 4, 2018 at 0:10 | comment | added | jrap |
Viewing EventQueueStats.aspx from your CM server will not help. If you're able to view that page from your CD server that could help to let you know if the Event Queue is healthy.
|
|
| Jan 4, 2018 at 0:09 | comment | added | jrap |
This is certainly part of the issue. Go in your core database and run the following query SELECT * FROM [Properties] where [Key] like EQSTAMP%' You should see separate instance names from all servers that are properly processing the event queue. The Value field should be almost identical as well- which implies all server shave processed the latest events. If you do not see more than one record returned, then your CD server is not processing events properly.
|
|
| Jan 3, 2018 at 14:59 | history | edited | Andrei Paliakou | CC BY-SA 3.0 |
change formatting
|
| Jan 3, 2018 at 14:57 | comment | added | novicecoder | Thanks Andrei. The other half of my question explains the steps I took after I changed the set up to use shared Core DB. I still can't get the index to update. | |
| Jan 3, 2018 at 14:53 | history | edited | Andrei Paliakou | CC BY-SA 3.0 |
added 769 characters in body
|
| Jan 3, 2018 at 14:39 | history | answered | Andrei Paliakou | CC BY-SA 3.0 |