Microsoft KB Archive/922355

= Error message when you try to use the SMS Web Reporting Tool: &quot;Server object error 'ASP 0178 : 80070005'&quot; =

Article ID: 922355

Article Last Modified on 2/8/2007

-

APPLIES TO


 * Microsoft Systems Management Server 2003, when used with:
 * Microsoft Windows Server 2003 Service Pack 1

-



Important This article contains information that shows you how to help lower security settings or how to turn off security features on a computer. You can make these changes to work around a specific problem. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this workaround in your particular environment. If you implement this workaround, take any appropriate additional steps to help protect your system.



SYMPTOMS
Consider the following scenario. You are a member of the Microsoft Systems Management Server (SMS) 2003 Reporting Users security group. You try to use the SMS Web Reporting Tool on a Microsoft Windows Server 2003 Service Pack 1 (SP1)-based computer. This computer is acting as the SMS site server. In this scenario, you may receive an error message that resembles the following:

Server object error 'ASP 0178 : 80070005' Server.CreateObject Access Error /SMSReporting_093/ReportsNav.asp, line 1055 The call to Server.CreateObject failed while checking permissions. Access is denied to this object.



CAUSE
This problem occurs because the following conditions are true:
 * You are a member of the SMS Reporting Users security group on the Windows Server 2003 SP1-based computer that is acting as the SMS site server.
 * You are not a member of the local Administrators group on the Windows Server 2003 SP1-based computer that is acting as the SMS site server.

In this case, the DCOM permissions are locked down on the Windows Server 2003 SP1 site server.



RESOLUTION
Warning This workaround may make your computer or your network more vulnerable to attack by malicious users or by malicious software such as viruses. We do not recommend this workaround but are providing this information so that you can implement this workaround at your own discretion. Use this workaround at your own risk.

To resolve this problem, follow these steps:
 * 1) Log on to the Windows Server 2003 SP1 computer that is acting as the SMS site server by using an account that has administrative permissions.
 * 2) Click Start, click Run, type dcomcnfg, and then click OK.
 * 3) In the Component Services MMC snap-in, expand Component Services, expand Computers, right-click My Computer, and then click Properties.
 * 4) In the My Computer Properties dialog box, click the COM Security tab.
 * 5) Under Launch and Activation permissions, click Edit Limits.
 * 6) In the Launch Permission dialog box, make sure that the Everyone group has Remote Launch and Remote Activation permissions.
 * 7) In the Component Services MMC snap-in, expand My Computer, expand DCOM Config, right-click SMS_Reporting_Point, and then click Properties.
 * 8) In the SMS_Reporting_Point Properties dialog box, click the Security tab. Under Launch and Activation Permissions, select Customize, and then click Edit.
 * 9) In the Launch Permission dialog box, make sure that the SMS Reporting Users local group has following permissions:
 * 10) * Local Launch
 * 11) * Remote Launch
 * 12) * Local Activation
 * 13) * Remote Activation

Additional query words: ASP 0178 : 80070005

Keywords: kbtshoot kbprb KB922355

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.