Hi all, i'm using infragistics ver 6.3 to generate webcharts(Infragistics2.WebUI.UltraWebChart.v6.3,
Version=6.3.20063.53 and UltraChart.DeploymentScenario.Scenario="Session"), and sometimes(extremely random), i get
the infamous "access denied" error image.
Then after a search, I read this kb:http://devcenter.infragistics.com/Support/KnowledgeBaseArticle.aspx?ArticleID=2041
I've a mixed scenario with a pure asp page with four charts(generate them by calling aspx pages obiouvsly).Then I try to turn every caching stuff off.
On pure asp page:response.expires = -1500 response.AddHeader "PRAGMA", "NO-CACHE" response.CacheControl = "PRIVATE"response.Buffer=False
On asp.net pages(chart generating pages):protected void Page_Load(object sender, System.EventArgs e) { Response.Expires = 0; Response.Cache.SetNoStore(); Response.AppendHeader("Pragma", "no-cache"); Response.Cache.SetCacheability(HttpCacheability.NoCache);
But still no luck...
Any suggestion?
Here are some addictional question:
1)There is a way to inercept the "access denied image" via javascript before diplaying it?I've seen that the output of a "good generated chart" is nearly the same of a "bad generated chart"i.e.<img style=''src='ImagePipe.aspx?ChartID=mychart_Base&KxRx=0x04813>
2)There is a way to change the "acess denied" image with some sort of custom image/custom text?
3)The last version of UltraWebChart(8.1.20081.1000) may solve the problem?
Thanks in advance
Hello,
I've seen this error message often while developing. I am not 100% sure that this covers your case, but could you please try disabling Indexing Services for the folder in your web-application?
You can take a look at this Microsoft KB article "PRB: Access Denied Error When You Make Code Modifications with Index Services Running" for more information and step-by-step instructions how to proceed.
http://support.microsoft.com/kb/329065
Hope this helps.
I have the same Problem. I am using Infragistics ver 5.1 to generate Webcharts (UltraChart.DeploymentScenario.Scenario="Session"), and sometimes , i get "Access denied" error Image. I try to apply http://support.microsoft.com/kb/329065 , then I disabling Indexing Services at all, but The Problem continue. This Problem is only on Windows Server 2003, it is OK on Windows XP. Can you help me, please?
Thanks in advance.
Oldrich Samolej
I've also found the following forum discussion in forums.asp.net regarding this problem and some approaches there seem to have resolved the problem.
http://forums.asp.net/p/583241/583682.aspx
Could you please try what is suggested there and let us know if this helps?
Also, please check the following KB article in our Dev Center:
http://devcenter.infragistics.com/Support/KnowledgeBaseArticle.Aspx?ArticleID=5010
Here is an explanation of what happens in a Session-Based Deployment Scenario:
This Deployment Scenario has issues when Server Page Caching is on; the result can be an occasional "Access Denied" message, where a browser refresh is needed. Please note that under most circumstances, the "Access Denied" message can only be seen during debugging, when the web application is built and launched in Internet Explorer; users of the web application will not see it, unless server caching is turned on for the pag
Thank you for your prompt reply.
I try this steps and still no luck:
1. I disabled Indexing Services at all.
2. I seted "HTTP Headers" - "Expire immediately" for my Web Application in IIS.
3. I seted on asp.net pages (chart generating pages):
Response.Expires = 0;
Response.Cache.SetNoStore();
Response.Cache.SetRevalidation(HttpCacheRevalidation.AllCaches);
Response.Cache.SetCacheability(HttpCacheability.NoCache);
Response.Cache.SetNoServerCaching();
Response.Cache.SetExpires(DateTime.Now);
Response.AppendHeader("Pragma", "no-cache");
http://localhost/OO/ImagePipe.aspx
I not see "Access Denied" only during debugging. Users of the web Application see this infamous Image too, but not on each occasion. As I wrote, I have this problem only on Windows Server 2003.
No way, the problem still persists. I got the problem both on win2003 and win2000.
Here's a little workaround for medium-high-skilled people. Not applicable for each scenario, but hope it's useful for someone.
You got a chart generating page called "mychart.aspx" like this:
<igchart:UltraChart id="mychart" runat="server" Width="400px" Height="270px" ....
So if you use ajax to call that page, you obtain an image. If you got the "access denied" image you got a 100pixel x 100pixel image, instead of a 400pixel x 270pixel image. Here's the trick: if the image is 100x100 reload(recall mychart.aspx) immediatly.
It works for me. Hope someone find the REAL solution.
it's hard to tell what is failing. if you want to try something to diagnose the problem, you could set up a test that puts an object like a DataSet into the session, then requests it later from another page.
at some point this object might be cleared from memory; for example if ASP.NET's memory usage gets to a certain point, the process will restart (this is to prevent memory leaks) and everything in the process memory will be gone.
considering the ineffectiveness of all the proposed solutions, I would try to implement vemistemi's workaround: http://forums.infragistics.com/forums/p/5477/26710.aspx#26710
I tried all the solutions and the only working one is to use the file system deployment scenario. It's not acceptable but it is my only solution.
there are many suggestions given in this thread to solve the problem, so you might want to look through and try some of the proposed solutions. but most importantly, make sure you are using the latest available hotfix for 7.2.
Are you able to fix the issue? I am getting the same error. I am using 7.2 verison.
ASP.NET has a feature where if memory usage gets too high for a web application, the worker process restarts itself. This is the framework's way of protecting against memory leaks. In this event, your session state might be lost at that moment; but it should be very rare. That is one possible reason for this problem, but it's just a guess.
Make sure you install the service pack for the version of the .NET Framework you are using on the web server; that might also resolve the problem.
I noticed you were using a hotfix of 7.2, but one that's almost a year old (7.2.20072.1063), so maybe try upgrading to a later hotfix. After looking at the source code changes in the past year, I don't think this is the solution, but it might be worth a try.