Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

The number of requests for "XXXServer\XXXUser" has exceeded the maximum number allowed for a single user. Expand / Collapse
Author
Message
Posted Monday, October 15, 2007 3:36 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Sunday, January 26, 2014 9:53 AM
Points: 2, Visits: 32
I have created a local user on Report Server Computer and the user has the administrative rights.
When i try to connect Report Server (http://xxx.xxx.xxx.xxx/reportserver) with this user's credantials. (ReportServer directory security is set -only- to Basic Authentication. ).
I get the following error.

Reporting Services Error
--------------------------------------------------------------------------------

The number of requests for "XXXServer\XXXUser" has exceeded the maximum number allowed for a single user.
--------------------------------------------------------------------------------
SQL Server Reporting Services

Then i try to login using a different user with administrative rights on the machine, i can logon successfully.
The system is up for a month but this problem occured today?!? What could be the problem?!?
Post #410741
Posted Tuesday, October 16, 2007 9:47 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Monday, August 25, 2014 5:00 PM
Points: 959, Visits: 419
You might want to check to see if you are limiting the number of connections:

In IIS, go to the properties for the web site that hosts the reports - by default - default web site, go to the performance tab - verify web site connections is set to unlimited or that the limited number meets your needs.

Also - you might want to try NOT using Basic Authentication.

Good luck.
-Megan



Post #411367
Posted Thursday, December 6, 2007 3:25 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Friday, July 26, 2013 12:43 AM
Points: 54, Visits: 33
Hi,

I am also facing similar problem... i have checked the performance tab as mentioned earlier. But still the issues persists.

Please help!!
Post #430109
Posted Thursday, December 6, 2007 8:26 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 9:30 PM
Points: 7,138, Visits: 15,185
There are settings in the rsreportserver.config file that might help with that...BOL mentions looking for this setting:


MaxActiveReqForOneUser
Specifies the maximum number of simultaneous and in-progress connections that a single user can open to the report server. Once the limit is reached, further connection requests from the user are denied. This configuration setting is intended to mitigate a denial of service attack. Valid values are 0 to a maximum integer. The default is 20.

Note that most requests process very quickly so it is unlikely that a single user will have more than 20 open connections at any given time. If users are opening more than 15 process-intensive reports at the same time, you might need to increase this value.

This setting is ignored for report servers that run in SharePoint integrated mode. For more information about server modes, see Deployment Modes for Reporting Services.



----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
Post #430226
Posted Thursday, December 20, 2007 4:15 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Friday, July 26, 2013 12:43 AM
Points: 54, Visits: 33
Hi, I got the answer for this. Try this, it may work for you also.

When you browse the Report Manager, you're getting the above error message.

To resolve this issue, Do the following,

Search for the key

---- MaxActiveReqForOneUser in RSREPORTSERVER.config file under the ReportServer directory,



And set the value to 400 that would look like this







Save the rsreportserver.config file and restart the IIS





Specifies the maximum number of simultaneous and in-progress connections that a single user can open to Report Manager. Once the limit is reached, further connection requests from the user are denied. This configuration setting is intended to mitigate a denial of service attack.

Valid values are 0 to a maximum integer. 0 indicates no limit on the number of connections. The default is 20.

Note that most requests process very quickly so it is unlikely that a single user will have more than 20 open connections at any given time. If users are opening more than 15 process-intensive reports at the same time, you might need to increase this value.


Post #435131
Posted Sunday, March 2, 2008 9:18 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, May 12, 2011 10:34 AM
Points: 5, Visits: 49
Hi All
i did the same changes recommended here(changed MaxActiveReqForOneUser to 0). it worked for few days now again the same error had occured. Now the things i can see is even Analysis services becomes unavailable.(can't get accessed from management studio too.)The state of the service is abnormal (can't say it is running or stopped).

The server is quite OK around 300 GB free space availabe with 4 GB Ram.
The size of OLAP cube is around 5GB.

Can anybody help me out on this?
Post #462972
Posted Wednesday, March 5, 2008 7:38 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 9:40 PM
Points: 1,231, Visits: 6,632
review where you set max active requests.
0 ( no limit ) will allow you to possibly overload the server.
Default was 20 - try 40 as suggested
GE
Post #464432
Posted Saturday, March 8, 2008 2:15 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, May 12, 2011 10:34 AM
Points: 5, Visits: 49
Thanks Greg,

The reason behind keeping MaxActiveReqForOneUser=0 is because i have seen connections getting exceeded beyond 105 (from performance monitor)during working hours. May be exceeding more after that.

But still, i will try to set to some minimum may be around 150.



Post #466257
Posted Wednesday, May 28, 2008 8:34 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Sunday, January 26, 2014 9:53 AM
Points: 2, Visits: 32
MaxActiveReqForOneUser is the solution that worked for me.
Also try not to set this value to '0', if you are not managing your connections. With too many requests server can be overloaded and crash (done that been there).
Post #507713
Posted Monday, July 16, 2012 5:21 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, March 17, 2014 5:35 AM
Points: 16, Visits: 103
found userful, i have encountered this problem today and fixed it based on this thread. thanks a lot
Post #1330033
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse