I have a problem in that AOD is not returning any results at all. Initially trying to search from the search bar resulted in nothing but a blank screen.
There was also a series of errors being logged:
Mon Apr 11 17:13:24 2016 [27085][44bc535b-103d-dc6e-00c6-54a3d594bf4d][FATAL] Exception in Controller: String could not be parsed as XML
Tue Apr 12 14:49:11 2016 [30686][44bc535b-103d-dc6e-00c6-54a3d594bf4d][FATAL] Exception in Controller: Unsupported segments file format
Tue Apr 12 14:49:44 2016 [30291][44bc535b-103d-dc6e-00c6-54a3d594bf4d][FATAL] Exception in Controller: Unsupported segments file format
Tue Apr 12 14:51:24 2016 [30291][44bc535b-103d-dc6e-00c6-54a3d594bf4d][FATAL] Exception in Controller: Unsupported segments file format
Wed Apr 13 14:02:42 2016 [30486][44bc535b-103d-dc6e-00c6-54a3d594bf4d][FATAL] Exception in Controller: String could not be parsed as XML
Wed Apr 13 14:03:08 2016 [30486][44bc535b-103d-dc6e-00c6-54a3d594bf4d][FATAL] Exception in Controller: String could not be parsed as XML
Wed Apr 13 22:58:56 2016 [32209][44bc535b-103d-dc6e-00c6-54a3d594bf4d][FATAL] Exception in Controller: Unsupported segments file format
Wed Apr 13 22:59:42 2016 [32209][44bc535b-103d-dc6e-00c6-54a3d594bf4d][FATAL] Exception in Controller: Unsupported segments file format
Wed Apr 13 23:11:14 2016 [32258][44bc535b-103d-dc6e-00c6-54a3d594bf4d][FATAL] Exception in Controller: Unsupported segments file format
So following some advice in another thread, I renamed the folder at /var/www/crm2015/modules/AOD_Index/Index/Index and performed a quick repair and rebuild. The /var/www/crm2015/modules/AOD_Index/Index/Index was recreated as expected. There have been no further errors logged either.
Better still, the search results page now loads correctly, but no results are generated at all.
OK, I have no idea what has happened - I have made no changes since posting here - but the AOD search seems to be working again. Sort of.
4 days after my original post and earches are now returning results, but they are incomplete. A search for string ‘2016-04 WMS’ returns an opportunity ‘2016-04 Veritas’ - despite there being an opportunity called ‘2016-04 WMS’.
Further testing shows that despite having several opportunities beginning ‘2016-04’, just one is ever returned when using the AOD search - ‘2016-04 Veritas’.
OK, further testing reveals that the AOD search results only update when the record is updated. So if I edit a record, it will then appear in the relevant AOD search.
The installation I was having trouble with was an installation upgraded from previous versions. I installed a fresh up to date version in another folder and copied the files over from /modules/AOD_Index/Index/Index to the installation that wasn’t working and voila! It’s now indexing the files.
The other thing i had to do was increase the max execution time in the php.ini to like 6000 seconds.
Yes, I copied the files in that folder over from a vanilla install and it worked no problem.
Don’t know what happend, but I had multiple sites that were upgraded from previous versions that the AOD did not work. Copying in the empty files from a vanilla new install from the current version got my other installations working.