none
KMS error 0xC004F074

    Question

  • I had KMS working on a windows 7 machine and had activated 100 clients.  the hard disk failed in the Windows 7 machine so I had to start a new KMS server.  I deceded to use one of our 2008 servers.  KMS wouldnt work so I installed KB968912 on server 2008 and restarted

    slmgr -ato

    slmgr.vbs /dlv

    output says:

    License Status: Licensed

    Key Management Service is enabled on this machine

    DNS says VLMCS Services location [0][0][1688] <srv name>

    on win 7 client add slmgr -ipk <client kms key>

    on the client slmgr -ato I get error 0xC004F074 The key management service is unavailable.

    Ive come to a dead end now and cant find the next step can anyone help.

    Friday, February 26, 2010 11:10 AM

Answers

  • The server sunning kms is not an R2 server.  I tried it anyway and got a 0xC004F050 error:  [Window Title]
    Windows Activation

    [Main Instruction]
    An error has occurred

    [Content]
    You can also contact Microsoft by phone to help resolve this problem.

    [^] Hide details  [Close]

    [Expanded Information]
    Code:
    0xC004F050

    Description:
    The Software Licensing Service reported that the product key is invalid.

    Thursday, March 04, 2010 7:27 AM
  • SUCCESS!  Your a genius.  Why would anyone install a 2008 R2 key on a 2008 server to activate Win7 clinets when there is a 2008 key that so obviously is the one to use?

    I had to do a slmgr /upk, restart then and /ipk for the R2 key and /ato and restart to get the key to work and on the clients I have had to do a /upk, /ipk even though the key is the same to get them to register but it works!

    So far only one client has registered as a result of a forced /ato but I'll leave it for an hour to see if any of the others activate automattically.

    Thanks so much for all your help.
    Thursday, March 04, 2010 8:06 AM

All replies

  • Hello David,
    I would check the KMS client first,
    run slmgr /dlv and check if the client is attempting to contact the correct KMS host machine.

    If it's attempting to contact the correct KMS host machine, you may want to start and stop the software licensing service on the KMS host.
    Thanks, Darrell Gorter This posting is provided "AS IS" with no warranties, and confers no rights
    • Proposed as answer by PhompAng Monday, October 21, 2013 5:36 PM
    Saturday, February 27, 2010 7:19 AM
  • Hey Darrell, good calls and thanks for your help but no cigar.  I ran slmgr /skms <srvname>:1688 to direct the client to the host to no avail.  I tried it with the firewall off too. I tried netsh advfirewall firewall set rule group="Key Management Services" new enable=yes, but that didnt help.  I stoped KMS service and restarted the server, still no go.

    As a workaround I have set up another KMS host on a Win 7 box and that works fine.  Its just KMS on Server 2008 that wont.
    Saturday, February 27, 2010 2:21 PM
  • Hello David,
    Can you post the slmgr /dlv output ( top three lines)from the KMS host machine?
    Example:
    Software licensing service version: 6.1.7600.16385

    Name: Windows(R) 7, Enterprise edition

    Description: Windows Operating System - Windows(R) 7, VOLUME_KMSCLIENT channel

    If you get the dialog box, you can do Ctrl-C to copy the text from the dialog box to the clipboard .


    Thanks, Darrell Gorter This posting is provided "AS IS" with no warranties, and confers no rights
    Saturday, February 27, 2010 3:17 PM
  • Here you go

    ---------------------------
    Windows Script Host
    ---------------------------
    Software licensing service version: 6.0.6002.18112

    Name: Windows Server(R), ServerStandardV edition

    Description: Windows Operating System - Windows Server(R), VOLUME_KMS_B channel

    Activation ID: 56df4151-1f9f-41bf-acaa

    Application ID: 55c92734-d682-4d71-983e

    Extended PID: 55041-00152-339-971802-03-2057

    Installation ID: 01750534514125483083945140772

    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=48189

    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=48190

    Use License URL: http://go.microsoft.com/fwlink/?LinkID=48192

    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=48191

    Partial Product Key:

    License Status: Licensed

     

    Key Management Service is enabled on this machine

        Current count: 0

        Listening on Port: 1688

        DNS publishing enabled

        KMS priority: Normal

     

    Key Management Service cumulative requests received from clients

        Total requests received: 0

        Failed requests received: 108

        Requests with License Status Unlicensed: 0

        Requests with License Status Licensed: 0

        Requests with License Status Initial grace period: 0

        Requests with License Status License expired or Hardware out of tolerance: 0

        Requests with License Status Non-genuine grace period: 0

        Requests with License Status Notification: 0


    ---------------------------
    OK  
    ---------------------------

    Monday, March 01, 2010 8:04 AM
  • Hello David,
    Hmm that is strange, everything looks to be correct.
    Can you look at the KMS event log on the KMS host machine.
    I would like to know if all the failed requests are reporting the 0xC004F074 error or if they are being reported with other errors. If there are other errors I would like to know what they are.

    I am thinking that the best course may be to uninstall the KB968912 update,
    restart the machine.
    Reinstall the KB968912 update again, they restart the machine.

    Thanks, Darrell Gorter This posting is provided "AS IS" with no warranties, and confers no rights
    Monday, March 01, 2010 10:38 PM
  • Event viewer on the server shows many kms requests with no errors but there are no activations.

    Log Name:      Key Management Service
    Source:        Microsoft-Windows-Security-Licensing-SLC
    Date:          26/02/2010 10:34:43
    Event ID:      12290
    Task Category: None
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      srv005.ngs.local
    Description:
    An activation request has been processed.
    Info:
    0xC004F042,25,AC5630ICT215.ngs.local,83540fd5-c68d-40cc-85ca-02c67ea90d4f,2010/2/26 10:34,0,1,223440,b92e9980-b9d5-4821-9c94-140f632f6312
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Security-Licensing-SLC" Guid="{1FD7C1D2-D037-4620-8D29-B2C7E5FCC13A}" EventSourceName="KmsRequests" />
        <EventID Qualifiers="16384">12290</EventID>
        <Version>0</Version>
        <Level>4</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2010-02-26T10:34:43.000Z" />
        <EventRecordID>6</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>Key Management Service</Channel>
        <Computer>srv005.ngs.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>0xC004F042,25,AC5630ICT215.ngs.local,83540fd5-c68d-40cc-85ca-02c67ea90d4f,2010/2/26 10:34,0,1,223440,b92e9980-b9d5-4821-9c94-140f632f6312</Data>
        <Data>0xC004F042</Data>
        <Data>25</Data>
        <Data>AC5630ICT215.ngs.local</Data>
        <Data>83540fd5-c68d-40cc-85ca-02c67ea90d4f</Data>
        <Data>2010/2/26 10:34</Data>
        <Data>0</Data>
        <Data>1</Data>
        <Data>223440</Data>
        <Data>b92e9980-b9d5-4821-9c94-140f632f6312</Data>
        <Binary>000004000000000001000000D06803003427C95582D6714D983ED6EC3F16059F80992EB9D5B921489C94140F632F63121952DE7FFAFB4A4882C934D1AD53E856D50F54838DC6CC4085CA02C67EA90D4F190000009956894FCFB6CA01000000000000000000000000000000004100430035003600330030004900430054003200310035002E006E00670073002E006C006F00630061006C00000065006300750072006900740079002D007300700070002D0063006F006D0070006F006E0065006E0074002D0073006B0075002D00700072006F00660065007300730069006F006E0061006C002D0070006C008E3B84E0A71C297DC97BAE4D96905EC5</Binary>
      </EventData>
    </Event>

    Wednesday, March 03, 2010 7:40 AM
  • Ok, I uninstalled and reinstalled KB968912 but still get the same error on the clients.  KMS event viewer entries do not show anything other than requests.  No errors to say failed request.  Could it be anything to do with the key being used on the client.  We are using FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4 on the clients with the server b key.
    Wednesday, March 03, 2010 8:14 AM
  • Looking round the net there are loose ends like mine all over the place.  Heres a link to one: http://episteme.arstechnica.com/eve/forums/a/tpc/f/12009443/m/762005511041, same problem, no solution from August last year.

    Wednesday, March 03, 2010 2:16 PM
  • Hello David,
    I posted but I do not see my last post so trying this again.
    From the event message
    Info:
    0xC004F042
    The0xc004F042 indicates a mismatch between the KMS client and KMS host machine.  Essentially the key on the KMS host key is not correct for the KMS client that is trying to activate.  We see this sometimes prior to the restart of the software licensing service but that is covered with your reboot.

    So looking at the KMS outout I missed this:
    Description: Windows Operating System - Windows Server(R), VOLUME_KMS_B channel
    This is a Windows Server 2008 KMS host key which will not activate Windows 7 KMS clients, you need to install a Windows Server 2008 R2 KMS host key

    Thanks, Darrell Gorter This posting is provided "AS IS" with no warranties, and confers no rights
    Wednesday, March 03, 2010 7:54 PM
  • The server sunning kms is not an R2 server.  I tried it anyway and got a 0xC004F050 error:  [Window Title]
    Windows Activation

    [Main Instruction]
    An error has occurred

    [Content]
    You can also contact Microsoft by phone to help resolve this problem.

    [^] Hide details  [Close]

    [Expanded Information]
    Code:
    0xC004F050

    Description:
    The Software Licensing Service reported that the product key is invalid.

    Thursday, March 04, 2010 7:27 AM
  • SUCCESS!  Your a genius.  Why would anyone install a 2008 R2 key on a 2008 server to activate Win7 clinets when there is a 2008 key that so obviously is the one to use?

    I had to do a slmgr /upk, restart then and /ipk for the R2 key and /ato and restart to get the key to work and on the clients I have had to do a /upk, /ipk even though the key is the same to get them to register but it works!

    So far only one client has registered as a result of a forced /ato but I'll leave it for an hour to see if any of the others activate automattically.

    Thanks so much for all your help.
    Thursday, March 04, 2010 8:06 AM
  • Hello,

     

    One important thing, always check the time/date settings, if they are not correct you can get this error (like in my case).

    Wednesday, March 31, 2010 6:17 AM
  • Ive seen it mentioned elsewhere about the time and date settings.  It was not relevant in this instance as its a large domain with everyting syncing to DNS.
    • Proposed as answer by avi83 Tuesday, August 24, 2010 3:45 AM
    Wednesday, March 31, 2010 12:29 PM
  • Hi!

    I tried exactly what you wrote. You wrote to insert the R2 key after /upk and /ipk but it doesn't work. It says "invalid key".

    So I tried to put the 2008 key and restarted.

    I also did on the client /upk and /ipk with the key, but I'm still getting the same error:

    ---------------------------
    Windows Script Host
    ---------------------------
    Activating Windows(R) 7, Professional edition (b92e9980-b9d5-4821-9c94-140f632f6312) ...
    
    Error: 0xC004F074 The Software Licensing Service reported that the computer could not be activated. The Key Management Service (KMS) is unavailable
    
    
    ---------------------------
    OK   
    ---------------------------
    

    Do you have any clue?

    Wednesday, October 19, 2011 1:45 PM
  • Hello,

    Do you have the KB article update installed

    http://support.microsoft.com/kb/968912

    It's not clear what you are attempting?  Is this Windows Server 2008 or Windows Server 2008 R2 machine?

    what is the output from the below command of the KMS host?

    Slmgr /DLV


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en
    Thursday, October 20, 2011 8:16 PM
  • I finally got this to work after trolling the forums for hours.  Having skimmed so many forums I can't remember who it was that said this but the fix or me was to use the Server 2012 R2 KMS key even though our KMS server is a 2008 R2 machine.  Everything I've read so far has told me to use the corresponding key to the OS you have installed but in this case it was not correct.

    To summarize: Trying to activate "Windows 8.1" client to a "2008 R2 KMS" server with error code "0xC004F074".

    Solution was to use the Server 2012 R2 KMS key even though my KMS server is 2008 R2.
    Monday, December 16, 2013 4:38 PM