none
Server 2008 (NOT R2) no longer genuine..this is a DC..need help RRS feed

  • Question

  • We had a working DC a couple weeks of ago but now when we login it keeps asking for a license.   So far we have tried the following in the order listed:

    1.  disabling the Plug-n-Plug

    2. changing the security on the Plug-n-play via gpo

    3. http://support.microsoft.com/kb/978305  resetting the permissions in the registry.

    4. http://social.microsoft.com/forums/en-US/genuinevista/thread/9b1e5560-bb0c-493c-a5bf-0e7e03b86538/ resetting the tokens.dat

    Still no go and getting an Error code of 0X8007000D when running slmgr.vbs -ipk

    If I run slui and then try changing the code to a KMS code I get the same error as above.  I then tried running the MGADIAG and the output is below.  I have tried both using a known good KMS key and also a known good MAK key.   Really need some help here.  Thanks

     

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: N/A, hr=0x8007000d
    Windows Product Key Hash: N/A, hr=0x8007000d
    Windows Product ID: 55041-339-2111367-76086
    Windows Product ID Type: 7
    Windows License Type: Volume KMS Server
    Windows OS version: 6.0.6002.2.00020110.2.0.007
    ID: {0B0B10F2-B0A4-459A-BC13-6310F82256F2}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: Registered, 1.9.42.0
    Signed By: Microsoft
    Product Name: Windows Server (R) 2008 Standard
    Architecture: 0x00000000
    Build lab: 6002.vistasp2_gdr.101014-0432
    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-80041013_025D1FF3-229-80041013_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 7.0; Win32)
    Default Browser: C:\Program Files\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\linkinfo.dll[Hr = 0x80070002]

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{0B0B10F2-B0A4-459A-BC13-6310F82256F2}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6002.2.00020110.2.0.007</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-BBBBB</PKey><PID>55041-339-2111367-76086</PID><PIDType>7</PIDType><SID>S-1-5-21-1174042771-2693432674-1401762280</SID><SYSTEM><Manufacturer>HP</Manufacturer><Model>ProLiant DL360 G6</Model></SYSTEM><BIOS><Manufacturer>HP</Manufacturer><Version>P64</Version><SMBIOSVersion major="2" minor="6"/><Date>20100113000000.000000+000</Date></BIOS><HWID>5C400800010000FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05: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(1000, 9) (null): The data is invalid.

    Windows Activation Technologies-->
    N/A

    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   HP      ProLiant
      FACP   HP      ProLiant
      SRAT   HP      Proliant
      HPET   HP      ProLiant
      MCFG   HP      ProLiant
      SPCR   HP      SPCRRBSU
      FFFF   HP      ProLiant
      SPMI   HP      ProLiant
      ERST   HP      ProLiant
      FFFF   HP      ProLiant
      BERT   HP      ProLiant
      HEST   HP      ProLiant
      DMAR   HP      ProLiant
      SSDT   HP  CRSPCI0
      SSDT   HP  CRSPCI0
      SSDT   HP  CRSPCI0
      SSDT   HP  CRSPCI0
      SSDT   HP  CRSPCI0

     

    Wednesday, August 24, 2011 5:08 PM

Answers

  • Solved this:

    File Mismatch: C:\Windows\system32\linkinfo.dll[Hr = 0x80070002]

    Turning on Desktop Experience per:

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

     I then turned reset Plug-N-Play back to Automatic, did all Microsoft updates and loaded the new Proliant Service Pack.  Then I was able use a MAK key again.  Weird.  Not

     


    • Marked as answer by Darin Smith MS Wednesday, August 31, 2011 9:01 PM
    Monday, August 29, 2011 6:13 PM

All replies

  • "DKHGeek" wrote in message news:ec0b7631-b5da-495a-b678-8d96ecd6528a...

    We had a working DC a couple weeks of ago but now when we login it keeps asking for a license.   So far we have tried the following in the order listed:

    1.  disabling the Plug-n-Plug

    2. changing the security on the Plug-n-play via gpo

    3. http://support.microsoft.com/kb/978305  resetting the permissions in the registry.

    4. http://social.microsoft.com/forums/en-US/genuinevista/thread/9b1e5560-bb0c-493c-a5bf-0e7e03b86538/ resetting the tokens.dat

    Still no go and getting an Error code of 0X8007000D when running slmgr.vbs -ipk

    If I run slui and then try changing the code to a KMS code I get the same error as above.  I then tried running the MGADIAG and the output is below.  I have tried both using a known good KMS key and also a known good MAK key.   Really need some help here.  Thanks

     

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: N/A, hr=0x8007000d
    Windows Product Key Hash: N/A, hr=0x8007000d
    Windows Product ID: 55041-339-2111367-76086
    Windows Product ID Type: 7
    Windows License Type: Volume KMS Server
    Windows OS version: 6.0.6002.2.00020110.2.0.007

    Licensing Data-->
    C:\Windows\system32\slmgr.vbs(1000, 9) (null): The data is invalid.

     

     

    The problem appears to be with the Licensing Store....
    Please try the below steps to recreate the Licensing Store files. This may resolve the issue.

    1) Open an Internet Browser window.
    2) Type: %windir%\system32 into the browser address bar.
    3) Find the file CMD.exe
    4) Right-Click on CMD.exe and select 'Run as Administrator'
    5) Type: net stop slsvc (it may ask you if you are sure, select yes - or it may say that it's not running - this is OK)
    6) Type: cd %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareLicensing
    7) Type: rename tokens.dat tokens.bar
    8) Type: cd %windir%\system32
    9) Type: net start slsvc
    10) Type: cscript slmgr.vbs -rilc (It may take a long time for this to complete, please be patient)

    Reboot TWICE
    If necessary, then you may be required to enter the Product Key and/or Activate.

    Reboot

    Once complete, please post back with a new MGADiag report



    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, August 24, 2011 9:21 PM
    Moderator
  • Rebooted twice and still no go.  This was the same thing that I did in Step 4 from the beginning.  It does ask to Activate as soon as I login and once I put in ANY known good key (KMS or MAK) it gives me this error:

    Windows Activation Error:

       A problem occurred when Windows tried to activate.  Error Code 0X8007000d. 

    and here again is the MGADIAGs but this time using a MAK key:

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: N/A, hr=0x8007000d
    Windows Product Key Hash: N/A, hr=0x8007000d
    Windows Product ID: 55041-098-5547185-76759
    Windows Product ID Type: 6
    Windows License Type: Volume MAK
    Windows OS version: 6.0.6002.2.00020110.2.0.007
    ID: {0B0B10F2-B0A4-459A-BC13-6310F82256F2}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: Registered, 1.9.42.0
    Signed By: Microsoft
    Product Name: Windows Server (R) 2008 Standard
    Architecture: 0x00000000
    Build lab: 6002.vistasp2_gdr.101014-0432
    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-80041013_025D1FF3-229-80041013_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 7.0; Win32)
    Default Browser: C:\Program Files\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\linkinfo.dll[Hr = 0x80070002]

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{0B0B10F2-B0A4-459A-BC13-6310F82256F2}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6002.2.00020110.2.0.007</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-BBBBB</PKey><PID>55041-098-5547185-76759</PID><PIDType>6</PIDType><SID>S-1-5-21-1174042771-2693432674-1401762280</SID><SYSTEM><Manufacturer>HP</Manufacturer><Model>ProLiant DL360 G6</Model></SYSTEM><BIOS><Manufacturer>HP</Manufacturer><Version>P64</Version><SMBIOSVersion major="2" minor="6"/><Date>20100113000000.000000+000</Date></BIOS><HWID>5C400800010000FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05: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(1000, 9) (null): The data is invalid.

    Windows Activation Technologies-->
    N/A

    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   HP      ProLiant
      FACP   HP      ProLiant
      SRAT   HP      Proliant
      HPET   HP      ProLiant
      MCFG   HP      ProLiant
      SPCR   HP      SPCRRBSU
      FFFF   HP      ProLiant
      SPMI   HP      ProLiant
      ERST   HP      ProLiant
      FFFF   HP      ProLiant
      BERT   HP      ProLiant
      HEST   HP      ProLiant
      DMAR   HP      ProLiant
      SSDT   HP  CRSPCI0
      SSDT   HP  CRSPCI0
      SSDT   HP  CRSPCI0
      SSDT   HP  CRSPCI0
      SSDT   HP  CRSPCI0

     

     

    I also am getting this under the Licensing tab for the MGA Diag tool:

    C:\windows\system32\slmgr.vbs(1000,9)(null): The data is invalid


    Thursday, August 25, 2011 8:26 PM
  • You might try posting your inquiry to the Windows Server experts in the Windows Server Forum.
    Carey Frisch
    Thursday, August 25, 2011 8:30 PM
    Moderator
  • "DKHGeek" wrote in message news:45e2ecac-b0c4-4923-94ab-5301306b4af8...

    Rebooted twice and still no go.  This was the same thing that I did in Step 4 from the beginning.  It does ask to Activate as soon as I login and once I put in ANY known good key (KMS or MAK) it gives me this error:

    Windows Activation Error:

       A problem occurred when Windows tried to activate.  Error Code 0X8007000d.

    and here again is the MGADIAGs but this time using a MAK key:

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: N/A, hr=0x8007000d
    Windows Product Key Hash: N/A, hr=0x8007000d
    Windows Product ID: 55041-098-5547185-76759
    Windows Product ID Type: 6
    Windows License Type: Volume MAK
    Windows OS version: 6.0.6002.2.00020110.2.0.007

    File Scan Data-->
    File Mismatch: C:\Windows\system32\linkinfo.dll[Hr = 0x80070002]

    Other data-->
    SYSTEM><Manufacturer>HP</Manufacturer><Model>ProLiant DL360 G6</Model></SYSTEM><BIOS><Manufacturer>HP</Manufacturer><Version>P64</Version><SMBIOSVersion major="2" minor="6"/><Date>20100113000000.000000+000</Date></BIOS

     

    Licensing Data-->
    C:\Windows\system32\slmgr.vbs(1000, 9) (null): The data is invalid.

     

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

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table


     
     
    I’m not sure about MAK Keys, but KMS Keys rely on the presence of a SLIC table in the BIOS to validate the fact that the installation is an Upgrade, rather than a clean install.
    If this is the case with MAK Keys also, then that may be the cause of your problem.
     
    There is also a file mismatch present -
    File Mismatch: C:\Windows\system32\linkinfo.dll[Hr = 0x80070002]
    Please look for the file, and see if it exists – if not, then try copying it from another system and pasting into the affected one – an SFC /SCANNOW may also be able to accomplish a repair/replacement of the file.
     
    Darin (the MS forum owner) may be able to throw more light on the BIOS subject, but in  the meanwhile it may be worth trying a BIOS update/refresh to see if that helps.
     
    In summary, then...
    1) try an SFC to repair the file mismatch – run an MGADiag report, and see f the mismatch is fixed.
    2) if not fixed, then try copy/pasting from another system
    3) If that fixes the mismatch, but the problem remains,  try the Licensing store recreation again. – post another MGADiag afterwards.
    4) Try a BIOS update, and post another MGADiag.
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Thursday, August 25, 2011 8:47 PM
    Moderator
  • "Noel D Paton" wrote in message news:b7eb3371-9c1c-4d96-b704-002d6f1681c7...
     
    There is also a file mismatch present -
    File Mismatch: C:\Windows\system32\linkinfo.dll[Hr = 0x80070002]
    Please look for the file, and see if it exists – if not, then try copying it from another system and pasting into the affected one – an SFC /SCANNOW may also be able to accomplish a repair/replacement of the file.
     
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
     
     
    Doing a little digging, it appears that a linkinfo.dll file is also implicated in a number of malware infections.
     
    When was the last time you ran a full system AV scan on the machine? Is it possible that the file was removed by a false-positive detection by the AV?
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Friday, August 26, 2011 10:26 AM
    Moderator
  • Solved this:

    File Mismatch: C:\Windows\system32\linkinfo.dll[Hr = 0x80070002]

    Turning on Desktop Experience per:

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

     I then turned reset Plug-N-Play back to Automatic, did all Microsoft updates and loaded the new Proliant Service Pack.  Then I was able use a MAK key again.  Weird.  Not

     


    • Marked as answer by Darin Smith MS Wednesday, August 31, 2011 9:01 PM
    Monday, August 29, 2011 6:13 PM
  • "DKHGeek" wrote in message news:512124e9-0714-4796-a775-b6d8e825b002...

    Solved this:

    File Mismatch: C:\Windows\system32\linkinfo.dll[Hr = 0x80070002]

    Turning on Desktop Experience per:

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

    I then turned reset Plug-N-Play back to Automatic, did all Microsoft updates and loaded the new Proliant Service Pack.  Then I was able use a MAK key again.  Weird.  Not

     


     
     
    Please post a new MGADiag report – there is no way that the Desktop Experience should affect the WGA status (at least, that I am aware of) – what made you try it?
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Monday, August 29, 2011 9:26 PM
    Moderator