Office Activation Code 0xc004f074 Kms

Applies to: Office 2013 Topic Last Modified: 2017-09-29 Summary: Explains how to troubleshoot common errors for KMS or MAK-based activation of Office 2013. Audience: IT Professionals If you are a user troubleshooting a personal Office 2013 install, review the list of. If you are an admin troubleshooting Office 365 ProPlus activation and licensing, see instead. If you are an admin troubleshooting a Volume license edition of Office 2013, you’re at the right place, keep reading. Setting up volume activation with Office 2013 by using Key Management Service (KMS) or Multiple Activation Key (MAK) can be challenging. Use these steps to troubleshoot the most common issues.

1. Office 2013 Kms Activation Error Code 0xc004f074
2. Office 2010 Kms Activation Error Code 0xc004f074

Many of the solutions include running the Office Software Protection Platform script ( ospp.vbs), which you can find either in the '%programfiles% microsoft office office15' or the '%programfiles(x86)% microsoft office office15' folder of the client computer. You have to run it at the administrative command prompt. You can also use the Software License Manager script ( Slmgr.vbs) to configure and manage volume activation. For detailed information about these scripts, see. In this article:.

This section lists common activation issues with Office 2013 KMS. KMS activation issues can be due to a misconfiguration on one or more of the following items:. Office client. Network/DNS. KMS host To quickly identify your KMS trouble spots, use either the Office Client KMS activation diagnostic or Office KMS Host Activation diagnostic tool to analyze your environment for known issues. These diagnostic tools automate almost all of the troubleshooting steps available for KMS issues and provide a detailed report with recommendations on how to fix the detected issues. You should always analyze the client first by using the Office Client KMS activation diagnostic tool, even if you feel you have a KMS Host configuration problem.

It’ll determine if your changes need to occur on the client, your network, or your KMS host. If the Office Client KMS activation diagnostic tool indicates you have KMS host issues, you should then run the Office KMS Host Activation diagnostic tool. To use the Office Client KMS activation diagnostic tool. As a local administrator, log into any Office client that is unable to activate using KMS activation. Go to and sign in to the Microsoft Support Diagnostics Self-Help portal with your Microsoft Account credentials. On the New Session page, choose Office Client KMS activation diagnostic. Enter a name in Session Name text box and then choose Create.

Office 2013 Kms Activation Error Code 0xc004f074

To start the analysis, choose Download. When you are prompted, choose Run or Save File. If you choose Save File, you can later run the file from the folder where you saved it. When prompted to select the computer on which to run the diagnostic, choose This Computer, and then choose Next. On the next page choose Start.

When the diagnostic displays an alert indicating a report has been saved, choose Open Report. Review the details listed in the report Summary section, and then review the problems listed in the Issues Detected section and follow the recommendations provided under Recommended steps and related resources. To use the Office KMS Host Activation diagnostic tool. As a local administrator, log into your Office KMS host computer. Go to and sign in to the Microsoft Support Diagnostics Self-Help portal with your Microsoft Account credentials. On the New Session page, choose Office Client KMS Host Activation diagnostic. Enter a name in Session Name text box and then choose Create.

To start the analysis, choose Download. When you are prompted, choose Run or Save File. If you choose Save File, you can later run the file from the folder where you saved it.

When prompted to select the computer on which to run the diagnostic, choose This Computer, and then choose Next. On the next page choose Start. A report is automatically generated and opened in your browser. Review the information listed in the Summary section and then review the problems listed in the Details section. Follow the recommendations provided under Action needed or comment for the items flagged with ‘ Attention Required’ in the Result column. Error codes help you troubleshoot activation issues. If you see a dialog box that contains an activation notification, an error code is usually displayed at the lower corner.

You can then run ospp.vbs /ddescr together with the error code to see the text of the error message. The text will help you better understand the issue and what to do to fix it.

Another way to obtain an error code is to run ospp.vbs /act on the client computer to manually activate Office. If activation fails, an error code will be shown. All Office 2013 volume-licensed products have a Generic Volume License Key (GVLK) preinstalled to activate against an Office 2013 KMS host.

If you entered a MAK key for a product and you want to change the activation method back to KMS, use the appropriate KMS client GVLK. For more information, see. The recommended way to enter the key is by using the Volume Activation Management Tool,. You can also use ospp.vbs /inpkey to enter the key. For Office 2013 suites, only one key is required for all the products in the suite. For example, if you use Office Professional Plus, you must enter only the Office Professional Plus 2013 key for the complete suite.

For a complete listing of the keys, see.

Given: Microsoft Windows Server 2008 R2 Enterprise 64-bit, all the latest security updates applied. KMS service set up and running, all the recommended updates applied (to handle possible activation issues for Windows 8 etc) Microsoft Office 2013 Standard deployed on the server mentioned above and on workstations on intranet, volume licensing in effect (proper KMS key for activation of Microsoft Ofice 2013 has been entered). Problem: I can't activate MS Office 2013 installation running on the same server where KMS service is being run. There are no entries in KMS event log related to this failure. Everything was restarted, reinstalled etc several times already (including installing 32-bit and 64-bit versions of the Office).

Note that KMS service works fine. All the workstations activate their MS Office 2013 without a single glitch. However, the installation on the server itself refuses to use KMS. Firewall is set up correctly. Host name is provided correctly (via 'cscript ospp.vbs /sethst:hostname', I tried all the hostnames relevant, starting with that working for activating from workstations). All the other documented required checks/actions are performed as well prior to activating.

Judging by what I include below, ospp.vbs hints the above can't be activated via KMS. Is it indeed the case (i.e., I should use MAK activation instead), or I am still missing something? I followed the and related articles, and currently on Technet there are no advice pieces whether the above is at all possible. Office 2013 seems to use DNS lookups exclusively for identifying its KMS server.

Office 2010 Kms Activation Error Code 0xc004f074

That was not the case with earlier KMS-activated versions of Office. What that means is that you cannot use names like localhost or 127.0.0.1 as your KMS server. You actually have to use the full ActiveDirectory/DNS name of your KMS server even if it happens to be the same machine. Oddly enough the Windows 7 activation script does not exhibit this behaviour. I haven't tested Windows 8 or 8.1 yet.

Before you attempt Office 2013 activation, please make sure that you can DNS look up your KMS host (even if it's the same machine!) with the nslookup command on the host where you're trying to activate Office 2013 (yes, even if it's all on the same machine). Finally, do not specify the port number with cscript ospp.vbs /sethst. The command isn't smart enough to understand that ':1688' is a port number reference and will literally use 'hostname:1688' as the hostname, instead of 'hostname' as the hostname and 1688 as the port number. I believe there's a separate command-line switch that sets the port, but you don't need to set it explicitly unless you actually attach the KMS service to a TCP port other than the default 1688.