Support Tip: DPM 2012 R2 UR3 agent install fails with error 0x80070643

ToolsHi folks, Chris Butcher here. I was recently working on some issues with the installation of our System Center 2012 R2 Data Protection Manager Update Rollup 3 agents on Windows Server 2003 computers, and while Mike’s blog covered the bulk of the issues a person might see when installing the agents, I discovered a few side issues that people may be hitting and wanted to get some supplemental information out here on the web to help with them.

This doesn’t affect the installation methods or any other part of process. These are just two additional prerequisites and the errors you may see when installing the agents if they are not met.

The first prerequisite is the Microsoft Visual C++ 2005 Redistributable Package. While Mike covered the v2008 companion to this, I determined that you actually have to have both. If you have either one without the other then the installation will fail. When it fails, a command prompt window will give this error:

DPMAgentinstaller failed with errorcode –0x80070643
Fatal error during installation.

Check log files in [WINDIR]Temp\MSDPM*.LOG
Press enter key to close the window

This is accompanied by several events in the System Event Log. This is where you will be able to tell if you are missing the 2005 version or the 2008 version. You will see several errors with a source of SideBySide.

Event Type: Error
Event Source: SideBySide
Event Category: None
Event ID: 32
Date: 
Time: 
User:  N/A
Computer: ServerName
Description:
Dependent Assembly Microsoft.VC80.CRT could not be found and Last Error was The referenced assembly is not installed on your system.

Event Type: Error
Event Source: SideBySide
Event Category: None
Event ID: 59
Date: 
Time: 
User:  N/A
Computer: ServerName
Description:
Resolve Partial Assembly failed for Microsoft.VC80.CRT. Reference error message: The referenced assembly is not installed on your system.

Event Type: Error
Event Source: SideBySide
Event Category: None
Event ID: 59
Date: 
Time: 
User:  N/A
Computer: ServerName
Description:
Generate Activation Context failed for C:\WINDOWS\Installer\MSI5E.tmp. Reference error message: The referenced assembly is not installed on your system.

Notably, you will want to look for the description where you will see this:

Dependent Assembly Microsoft.VC80.CRT could not be found and Last Error was The referenced assembly is not installed on your system.

The assembly noted dictates the version of Visual C++. For example, VC80 indicates 2005 and VC90 indicates 2008.

In short, if you see this SideBySide error in the System Event Log and it lists an assembly with VC80 in it then you will need to install the Microsoft Visual C++ 2005 Redistributable Package. This can be found using the links below:

If you see this SideBySide error in the System Event Log and it lists an assembly with VC90 in it then you will need to install the Microsoft Visual C++ 2008 Redistributable Package which can be found using the links below.

There was one other issue that we found which also shows itself with the same “Fatal error during installation” error in the command prompt. This time however, it doesn’t give the same clues in the System Event Log. So, if you aren’t seeing anything logged in the System Event Log you will need to navigate to the \Windows\Temp directory and find the most recent MSDPMAgentInstall.log file.

You can open this file with Notepad. When open, search from the top down for “return value 3”. Once you locate this, look immediately above that line for the following information. If you see the “Failed to load Xml Doc” then this indicates you are missing the XML parser.

UpdatePSDataSourceConfigXML Entered
LoadPSDataSourceConfigXML Entered
LoadLHSystemStateDSConfigXML: xml file path <c:\Program Files\Microsoft Data Protection Manager\DPM\Datasources\PSDatasourceConfig.xml>
LoadPSDataSourceConfigXML: Failed to load Xml Doc .
UpdatePSDataSourceConfigXML return code = 0x80040154
Action ended 11:45:40: InstallExecute. Return value 3.

DPM 2012 R2 is using a new XML parser technology and by default, Windows Server 2003 does not have this. If it has not been added then the installation will fail. While either MSXML 3.0 Parser or MSXML 6.0 Parser should resolve this, I recommend that you go ahead and get the latest version.

MSXML 6.0 Parser: http://www.microsoft.com/en-us/download/confirmation.aspx?id=3988

I hope this helps eliminate some searching for answers. Enjoy!

Chris Butcher | Solution Asset PM | Microsoft GBS Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/