1

We have a sitecore 9.1.1 CM instance configured to use Azure Cloud. We have the relevant configurations enabled & disabled.

However we are seeing the following:-

16784 22:55:11 WARN  Could not compute value for ComputedIndexField: potential for indexable: sitecore://master/{3FF23DB1-A0F7-46DF-84D3-E17FCC19CB06}?lang=ar-AE&ver=2
Exception: System.Reflection.TargetInvocationException
Message: Exception has been thrown by the target of an invocation.
Source: mscorlib
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at Sitecore.Reflection.ReflectionUtil.CreateObject(Type type, Object[] parameters)
   at Sitecore.Configuration.DefaultFactory.CreateFromTypeName(XmlNode configNode, String[] parameters, Boolean assert)
   at Sitecore.Configuration.DefaultFactory.CreateObject(XmlNode configNode, String[] parameters, Boolean assert, IFactoryHelper helper)
   at Sitecore.Configuration.DefaultFactory.CreateObject(XmlNode configNode, String[] parameters, Boolean assert)
   at Sitecore.Configuration.DefaultFactory.CreateObject(String configPath, String[] parameters, Boolean assert)
   at Sitecore.Xdb.Reporting.Datasources.Remote.RemoteReportDataSourceProxy.GetData(ReportDataQuery query)
   at Sitecore.Xdb.Reporting.ReportDataProvider.ExecuteQueryWithCache(ReportDataQuery query, ReportDataSource dataSource, CachingPolicy cachingPolicy)
   at Sitecore.Xdb.Reporting.ReportDataProvider.GetData(String dataSourceName, ReportDataQuery query, CachingPolicy cachingPolicy)
   at Sitecore.Xdb.Reporting.ReportingQueryBase.ExecuteQuery(Dictionary`2 parameters)
   at Sitecore.ContentTesting.Analytics.Reporting.TestPotentialQuery.Execute()
   at Sitecore.ContentTesting.ContentSearch.ComputedIndexFields.TestPotentialMetricBase.ComputeFieldValue(IIndexable indexable)
   at Sitecore.ContentSearch.AbstractDocumentBuilder`1.<>c__DisplayClass57_0.<AddComputedIndexFieldsInParallel>b__0(IComputedIndexField computedIndexField, ParallelLoopState parallelLoopState)

Nested Exception

Exception: System.ArgumentException
Message: Service Host URI is not a valid URI.
Parameter name: serviceHostUrl
Source: Sitecore.Framework.Conditions
   at Sitecore.Framework.Conditions.RequiresValidator`1.ThrowExceptionCore(String condition, String additionalMessage, ConstraintViolationType type)
   at Sitecore.Framework.Conditions.Throw.ValueShouldBeTrue[T](ConditionValidator`1 validator, String conditionDescription)
   at Sitecore.Analytics.Core.ConfigurationBasedHttpTransportFactory..ctor(String serviceHostUrl, String timeout, BaseLog logger)
   at Sitecore.Analytics.Core.ApiKeyHttpTransportFactory..ctor(String serviceHostUrl, Boolean requireHttps, String connectionStringName, String headerName, String minimalApiKeyLength, String timeout)

I know the computed index is defined by configuration for sitecore_suggested_text_index. The easiest option is to disable the fields but not really a fan of turning things off because they aren't working.

I'd like to know if we are missing something or if we do turn it of what is the potential setback of turning off fields "potential", "impact" & "recommendation"?

Also can confirm that the azure search connection string is correct.

0

did you checked if your processing and reporting roles are correctly configured. And also you have made proper configurations in your CM instance to use the reporting instance? Seems like a similar issue https://community.sitecore.net/developers/f/9/t/5594

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.