DPM 2016 and SQL 2016 – Error 4387

Post a Comment

 

Scenario:

SQL01 – SQL 2016 RTM install (At this point in time I still recommend SQL2014 for DPM2016)

DPM01 – Data Protection Manager 2016 RTM install

When ‘check and install’ get the below error. Clicking on OK then closes the installer

image

 

How did we get here?

  1. Install SQL 2016 RTM on SQL01.
  2. Setup remote access for DPM01.
  3. Install DPM Prereq’s on SQL01.
  4. attempt to Install DPM 2016 RTM… and baboom… Error 4387.

 

How to fix?

Well, having a quick search lead me to here.. The solution that worked for my scenario was in the comments from a chap named Edward.

So, I uninstalled SSMS 17.1 (even though you don’t need to, it’s just a ‘me’ thing), then installed 16.5.3 from here.

Reran the installer and I was presented with great success!

Hope this helps anyone deploying DPM 2016 and hoping to get it running on SQL 2016 without embarking on the SQL2014 upgrade option..

Enjoy!
Dan

Dan

Daniel is an accomplished Hybrid Cloud Architect specializing in Azure hybrid solutions, cloud modernization, and software-defined platforms. With extensive expertise in HPE and Dell solutions, he focuses on cutting-edge technologies, including GPU-as-a-Service platforms and liquid immersion cooling. A Microsoft MVP with over seven years of recognition, Daniel is passionate about bridging on-premises and cloud environments to deliver innovative, scalable, and efficient IT solutions. His career is defined by a commitment to community engagement through blogging, speaking at tech conferences, and leading user groups, making him a recognized thought leader in hybrid cloud strategy.

Leave A Comment