Error executing child request for handler in view

Question

I have an MVC 4 view where I render the following actions

@{
    Html.RenderAction("Index", "Logo");
    Html.RenderAction("Index", "MainMenu");
}

I have a form on my view which is filled out and posted to the controller. In the controller I perform some tasks and then send the model back to my view

[HttpPost]
public ActionResult Index(ManageAdministratorModel manageAdministratorModel)
{
     // I save some of the fields to the database here.
     return View(manageAdministratorModel);
}

When I'm redirected to the view I receive the following error

Error executing child request for handler 'System.Web.Mvc.HttpHandlerUtil+ServerExecuteHttpHandlerAsyncWrapper'.

on this line

Html.RenderAction("Index", "Logo");

Any idea why this is happening?

Top Tip: Error messages work better as quotes, rather than code blocks (my edit) — musefan, Oct 09 '13 at 13:04

score 38 · Accepted Answer · answered Oct 09 '13 at 14:08

38

Ok I found the problem, hopefully this will help someone in future.

The controllers for the partial views each contained the [HttpGet] attribute. For example

[HttpGet]
public ActionResult Index()
{
}

I remove the attribute from both controllers

public ActionResult Index()
{
}

and everything is now working.

answered Oct 09 '13 at 14:08

Andre Lombaard

6,985
13
55
96

3

Nice. I came across a similar problem which was solved using this information. – Venugopal M Aug 12 '14 at 04:54
1

thx alot you saved my time ..i kept [HttpPost] . i removed it now its working – Asad May 24 '16 at 15:31
for people who want to know the difference, one can be System.Web.Http and the over can be System.Web.Mvc – Netferret Mar 15 '17 at 15:14
Still I am getting the same issue, even if I remove. – Jeeva J Aug 16 '17 at 10:07
Solved ! Thanks ! – Suhas Dhongade Apr 17 '18 at 08:28

score 28 · Answer 2 · answered Dec 19 '14 at 16:27

28

I just got this error occurring in my razor when my partial view had a code formatting error in it.

If you click 'Continue' to get past the error, you'll see the actual error message displayed in the browser window that you loaded it from.

Correct the error in the partial view and it'll work!

answered Dec 19 '14 at 16:27

Luke

22,826
31
110
193

This helped me, I was trying to add css and script parts in the partial which it did not like. Tanks @Luke – Web Dev Guy Nov 29 '17 at 00:15
For me, it was a missing reference in the project. I opened each .cshtml file to see if there are errors inside, then I found the @using calling to a namespace in a DLL that wasn't referenced. – Ester Kaufman Nov 01 '18 at 13:59

Darin Dimitrov · Answer 3 · 2013-10-09T13:11:43.003

9

Replace:

return View(manageAdministratorModel);

with:

return PartialView(manageAdministratorModel);

otherwise you might be ending in an infinite loop because you are rendering a view which is attempting to render a view which is attempting to render a view, ...

Also you might need to remove the [HttpPost] attribute from your child action.

edited Oct 09 '13 at 13:11

answered Oct 09 '13 at 13:05

Darin Dimitrov

1,023,142
271
3,287
2,928

Oh wait. Your controller action is decorated with the `[HttpPost]` attribute. Get rid of it. For child actions there shouldn't be such attribute. – Darin Dimitrov Oct 09 '13 at 13:11
When I remove the [HttpPost] attribute and add the [ChildActionOnly] attribute I'm getting an "The action 'Index' is accessible only by a child request." error. – Andre Lombaard Oct 09 '13 at 13:31
Oh I misread.. Ignore my comment, remove the `[ChildActionOnly]` attribute. – Henk Mollema Oct 09 '13 at 13:39
Ok found the problem. Will post below to clarify. – Andre Lombaard Oct 09 '13 at 14:03
I have replace with the partial view and removed all the attributes. Still I am getting the issue. I am ending up with the infinite loop. How to solve this issue? – Jeeva J Aug 16 '17 at 10:09

score 2 · Answer 4 · answered Oct 16 '15 at 12:17

The example of "Child Action Only" is:

     public class FiltersController : Controller
    {
        public ActionResult Index()
        {
            return View();
        }

        [ChildActionOnly]
        public ActionResult Departments()
        {
            string s = "Mahi and kallu";
            return View(s);
        }

    }

**for this am creating 2 views** 
1) Index:

    <html>
<head>
    <meta name="viewport" content="width=device-width" />
    <title>Index</title>
</head>
<body>
    <div>
         @Html.Partial("Departments","Filters")

</body>
</html>
**and for Departments View:**
<html>
<head>
    <meta name="viewport" content="width=device-width" />
    <title>Departments</title>
</head>
<body>
    <div>
       @Model      
    </div>
</body>
</html>


the ***childactions*** can be rendered with the help of "Partial" keyword.

score 2 · Answer 5 · edited May 12 '16 at 15:29

2

I had the same error. It began when I changed an action to another controller, so when running the program couldn't find the view in the folder. So if you move an action to another controller, also move the view to the respective folder's controller.

edited May 12 '16 at 15:29

Brian Leeming

11,540
8
32
52

answered May 12 '16 at 14:34

Jahiron Rodriguez

21
2

score 2 · Answer 6 · edited Jul 30 '16 at 23:23

2

Get rid of the layout @{ Layout = null; } in the child view.

edited Jul 30 '16 at 23:23

Laurel

5,965
14
31
57

answered Jul 30 '16 at 22:25

moral

150
1
6

This actually helped me, I had Layout = null in my partialview which caused this error. – Ziv Weissman Aug 29 '16 at 09:46

Fox Eyes · Answer 7 · 2016-10-15T06:03:30.807

2

I was facing the same issue but I put [HTTPGet] attribute over the function name and it worked for me.

[HttpGet]
//for Filter parital view
[ChildActionOnly]
public ActionResult Filter()
{ 
  // Your code will come here.
}

edited Oct 15 '16 at 06:03

answered Oct 15 '16 at 05:58

Fox Eyes

21
2

score 1 · Answer 8 · answered Oct 20 '15 at 21:48

I had exactly the same problem, and because I was using attribute routing, the inner exception error message was:

No matching action was found on controller ''. 
This can happen when a controller uses RouteAttribute for routing, 
but no action on that controller matches the request.

Remove the [HttpGet] attributes from action methods called by Html.Action() and it works. Nothing to do with routing.

score 1 · Answer 9 · answered Jul 29 '16 at 16:31

I got this error, but my problem was diferent. To see what is the error about, involve the line you get the error inside a try catch code, like this:

 try 
    {           
         @Html.RenderAction("Index", "Logo", new {id = Model.id});
    }
    catch (Exception e)
    {
        throw;
    }

Execute it with a break point at throw line and check the inner exception of the 'e'. My problem was that I'd changed the parameter name on my Controller and forgot to change it on my View.

It's easier to get the error using try catch.

score 1 · Answer 10 · answered Feb 07 '17 at 06:53

I had this problem, It could happen because render engine can't find any view (corresponding to the name that is given in acton) I'd given wrong name of view (I mistakenly had given action name instead of view name) when I return view name and view model using PartialView() method, I corrected my view name and it worked fine

score 1 · Answer 11 · answered Mar 20 '18 at 10:38

This happened to me, because I was calling the view from different areas.

The view I wanted to call was not within an area, so when calling it from outside of all areas a call like

@Html.RenderAction("Index", "Logo");

would work without problems.

But when I wanted that same view called from another view that was inside an area, I would have to add some additional information to the call to make it explicit:

@Html.RenderAction("Index", "Logo", new { area = "" });

score 0 · Answer 12 · answered Sep 29 '19 at 19:57

In my case, I added the following code into Global.asax.cs:

protected void Application_Error(object sender, EventArgs e)
{
    var ex = Server.GetLastError();
    ...
}

Then I added a break point there and see the ex's InnerException is the SQL DB Connection error. So I replaced my Web.config file with my local development one with the correct connection string, and the problem is gone.

Error executing child request for handler in view

12 Answers12

Linked