|
 |
 |
 |
 |
Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms
of Use |
Trademarks
Article ID: 936118 - Last Review: May 1, 2007 - Revision: 1.1 Error message when you try to run a report in Systems Management Server (SMS) 2003: "Cannot set application role 'webreport_approle' because it does not exist or the password is incorrect"Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base: 256986Â
(http://kbalertz.com/Feedback.aspx?kbNumber=256986/
)
Description of the Microsoft Windows registry When you try to run a report in Microsoft Systems Management Server (SMS) 2003, you receive one of the following error messages: Error message 1An error occurred when the report was run. The details are as follows:
Cannot set application role 'webreport_approle' because it does not exist or the password is incorrect.
Error Number: -2147217900
Source: Microsoft OLE DB Provider for SQL Server
Native Error: 15161 Error message 2An error occurred when the report was run. The details are as follows:
The specified schema name "webreport_approle" either does not exist or you do not have permission to use it.
Error Number: -2147217900
Source: Microsoft OLE DB Provider for SQL Server
Native Error: 2760 This problem occurs if either of the following conditions is true: - SMS Reporting has an incorrect password for the webreport_approle database role.
- The webreport_approle role is not present in SQL Server.
To determine whether the webreport_approle role is present, follow these steps: - Start the SQL Server Management Studio program.
- Expand Databases, expand the SMS 2003 site database, and then expand Security.
- Expand Roles, and then click Application Roles.
- The webreport_approle object appears in the details pane if this object is present.
Note These steps describe how to locate the webreport_approle role by using the Microsoft SQL Server 2005 SQL Server Management Studio program. If you are running an earlier version of SQL Server, modify these steps as appropriate for your situation. To resolve this problem, use one of the following methods, as appropriate for your situation. Method 1: The password is incorrect for the webreport_approle roleIf the password has been changed on the webreport_approle role in SQL Server, you must perform a SMS 2003 site reset operation to synchronize the password.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
828366Â
(http://kbalertz.com/Feedback.aspx?kbNumber=828366/
)
How to use the site reset functionality in Systems Management Server 2003
Method 2: The webreport_approle role is missingWarning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk. If the webreport_approle does not exist, you must reinstall SMS Reporting. To do this, follow these steps: - Export any custom reports by using the Export Object Wizard in the SMS Administrator Console. To start the Export Objects Wizard, follow these steps:
- Start the SMS Administrator Console.
- Expand Site Database (siteName - organizationName), and then expand Reporting.
- Right-click Reports, point to All Tasks, and then click Export Objects.
Note You do not have to export the default reports. The default reports are re-created when you install SMS Reporting. - Remove the reporting point site system role from each server that acts as a reporting point. To do this, follow these steps:
- Start the SMS Administrator Console.
- Expand Site Database (siteName - organizationName), expand Site Hierarchy, and then expand the site.
- Expand Site Settings, and then click Site Systems.
- In the details pane, right-click a server, and then click Properties.
- In the \\ServerName Site System Properties dialog box, click the Reporting Point tab.
- Click to clear the Use this site system as a reporting point check box, and then click OK.
- Confirm that both of the following objects have been removed:
- Add the reporting point site system role to each server, as appropriate for your situation. To do this, follow these steps:
- Start the SMS Administrator Console.
- Expand Site Database (siteName - organizationName), expand Site Hierarchy, and then expand the site.
- Expand Site Settings, and then click Site Systems.
- In the details pane, right-click a server, and then click Properties.
- In the \\ServerName Site System Properties dialog box, click the Reporting Point tab.
- Click to select the Use this site system as a reporting point check box, and then click OK.
- Import the custom reports that you exported in step 1. To start the Import Objects Wizard, follow these steps:
- Start the SMS Administrator Console.
- Expand Site Database (siteName - organizationName), and then expand Reporting.
- Right-click Reports, point to All Tasks, and then click Import Objects.
The SMS Reporting component accesses the SMS 2003 SQL Server views by using a SQL Server application role that is named webreport_approle. This role has a random password that SMS 2003 automatically generates and stores. For more information, visit the following Microsoft Web site:
APPLIES TO- Microsoft Systems Management Server 2003
| kbregistry kbtshoot kberrmsg kbprb KB936118 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
|
 |
 |
 |
 |
 |
 |
 |
| |