Error in '/' Application. Value cannot be null.
Parameter name: fieldNameTranslatorDescription: An unhandled exception occurred during the
execution of the current web request. Please review the stack trace for more
information about the error and where it originated in the code.
Exception Details: System.ArgumentNullException: Value cannot be null.
Parameter name: fieldNameTranslator
Source Error: An unhandled exception was generated during
the execution of the current web request. Information regarding the origin
and location of the exception can be identified using the exception stack
trace below. Stack Trace:
[ArgumentNullException: Value cannot be null. Parameter name: fieldNameTranslator] Sitecore.ContentSearch.Linq.Solr.SolrIndexParameters..ctor(IIndexValueFormatter
valueFormatter, IFieldQueryTranslatorMap`1 fieldQueryTranslators,
FieldNameTranslator fieldNameTranslator, IExecutionContext executionContexts,
IFieldMapReaders fieldMap, Boolean convertQuer…
I recently integrated Solr with Sitecore 7.2 and found that the Schema.xml generated by Sitecore is only supported up to Solr 4.x. Configuring Solr for Sitecore 8 provides the steps required to upgrade Schema.xml to work with Solr 5.x, especially the Step 3 that mentions that Solr.IntField is deprecated and must be replaced with Solr.TrieIntField.
What is fails to mention is that you need to replace the other field types as well else you run into the following error for each of the field types:
Could not load conf for core contentindex: Plugin init failure for [schema.xml] fieldType "plong": Error loading class 'solr.LongField'.The Fix:
In all my experience delivering Sitecore solutions, and having worked for a few platinum implementation partners, I have come to know the "Crawl, Walk & Run" pitch quite well. To most customers, when they hear the crawl, walk and run, I think all they hear is Phase 1, Phase 2, other parking lot items. And guess what is often a Phase 2 item...enabling xDB and its features such as content personlization, visitor identification, campaign management etc. Implementation partners actually may help you justify this by giving various excuses such as, the implementation of these featured will have a significant impact to budget, timeline, etc.
I think this has been the challenge Sitecore as a company has been trying very hard to overcome. Moreover, the past two Gartner reports show Sitecore neck to neck with Adobe as clear leaders in the Digital Marketing space but falling short on execution of it's experience management features (now digital exeprience).