In this post, I’m going to tackle an error I encountered previously during my upgrade execution to v.8.1 Update-2. There were various discussions over the internet related to this common issue, so if the fix I’m going to provide shortly didn’t resolve your issue, I encourage you to take a look at these blogs / posts, as well.
- Getting error on Content Editor after upgrading to Sitecore 8, here
- Error in contenttestingupdate.aspx while performing a Sitecore upgrade, here
- Content Search rebuild index error, here
- Resolved Sitecore SOLR provider error, here
If you have a blog post, that tackles the same issue with different approach / suggestions from the above links, please feel free to comment below so I can add it also in the list.
I faced this issue when configuring SOLR as my search provider in my local instance – migrated from the production instance of one of my clients.
- I log-in to Sitecore, and the dashboard page loaded properly
- I navigated to Desktop interface, and it loads properly as well.
- I navigated to Content Editor, and it throw the above error.
Upon checking on my configurations, I missed to disabled every single file that has ‘Lucene’ on its file name. I did, but it’s still showing the same error.
I compared the DLLs of Content Search and Castle Windsor – in this case my IOC, and they were not assembly identical. So, I replaced all the DLLs from a freshly installed instance – in this case v.8.1 Update-2, but the issue keeps showing.
The above were just two (2) out of many file version discrepancies I had encountered.
When you upgrade to a particular Sitecore Platform version, in the Sitecore Experience Platform page (eg. v.8.1 Update-2), there is a SOLR Support package you should use to overwrite the existing assemblies you have in your bin folder.
Warning: You don’t need all of these DLLs. In my case, I used Castle Windsor as my IOC. So what I only need are:
The Sitecore Search Scaling Guide is an essential documentation that explained the files you only need in a particular IOC implementation. You can read the chapter 3.3.1, but I would just paste it here to make it more easier for you.
Lastly, I altered the Global.asax file.
I tried it again, and the Content editor loads properly now.