Problem with Office 2019 KMS Server Activations - First attempt hardware ID binding issue. Second attempt works.

Moltano5k 0 Reputation points
2023-07-17T20:46:00.25+00:00

Hi -

Recently started getting Office 2019 activation issues. There are a lot of things changing on our network recently so I am not exactly sure what may have triggered this. I can get into that if needed. Here's the issue. Many users see an activation failure message when they open Office up for the first time they log in. Running ospp.vbs /dstatus shows an error code of 0XC004F00F "The Software Licensing Service reported that the hardware ID binding is beyond the level of tolerance." The license status is --NOTIFICATIONS--. Then if the users close all Office applications and any activation dialog boxes that may have popped up and open an office app for the second time, it shows as activated in the GUI. And from ospp.vbs it then says its --LICENSED--. Still has an error code of 0x4004f040, which says "The software licensing service reported that the product was activated but the owner should verify the Product Use Rights.". In the Office GUI it says its licensed. Works fine the rest of the day.

Environment - Our KMS server mostly is for our virtual desktops, which are non-persistent VMware Horizon based, with VMware writable app volumes and Office 2019 is in its own app volume (if you are familiar with VMware). Its been working fine till around 2 weeks ago. At one point my coworker tried to upgrade the KMS server (currently 2012 R2) to a newer server and noticed it stopped activating office all together and rolled back a snapshot. VMware tools has since been updated.

Looking at the server logs I don't see anything odd. Activation requests come in, and the logged message going back is to activate it. I've made sure my VDI pool base images don't have any remnants of office in them (used to have Office 365 installed). I removed the license from the KMS server and added it back. Oddly, it kept all the stats so maybe it didn't remove all the way? I've reactivated the KMS server's OS - for what its worth.

Looking for some leads for troubleshooting. At this point I am still not sure is the hardware ID Binding error from the client or does it indicate an issue on the KMS host? Also slmgr on the KMS host doesn't report anything odd about the 2019 office license. I am using GVLK license on the client and CSVLK on the KMS host.

Thank you!!

Office
Office
A suite of Microsoft productivity software that supports common business tasks, including word processing, email, presentations, and data management and analysis.
1,315 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,170 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Limitless Technology 43,951 Reputation points
    2023-07-18T15:44:17.8833333+00:00

    Hello there,

    If you're experiencing an issue with Office 2019 KMS (Key Management Service) server activations where the first attempt fails due to a hardware ID binding issue, but the second attempt is successful, it could be caused by several factors. Here are a few potential explanations and solutions:

    Network Connectivity: Ensure that there are no network connectivity issues between the client machines and the KMS server. If the first attempt fails due to a network interruption or connectivity problem, the second attempt might succeed when the connection is stable. Check network configurations, firewalls, and any network infrastructure that could impact the communication between clients and the KMS server.

    Timing and Activation Thresholds: KMS activations have specific timing and threshold requirements. Make sure that the time on the client machine and the KMS server is synchronized accurately. Additionally, note that Office 2019 requires at least 25 unique client requests before activations can occur. Ensure that the number of client machines attempting activation meets this threshold.

    KMS Server Configuration: Verify the configuration of your KMS server to ensure it's set up correctly. Double-check that the server is running the appropriate version of the KMS service, is properly activated with a valid KMS host key, and has the necessary DNS records (SRV) in place. Review the server's event logs for any related errors or warnings that could indicate configuration issues.

    DNS Resolution: Ensure that the client machines can resolve the KMS server's DNS records correctly. If the first activation attempt fails due to DNS resolution problems, the second attempt might succeed if the issue is resolved. Verify that the client machines can resolve the KMS server's fully qualified domain name (FQDN) correctly.

    I used AI provided by ChatGPT to formulate part of this response. I have verified that the information is accurate before sharing it with you.

    Hope this resolves your Query !!

    --If the reply is helpful, please Upvote and Accept it as an answer--