Welcome Guest Search | Active Topics | Sign In | Register

Essential Objects Product Support Forum » All Products » Support » Invalid Viewstate , ScriptResource.axd

Invalid Viewstate , ScriptResource.axd Options
Previous Topic · Next Topic
Jay
Posted: Monday, March 14, 2011 8:49:14 AM
Rank: Member
Groups: Member

Joined: 8/31/2007
Posts: 9
Hi,

I am getting an Invalid Viewstate error from one of our web applications using EO controls.
( All other websites Not using Essential object controls are working fine)

It was working fine for a long time and it started recently.

We did not make any changes to the application recently. So I am not sure why it is happening all of a sudden. Only thing I can think of is that we moved to IE 8 from IE 6.


Any help would be appreciated.


Thanks,
Jay


Error message : ScriptResource.axd

Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 3/9/2011 8:56:11 AM
Event time (UTC): 3/9/2011 1:56:11 PM
Event ID: 76359ae1ed6b47a681e4bff94cf15d4f
Event sequence: 651
Event occurrence: 2
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/904315713/Root/AuditApp-2-129441459880305000
Trust level: Full
Application Virtual Path: /AuditApp
Application Path: <app path>

Process information:
Process ID: 4232
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE

Exception information:
Exception type: HttpException
Exception message: Invalid viewstate.

Request information:
Request URL: http://<servername>/AuditApp/ScriptResource.axd?d=MSdnNdhBDePNzbaUFD-mbCkbXoXWFpWQBQyXh04jqGmhAP605iRY5mKdGMTtA5zDwBq5oS_unz-ZHsvwte3fKr_7xHt8BZgIaa_RLSs-H8ruIYqyFypress=
Request path: /AuditApp/ScriptResource.axd
User host address: xxx.xx.x.xx
User: <userName >
Is authenticated: True
Authentication Type: Negotiate
Thread account name: NT AUTHORITY\NETWORK SERVICE

Thread information:
Thread ID: 6
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace: at System.Web.UI.Page.DecryptStringWithIV(String s, IVType ivType)
at System.Web.UI.Page.DecryptString(String s)
at System.Web.Handlers.ScriptResourceHandler.DecryptParameter(NameValueCollection queryString)
at System.Web.Handlers.ScriptResourceHandler.ProcessRequestInternal(HttpResponse response, NameValueCollection queryString, VirtualFileReader fileReader)
at System.Web.Handlers.ScriptResourceHandler.ProcessRequest(HttpContext context)
at System.Web.Handlers.ScriptResourceHandler.System.Web.IHttpHandler.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Back to top
 
eo_support
Posted: Monday, March 14, 2011 9:31:18 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,194
Hi,

Most of the time this problem occurs when some rogue web crawlers/spammers trying to automatically post data through your Web site. For example, we get that a lot from our contact us page when those programs try to send junk through that page. Sometimes legitimate but low quality web crawlers will cause that error as well but it is relatively rare because legitimate web crawlers almost never do post backs. In any case unless you are sure the error comes from human, then I would not worry about it at all.

Thanks!
Back to top
 
Jay
Posted: Monday, March 14, 2011 9:47:41 AM
Rank: Member
Groups: Member

Joined: 8/31/2007
Posts: 9
Hi,
I do not think it has anything to do with web crawlers, because it an intranet website?
When this error occurs, user will be kicked out and they have to refresh/reload the page to get in again.
It is making a lot of headache.

Do you think if I cache the ScriptResource.axd page, will remove this error?
I use .net 2008 and IE 8.
This is the docu type I use in the page.
<!DOCTYPE html PUBLIC "-//W3C//DTD html 4.0 Transitional//EN">
And I use <add type="Menu" version="5.0" /> , I guess the menucontrol of version 5 of EO
Please let me know if you need anyother information.
Thanks.
Back to top
 
eo_support
Posted: Monday, March 14, 2011 9:58:37 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,194
Hi,

The cache could cause this problem but it should go away over time as caches are getting updated.

You have a very old version of our product that does not officially support IE 8 (IE 8 was released much later than your version), so you can try to switch to the latest version and see if it changes anything. I do not believe this has anything to do with us though. Both ViewState and ScriptResource are handled by ASP.NET. We use it the same as every other server controls and we don't tamper with it as every other server controls. So there is no reason why our controls would cause lower level view state encryption failure.

Thanks
Back to top
 
Jay
Posted: Monday, March 14, 2011 10:11:13 AM
Rank: Member
Groups: Member

Joined: 8/31/2007
Posts: 9
Thanks for the prompt response!

I read that, when you get a app domain recycle, the key changes. the browser is caching a page, but the *.axd are not being cached,
so when fetched the parameters can not be decoded because of the use of the old key.

But I am not sure how to cache the axd page.Can you please give me some sample code, if you how how to do it.
( or may be I need fix the machine key in the web config?)
Thank you.
Back to top
 
eo_support
Posted: Monday, March 14, 2011 10:17:29 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,194
Jay wrote:
Thanks for the prompt response!

I read that, when you get a app domain recycle, the key changes. the browser is caching a page, but the *.axd are not being cached,
so when fetched the parameters can not be decoded because of the use of the old key.

This makes a lot of sense and can be very much the root of your problem. An easy fix is to put a fixed machineKey in your web.config. You will want to search online to find out how.


Jay wrote:
But I am not sure how to cache the axd page.Can you please give me some sample code, if you how how to do it.
( or may be I need fix the machine key in the web config?)

Yes. That's probably what you need to do. However you are pushing over the support boundary here. We support our product only (in fact even the one year support period for your purchase has already expired). We do not provide support on how to configure your machineKey or how to troubleshoot view state problem because those are general ASP.NET issues.

Thanks
Back to top
 
Jay
Posted: Monday, March 14, 2011 2:41:38 PM
Rank: Member
Groups: Member

Joined: 8/31/2007
Posts: 9
All right. Sorry about that, for pushing over the support boundary.
I saw that EO controls sent out a lot of javascripts and thought that may be making some issues with the ScriptResource.axd decoding. I was thinking of removing the EO - menu and other controls one at a time and was thinking of adding .net controls for testing.

Now I will try the fixed machine key and hopefully that will fix the issue.
Thank you very much for your help!
Jay
Back to top
 


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.