401 error when calling REST_V2 that does not have obvious explanation

Problem Description:

If you are getting an HTTP 401 error from calling REST_V2 that cannot be explained by normal thorectical analysis.  The problem may be else where unexpected.

For example, you are getting an HTTP 401 error when using ROLE_AMINISTRATOR with a root user to login but you cannot duplicate the problem on a default installation.

Solution:

For this particular situation, turned out there is an overflow in the number of organization [2100] on the jasperserver when using MSSQL database as repository.  You might also see an error like this,

Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The incoming request has too many parameters. The server supports a maximum of 2100 parameters. Reduce the number of parameters and resend the request.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:262)

Jasperserver issues the MSSQL call with the number of parameters based on the number of organizations.  However, MSSQL has a limit of 2100 and therefore the REST_V2 call fails.  

Currently, as of v8x, there is no patch fix for this issue.  You can delete unused organizations to get it down to below 2100 or migrate the repository to a different database type.