Any ideas what causes the following error message:
Sys.WebForms.PageRequestManagerServerErrorException: An unknown error occurred while processing the request on the server. The status code is:
I receive one of 4 error numbers: 12019 12130 12031 or 12152
I believe it might have to do with a content switch but not sure. Any help would be greatly appreciated.
I am getting the same Error Message with error number :12031...
Any suggestion ?
Hi,
Please refer to this:http://support.microsoft.com/kb/193625
The issue seems to be with the WinInet api, may be you can try to access it with another browser to see if it works.
Hi,
it is true that it is about Wininet api.i can access my page and can work with Another browsers but with IE 7.0 OR 6.0 i come accross with this error.(in I.E The error code is 404)..What is ur advice to solve this problem?When i launch the project without connecting to source safe,it works but after i connect to sourcesafe,this problem occurs..This error is very annoying.What should i do?Thank u very much for ur Help.(My problem doesnt depend on Data Intesivity or row count)
Raymond Wen - MSFT:
Hi, Please refer to this:http://support.microsoft.com/kb/193625
The issue seems to be with the WinInet api, may be you can try to access it with another browser to see if it works.
So, seeing this error on a partial-page update (UpdatePanel Async postback) means that the application I'm developing is not going to work with Internet Explorer? Or is this just a fluke that will go away on a restart / deployment scenario / etc.
I'm getting this one:
12019 ERROR_INTERNET_INCORRECT_HANDLE_STATE
The requested operation cannot be carried out because the handle supplied is not in the correct state.
Hi
we had the same problem on our live-system. It was caused by SSL-Connection. If you have SSL, try turning off Keep Alive for IE.
hth
Just so you know, we did find one possible cause of this problem.
It seems to crop up sometimes if you are using IE6 supplied with MultipleIEs package.
http://forums.asp.net/t/1123365.aspx
No comments:
Post a Comment