locked
KMS activation error 0xC004E003 RRS feed

  • Question

  • *****************************

    I was redirected from here:

    http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_install/kms-activation-error-0xc004e003/0789b0c2-2e82-4da1-9272-70e7e5dac86b

    *****************************

    I am trying to activate a PC with a KMS key, and I have run into a strange error. It is giving me "Code: 0xC004E003, Description: The software licensing service reported that license evaluation failed."

    The key I am using is for Windows 7 Pro, and it has worked fine on over 200 Win7 PC's in my building. The particular PC I am trying to activate used to run Windows XP Pro, but I had to upgrade it for something that the user wants to do on it. I have done some research on this error, and several articles I have found suggest that I should rename a file called "tokens.dat" on the KMS Server, and then run "slmgr /rilc" via command line to generate a new tokens.dat file on the server. However before I go and do this, I want to know if there are any possible consequences? Is this safe to do? I didn't create this server - I am a new hire, and I don't want to risk breaking something I can't fix. What is tokens.dat, why does the server need it, and what happened to it that now I need to replace it? Do I need to replace it at all? Can I fix this without mucking around on my KMS server?

    Thanks for your time.

    Thursday, November 14, 2013 7:34 PM

Answers

  • Hi,

    Maybe you have an misunderstanding about the issue. You may have to reset the activation components in the specific pc.

    The Tokens.dat is a digitally signed file, which stores most of the Windows activation files.

    The problem you encountered may be related to the activation component, so the steps is to reinstall the activation components and then  generate a new tokens.dat file for re-activation successfully.

    Hope this helps,


    Ada Liu
    TechNet Community Support

    • Marked as answer by Cloud_TS Monday, November 25, 2013 1:06 PM
    Wednesday, November 20, 2013 12:58 AM
  • as Ada says, tokens.dat is the encrypted store for licensing data.
    sometime, this store becomes "corrupt" and needs to be rebuilt.

    But, I wouldn't see this as necessary upon a KMShost (unless the KMShost is malfunctioning and isn't valid itself)

    You will find several references to rebuilding tokens.dat, as a resolution for client machines, and also retail licensed machines.

    I wouldn't rebuild tokens.dat on a KMShost.

    For that particular hresult code, I get these hits:

    http://support.microsoft.com/kb/931276/en-us

    http://support.microsoft.com/kb/950755/en-us

    Also, this particular machine might have an underpinning issue in the SLIC table or the OEM marker in firmware/BIOS, you can check that by using the mgadiag utility.
    If a machine is missing the SLIC table or OEM marker in bios, VL channel products may fail to activate.
    A machine without a valid SLIC table or bios marker, has either been incorrectly built by the manufacturer, or, it was never licensed for Windows by the OEM. Only the OEM can fix that. If this is your issue, it may be simpler to apply a Retail license to that machine.


    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!)




    • Edited by DonPick Wednesday, November 20, 2013 12:09 PM
    • Marked as answer by Cloud_TS Monday, November 25, 2013 1:07 PM
    Wednesday, November 20, 2013 12:02 PM
  • I'm having this same issue again with another PC this year. Again we have 100's of this same model PC in our district, and we are using the same KMS key for all our PC's. Just this one refuses to activated with the 0xc004e003 error code.

    I have been going through the answers at http://support2.microsoft.com/kb/950755

    1. Use the "Change Product Key" feature - does not work. I have tried re-entering our key multiple times.

    2. Restore your computer to an earlier date or time - It's an image. I have re-imaged the PC with a fresh install of Windows multiple times. This same image works and activates fine on hundreds of other PC's in our district. There isn't a system restore date on it, because it's an image of a fresh install of Windows 7.

    3. Activate over telephone - This is an odd one. I tried entering "slui.exe 4" at the command line, and a window pops up asking you to select the nearest phone center to your location. The drop-down box to select a location is grayed out and stuck on Afghanistan. I can't change it, so I can't activate over phone.

    Last year I sent the affected machine back for recycling. I hope I don't have to recycle this one too. I just wanted to let you know that this problem hasn't been fixed yet.


    check this machine, using the mgadiag utility from MSFT.
    if mgadiag reports "no SLIC table" or "Windows marker version: N/A", the pc mainboard is missing a necessary firmware component, and only the manufacturer can resolve that.

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table
    Windows marker version: N/A

    Some suggestions, should you find this, are to instead of KMS pkey, use MAK pkey, and activate the MAK with MSFT.

     

    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!)

    • Marked as answer by iofhua1 Thursday, October 2, 2014 5:26 PM
    Wednesday, October 1, 2014 9:26 PM

All replies

  • Hi

    This may be a little help to you.

    How to rebuild the Tokens.dat file when you troubleshoot Windows activation issues

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

    For licensing related issue, you’d better contact Microsoft licensing team. In the United States and Canada, you may call the licensing team directly at 1-800-426-9400 (select option 4), Monday through Friday, 6:00 A.M. to 5:30 P.M. (PST) to speak directly to a Microsoft licensing specialist. In this way, you will know the detailed information about license.

    Worldwide customers can use the Guide to Worldwide Microsoft Licensing Sites http://www.microsoft.com/licensing/worldwide.aspx to find contact information in their locations.

    Thanks for your understanding!

    Regards,


    Ada Liu
    TechNet Community Support


    • Edited by v-Ada Friday, November 15, 2013 12:33 PM
    Friday, November 15, 2013 12:24 PM
  • While that page is helpful in showing someone how to rebuild the tokens.dat file, what I want to know is what the tokens.dat file is used for, why I need to rebuild it, and whether or not it is safe to do this. I don't want to go blindly changing settings like this without knowing what I'm doing.


    • Edited by iofhua1 Friday, November 15, 2013 1:48 PM
    Friday, November 15, 2013 1:48 PM
  • Hi,

    Maybe you have an misunderstanding about the issue. You may have to reset the activation components in the specific pc.

    The Tokens.dat is a digitally signed file, which stores most of the Windows activation files.

    The problem you encountered may be related to the activation component, so the steps is to reinstall the activation components and then  generate a new tokens.dat file for re-activation successfully.

    Hope this helps,


    Ada Liu
    TechNet Community Support

    • Marked as answer by Cloud_TS Monday, November 25, 2013 1:06 PM
    Wednesday, November 20, 2013 12:58 AM
  • as Ada says, tokens.dat is the encrypted store for licensing data.
    sometime, this store becomes "corrupt" and needs to be rebuilt.

    But, I wouldn't see this as necessary upon a KMShost (unless the KMShost is malfunctioning and isn't valid itself)

    You will find several references to rebuilding tokens.dat, as a resolution for client machines, and also retail licensed machines.

    I wouldn't rebuild tokens.dat on a KMShost.

    For that particular hresult code, I get these hits:

    http://support.microsoft.com/kb/931276/en-us

    http://support.microsoft.com/kb/950755/en-us

    Also, this particular machine might have an underpinning issue in the SLIC table or the OEM marker in firmware/BIOS, you can check that by using the mgadiag utility.
    If a machine is missing the SLIC table or OEM marker in bios, VL channel products may fail to activate.
    A machine without a valid SLIC table or bios marker, has either been incorrectly built by the manufacturer, or, it was never licensed for Windows by the OEM. Only the OEM can fix that. If this is your issue, it may be simpler to apply a Retail license to that machine.


    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!)




    • Edited by DonPick Wednesday, November 20, 2013 12:09 PM
    • Marked as answer by Cloud_TS Monday, November 25, 2013 1:07 PM
    Wednesday, November 20, 2013 12:02 PM
  • I'm having this same issue again with another PC this year. Again we have 100's of this same model PC in our district, and we are using the same KMS key for all our PC's. Just this one refuses to activated with the 0xc004e003 error code.

    I have been going through the answers at http://support2.microsoft.com/kb/950755

    1. Use the "Change Product Key" feature - does not work. I have tried re-entering our key multiple times.

    2. Restore your computer to an earlier date or time - It's an image. I have re-imaged the PC with a fresh install of Windows multiple times. This same image works and activates fine on hundreds of other PC's in our district. There isn't a system restore date on it, because it's an image of a fresh install of Windows 7.

    3. Activate over telephone - This is an odd one. I tried entering "slui.exe 4" at the command line, and a window pops up asking you to select the nearest phone center to your location. The drop-down box to select a location is grayed out and stuck on Afghanistan. I can't change it, so I can't activate over phone.

    Last year I sent the affected machine back for recycling. I hope I don't have to recycle this one too. I just wanted to let you know that this problem hasn't been fixed yet.


    • Edited by iofhua1 Wednesday, October 1, 2014 6:14 PM
    Wednesday, October 1, 2014 6:13 PM
  • I'm having this same issue again with another PC this year. Again we have 100's of this same model PC in our district, and we are using the same KMS key for all our PC's. Just this one refuses to activated with the 0xc004e003 error code.

    I have been going through the answers at http://support2.microsoft.com/kb/950755

    1. Use the "Change Product Key" feature - does not work. I have tried re-entering our key multiple times.

    2. Restore your computer to an earlier date or time - It's an image. I have re-imaged the PC with a fresh install of Windows multiple times. This same image works and activates fine on hundreds of other PC's in our district. There isn't a system restore date on it, because it's an image of a fresh install of Windows 7.

    3. Activate over telephone - This is an odd one. I tried entering "slui.exe 4" at the command line, and a window pops up asking you to select the nearest phone center to your location. The drop-down box to select a location is grayed out and stuck on Afghanistan. I can't change it, so I can't activate over phone.

    Last year I sent the affected machine back for recycling. I hope I don't have to recycle this one too. I just wanted to let you know that this problem hasn't been fixed yet.


    check this machine, using the mgadiag utility from MSFT.
    if mgadiag reports "no SLIC table" or "Windows marker version: N/A", the pc mainboard is missing a necessary firmware component, and only the manufacturer can resolve that.

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table
    Windows marker version: N/A

    Some suggestions, should you find this, are to instead of KMS pkey, use MAK pkey, and activate the MAK with MSFT.

     

    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!)

    • Marked as answer by iofhua1 Thursday, October 2, 2014 5:26 PM
    Wednesday, October 1, 2014 9:26 PM
  • I ran mgadiag on the machine and that's what I got. It says:

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: no, invalid Windows marker
    Windows marker version: N/A

    I was able to activate it with a MAK key. So there is something wrong with the BIOS on this machine? Thank you for your help.

    Thursday, October 2, 2014 5:26 PM
  • The SLIC Table is installed at the factory by a major manufacturer such as Dell.  It is used in an OEM SLP install to self activate the machine.  If you are using a KMS install, you activate via a local server and do not need the SLIC Table.  I would try posting the entire results of your diagnostic in a new thread to the Windows 7 Genuine Issues forum because there may be a technical reason that the activation is failing.

    Please do not read this sentence. Please ignore the previous sentence.

    Friday, October 3, 2014 1:57 PM
  • I ran mgadiag on the machine and that's what I got. It says:

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: no, invalid Windows marker
    Windows marker version: N/A

    I was able to activate it with a MAK key. So there is something wrong with the BIOS on this machine? Thank you for your help.

    Yes, the necessary markers in BIOS are missing. This can only be implanted by the computer manufacturer.Without these markers in BIOS, KMS licenses will *not* activate, because KMSclient licenses require the markers to be present.

    This is because Volume Licensing for Windows Client OS requires that the computer "qualify" for VL by having a correctly applied "business/professional" edition from the OEM, and the markers are how that is confirmed.

    MAK doesn't perform the same checks for markers, but, you are still required to have a qualifying OEM OS.

    VL OS licenses for Windows Client OS are upgrades (over the OEM license) - VL licenses are not "full" licenses.

    Ensure that you are correctly complying with your VL agreement, or you run the risk of being unlicensed for such computers.


    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!)

    Saturday, October 4, 2014 6:44 AM
  • If you are using a KMS install, you activate via a local server and do not need the SLIC Table.   

    This is not correct.

    For KMS activations, both the SLIC table, and, BIOS markers must be present, or KMS client activation will fail.

    Typically, if the SLIC table is missing or BIOS markers are absent, the activation error: 0xC004F035 will occur: http://support.microsoft.com/kb/938450 


    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!)


    • Edited by DonPick Saturday, October 4, 2014 6:49 AM
    Saturday, October 4, 2014 6:48 AM