none
Key Could Not Be Validated RRS feed

  • Question

  • Hello,

    When I try to add my MAK Key to the Volume Activation Management Tool, I get the following error:

    The Product Key You Entered Could Not Be Validated.
    Please check the key and try again.

    If you have validated that the product key is correct, you may need to update this version of VAMT.

    I know the MAK is valid because I just activated it on another machine. Any ideas on how to fix this? I'm running VAMT 1.1.264.0

    Thanks,

    Friday, July 24, 2009 7:58 PM

Answers

  • Hello Charlie,
    The output is not from a MAK activated machine, this is from a KMS client machine.
    You can capture the output of the text content directly from the dialog box by using Control+C keys( Copies the output from the dialog box into the clipboard which you can then paste.  Most error message dialogs support this as well, with current products.

    The question is really whether the MAK key is for Windows Server 2008 or Windows Server 2008 R2?
    VAMT was updated to be able to handle Windows Server 2008 R2 keys which is most likely occurance of this erorr message.
    VAMT 1.2 is included in the Windows AIK for Windows 7\Windows Server 2008 R2
    Thanks, Darrell Gorter This posting is provided "AS IS" with no warranties, and confers no rights
    • Marked as answer by cgehr Thursday, July 8, 2010 5:59 PM
    Wednesday, November 11, 2009 6:56 PM

All replies

  • Hello cgehr,
    On the machine you activated with this key,
    Open an elevated CMD prompt.
    Run slmgr /dlv and report back the output
    Thanks, Darrell Gorter This posting is provided "AS IS" with no warranties, and confers no rights
    • Marked as answer by cgehr Thursday, July 8, 2010 5:59 PM
    • Unmarked as answer by cgehr Thursday, July 8, 2010 5:59 PM
    Wednesday, July 29, 2009 4:06 AM
  • I am having this same issue, here is my output from the command above:


    I wish i could upload the actual screenshot.

    Software licensing service verions: 6.6.6002.18005
    Name Windows SErver, ServStandare edition
    Description windows operating system - windows server
    volume_kmsclient chanel
    activation ID: ad25542d4-9454-4c6d-8a44-30f11ee96989
    Application Id: 55c92734-d682-4d71-983e-d6ecf16009f
    extended path: 6as5d4f6sd-asd65f46as5d4f-s6ad54f65asd4f-a6sd5f465asd (let me know if really you need this specific information)
    installation id: a;sldkfj90wej2jkef09jisakfj02j02 (let me know if really you need this specific information)
    partial product key: BFGM2
    License Status: initial grace period
    Time REmaining: 86280 minute(s) (59 days(s))

    key mgmt service client information
    client machine id (cmdi): ww2039ru2k3jr0293rj23i0jr9023jr0923 (let me know if really you need this specific information)
    dns auto-discovery: kms: not available
    KMS machine extended pid:
    activation interval: 120 minutes
    renewal interval: 10080



    That partial product key field is not part of my actual key.  could that be an issue?
    There is not a KMS server, and will not be one.
    this is a Active Directory machine with 5 other machines attached.  I h ave this same error if the other machines are on or off(tried 3 times).

    Thanks for any information.

    Charlie
    Monday, November 9, 2009 5:17 PM
  • Hello Charlie,
    The output is not from a MAK activated machine, this is from a KMS client machine.
    You can capture the output of the text content directly from the dialog box by using Control+C keys( Copies the output from the dialog box into the clipboard which you can then paste.  Most error message dialogs support this as well, with current products.

    The question is really whether the MAK key is for Windows Server 2008 or Windows Server 2008 R2?
    VAMT was updated to be able to handle Windows Server 2008 R2 keys which is most likely occurance of this erorr message.
    VAMT 1.2 is included in the Windows AIK for Windows 7\Windows Server 2008 R2
    Thanks, Darrell Gorter This posting is provided "AS IS" with no warranties, and confers no rights
    • Marked as answer by cgehr Thursday, July 8, 2010 5:59 PM
    Wednesday, November 11, 2009 6:56 PM
  • I found out that the person that actually ran my installs, was...well, using the wrong .iso.  Now we have no activation issues using the correct .iso.
    Monday, November 16, 2009 3:20 PM
  • I ended up just calling it in, but thanks for the help (I know I'm a little late though lol)
    Thursday, July 8, 2010 5:59 PM