Office 2016 KMS key issue with Server 2016, error 0xC004F050

Luke Anthony
Luke Anthony used Ask the Experts™
on
Good morning,

We have just migrated our KMS server from an old 2008R2 server to a new 2016 server. The old server only really activated Office 2016 Pro Plus and a couple of old 2008R2 machines. We removed the keys and put them into the new 2016 KMS server and all was well except for the Office key. Also there are new Server 2016 keys on the new server that have taken and are activating the new VMs without issue.

The Office 2016 key will not load into the new KMS server, it returns "error 0xC004F050 The software service reported that the product key is invalid". So we contacted the supplier and they verified with Microsoft that the key is genuine and valid (we have been using it for over a year already).

Some online searches later we found many other users with this same issue when moving to Server 2016 KMS activation for Office, however no solutions that were presented have been effective.

The 'technical guy' from the licence supplier was able to replicate the error using his test environment, however they have no solutions for the issue.
All our Windows Server keys are working from the new KMS and activating as expected, which suggests it's some kind of compatibility issue with 2016 office and 2016 KMS.

So, have any of you ever managed to resolve this issue? We are running out of grace period for the Office 2016 (about 12 days left) and seem to have run out of ideas.

Can you help?


info:
Office 2016 Pro Plus is on a perpetual licence, we don't use 365 here.


Kind regards,
Luke Anthony
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Is the Windows Server 2016 completely patched?

according to this: did you download and install Microsoft Office 2016 Volume License Pack? https://www.microsoft.com/en-us/download/details.aspx?id=49164
Luke Anthony1st line IT support assistant

Author

Commented:
Thanks, this missing package was the cause of the issues. Weirdly the MS documentation didn't mention it at all, you've resolved a big headache there, thanks again.
After a while I rembered having the same problem about 2 years ago :-)
Glad it helped.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial