I came accross this post, which seems to be the issue I am having, my question is how do you do the following to fix the problem?
You will need to be sure that the chart httphandler is served by the same machine, which served the page.
You will need to be sure that the chart httphandler is served by the same machine, which served the page.
Posted on Feb 17, 2010
Hi mukund,
This is my reply to the bug report you have open:
The httphandler registration is different for IIS6 and IIS7. For IIS7 you need to add an additional registration in <system.webServer> section in your web.config file. You can fine more details in this help topic. We recommend removing the chart httphandler registration completely and using the link in the VisualStudio smart tag (check the second image in this help topic) -- it will register the httphandler correctly for both IIS6 and IIS7.
As for the web farm -- RadChart will work in web farm environment under certain conditions. It would be an issue if the page is served and therefore the chart image is generated by one machine and the next request for the image itself is served by another machine. Then this second machine will not be able to find the image. You will need to be sure that the chart httphandler is served by the same machine, which served the page.
Please, keep the correspondence in a single thread, so it easier for both you and us to follow it. Thanks.
Sincerely,
Ves
the Telerik team
This is my reply to the bug report you have open:
The httphandler registration is different for IIS6 and IIS7. For IIS7 you need to add an additional registration in <system.webServer> section in your web.config file. You can fine more details in this help topic. We recommend removing the chart httphandler registration completely and using the link in the VisualStudio smart tag (check the second image in this help topic) -- it will register the httphandler correctly for both IIS6 and IIS7.
As for the web farm -- RadChart will work in web farm environment under certain conditions. It would be an issue if the page is served and therefore the chart image is generated by one machine and the next request for the image itself is served by another machine. Then this second machine will not be able to find the image. You will need to be sure that the chart httphandler is served by the same machine, which served the page.
Please, keep the correspondence in a single thread, so it easier for both you and us to follow it. Thanks.
Sincerely,
Ves
the Telerik team
1 Answer, 1 is accepted
0
Hello Randy,
This is usually referred to as Sticky Sessions and it would be specific for your load balancer. You can check this blog post for more details. An alternative suggestion here would be to implement State server or SQL server session state mode.
All the best,
Ves
the Telerik team
This is usually referred to as Sticky Sessions and it would be specific for your load balancer. You can check this blog post for more details. An alternative suggestion here would be to implement State server or SQL server session state mode.
All the best,
Ves
the Telerik team
Thank you for being the most amazing .NET community! Your unfailing support is what helps us charge forward! We'd appreciate your vote for Telerik in this year's DevProConnections Awards. We are competing in mind-blowing 20 categories and every vote counts! VOTE for Telerik NOW >>