Monday, 29 September 2014

Error 347 when installing DPM 2012 R2 agent on Hyper-V 2008 R2

 "He who laughs last, probably made a backup"
The attempt to install the protection agent failed on a Hyper-V 2008 R2 target. The build number of the agent was 4.2.1254.0. The DPM version was Data protection Manager 2012 R2 with Rollup 3.

Install protection agent on Hyper-V06.nwtrader.local failed:
Error 347: An error occurred when the agent operation attempted to create the DPM Agent Coordinator service on Hyper-v06.nwtraders.local.
Error details: The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line-sxstrace for more detail
Recommended action Verify that the Agent Coordinator service on Hyper-V06.nwtrader.local is responding, if it is present. Review the error details, take the appropriate action, and then retry the agent operation.


Cause
The DPM is unable to detect or install all the prerequisites for the protection agent and this resulted in a failed agent installation. Some of the prerequisites needed to be installed manually.

Note that this scenario is about these products:
  1. Microsoft Hyper-V Server 2008 R2 (6.1.7601)
    Not to be confused with Microsoft Windows Server 2008 R2 Core installation
  2. Microsoft Data Protection Manager 2012 R2 Rollup 3 (4.2.1254.0)


Solution
1)      Installing .NET Framework 2
  • Checking for .NET Framework 2
I retrieved the list of activated features using the DSIM tool in an elevated command prompt. The resulting output looked (abbreviated) looked like this:

 C:\Users\ben>DISM /Online /Get-Features

Deployment Image Servicing and Management tool

Version: 6.1.7600.16385
Image Version: 6.1.7601.18489

Features listing for package : Microsoft-Windows-ServerCore-Package~31bf3856ad36
4e35~amd64~~6.1.7601.17514

Feature Name : WindowsServerBackup
State : Disabled

Feature Name : MultipathIo
State : Disabled

Feature Name : Microsoft-Windows-RemoteFX-Host-Package
State : Disabled

Feature Name : Microsoft-Windows-RemoteFX-EmbeddedVideoCap-Setup-Package
State : Disabled
....
Feature Name : NetFx2-ServerCore
State : Disabled

The operation completed successfully.

C:\Users\ben>
 Note the missing .NET Framework 2
  • Installing the missing .net Framework 2 

C:\Users\ben>DISM /Online /Enable-Feature /FeatureName:NetFx2-ServerCore

Tool zur Abbildverwaltung für die Bereitstellung

Version: 6.1.7600.16385
Abbildversion: 6.1.7601.18489

Funktionen werden aktiviert

[==========================100.0%==========================]

Der Vorgang wurde erfolgreich beendet.

C:\Users\ben>
  • Confirm .NET Framework 2 installation
Using 
DISM /Online /Get-Features
 I found the following features enabled
  • ServerCore-EA-IME
  • Microsoft-Hyper-V
  • Microsoft-Hyper-V-Configuration
  • ServerCore-WOW64
  • NetFx2-ServerCore
NetFx2-ServerCore-WOW64 was not activated and not needed because the protection agent seemed to be a native x64 application, located in "c:\Program Files".

2)      Installing .NET Framework 4
I tried to install the agent but the .NET 4 was still missing

  •  Installing .NET Framework 4
I downloaded the installation package “Microsoft .NET Framework 4 (Standalone Installer) for Server Core” for Windows Server 2008 R2 SP1 Server Core or later at http://www.microsoft.com/en-us/download/details.aspx?id=22833

I made sure the requirements were met
  • Turn on WoW64: Start /w ocsetup ServerCore-WOW64
  • Turn on .NET 2.0 layer: Start /w ocsetup NetFx2-ServerCore
  • Turn on .NET 2.0 layer for WoW64: Start /w ocsetup NetFx2-ServerCore-WOW64
As I mentioned before, I skipped “.NET 2.0 layer for WoW64”

I started dotNetFx40_Full_x86_x64_SC.exe in an elevated command prompt



c) Verifying .NET Framework 4 installation

I checked for the presence of the .NET Framework 4 by displaying the list of installed applications like I would in the control panel if I had a GUI.
C:\Users\ben>wmic product get name

Name

Microsoft .NET Framework 4 Extended

Microsoft .NET Framework 4 Client Profile

C:\Users\ben>

3)      Then it was time to check for and install updates


I ignored some mscoree.dll errors during the update process. Presumably they are caused by my choice not to install the not needed WOW64 component of .NET Framework 2.


Note that all updates succeeded.

4)      Lastly, I rebooted

5)      I was then able to install the protection agent without any further issues.


I was able to verify the installation using wmic. I found that “Microsoft Visual C++ 2010  x64 Redistributable - 10.0.30319” had been installed along with the agent.
C:\Users\ben>wmic product get name

Name

Microsoft System Center 2012 R2 DPM Protection Agent

Microsoft Visual C++ 2010  x64 Redistributable - 10.0.30319

Microsoft .NET Framework 4 Extended

Microsoft .NET Framework 4 Client Profile

C:\Users\ben>

No comments:

Post a comment