DPM Agent Installer Fails with errorcode =0x80070643

Question

I've seen this all over the place. Sometimes it's with DPM 2007 but I'm using an evaluation version of DPM 2010. I'm trying to install the agent on a protected server running Windows
2008 Standard with Service Pack 2. This is our Exchange 2007 server and is also running ForeFront. 
I initially tried installing from the DPM server and received the following error code
Install protection agent on PS failed:
Error 313: The agent operation failed because an error occurred while running the installation program on PS.
Error details: Fatal error during installation (0x80070643)
Recommended action: Review the log files on PS: [windir]\temp\msdpm*.log and take appropriate action. Retry the operation, and if the error persists, restart the computer
and then retry the operation again.
I reviewed the error logs but I didn't know exactly what to look for and I don't see anything that jumps out at me.
On other sites I have seen instructions for a manual install on the protected server after disabeling the firewall and so I tried that.
On the protected server I mapped a drive to the folder containing the agent on the DPM server. I ran Net stop mpssvc. Then I launched the installer  DPMAgentInstaller_x64.exe. When
I ran that I received a different error.
DPMAgentInstaller failed with errorcode =0x80070643, error says: Fatal error during installation.
Check log files in [WINDIR]temp\MSDPM*.LOG
Press Enter key to close the window
I rebooted and tried again with the same error.
On another page I read that someone asked about the paging file so I verified that there was sufficient space allocated (only 2/3 of the allocated space is being used).
Our primary partition has over 50GB of free space and our data partition has over 370 GB free.
I can post sections of the log files if that would help.
Thanks

Answer 1

Dan,
This is usually a problem with the installer. I've seen this in DPMRA.msi installation failures when In some instances the default permissions of the scheduled tasks directory altered.
The following is a sample from the failing MSDPMAgentBoostrap0Curr.errlog file.
WARNING Failed: Hr: = [0x80070424] : F: lVal : (HANDLE)(schService = OpenServiceW( schSCManager, strServiceName.PeekStr(), (0x00010000L) | 0x0020 | 0x0004 | 0x0002))
WARNING Failed: Hr: = [0x80070424] DeleteServiceByName for service[DPMClientService] failed                                                                         
WARNING Failed: Hr: = [0x80070002] : Error while deleting the Scheduled Task [ScheduledDPMClientBackup]                                                             
WARNING Failed: Hr: = [0x80070002] DeleteScheduledTaskByName failed                                                                                                 
WARNING Failed: Hr: = [0x80070005] : F: lVal : pTaskScheduler->NewWorkItem(pwszClientTaskName, CLSID_CTask, IID_ITask, (IUnknown**)&pTask)                          
WARNING Failed: Hr: = [0x80070005] AddScheduledTaskForClient failed  
The service deletion failure is fine since it fails with 0x80070424 (ERROR_SERVICE_DOES_NOT_EXIST - The specified service does not exist as an installed service). The same goes with the scheduled task deletion with the error 0x80070002 (ERROR_FILE_NOT_FOUND
- The system cannot find the file specified). The installer was removing old services or tasks that may be lingering and if they do not exist we will get the above errors.
The access is denied error on the task creation is the aberration that must be addressed.
The permissions on %windir%\Tasks need to allow write access to the account doing the DPMRA.msi install.
Some have implemented group policies to lock down the permissions on the Tasks directory. This was done to combat the Conficker worm. Please see
KB 962007 Virus alert about the Win32/Conficker worm for more details.
Note: You must reset the default permissions on the Task directory. See the "After the environment is fully cleaned" section of the KB article.
If not this let us know.
/Steve
Steve L [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.