none
KMS: Notification Reason: 0xC004F056.

    Question

  • KMS Client:

    Partial Product Key: HVTHH

    License Status: Notification

    Notification Reason: 0xC004F056.

    Any known issue?

    tnx


    • Edited by MGerio Friday, March 15, 2013 8:02 AM
    Friday, March 15, 2013 7:45 AM

Answers

  • Ah, that's a useful clarification.

    I have no Windows-activation-specific help for that error code, but, many of the activation error codes are shared/common for both Windows-activation and Office-activation.

    Is this error occurring on a healthy client machine? Is Windows activation healthy on that machine? Are there any other symptoms on that machine which suggest ill-health?

    Is your KMShost healthy and otherwise issuing activations to other clients ok?

    Some research suggests that this error code is often related to tampered or hacked or emulated activation attempts.
    I'm not suggesting that's your cause, but anti-tampering detection can sometimes be triggered when corruption or ill-health occurs.

    If this error is only affecting a single KMSclient, and other KMSclients are ok, I would suspect this particular KMSclient might be corrupted/damaged or unhealthy. As it's Windows7, you could also try the MGADiag tool, it may reveal other underlying issues.
    http://support.microsoft.com/kb/942962

    CheckSUR may also be useful as a health check for that KMSclient.
    http://support.microsoft.com/kb/947821


    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, March 16, 2013 7:33 AM
  • Hi MGerio,

    It would help the folks here if you could run the following command from an elevated command prompt on your KMS host and post the output back here:

    cscript //nologo %windir%\system32\slmgr.vbs /dlv

    This will provide important information as to the activation status of each licencing channel. It would also be useful to know what operating system the KMS host is using (i.e. Server 2008, 2008 R2 or 2012).

    Please make sure you remove/replace any hostnames from the output.

    As to the translation of your error, you can determine that by running the following from an elevated command prompt:

    slui 0x2a 0xC004F056

    Unfortunately, the descriptive text for this error is quite generic and doesn't reveal a whole lot on its own, as you can see below.

    0xC004F056

    Cheers,
    Lain

    Tuesday, March 19, 2013 2:03 PM

All replies

  • only these

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

    http://blogs.technet.com/b/odsupport/archive/2010/06/10/when-activating-office-2010-you-receive-the-error-code-0x80070005.aspx


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

    Friday, March 15, 2013 8:11 AM
  • for win 7 sir?
    Friday, March 15, 2013 8:54 AM
  • Ah, that's a useful clarification.

    I have no Windows-activation-specific help for that error code, but, many of the activation error codes are shared/common for both Windows-activation and Office-activation.

    Is this error occurring on a healthy client machine? Is Windows activation healthy on that machine? Are there any other symptoms on that machine which suggest ill-health?

    Is your KMShost healthy and otherwise issuing activations to other clients ok?

    Some research suggests that this error code is often related to tampered or hacked or emulated activation attempts.
    I'm not suggesting that's your cause, but anti-tampering detection can sometimes be triggered when corruption or ill-health occurs.

    If this error is only affecting a single KMSclient, and other KMSclients are ok, I would suspect this particular KMSclient might be corrupted/damaged or unhealthy. As it's Windows7, you could also try the MGADiag tool, it may reveal other underlying issues.
    http://support.microsoft.com/kb/942962

    CheckSUR may also be useful as a health check for that KMSclient.
    http://support.microsoft.com/kb/947821


    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, March 16, 2013 7:33 AM
  • Hi MGerio,

    It would help the folks here if you could run the following command from an elevated command prompt on your KMS host and post the output back here:

    cscript //nologo %windir%\system32\slmgr.vbs /dlv

    This will provide important information as to the activation status of each licencing channel. It would also be useful to know what operating system the KMS host is using (i.e. Server 2008, 2008 R2 or 2012).

    Please make sure you remove/replace any hostnames from the output.

    As to the translation of your error, you can determine that by running the following from an elevated command prompt:

    slui 0x2a 0xC004F056

    Unfortunately, the descriptive text for this error is quite generic and doesn't reveal a whole lot on its own, as you can see below.

    0xC004F056

    Cheers,
    Lain

    Tuesday, March 19, 2013 2:03 PM