none
KMS activation error 0x80070426

    Question

  • We have a few Server 2008 R2 Standard Edition servers that have recently begun to fail KMS activation. Many other equivalent servers in the environment continue to activate with no problem. There are no errors reported on the KMS host side.

    I'm pasting the report from MGADiag.exe 1.9.0027.0 below. Please let me know if other information is required, and thanks!

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->

    Validation Code: 50
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-YTKYR-T4X34-R7VHC
    Windows Product Key Hash: /uTAWFVa/vPwhjyCok7KW4mCaqQ=
    Windows Product ID: 00477-001-0000421-84473
    Windows Product ID Type: 1
    Windows License Type: KMS Client
    Windows OS version: 6.1.7601.2.00030010.1.0.007
    ID: {A6B202BC-3FAE-4269-9F24-DA51D6031368}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows Server 2008 R2 Standard
    Architecture: 0x00000009
    Build lab: 7601.win7sp1_ldr.160210-0600
    TTS Error:
    Validation Diagnostic:
    Resolution Status: N/A

    Vista WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002

    Windows XP Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    File Exists: No
    Version: N/A, hr = 0x80070002
    WgaTray.exe Signed By: N/A, hr = 0x80070002
    WgaLogon.dll Signed By: N/A, hr = 0x80070002

    OGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    OGAExec.exe Signed By: N/A, hr = 0x80070002
    OGAAddin.dll Signed By: N/A, hr = 0x80070002

    OGA Data-->
    Office Status: 109 N/A
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files (x86)\Citrix\system32\iexplore.exe
    Download signed ActiveX controls: Prompt
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Allowed
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Allowed
    Script ActiveX controls marked as safe for scripting: Allowed

    File Scan Data-->
    File Mismatch: C:\Windows\system32\wat\watadminsvc.exe[Hr = 0x80070003]
    File Mismatch: C:\Windows\system32\wat\npwatweb.dll[Hr = 0x80070003]
    File Mismatch: C:\Windows\system32\wat\watux.exe[Hr = 0x80070003]
    File Mismatch: C:\Windows\system32\wat\watweb.dll[Hr = 0x80070003]

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{A6B202BC-3FAE-4269-9F24-DA51D6031368}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00030010.1.0.007</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-R7VHC</PKey><PID>00477-001-0000421-84473</PID><PIDType>1</PIDType><SID>S-1-5-21-575433757-2849991761-278737117</SID><SYSTEM><Manufacturer>VMware, Inc.</Manufacturer><Model>VMware Virtual Platform</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies LTD</Manufacturer><Version>6.00</Version><SMBIOSVersion major="2" minor="4"/><Date>20131022000000.000000+000</Date></BIOS><HWID>9E290200010000FA</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Standard Time(GMT-06:00)</TimeZone><iJoin>1</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  

    Spsys.log Content: 0x80070002

    Licensing Data-->
    C:\Windows\system32\slmgr.vbs(1333, 5) (null): The service has not been started.

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: N/A
    HealthStatus: 0x0000000000000000
    Event Time Stamp: N/A
    ActiveX: Not Registered - 0x80040154
    Admin Service: Not Registered - 0x80040154
    HealthStatus Bitmask Output:


    HWID Data-->
    N/A, hr = 0x8007000d

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information:
      ACPI Table Name    OEMID Value    OEMTableID Value
      APIC            PTLTD              APIC  
      FACP            INTEL         440BX   
      SRAT            VMWARE        MEMPLUG
      WAET            VMWARE        VMW WAET
      HPET            VMWARE        VMW HPET
      BOOT            PTLTD         $SBFTBL$
      MCFG            PTLTD         $PCITBL$

    Tuesday, March 22, 2016 9:00 PM

Answers

  • Thanks for the reply Tao. In our case, the Software Protection service was already running and also set to Automatic startup type.

    The fix appears to have been to follow instructions from https://support.microsoft.com/en-us/kb/2736303 to rename the token.dat file. Once the token.dat file was recreated, the Windows product key for Server 2008 R2 Standard Edition (YC6KT-GKW9T-YTKYR-T4X34-R7VHC) had to be re-entered. Volume license product keys are available publicly and can be found here: https://technet.microsoft.com/en-us/library/jj612867.aspx. Once the server rebooted, the OS was activated automatically by our KMS host.

    • Proposed as answer by DonPick Thursday, March 24, 2016 9:58 PM
    • Marked as answer by tdoan Thursday, March 24, 2016 10:11 PM
    Thursday, March 24, 2016 9:39 PM

All replies

  • Hi tdoan,

     

    Based on your description, I noticed the error message:

     

    "Licensing Data-->

       C:\Windows\system32\slmgr.vbs(1333, 5) (null): The service has not been started. "

     

    Please restart the service and check the result.

     

    In addition, for more about the error code, please refer to the link:

    Activation Error Codes for Volume Activation:

    https://technet.microsoft.com/en-us/library/dn502528.aspx

     

    Best Regards,

    Tao


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Wednesday, March 23, 2016 11:34 AM
    Moderator
  • Thanks for the reply Tao. In our case, the Software Protection service was already running and also set to Automatic startup type.

    The fix appears to have been to follow instructions from https://support.microsoft.com/en-us/kb/2736303 to rename the token.dat file. Once the token.dat file was recreated, the Windows product key for Server 2008 R2 Standard Edition (YC6KT-GKW9T-YTKYR-T4X34-R7VHC) had to be re-entered. Volume license product keys are available publicly and can be found here: https://technet.microsoft.com/en-us/library/jj612867.aspx. Once the server rebooted, the OS was activated automatically by our KMS host.

    • Proposed as answer by DonPick Thursday, March 24, 2016 9:58 PM
    • Marked as answer by tdoan Thursday, March 24, 2016 10:11 PM
    Thursday, March 24, 2016 9:39 PM