NLB Server Affinity dependency with ReportViewer and SSRS RemoteServer mode - by nonnb

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 734486 Comments
Status Closed Workarounds
Type Bug Repros 2
Opened 3/30/2012 3:01:39 AM
Access Restriction Public


We seem to have picked up a latent issue in the VS 2010 ReportViewer Webforms control (v10) when the NLB cluster affinity setting on our IIS 6 web server was changed from "Single" affinity to "None.

It seems that when the RV control renders using Ajax, that the Server assumes that the browser control will return to the same server during rendering (which will not necessarily be the case with NLB without affinity). (also it is apparant that the RV control uses another state tracking mechanism other than Session State - we use SQL Session state on the application in which the Control is used).

(The application has been in a production environment for 2 years without this issue. And the issue doesn't occur if a) we re-enable affinity on the NLB cluster or b) Instruct users to directly access one of the indivdual servers in the NLB)

Applicable settings on the control are

ProcessingMode = Microsoft.Reporting.WebForms.ProcessingMode.Remote;
AsyncRendering = true;
We also use SQL Session state.

Instead of displaying a report, users receive the following javascript errors and the control doesn't render any content.

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; Trident/4.0; SLCC1; .NET CLR 2.0.50727; .NET CLR 1.1.4322; .NET CLR 3.5.21022; .NET CLR 3.5.30729; .NET CLR 3.0.30618; MS-RTC LM 8; InfoPath.3; .NET4.0C; .NET4.0E)
Timestamp: Fri, 30 Mar 2012 09:29:32 UTC

Message: Sys.InvalidOperationException: Type Sys.UI._Timer has already been registered. The type may be defined multiple times or the script file that defines it may have already been loaded. A possible cause is a change of settings during a partial update.
Line: 1717
Char: 42
Code: 0
URI: http://myserver/myapp/ScriptResource.axd?d=mbNzvpNkDq3Jde4Nr8uCF6mu1W-z3r3R0xRgq2UWsdj4eDfPUVuQdDYSHeKqGBdAcI__KNmPE5cOxD5iMTw2pMISCyOdBkiaGPwKM7-UJiUL1JCYVCX2y1JxkCGW_VRsIbV4WWcIl5wc8-vrL4Q0fx7qcfS8d5h3eVJ4R-fl3DPWWCwZ0&t=ffffffffc7040a5c

Message: Sys.ScriptLoadFailedException: The script '/myApp/ScriptResource.axd?d=zIwq3H9TfZpVP2jrtOYLZJK7knZ4dYRnF8jieeZ0WV6cAW_sAVjbLL-M_mFO20YL6UeRpXRFCXWAe1PawNn6r7TxmEjGZLUys1lrcICU4G7UFj8ZnRV9HNNYMGuh7XZMyv48_0ZYA1VJy7Qf7kIAFRu3stao2NUiByAw20xTrbMhHDok0&t=14af6a58' failed to load. Check for:
 Inaccessible path.
 Script errors. (IE) Enable 'Display a notification about every script error' under advanced settings.
 Missing call to Sys.Application.notifyScriptLoaded().
Line: 1266
Char: 13
Code: 0
URI: http://myserver/myapp/ScriptResource.axd?d=ZlTwRV65K_sYZcdp_0XXaPPwnNzuIGj6dHQl6KSgbflmAnHeDOj0Q6mPTXSGu0tIMdipb4gcf6Rud5_3SV_iS9PDdPAur6CsOhYHcLqcnzXhkOi1c-44AXkNNp1AhhsC_zT_b5e8LRoJT9aJvIDopQlUy5lrCdrKYmdBHOytlNW4GO0lYjSHiL42t9XP7IpsnuAx0g2&t=ffffffffc7040a5c
Sign in to post a comment.
Posted by Baskar Purushothaman on 7/19/2012 at 8:22 AM
Hi Lukasz

Do you guys have any solution for this problem. I have been waiting for past 4 months.
Posted by nonnb on 4/27/2012 at 9:50 AM
Hi Lukasz

As I pointed out in the issue report above, we ARE using SQL Sessions, so the ReportViewer server control is using a mechanism other than Session State for script management tracking, which seems to be the root cause of the issue.

Also, while you are at it, there is an additional bug in the way ReportViewer uses SessionState. Full details are here:


Posted by Microsoft on 4/27/2012 at 9:03 AM
Thank you for filing this issue. The issue is that the Viewer requires session state. The resolution is to use a Session State mode that makes the session state available to all nodes in the scale-out (NLB) deployment. Please see

Posted by jagadeeshkoneti on 4/15/2012 at 9:38 PM
In production environment, facing the same issue. Please specify any workarounds. Thanks in advance.
Posted by MS-Moderator07 [Feedback Moderator] on 4/1/2012 at 6:59 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Posted by MS-Moderator01 on 3/30/2012 at 3:52 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(