The controller for path '/mini-profiler-resources/results' was not found or does not implement IController

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
7 years ago
Hello,
I am using Nopcommere 3.8 and getting frequently this error in the log.
Showing the mini-profiler on Webfrontend is deactivated.

I assume it's a Google bot/crawler or something like this calling that url since the user calling that is "builtin@search_engine_record.com"

Here the complete log:

The controller for path '/mini-profiler-resources/results' was not found or does not implement IController.

System.Web.HttpException (0x80004005): The controller for path '/mini-profiler-resources/results' was not found or does not implement IController. at System.Web.Mvc.DefaultControllerFactory.GetControllerInstance(RequestContext requestContext, Type controllerType) at System.Web.Mvc.DefaultControllerFactory.CreateController(RequestContext requestContext, String controllerName) at System.Web.Mvc.MvcHandler.ProcessRequestInit(HttpContextBase httpContext, IController& controller, IControllerFactory& factory) at System.Web.Mvc.MvcHandler.BeginProcessRequest(HttpContextBase httpContext, AsyncCallback callback, Object state) at System.Web.Mvc.MvcHandler.BeginProcessRequest(HttpContext httpContext, AsyncCallback callback, Object state) at System.Web.Mvc.MvcHandler.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)


http://www.myshop.com/mini-profiler-resources/results?id=bd9446c7-cad2-4ae1-abac-6aaf2cf2bac6

Would be nice if someone could provide a solution or help how to avoid this error.
Thanks.
7 years ago
Just go to admin area > configuration > settings > all settings > set "commonsettings.log404errors" to "False"
7 years ago
Hello,

Thanks for quick answer,  will do so.
So that "error" is nothing to worry about? The built-in-searchengine-record should not be able to access the mini-profiler anyway ? I assume it was Google trying to reach this url.

The weird is that sometimes this URL could be reached. Do you know why google could be interested in this url ?

Regards
Jens Fiedler
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.