September 6, 2011 at 8:48 am
One of our reports ssrs2008r2 takes more than 10 seconds to finish and for 1 person they get this message after about 10 seconds
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; GTB7.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET4.0C; .NET4.0E)
Timestamp: Tue, 6 Sep 2011 10:20:10 UTC
Message: Sys.WebForms.PageRequestManagerServerErrorException: An unknown error occurred while processing the request on the server. The status code returned from the server was: 12002
Line: 5
Char: 62099
Code: 0
If I run this report on his pc as me, it works fine, and if he runs as himself from my pc it works fine, so its just as him from his pc, so we've ruled out versions.
We've cleared out internet files etc. and reset IE, the only task left is to recreate his enter profile, but this is a big task if we need to do this for all other users in the future without knowing why or when it will happen again.
The error is just displayed by the icon and the word Done in the bottom left hand corner, so no graceful error message.
When it runs it takes about 30 seconds to run, but the fail happens after about 10 seconds for this one person.
We don't want to just recreate the profile, without knowing if this will help or not, as then we won't know if the other 100+ users will experience the same issue at some point.
I think 12002 is a timeout error number, but when the report runs it takes 2-3 times longer to run than when it fails.
This is from an XP machine, IE 8.
Any ideas?
September 6, 2011 at 9:02 am
Just wondering where the Mozilla reference is coming from - could Firefox be involved?
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
September 6, 2011 at 9:03 am
Hi Phil,
No its definetly IE 8. 🙂
September 29, 2011 at 10:38 am
Having a similar issue - a report working on Firefox, givig the same 12002 status code on IE.
(I love IE, today I had all kind of problems with IE with All versions from 7 to 9:w00t:)
September 29, 2011 at 10:48 am
There could be a memory leak being revealed when executing this report.
Other things you could try involve fixing the queries for the datasets to prevent parameter sniffing. Also, try optimizing SSRS config settings.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
September 29, 2011 at 10:54 am
Thanks a lot Jason for your reply, can you please tell me more about optimizing SSRS config settings. and how this might help in a problem that "sounds" browser (and version) related?
September 29, 2011 at 11:32 am
Your browser is throwing an error for 1 of 2 reasons - memory leak or the query takes too long.
By fixing your datasets to eliminate parameter sniffing you are helping to eliminate a possible cause for the timeout.
By optimizing SSRS settings, you can help the report process faster which will also help to eliminate a possible cause for the timeout.
If neither of those things helps - then I would be more apt to say that it is a memory leak. You could also try the report in several other browsers to test for the memory leak.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
October 3, 2011 at 8:53 am
So We tried to do what you proposed Jason and enhanced the stored procedure to be faster and faster, each time we enhance it, we get one user on one machine to run the report on IE (before, they were getting the 12002 exception), till all the users are running it with no problems (till now)
I'm wondering why a browser triggers such exception while another browser doesn't? Are there any browser specific timeout settings?
Thanks,
John
October 3, 2011 at 9:07 am
This wasn't browser or memory leak or performance related as such as any other user could use the same browser the same report report on the same pc and it worked fine, and that person could run the report on another pc with no problems.
There was something wrong in the profile for 1 person on 1 pc.
We have rebuilt the laptop and the problem has gone away but we don't know exactly what was wrong and if it would happen again.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply