Hi,
I'm trying to understand the "Media Files Usage" local index.
We run in azure, Client and Admin run on separate Web Apps, and the Client site runs from package, so doesn't have write permission to App_Data.
So last year we were getting multiple errors in the local index task, so I patch to the latest version to allow me to disable the media file usage index. Which prevented the errors and didn't cause us any issues.
Now we would like to re-enable as we would like the usage stats. But if I rebuild the index it runs for the CMS and for the client site. The CMS completes and seems to work showing the usage, but the Client errors with "Error while processing index MediaFilesUsage: An error occurred while obtaining the index writer.".
I don't understand why the task needs to run on the Client site, but I can't see a way to disable.
I cleared the error and ran the "Execute local search tasks" task and it didn't appear to generate an error. Do this just execute the CMS task?
Thanks
Mat
I would try using a "shared" indexes. I mean, using e.g. custom or Azure storage provider and map the search index files to this location and then disable the web farm synchronization for search index files. Or, if the front end app has permissions to write to a different folder than App_Data, set a custom index location using the CMSSearchIndexPath key
Thank you Juraj, Does the index need to run on the client app as well? is there anyway to disable?
There is no setting to disable just this one index. Only to disable the web farm sync for all indexes.
Sorry Juraj last question, does it need to run on the client app? what is the purpose of it running there?
I do not see any reason why it is on the live site app. I will bring this up to the product team as an improvement idea.
Amazing, thank you.
Please, sign in to be able to submit a new answer.