This is a short blog post about my experience in deploying System Center Data Protection Manager 2016.
I am involved currently with several DPM projects on upgrading System Center Data Protection Manager 2012 R2 to 2016.
For more information, please check my recent DPM articles here.
While installing DPM 2016 (greenfield deployment) on top of Windows Server 2016 and SQL Server 2014 SP2, I came across a very strange issue!
The error is the following:
First things first is to look at the error logs file.
As you can see below, all the errors are related to System.IO.FileNotFoundException.
This led me to think it could disk error or volume.
I scanned all the disks, even I created a new virtual machine and tried again, but still I received the same error!
The next thing is to look online… Bing it… Google it… Search engine failed on me to return any result regarding this error!
…I did recently many successful deployments without any error, so what is the difference in this environment versus the others?
In this particular deployment, I downloaded the DPM installation media from the Internet. However, in the other installation, I copied the media over the network.
Could it be that Windows blocked the setup files that came from the Internet to help protect this machine…
So let’s double check!
As you can see, one of the file is blocked. In fact, I noticed that all setup files are blocked and not only the .exe or .dll files.
So how can we unblock 677 files?
With PowerShell of course!
Get-Childitem -Path 'D:\SC 2016 SCDPM\' -Recurse | Unblock-File -Confirm:$false –Verbose
Let’s try the installation again now…
And here you go
Hope that helps!
With that I will sign-off for 2016.
I want to thank the Community, Followers, Readers, Microsoft Product Groups, MVP Award Program, MVP’s, Developers and ITPro’s!
Until then… see you in 2017…