SearchApiException fields of index... [#2230771]

I hope someone who reads this might respond, perhaps sooner then they ordinarily might, this is a small crisis for me-THANK YOU FOR YOUR HELP

I had made some changes re: how facets display and changed a few fields from fulltext to string.
Now I have no index(s), and attempting to build one fails. I am not a very advanced developer, and I have not yet tried adding a patch.

I have tried undoing the changes, no go.

Error below appears to indicate a pending job, but I don't know how to clear it.

here are errors from the log (in revers chron order)

Tuesday, April 1, 2014 - 10:10
SearchApiException: Could not index items since important pending server tasks could not be performed. in search_api_index_specific_items() (line 1481 of /home/[domain]/public_html/sites/all/modules/search_api/search_api.module).

Tuesday, April 1, 2014 - 10:10
SearchApiException while updating the fields of index Product Node Index on server Drupal Server: Cannot add field search_api_db_default_node_index_type.word: field already exists. in SearchApiDbService->fieldsUpdated() (line 515 of /home/[domain]/public_html/sites/all/modules/search_api_db/service.inc).

Comment	File	Size	Author
#6	search_api_index-wsod_server_unavailable-2575651-6-D8.patch	2.34 KB	devd

Comments

Comment #1

jrandell commented 1 April 2014 at 21:24

Category:	Support request	» Bug report
Priority:	Critical	» Normal

I found the banana peel, but I don't know how it got there in the first place.

reading and re-reading the threads, here and other places, regarding similar issues, I came across deactivating, then reactivating the index, which I had tried multiple times through out my troubleshooting process, but finly found a thread where someone suggested disabling, then re-enabling the Server.

So I disabled each of my two Search Indexes, then the Server they both were using.
I then re-enabled the Server, then each of the Search Indexes.
After that, I ran an index update on the first Index (my heart skipped a beat as it actually began indexing),
and after completion, the I did the second (holding my breath).

I went to my search page, then proclaimed to the universe, ITS ALIVE!!!!

If anyone want more detailed info to help track the issue, I would be happy to oblige.

Thanks All,
-Jim

Comment #2

drunken monkey

he/him

German

Vienna, Austria

commented 14 April 2014 at 09:00

Status:

Active

» Closed (cannot reproduce)

Good to hear you managed to fix this. I cannot really offer you any further insights here, though, I also don't know how this might have happened. If the server was created with an earlier version of this module and the Search API, there might have been some bug that caused an internal inconsistency, which only now manifested itself in an error – but it's hard to analyze now.

So, unless someone else has this problem or it occurs again, I think we should just close this issue.

Comment #3

PMorris commented 9 May 2014 at 15:03

I had this same error today. It happened when I had been working with an index and decided to turn on "node id" field for index. I couldn't re-index without this error! But disabling and re-enabling server fixed it.

SearchApiException: Could not index items since important pending server tasks could not be performed. in search_api_index_specific_items() (line 1481 of /Users/me/WORK-PAUL/GroupBBH/website/htdocs2/sites/all/modules/search_api/search_api.module).

SearchApiException while updating the fields of index Product Index on server GroupeBBH Server: Cannot add field <em class="placeholder">search_api_db_product_index_field_brand</em>.<em class="placeholder">word</em>: field already exists. in SearchApiDbService->fieldsUpdated() (line 515 of /Users/me/WORK-PAUL/GroupBBH/website/htdocs2/sites/all/modules/search_api_db/service.inc).

Comment #4

alamp commented 10 May 2014 at 02:54

+1 vote for #3,#2. It works fine for me.

WD search_api: SearchApiException while updating the fields of index Default node index on server database service of local: Cannot[error]
add field search_api_db_default_node_index_type.word: field already exists. in SearchApiDbService->fieldsUpdated() (line 515 of
/Drupal /sites/all/modules/search_api_db/service.inc).

Comment #5

input commented 3 June 2014 at 14:24

Can confirm this.
changed on field from Sting to fulltext -> indexing is throwing error the second error message to watchdog.
switching back -> everything is fine

Following jrandell's workaround seems to fix it for the moment if you have changed the type.
But looking into the database the fieldvalues seem to be indexed as full string and not as single words as i belive it should.

edit: After clearing all indexed data within the search index and the server it seems that everything is indexed correct

Comment #6

devd commented 29 September 2015 at 17:37

Status	File	Size
new	search_api_index-wsod_server_unavailable-2575651-6-D8.patch	2.34 KB

Thanks Thomas,

To acknowledge the issues. I did update the error message and line no. as per throwing exception class.
Also added the $class variable with 'error'.

Comment #7

devd commented 30 September 2015 at 08:04

1 file was hidden/shown/deleted

Status	File	Size
hidden	search_api_index-wsod_server_unavailable-2575651-6-D8.patch	2.34 KB

Sorry for all,

By mistake i have uploaded patch on this issue.

Comment #8

NewZeal commented 9 February 2016 at 18:20

I had this problem, after changing a field from string to fulltext and followed the suggestion in comment #1, restart both server and index, and the problem vanished.

Comment #9

respown commented 24 February 2016 at 19:47

Same for me #2 solution worked for error:
SearchApiException while deleting items from server Frontend: SQLSTATE[42000]: Syntax error or access violation: 1103 Niedozwolona nazwa tabeli 'drup_search_api_db_product_display_field_product_commerce_price_amo'... in SearchApiDbService->deleteItems() (line 1147 of /myserver/profiles/commerce_kickstart/modules/contrib/search_api_db/service.inc).