Resolution 1:
Refer to the following article for the resolution:
2608328 When you click on the Executive Center in Business Portal, the error “The Request Failed with HTTP Status 401: Unauthorized” appears in the SQL Server Reporting Services web parts.
Resolution 2:Refer to the SQL Server Reporting Services Guide for information regarding the deployment of the Microsoft SQL Server Reporting Services reports for Microsoft Dynamics GP. You can download the SQL Server Reporting Services Guide at the link below:
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=18981
Resolution 3:
If you are using SSRS in Native Mode, use the Report Manager site to add or verify the user's access to the reports. If you've deployed the SSRS reports in SharePoint Integrated Mode, use SharePoint security to verify that the user has access to the report library site. For more information on SSRS permissions review Chapter 7 of the SQL Server Reportings Services Guide at the link below:
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=18981Resolution 4:Refer to the steps below to create a SQL Server login for a domain user:
1. Log on to the server where SQL Server is installed.
2. Click Start, click All Programs, point to Microsoft SQL Server 2008 (or 2008 R2) and then click SQL Server Management Studio.
3. Connect to the instance of SQL Server where the Microsoft Dynamics GP databases are located.
4. Click to expand Security, click to expand Logins in the Object Explorer.
5. Right-click on the Logins folder and click New Login...
6. In the Login Name field specify the domain user from the error message in the format of domainname\username
7. Click the User Mapping tab on the left to assign the user access to the appropriate Microsoft Dynamics GP databases. Refer to Chapter 7 in the above SQL Server Reporting Service Guide for details on company and role assignment.
Resolution 5:To verify the database assignment of the SQL Server login given in the error you can use the following steps:
1. Log on to the server where SQL Server is installed.
2. Click Start, click All Programs, point to Microsoft SQL Server 2008 (or 2008 R2) and then click SQL Server Management Studio.
3. Connect to the instance of SQL Server where the Microsoft Dynamics GP databases are located.
4. Click to expand Security, click to expand Logins in the Object Explorer.
5. Right-click the SQL Server login for the domain user given in the error message and click Properties.
6. Click the User Mapping tab on the left.
7. All logins that need to run the Microsoft Dynamics GP SSRS reports must be mapped to the system (DYNAMICS) database as well as any company database they intend to report against. Refer to Chapter 7 of the SQL Server Reporting Services Guide below for more information on user security.
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=189818. Click OK and have the user run the report again.
Resolution 6:
To change the database role assignment for your SQL Server logins you can review the following:
1. Log on to the server where SQL Server is installed.
2. Click Start, click All Programs, point to Microsoft SQL Server 2008 (or 2008 R2) and then click SQL Server Management Studio.
3. Connect to the instance of SQL Server where the Microsoft Dynamics GP databases are located.
4. Click to expand Security, click to expand Logins in the Object Explorer.
5. Right-click the SQL Server login for the domain user given in the error message and click Properties.
6. Click the User Mapping tab on the left.
7. Click one of the Microsoft Dynamics GP databases the login has access to (e.g. DYNAMICS or TWO).
8. Review the selection in the 'Database role membership for 'xxxxx' section on the bottom of this database for each database. A list of what database roles give access to what SSRS reports can be found in the MDGP11R2_SRS_Report_Roles.pdf file on page 50 of the of the SQL Server Reporting Services Guide. Click the link below to download the SQL Server Reporting Services Guide:
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=189819. Click OK and run the report again.