Gravatar for nicolas.a.slavik@accenture.com

Question by yonico, Dec 30, 2014 3:54 PM

Running Coveo page for the first time

Hello - Coveo is not working in the example I doing. All seems to be installed correctly and may be missing some configuration changes because it cant connect once I create the page(Oops! Something went wrong in the server.). Here is what I did:

  • Remove example from Coveo.SearchProvider.config
  • Add example to lucene config files.
  • change the yml with the instance of my sitecore
  • Index the whole database

Do I have to change anything else from the config files? I dont know what else to check.

4 Replies
Gravatar for nicolas.a.slavik@accenture.com

Answer by yonico, Jan 2, 2015 12:56 PM

Hey - it says Coveo Search REST Endpoint () The remote server returned an error: (500) Internal Server Error. Problem was solved by adding the prefix "\coveo\" in IgnoreUrlPrefixes tag in webconfig. Details here: https://developers.coveo.com/display/public/SC201412/Internal+Server+Error+When+Querying+the+REST+Service

Gravatar for jflheureux@coveo.com

Comment by Jean-François L'Heureux, Jan 2, 2015 1:43 PM

If you're using Coveo for Sitecore without the Coveo .Net Front-End, you should not add coveo to the Sitecore's list of url prefix to ignore. This causes the REST endpoint to fail to retrieve the Sitecore context.

I suggest you remove the coveo prefix to ignore and instead find the real error by examining the network transactions on the JavaScript Search UI page using your browser developer tools.

Gravatar for jflheureux@coveo.com

Comment by Jean-François L'Heureux, Jan 2, 2015 1:44 PM

Please do not use the answer field to expand on your issue. Use the Add New Comment button under an answer or update your original question if the comment section does not contain enough characters. This will keep the post clean and make it easier for visitors to see the answer to the original question.

Gravatar for nicolas.a.slavik@accenture.com

Comment by yonico, Jan 5, 2015 9:21 AM

I took a look in the network tab and it says: Server Error in '/' Application.

Session state can only be used when enableSessionState is set to true, either in a configuration file or in the Page directive. Please also make sure that System.Web.SessionStateModule or a custom session state module is included in the \\ section in the application configuration.

Any ideas of what it might be the issue?

Gravatar for nicolas.a.slavik@accenture.com

Comment by yonico, Jan 5, 2015 4:01 PM

Hello - the stacktrace shows that is trying to use this a session variable. Sitecore.Context.ClientPage.Session[CultureKey] = this.IsoCulture; I added and error remains the same. Is there any other setting I should set up?

Gravatar for jflheureux@coveo.com

Comment by Jean-François L'Heureux, Jan 7, 2015 10:20 AM

If I understand correctly, you added this XML element to your web.config file. Is it possible that the page used to render your website (the Sitecore layout) have enableSessionState set to false in its Page directive?

Otherwise, I have no other ideas for this problem. I recommend that you contact Coveo support if you have a Coveo for Sitecore support plan.

Gravatar for vseguin@coveo.com

Answer by Vincent Séguin, Dec 30, 2014 3:55 PM

Hello,

You can go see in the Sitecore logs what is wrong when you access the page, it will at least give you a better hint on how to troubleshoot.

Gravatar for nicolas.a.slavik@accenture.com

Answer by yonico, Jan 2, 2015 10:09 AM

Hey Vincent - this is the only thing that appear to be related.

4952 06:43:36 WARN The query node type 'StartsWith' is not supported in this context. Heartbeat 06:45:31 INFO Health.PrivateBytes: 328,626,176 Heartbeat 06:45:31 INFO Health.CacheInstances: 107 Heartbeat 06:45:31 INFO Health.CacheTotalCount: 19,654 Heartbeat 06:45:31 INFO Health.CacheTotalSize: 64,457,204 3852 06:45:42 INFO HttpModule is being initialized ManagedPoolThread #3 06:45:43 INFO Job started: Sitecore.Tasks.DatabaseAgent ManagedPoolThread #3 06:45:43 INFO Scheduling.DatabaseAgent started. Database: core ManagedPoolThread #3 06:45:43 INFO Examining schedules (count: 0) ManagedPoolThread #3 06:45:43 INFO Job ended: Sitecore.Tasks.DatabaseAgent (units processed: ) ManagedPoolThread #9 06:45:43 INFO Job started: Sitecore.Tasks.DatabaseAgent ManagedPoolThread #9 06:45:43 INFO Scheduling.DatabaseAgent started. Database: master ManagedPoolThread #9 06:45:43 INFO Examining schedules (count: 1) ManagedPoolThread #9 06:45:43 INFO Starting: __Task Schedule ManagedPoolThread #9 06:45:43 INFO Ended: _Task Schedule ManagedPoolThread #9 06:45:43 INFO Job ended: Sitecore.Tasks.DatabaseAgent (units processed: 1) ManagedPoolThread #3 06:45:43 INFO Job started: Sitecore.Tasks.TaskDatabaseAgent ManagedPoolThread #3 06:45:43 INFO Processing tasks (count: 0) ManagedPoolThread #3 06:45:43 INFO Job ended: Sitecore.Tasks.TaskDatabaseAgent (units processed: ) ManagedPoolThread #8 06:45:47 INFO Starting update of index for the database 'master' (2 pending). ManagedPoolThread #10 06:45:47 INFO Starting update of index for the database 'core' (3 pending). ManagedPoolThread #10 06:45:47 INFO Update of index for the database 'core' done. ManagedPoolThread #8 06:45:47 INFO Update of index for the database 'master' done. ManagedPoolThread #17 06:50:47 INFO Starting update of index for the database 'core' (3 pending). ManagedPoolThread #17 06:50:47 INFO Update of index for the database 'core' done. ManagedPoolThread #19 06:50:47 INFO Starting update of index for the database 'master' (2 pending). ManagedPoolThread #19 06:50:47 INFO Update of index for the database 'master' done. 5488 06:53:47 INFO HttpModule is being initialized 5488 06:53:47 ERROR Application error. Exception: System.Web.HttpUnhandledException Message: Exception of type 'System.Web.HttpUnhandledException' was thrown. Source: System.Web at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(HttpContext context) at ASP.coveorestdefaultaspx.ProcessRequest(HttpContext context) in c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\root\5254753c\ca55273d\AppWebdefault.aspx.51be884c.v1bk-osm.0.cs:line 0 at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

can this be related to editing the Coveo.SearchProvider.config. What needs to be edited here? Any link from cover to check this out?

Gravatar for vseguin@coveo.com

Comment by Vincent Séguin, Jan 2, 2015 10:44 AM

Hi,

Not much relevant here… If you're using Google Chrome, you may also want to check in the Network tab for the faulty request and double-click on it to see the real error (it should open in a new tab and you should see an erroneous yellow screen).

Gravatar for slangevin@coveo.com

Comment by Simon, Jan 2, 2015 10:44 AM

Please do not use the answer field to expand on your issue. Use a comment on Vincent's answer or update your original question if the comment section does not contain enough characters. This will keep the post clean and make it easier for visitors to see the answer to the original question.

Gravatar for jflheureux@coveo.com

Answer by Jean-François L'Heureux, Jan 2, 2015 10:47 AM

You can use the Diagnostic Page to check if everything's working (see Troubleshooting Problems Using the Coveo Diagnostic Page). On your search page, you can open your browser's developer tools at the network tab and check the response of the failing request to see the error details.

Ask a question