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
Thank you for your instructions how to solve my problem. I changed the session <sessionState mode="InProc"> web.config to <sessionState mode="SQLServer" ......> and made propriete settings on SQL Server where we store our data and everything works just perfectly .
I was having a similar problem here when I would dynamically load two instances of a web control containing an UltraChart (called "LineChart1") and tried to use them to render two different line charts via the "RenderControl" method. The second chart would show up fine but the first one would always show "access denied". I tried using the session state service and a few other things but nothing helped.
I noticed that the URL for the chart image pipe had the same "base" name for both images. For example, the first chart would be:
http://localhost:1865/Website/ImagePipe.aspx?ChartID=LineChart1_Base&KxRx=0x06428
and the second chart would be:
http://localhost:1865/Website/ImagePipe.aspx?ChartID=LineChart1_Base&KxRx=0x08767
Note that the "ChartID" is the same in both cases. I had a theory that maybe the system wouldn't keep the first image in session once the second one was rendered if the base name was the same, so I created a property in our custom control that allowed me to set the "ID" field on the UltraChart to "LineChart2" for the second chart. That changed the second URL's ChartID to "LineChart2_Base" and then both images showed up fine. Just thought this might help someone else in a similar situation.
Thanks tolchinj, but my charts have differents IDs. I noticed that if you call each single chart directly, using the chart url from the browser's address bar, the problem won't not show up(I try to reload the page again and again). But if you load more than one chart simultaneously, I encounter the "access denied message" sometimes. In my opinion I don't think it's a "session state" related issue, but I will try to make some test..
i believe there was one fix i made since the 6.3 release to prevent concurrency/timing issues with the ImagePipe. if you haven't already, try testing this with the latest 6.3 hotfix.
Thanks David, I think is the right answer.
I've tried the 6.3 hotfix and it seems to work. The error seems not to show anymore.
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.