I have an solr instance running and trying to pull the data with search_api_solr. The url is correct and when I save I get a notification that it successfully connected. However, when I go to add an index view, I get a 500 error (set as drupal message).

Then I enabled and configured Sarnia, which I actually need because the solr index doesn't contain any drupal specific data. It does successfully find the solr fields from luke. When I try to add an index this time, I receive the same error as an ajax error in a js alert box:

An AJAX HTTP error occurred.
HTTP Result Code: 500
Debugging information follows.
Path: /admin/structure/views/view/testview/preview/page/ajax
StatusText: Service unavailable (with message)
ResponseText: EntityMetadataWrapperException: Invalid data value given. Be sure it matches the required data type and format. in EntityDrupalWrapper->set() (line 731 of /Applications/MAMP/htdocs/d7theming.local/sites/all/modules/entity/includes/entity.wrapper.inc).

When I save the view and go to the url, I get an unrecoverable error which contains the same error.

Any ideas?

Comments

guillaumev’s picture

guillaumev CreditAttribution: guillaumev commented

Same error here, with sarnia properly configured, but the error appears only when I try to add the a specific field (ie the body field): other fields work fine...

guillaumev’s picture

guillaumev CreditAttribution: guillaumev commented

Better said, any t_* field causes the error, besides t_title...

remydenton’s picture

remydenton CreditAttribution: remydenton commented

I also ran into this error. In my case, the issue was that the solr field I'd selected as the entity ID field contained text strings, not integers.

It sounds like guillaumev may have run into something slightly different, though not unrelated...

remydenton’s picture

remydenton CreditAttribution: remydenton commented
Issue summary: View changes

Added a note to state I have the same error when accessing the views path

anj’s picture

anj CreditAttribution: anj commented
Issue summary: View changes

After upgrading search_api_solr to 1.4, I got this error. I downgraded to version 1.1 again and the error went away.

drunken monkey’s picture

drunken monkey
he/him
Primary language German
Location Vienna, Austria
CreditAttribution: drunken monkey commented

Have you updated to the newest Entity API version? If not, that might explain this error.

However, it is not triggered in Solr but in Drupal, though the underlying problem might be specific to Solr.
Are you using Sarnia as well? Maybe that is the problem, modules building on this one often lag behind a bit in regard to reacting to the latest changes.
Otherwise, please give a more detailed description of your setup and the error you receive.

rajeshsp39’s picture

rajeshsp39 CreditAttribution: rajeshsp39 as a volunteer and commented
OanaIlea’s picture

OanaIlea CreditAttribution: OanaIlea at bio.logis Genetic Information Management GmbH commented
Status: Active » Closed (outdated)

This issue was closed due to lack of activity over a long period of time. If the issue is still acute for you, feel free to reopen it and describe the current state.