Gravatar for christopher.everitt@abc.virginia.gov

Question by Chris, Jan 30, 2018 4:22 PM

'The user "coveo\admin" does not exist' after Coveo for Sitecore upgrade

I have updated from On Prem Coveo for Sitecore version 4.0.402.0 to 4.0.1606.9. The update seems to go smoothly. The Diagnostic Page seems to indicate the update succeeded and everything is healthy. My indexes seem to be working just fine.

Now I am seeing this error in the logs:

10184 10:43:09 ERROR An error occurred while calling method "GetUserMembers".
Exception: Coveo.Connectors.Sitecore2.SitecoreWebServiceExceptions.SitecoreWebServiceUserNotFoundException
Message: The user "coveo\admin" does not exist.
Source: Coveo.Connectors.Sitecore2.SitecoreWebService
   at Coveo.Connectors.Sitecore2.SitecoreWebService.Wrapper.BaseSitecoreWrapper.GetUserMembers(String p_UserName)
   at Coveo.Connectors.Sitecore2.SitecoreWebService.SitecoreWebService.<>c__DisplayClass1d.<GetUserMembers>b__1c()
   at Coveo.Connectors.Sitecore2.SitecoreWebService.SitecoreWebService.TryCatchWrapper[T](Func`1 p_Action, String p_MethodName)

This error seems to be happening during reindexing.

What is the cause of this error and how to I resolve it?

1 Reply
Gravatar for aasanovic@coveo.com

Answer by Aljosa Asanovic, Jan 30, 2018 4:39 PM

Hi @ceveritt,

You can safely disregard this error as it does not impact the functionality in any way. The user technically does not exist as it's a virtual user that we use only in Coveo for Sitecore.

Suppressing these specific logs would require changes to two components and the fix was thus rejected for the moment in favor of more essential or pressing contributions, especially since the logged error is harmless.

I presume that this is an on-premises installation as a Cloud index uses our new expanded security provider which is push only and does not ping back to the Sitecore instance in the same way your current Sitecore2 Security provider does.

Hopefully that answers your question!

Gravatar for christopher.everitt@abc.virginia.gov

Comment by Chris, Jan 30, 2018 7:12 PM

Thanks for your answer. I ended up configuring a log4net filter to exclude these messages from our logs.

Ask a question