.NET 3.5 chart controls exception: Error executing child request for ChartImg.axd

Question

Anyone getting this error when using the new free chart controls MS bought from Dundas?

\"Error executing child request for ChartImg.axd\"

On the MSDN forum

Answer 1

Just wanted to point out that it is also a permission problem with the image not found error.

Set the "Allow modify" permissions on your image folder (per default it is "C:\TempImageFiles" for the account under which your website is running.

Problem disappears.

Answer 2

In IIS 6.0 (Server 2003) this error will occur if the httpHandler is missing (see Previous Answer)

Looking into the stack trace it appears that IIS 6.0 assumes that a handler will be loaded. It does an Execute on the statement and the exception is swallowed. Including the following attribute (as shown above) under the httpHandlers in IIS 6.0 fixed this for me.

<add path="ChartImg.axd" verb="GET,HEAD" type="System.Web.UI.DataVisualization.Charting.ChartHttpHandler, System.Web.DataVisualization, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"  validate="false"/>

Note that I changed the Version from the previous answer to 4.0.0.0 and tested in Server 2008 (IIS 7.0) and Server 2003 (IIS 6.0)

Answer 3

On .NET 4.0 the charts come built-in, but you still may need to add the similar tag below:

<add path="ChartImg.axd" verb="GET,HEAD,POST" type="System.Web.UI.DataVisualization.Charting.ChartHttpHandler, System.Web.DataVisualization, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" validate="false" />

Answer 4

More info on this:

I was having trouble with the web.config issues as well and remedied that by ensuring web.config was not open in the code editor when I dragged and dropped the Chart control onto the page. If web.config was not already open, Visual Studio 2010 would make the appropriate modifications.

I was able to successfully get past the "error executing child request" error after successfully applying the web.config issues.

Also regarding usage in an MVC application, I was struggling to implement this in my MVC 2 application (VS2010/.NET 4) and ran into another gotcha.

The page's call to ChartImg.axd was resulting in an HTTP 404 error. (I found this using Fiddler.)

It turns out the page was trying to access the handler from /MyController/ChartImg.axd instead of /ChartImg.axd (from the root).

I was able to fix the problem by adding this line to my Global.asax.cs file:

routes.IgnoreRoute("{controller}/{resource}.axd/{*pathInfo}");

This might have been the problem for some users who had to resort to changing the Chart.ImageStorageMode property.

Answer 5

Please Add it in webconfig

add verb="GET,HEAD" path="ChartImg.axd" type="System.Web.UI.DataVisualization.Charting.ChartHttpHandler, System.Web.DataVisualization, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"

Thanks

Basanth

Answer 6

I posted a way I fixed this problem on the MSDN forum:

Well I still don't know why I was getting the exception but I seem to have found a workaround. I did an experiment where I took the supposed offending web.config and copied it to a new project where I added a new web form and chart control and the chart control rendered fine with the "UseHttpHandler" option. This led me to believe that it wasn't actually the web.config that was the problem in my case, so I went back to the original project and added a chart to another web form as an experiment, and it worked! Even more surprising was that after that I went to the offending page and it worked too! Then I took the new chart off the other page and checked the original offending page and it was broken again. Then I found out if I put a chart control on any page before the offending page, it would work, otherwise it threw the exception. These controls are so cool though that I didn't have a problem finding another page to put one on in the path of the offending page :)

This fixed the problem but if anyone has any theory why I'd be interested...maybe a bug?