Skip to main content

Sitecore 9 : Error in controller rendering throws Error rendering controller:the current route url is: '{*pathinfo}'. this is the default sitecore route which is set up in the 'initializeroutes' processor of the 'initialize' pipeline sitecore 9

Hello Guyz,
Believe me but I just had the nightmarish situation where I got trapped in this controller rendering issue where it kept on giving me below error

Error rendering controller: the current route url is: '{*pathinfo}'. this is the default Sitecore route which is set up in the 'initializeroutes' processor of the 'initialize' pipeline

There mainly two reasons for this exception

  • Controller rendering you have used is having either wrong namespace, wrong controller name or wrong assembly name.
  • There is something wrong with System.Web.Mvc.dll

you should first observe your controller rendering configuration, see if namespace or controller name or assembly name are correctly given? this is common issue when we copy and paste the path and it could contain spaces or aeesmbly name could be wrong, if everything looks good there, read further

I tried everything like changing the name of controller, deleting the physical controller and creating It with different name, deleting renderings from sitecore and try creating them again, deleting global.asax file deleting sitecore cache, but I was ending in the same error all the time, and finally one fine moment I was out side my home one small thing clicked me and I run back to my laptop and tried implementing it and it worked !! Phew !!! which is following .

Solution


Well, When I created my visual studio project it added the System.Web.Mvc.dll by default and it was added with the version 5.2.4.0 which is fine but the issue was that sitecore installation was using the version 5.2.3.0

Now because my general practice is that I delete my projects web.config file and also web..config files from the view, and copy it from sitecore's installation, now my solution had config from sitecore which were pointing to 5.2.3.0 DLL and my solution had 5.2.4.0, which could never work and end up in assembly manifest error, if i deploy, as i did not copied it to BIN that error was not there but somehow solution was using 5.2.4.0 when sitecore requested that page or controller/action path, and due to it the route was not working

A small change i did,

  • Deleted the any old reference from bin folder of my IIS site
  • Copied sitecore's System.Web.Mvc.dll and added it as a reference to my project so i downgraded my project from 5.2.4.0 to 5.2.3.0
  • Deleted web.config and copied it from sitecore's instance
And it worked now sitecore is able to find the route and hitting the MVC controller, Phew !!!

Try above tips if you get trapped in similar situation


Comments

  1. AnonymousFebruary 1, 2022 at 9:07 PM

    Lucky Club Casino Site » Review, Including Bonuses, Games
    Lucky luckyclub.live Club Casino ✓ Real players' reviews, ratings, games, complaints, bonus codes ✓ Check Lucky Club Casino. Check Lucky Club Casino 2021 bonuses. Rating: 8.2/10 · ‎Review by LuckyClub.live

    ReplyDelete
  2. AnonymousAugust 12, 2022 at 7:09 AM

    Thank you you just saved my life with this one!!

    ReplyDelete

Post a Comment

Popular posts from this blog

401.1 Unauthorized with windows authentication error code 0xc000006d

How many of you have faced this hosting issue when you do everything what it takes to run the site with windows authentication but still you are getting the same error again and again? If you think you also have faced the same issue and you tired of reading MSDN KBs for it and still have not found the issue (If KB has solved the issue, well and good, if not you can try this trick),Please Read below Typical scenario In typical hosting with IIS, i did every possible things like enabling windows authentication, changing it in web.config, configuring connection pool, authorization rules, it asks me for window authentication login and despite of entering correct credentials it always fails and keeps on asking for login, and when pressed cancel it gives 401.1 with 0xc000006d error code Solution (Which worked for me at-least after trying for almost 6-9 hrs) You need to change the Loop Back Check in registry so that it allows the host names which you are giving in url are allowed and au...
2 comments
Read more

Set up leprechaun code generation with Sitecore XM Cloud Starterkit

Hi Sitecorians, It has been amazing learning year so far and with the change in technology and shift of the focus on frontend frameworks and composable products, it has been market demand to keep learning and exploring new things. Reasons behind this blog Today's topic is something that was in my draft from April-May, and I always thought that there is already a good documentation out there for  Leprechaun  and a blog post is not needed, Until I realized that there was so many of us facing same kind of issues and same kind of problems and spending same amount of time, That is where I thought, if I could write something which can reduce that repetitive troubleshooting time, That would really help the community. 1)  In a project environment, if we get into some configuration issues, we resolve them, we make sure we are not blocked and continue, but if you think same issue, same step and same scenario will come to other people, so if we can draft it online, it will help othe...
Post a Comment
Read more

One or more exceptions occurred while processing the subscribers to the 'item:creating' event

I was recently installing the packages from one of the QA environment to my local Sitecore instance, "Media library package" to be precise, And it started giving me this below error One or more exceptions occurred while processing the subscribers to the 'item:creating' event Looking at the sitecore logs, it gave me more info on the context and the actual inner exception was following Solution: 'Name' should consist only of letters, digits, dashes or underscore Now it was evident that some of my file names were violating the naming rule, I could see in the log just before exception from where the installer stopped creating items, and that file name had round braces "(" and ")" at the end of it, with my surprise I was able to create the item with those name in the content tree, but below was the solution for it, Solution I am using SC 9.0.1 and in that Go to Sitecore.Marketing.config file residing in "App_Config\Sitecore\Mar...
9 comments
Read more