London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
AI OnAI Off
ElasticSearchIllegalArgumentException[failed to execute script]; nested: ScriptException[dynamic scripting disabled];
We are using "Random2Find" lib, that uses script-based sorting. Find started returning "400 Bad Request" in development environments recently. We have a similar error: "ScriptException[dynamic scripting disabled]". Didn't fix it yet :(
And yes, production indexes work fine.
Edited,
Feb 25, 2015 15:12
Hi!
Thank you for reply.
What version of elasticsearch is used for developer indexes?
Edited,
Feb 26, 2015 6:31
I don't know. I wrote a request to EPiServer support regarding this problem and waiting for their help.
Feb 26, 2015 11:12
As I found out from EPiServer, in EPiServer.Find 9 custom scripting is disabled, so you will need to find another way how to solve your tasks.
I assume this was done for security reasons.
Mar 04, 2015 14:26
"Random2Find" lib was updated a week ago and it uses native "randomvaluegenerator" instead of custom scripting, so it works fine with Find 9. This update fixed our issue.
Mar 10, 2015 12:54
This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.
Hi!
We found that the developers indexes were cleared yesterday.
We created new indexes and the appropriate ps scripts were run to check dynamic mappings.
But during the indexing the errors appeared:
2015-02-25 09:36:19,927 [13] ERROR Customer.Commerce.Business.Search.FindProvider.FindSearchProvider: Indexing error:
ElasticSearchIllegalArgumentException[failed to execute script]; nested: ScriptException[dynamic scripting disabled];
How could we fix the issue with developer indexes?