Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. You may receive a "The installation cannot proceed" error when you install Data Protection Manager 2006 on a computer that is running Windows Server 2003 with Service Pack 1

You may receive a "The installation cannot proceed" error when you install Data Protection Manager 2006 on a computer that is running Windows Server 2003 with Service Pack 1

View products that this article applies to.

Symptoms

When you install Data Protection Manager (DPM) 2006 on a computer that is running Microsoft Windows Server 2003 with Service Pack 1 (SP1), you may experience one or more of the following symptoms:
  • You receive the following error:
    The installation cannot proceed because some prerequisites were not met. Each error condition in the Details area must be resolved before Data Protection Manager can be installed.
  • The Data Protection Manager Setup Wizard displays the following error in the Details area of the Installation page:
    Failure error 812 (Report deployment failed)
  • When you try to connect to http://localhost/reportserver, you receive a "Service Unavailable" error.
  • The following entries are logged in the Documents and Settings\All Users\DPMLogs\DpmSetup.log file:
    Exception :  => System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Net.WebException: The request failed with HTTP status 503: Service Unavailable.

   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)

   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)

   at Microsoft.EnterpriseStorage.Dls.UI.Reporting.ReportingService.FindItems(String Folder, BooleanOperatorEnum BooleanOperator, SearchCondition[] Conditions)

   at Microsoft.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.SearchItemInServer(String itemName, String itemPath)

   at Microsoft.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.CreateReportRootFolder(String serverName, Boolean recreate)

   at Microsoft.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.InstallReports(Boolean isUpgradeOrRepair)

   --- End of inner exception stack trace ---

   at System.Reflection.RuntimeMethodInfo.InternalInvoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean isBinderDefault, Assembly caller, Boolean verifyAccess)

   at System.Reflection.RuntimeMethodInfo.InternalInvoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean verifyAccess)

   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)

   at System.RuntimeType.InvokeMember(String name, BindingFlags invokeAttr, Binder binder, Object target, Object[] args, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParameters)

   at Microsoft.EnterpriseStorage.Dls.Setup.Wizard.ReportingConfiguration.ConfigureReporting(Boolean isUpgrading)
  • An event that is similar to the following is logged in the Application log:

    Event Type: Error
    Event Source: DCOM
    Event Category: None
    Event ID: 10016
    Date: Date
    Time: Time
    User: NT AUTHORITY\NETWORK SERVICE
    Computer: Computer Name
    Description:
    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {A9E69610-B80D-11D0-B9B9-00A0C922E750}
    to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security permission can be modified using the Component Services administrative tool.

↑ Back to the top

Cause

The problem is caused by a mismatch of files that occurs when you install Microsoft Internet Information Services. DPM requires Windows Server 2003 SP1. This problem occurs if you install IIS from an installation point that is not running Windows Server 2003 SP1.

Before you install DPM, you must install IIS. IIS Setup depends on the following registry subkeys for installation:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\SourcePath
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\ServicePackSourcePath
If the IIS installation cannot find a Windows Server 2003 SP1 installation, you are prompted to supply a valid path. If you point to an original release version of Windows Server 2003, IIS is not correctly installed.

↑ Back to the top

Resolution

Warning 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 your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To solve this problem, follow these steps:
  1. Use Add/Remove Programs in Control Panel to uninstall the following items:
    • Microsoft SQL Server 2000 Reporting Services
    • Internet Information Services (IIS)
  2. Click Start, click Run, type regedit, and then click OK.
  3. Locate and then right-click the following registry subkey:
    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup
  4. Right-click the ServicePackSourcePath entry in the right pane, and then click Modify. Type a valid path of a Windows Server 2003 SP1 installation in the Value data box.
  5. Locate and then right-click the following registry subkey:
    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup
  6. Right-click the SourcePath entry, and then make sure that the value points to the location where the original release version of Windows Server 2003 was installed.
  7. Rerun DPM Setup.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More information

If you do not follow the procedures in the "Resolution" section and you try to re-install DPM after a failed initial installation, you may experience the following symptoms:
  • The Data Protection Manager Setup Wizard displays the following message in the Details pane under System Attributes:


    DPM Setup could not determine the edition of SQL Server 2000 Reporting Services used in the current installation of DPM. Verify that the ReportServer and the World Wide Web Publishing services are running: In Control Panel, click Administrative Tools, click Services, and check the Status column for each service.

  • The DpmSetup.log file contains the following entries: Exception : => System.Net.WebException: The underlying connection was closed: Unable to connect to the remote server. at System.Net.HttpWebRequest.CheckFinalStatus() at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult) at System.Net.HttpWebRequest.GetRequestStream() at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Microsoft.EnterpriseStorage.Dls.UI.Reporting.ReportingService.ListSecureMethods() at Microsoft.EnterpriseStorage.Dls.Setup.Inspect.InspectReportingPrerequisites.DetectRosettaEval(InspectContext context) Error : DPM Setup could not determine the edition of SQL Server 2000 Reporting Services used in the current installation of DPM.Verify that the ReportServer and World Wide Web Publishing services are running: In Control Panel, click Administrative Tools, click Services, and check the Status column for each service.

↑ Back to the top

Keywords: KB908181, kbprb, kbbug

↑ Back to the top

Article Info
Article ID : 908181
Revision : 3
Created on : 10/30/2006
Published on : 10/30/2006
Exists online : False
Views : 262