Troubleshoot volume activation for Office 2013
Published: February 5, 2013
Summary: Explains how to troubleshoot common errors for KMS, MAK, or Active Directory-based activation of Office 2013.
Applies to: Office 2013
Audience: IT Professionals
You can learn to troubleshoot issues that you might encounter when you activate Office 2013. Before you read this article, we recommend that you first read Volume activation methods in Office 2013, Plan volume activation of Office 2013, Deploy volume activation of Office 2013, and Configure client computers for volume activation in Office 2013. In addition, for a good understanding of volume activation, we recommend that you read Volume Activation Overview.
Important:
|
|---|
|
This information applies to volume-licensed editions of Office 2013. It does not apply to either Office Professional Plus for Office 365 or Office 365 ProPlus, both of which are licensed through subscription. |
In this article:
KMS activation issues
The client activation request count on the Office 2013 KMS host is not high enough for client computers to activate
Relevant error code: 0xC004F038
The Office 2013 KMS host must receive activation requests from at least five Office 2013 KMS clients before KMS clients on that network can be activated. If the KMS host doesn’t receive more than five requests, KMS clients won’t be activated. If you deploy Office 2013 to more than five computers, their initial activation requests will be used to build up the count. If activation fails, the computers will try to activate Office two hours later. At that time, if the KMS host has a sufficient count, activation will be successful. To trigger activation manually on the KMS client, run ospp.vbs /act. For more information about the ospp.vbs script, see Configure client computers for volume activation in Office 2013.
To determine the current count on the KMS host, at the command prompt (with administrator permissions), run the following command:
cscript slmgr.vbs /dlv 2E28138A-847F-42BC-9752-61B03FFF33CD
After Office 2013 is installed, the Office Software Protection Platform (OSPP) service automatically sends activation requests to the KMS host every two hours until activation occurs, regardless of whether Office 2013 is running. Once five of these KMS clients connect to the corporate network and successfully request activation against the KMS host, the KMS clients are activated. Clients that later connect to the corporate network are also activated. KMS clients that aren’t on the corporate network (at home, for example) become activated as soon as they connect to the network.
The Office 2013 KMS client does not activate
There might be several reasons why the Office 2013 Key Management Service (KMS) client isn’t activated. This section describes issues and how to resolve them.
The KMS host is not activated
Relevant error code: 0xC004F041
The KMS host must be activated first, and then you can activate the KMS clients. For more information, see Prepare and configure the Office KMS host in Deploy volume activation of Office 2013. On the Microsoft Office 2013 Volume License Pack website, download and run office2013volumelicensepack_en-us_x86.exe. Then, follow the steps in the Instructions section on the website.
Note:
|
|---|
|
When you enable the firewall on a KMS host, the default TCP communications port number is 1688. |
If you use slmgr.vbs, you must activate the KMS host within the command and include the following Office 2013 activation ID:
cscript slmgr.vbs /ato 2E28138A-847F-42BC-9752-61B03FFF33CD
The KMS host cannot be reached
Relevant error code: 0xC004F041
If you want the KMS clients to use auto-discovery of the KMS host, review the Windows Volume Activation Deployment Guide to make sure that the DNS configuration is correct. Ensure that the KMS host has network connectivity, and that it is reachable by the KMS clients.
As a test on the KMS client, you might want to use ospp.vbs /sethst to specify the KMS host computer name. Then, run ospp.vbs /act to send an activation request directly to the KMS host. If this is successful, KMS host auto-discovery might be the issue. Remember to use ospp.vbs /remhst to remove the KMS host name after the test is completed.
MAK activation issues
The Office 2013 client does not activate when it is connected to the network through an authenticated proxy
Independent MAK activation requires an Internet connection. If the Office 2013 client is connected to the Internet through an authenticated proxy, you must activate the client over the telephone. For more information about how to resolve this issue, see Knowledge Base article 921471: Activation fails when you try to activate Windows over the Internet.
Activation error codes
Error codes help you troubleshoot activation issues. If a user sees a dialog box that contains an activation notification, an error code might be displayed at the lower corner of the dialog box. Another way to obtain an error code is to run ospp.vbs /act on the client computer to try to activate Office. If activation fails, an error code is reported. Use ospp.vbs /ddescr together with the appropriate error code to receive the error message. For more information about the ospp.vbs script, see Configure client computers for volume activation in Office 2013.
Note:
|
|---|
|
You can complete tasks in all Office 2013 suites by using a mouse, keyboard shortcuts, or touch. For information about how to use keyboard shortcuts and touch with Office products and services, see Keyboard shortcuts and Office Touch Guide. |
General activation issues
The following are general activation issues and their solutions.
Office 2013 Volume License Pack installation incorrectly says you’ve installed Preview
When you first install the Microsoft Office 2013 Volume License Pack, you may see a dialog box that is labeled Microsoft Office 2013 Volume License Pack Preview. "Preview" is incorrect: the final release Office 2013 version is installed correctly, and functionality isn’t affected. A workaround isn’t required.
Users see notifications to activate
An activation notification dialog box usually appears when a copy of Office 2013 isn’t yet activated. An error code is displayed on the lower corner of the dialog box to help you troubleshoot activation issues. No dialog box is shown until 25 days after installation, at which time the user sees a notification dialog box. If Office 2013 has not been activated 30 days after installation, the notification dialog box contains a red title bar.
When you install Office 2013, you must activate it by using either a Multiple Activation Key (MAK) or a Key Management System (KMS) key that is connected to a KMS host on the intranet.
If you install a MAK key, you must activate Office 2013 online.
The Office 2013 client software includes an embedded KMS client key. After the Office 2013 KMS client automatically discovers the Office 2013 KMS host on the intranet, and at least five Office 2013 KMS clients have already requested activation from the KMS host, the KMS client is automatically activated.
Licensing information is not updated in the Backstage view
To display licensing information, on the File menu, choose Account. You must restart the Office 2013 applications for the licensing information to be updated. For example, if you open Word 2013 and then choose Account on the File menu, you might see that product activation is required. If you activate by using ospp.vbs /act or Volume Activation Management Tool (VAMT), you must restart Word 2013 to see that the product is activated, even though Office 2013 is in the licensed state. For more information about the ospp.vbs script, see Configure client computers for volume activation in Office 2013.
Generic Volume License Keys (GVLKs) for Office 2013
All Office 2013 volume 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 the KMS client key that is shown in the table later in this article. The recommended way to enter the key is by using VAMT. You can also use ospp.vbs /inpkey to enter the key. For more information about the ospp.vbs script, see Configure client computers for volume activation in Office 2013.
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.
The following table shows the KMS client keys for the Office 2013 suites and stand-alone products.
|
Suites |
|
|
|
|
Office 2013 Professional Plus |
YC7DK-G2NP3-2QQC3-J6H88-GVGXT |
|
|
Office 2013 Standard |
KBKQT-2NMXY-JJWGP-M62JB-92CD4 |
|
Stand-alone products |
|
|
|
|
Access 2013 |
NG2JY-H4JBT-HQXYP-78QH9-4JM2D |
|
|
Excel 2013 |
VGPNG-Y7HQW-9RHP7-TKPV3-BG7GB |
|
|
InfoPath 2013 |
DKT8B-N7VXH-D963P-Q4PHY-F8894 |
|
|
Lync 2013 |
2MG3G-3BNTT-3MFW9-KDQW3-TCK7R |
|
|
OneNote 2013 |
TGN6P-8MMBC-37P2F-XHXXK-P34VW |
|
|
Outlook 2013 |
QPN8Q-BJBTJ-334K3-93TGY-2PMBT |
|
|
PowerPoint 2013 |
4NT99-8RJFH-Q2VDH-KYG2C-4RD4F |
|
|
Project 2013 Professional |
FN8TT-7WMH6-2D4X9-M337T-2342K |
|
|
Project 2013 Standard |
6NTH3-CW976-3G3Y2-JK3TX-8QHTT |
|
|
Publisher 2013 |
PN2WF-29XG2-T9HJ7-JQPJR-FCXK4 |
|
|
Visio 2013 Professional |
C2FG9-N6J68-H8BTJ-BW3QX-RM3B3 |
|
|
Visio 2013 Standard |
J484Y-4NKBF-W2HMG-DBMJC-PGWR7 |
|
|
Word 2013 |
6Q7VD-NX8JD-WJ2VH-88V73-4GBJ7 |

Important:
Note: