none
KMS Activation Error 0xC004F056

    Question

  • We're running a KMS Server on a Windows 2008 R2 SP1 system. We've installed our Server 2012-R2 key and applied the Hotfix 2885698. We're having problems activating some Server 2012 Datacenter R2 systems. The Application logs, on the clients, show attempting to contact our KMS server but they ultimately fail to activate. Our KMS server licensing looks like this:

    C:\Windows\system32>cscript slmgr.vbs /dlv
    Microsoft (R) Windows Script Host Version 5.8
    Copyright (C) Microsoft Corporation. All rights reserved.

    Software licensing service version: 6.1.7601.22449

    Name: Windows Server(R), ServerEnterprise edition
    Description: Windows Operating System - Windows Server(R), VOLUME_KMS_2012-R2 channel
    Activation ID: dcb88f6f-b090-405b-850e-dabcccf3693f
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 55041-00206-271-051856-03-1033-7601.0000-2952013
    Installation ID: 017013793711071782473952179116233613374391945873535013
    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88342
    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88343
    Use License URL: http://go.microsoft.com/fwlink/?LinkID=88345
    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88344
    Partial Product Key: GGQH7
    License Status: Licensed
    Remaining Windows rearm count: 5
    Trusted time: 12/2/2013 3:20:43 PM

    Key Management Service is enabled on this machine
        Current count: 50
        Listening on Port: 1688
        DNS publishing enabled
        KMS priority: Normal

    Key Management Service cumulative requests received from clients
        Total requests received: 312049
        Failed requests received: 150442
        Requests with License Status Unlicensed: 0
        Requests with License Status Licensed: 158688
        Requests with License Status Initial grace period: 2672
        Requests with License Status License expired or Hardware out of tolerance: 65
        Requests with License Status Non-genuine grace period: 0
        Requests with License Status Notification: 182

    The clients attempts look like this

    C:\Windows\system32>cscript slmgr.vbs /ato
    Microsoft (R) Windows Script Host Version 5.8
    Copyright (C) Microsoft Corporation. All rights reserved.

    Activating Windows(R), ServerDatacenter edition (00091344-1ea4-4f37-b789-01750ba
    6988c) ...
    Error: 0xC004F074 The Software Licensing Service reported that the computer coul
    d not be activated. No Key Management Service (KMS) could be contacted. Please s
    ee the Application Event Log for additional information.

    C:\Windows\system32>cscript slmgr.vbs /dlv
    Microsoft (R) Windows Script Host Version 5.8
    Copyright (C) Microsoft Corporation. All rights reserved.

    Software licensing service version: 6.3.9600.16402

    Name: Windows(R), ServerDatacenter edition
    Description: Windows(R) Operating System, VOLUME_KMSCLIENT channel
    Activation ID: 00091344-1ea4-4f37-b789-01750ba6988c
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 06401-02535-000-000000-03-1033-9600.0000-2732013
    Product Key Channel: Volume:GVLK
    Installation ID: 099461110857633173016068560124014433734000349035501875303903680

    Partial Product Key: Q3VJ9
    License Status: Notification
    Notification Reason: 0xC004F056.
    Remaining Windows rearm count: 999
    Remaining SKU rearm count: 1000
    Trusted time: 12/2/2013 3:29:00 PM
    Configured Activation Type: All
    Please use slmgr.vbs /ato to activate and update KMS client information in order
     to update values.

    C:\Windows\system32>

    I've checked the networking side of things and everything is clear. The only thing I can think is that the client is Server 2012 R2 and the host is Server 2008 R2 SP1 and maybe they don't like the down-level relationship.

    Any suggestions are greatly appreciated.


    Orange County District Attorney

    Monday, December 02, 2013 11:30 PM

All replies

  • Hi,

    Thanks for posting in the forum.

    Regarding the current issue, please first try to reinstall the hotfix using the Installation instructions section of the KB article you mentioned. In addition, you could also try to refer to the following article to troubleshoot the issue manually.

    How to Fix Activation Error 0xC004F074 in Windows 8 and 8.1?

    http://atechjourney.com/how-to-fix-activation-error-0xc004f074-in-windows-8.html/

    Hope this helps.

    Best Regards,

    Andy Qi

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.


    Andy Qi
    TechNet Community Support

    Wednesday, December 04, 2013 7:54 AM
    Moderator
  • your KMShost seems to have successfully accepted and activated/licensed the WS2012R2 product key, so that all looks fine, but you should reboot it and check the status of it again (based on the large cumulative request count, it doesn't seem like it's had a reboot for a while, and, after applying the hotfix, a reboot is needed).

    check on the KMSclient event logs, to confirm that the client is discovering the expected KMShost via DNS (it could be contacting a different KMShost, one that doesn't have the WS2012R2 host key)


    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

    Wednesday, December 04, 2013 8:23 AM
  • Thanks to both of you for your suggestions. I reapplied the hotfix and restarted the KMS server but still no change. I'll open a support case on this one and see if the Microsoft folks can help figure it out.

    Orange County District Attorney

    Wednesday, December 04, 2013 3:48 PM
  • sure.

    if you need to review and "decode" the event logs, this article is a great help with that:
    http://technet.microsoft.com/en-us/library/ee939272.aspx


    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

    Wednesday, December 04, 2013 8:07 PM
  • Hi,

    Any update?

    Just checking in to see if the suggestions were helpful. Please let us know if you would like further assistance.

    Best Regards,

    Andy Qi

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.


    Andy Qi
    TechNet Community Support

    Wednesday, December 18, 2013 3:35 PM
    Moderator
  • I finally found that the DNS Service record that was originally created was trying to use port 0 instead of port 1688. Once I changed it to 1688, all the KMS problems went away.

    Orange County District Attorney

    • Proposed as answer by DonPick Wednesday, December 18, 2013 7:12 PM
    Wednesday, December 18, 2013 3:57 PM