Windows Activation Issues - 0xd000009a - Windows 2008 R2 RRS feed

  • Question

  • I posted this in the Windows 2008 area and it was suggested I post this here, so here goes:


    Winodws 2008 R2, using Windows Volume Licensing, and a KMS license activation server.

    At times, when I log in to the server, it reports that it is not a genuine copy.  I then go through the steps to make it genuine, and it then gives me the following error:

    "A problem occurred when Windows tried to activate. Error Code 0xD000009a.  for a possible resolution click More Information.  Contact your sytem administrator for assistance."

    When I click on More Information I get "the following information was found for this error: Code 0xd000009a  Description Unable to find a detailed error description.  Unknown facility code of 0x1000 (4096L) facility error: 0x9a (154L)

    If I restart, the server becomes genuine again, and then some time later, if I need to login (varying lengths of time), I get the not genuine issue again.

    If anyone can help, I'd appreciate it.  I don't find anything in the error logs to coincide with the issue

     I have downloaded the MGA Diag tool.  Here are the current results (i may need to do this when the issue happens):

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

    Validation Code: 0
    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-84418
    Windows Product ID Type: 1
    Windows License Type: KMS Client
    Windows OS version: 6.1.7600.2.00030110.0.0.007
    ID: {29F4DD95-E8A9-4FAE-9D82-A137632C9E60}(0)
    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: 7600.win7_gdr.100618-1621
    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: B4D0AA8B-543-80070002_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)\Internet Explorer\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>{46F77DC8-98AB-4A20-99DA-7A852C981732}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00030110.0.0.007</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-R7VHC</PKey><PID>00477-001-0000421-84418</PID><PIDType>1</PIDType><SID>S-1-5-21-1308426171-318996055-338928232</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>20091013000000.000000+000</Date></BIOS><HWID>87B93607018400F4</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Pacific Standard Time(GMT-08: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-->
    Software licensing service version: 6.1.7600.16385

    Name: Windows Server(R), ServerStandard edition
    Description: Windows Operating System - Windows Server(R), VOLUME_KMSCLIENT channel
    Activation ID: 68531fb9-5511-4989-97be-d11a0f55633f
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00477-00168-001-000042-03-1033-7600.0000-3212010
    Installation ID: 006390974386073346658361926593684636093263418711598693
    Partial Product Key: R7VHC
    License Status: Licensed
    Volume activation expiration: 257700 minute(s) (178 day(s))
    Remaining Windows rearm count: 1
    Trusted time: 3/23/2011 10:29:53 AM

    Key Management Service client information
        Client Machine ID (CMID): aedb0b7d-cd31-469b-9e32-95b7dc6d786b
        KMS machine name from DNS: ibprn01.domain.hidden:1688
        KMS machine extended PID: 55041-00168-313-142092-03-1033-7600.0000-0242010
        Activation interval: 120 minutes
        Renewal interval: 10080 minutes
        KMS host caching is enabled

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

    OEM Activation 1.0 Data-->

    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  


    Wednesday, March 23, 2011 5:26 PM


All replies