Troubleshoot Volume Activation for Office 2010

7/22/2019 Troubleshoot Volume Activation for Office 2010

1/6

2010 Microsoft Corporation. All rights reserved.

Published: May 12, 2010

This article contains troubleshooting information for issues that you might encounter when you activateMicrosoft Office 2010. Before you read this article, we recommend that you first read Volume activationoverview for Office 2010 [ http://technet.microsoft.com/en-us/library/ee624349.aspx ] , Plan volumeactivation of Office 2010 [ http://technet.microsoft.com/en-us/library/ee624358.aspx ] , Deploy volumeactivation of Office 2010 [ http://technet.microsoft.com/en-us/library/ee624357.aspx ] , and Tools toconfigure client computers in Office 2010 [ http://technet.microsoft.com/en-us/library/ee624350.aspx ] .

In this article:

Activation error codes

General activation

Users see notifications to activate

Licensing information is not updated in the Backstage view

KMS client keys

MAK activation issues

MAK activation fails with Windows XP

The Office 2010 client does not activate when it is connected to the network through

an authenticated proxy

KMS activation issues

The Office 2010 KMS client does not activate

The KMS host is not activated

The client activation request count on the KMS host is not high enough for client

computers to activate

The KMS host cannot be reached

Activation error codes

Error codes help troubleshoot activation issues. If a user sees a dialog box that contains an activationnotification, an error code might be displayed at the lower-left portion of the dialog box. Another way toobtain an error code is to run ospp.vbs /act on the client computer to attempt activation. If activation fails,an error code is reported. Use ospp.vbs /ddescr with the appropriate error code to receive the errormessage. For more information about the ospp.vbs script, see Tools to configure client computers in Office2010 [ http://technet.microsoft.com/en-us/library/ee624350.aspx ] .

General activation

The following are general activation issues and their solutions.

Users see notifications to activate

An activation notification dialog box usually appears when a copy of Office 2010 is not yet activated. An errorcode is displayed on the lower-left portion of the dialog box to help you troubleshoot activation issues. Nodialog box is shown until 25 days after installation, at which time the user sees a notification dialog box. If

ubleshoot volume activation for Office 2010 http://technet.microsoft.com/en-us/library/ee624355(printer).aspx

6 09/08/2010 00:39


2/6

Office 2010 has not been activated 30 days after installation, the notification dialog box contains a red titlebar.

When you install Office 2010, you must activate it by using either Multiple Activation Key (MAK) or KeyManagement System (KMS) connecting to a KMS host on the intranet.

If you install a MAK key, you must activate Office 2010 online.

The Office 2010 client software includes an embedded KMS client key. Once the Office 2010 KMS clientautomatically discovers the Office 2010 KMS host on the intranet, and at least five Office 2010 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, click Help. You must restart the Office 2010 applicationsfor the licensing information to be updated. For example, if you open Microsoft Word 2010 and then clickHelp 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) 2.0 [ http://go.microsoft.com/fwlink/?LinkId=183042 ](http://go.microsoft.com/fwlink/?LinkId=183042), you must restart Word 2010 to see that the product hasbeen activated, even though Office 2010 is in the licensed state. For more information about the ospp.vbsscript, see Tools to configure client computers in Office 2010 [ http://technet.microsoft.com/en-us/library

/ee624350.aspx ] .

KMS client keys

All Office 2010 volume products have the KMS client keys preinstalled. If you entered a MAK key for a productand you want to change the activation method back to KMS, use the appropriate the KMS client key shown inthe table later in this article. The recommended way to enter the key is by using VAMT 2.0 [http://go.microsoft.com/fwlink/?LinkId=183042 ] (http://go.microsoft.com/fwlink/?LinkId=183042). You canalso use ospp.vbs /inpkey to enter the key. For more information about the ospp.vbs script, see Tools toconfigure client computers in Office 2010 [ http://technet.microsoft.com/en-us/library/ee624350.aspx ] .

For Office 2010 suites, only one key is required for all the products in the suite. For example, if you useMicrosoft Office Professional Plus 2010, you must enter only the Office Professional Plus 2010 key for theentire suite.

If you are deploying Microsoft Visio 2010, the key that you enter determines which features are available. Formore information, see Deploy Visio 2010 [ http://technet.microsoft.com/en-us/library/ee624357.aspx ] inDeploy volume activation of Office 2010 [ http://technet.microsoft.com/en-us/library/ee624357.aspx ] .

The following table shows the KMS client keys for the Office 2010 suites and stand-alone products.

Suites

Office Professional Plus 2010 VYBBJ-TRJPB-QFQRF-QFT4D-H3GVB

Office Standard 2010 V7QKV-4XVVR-XYV4D-F7DFM-8R6BM

Office Home and Business 2010 D6QFG-VBYP2-XQHM7-J97RH-VVRCK

Stand-alone products

Access 2010 V7Y44-9T38C-R2VJK-666HK-T7DDX

Excel 2010 H62QG-HXVKF-PP4HP-66KMR-CW9BM

SharePoint Workspace 2010 QYYW6-QP4CB-MBV6G-HYMCJ-4T3J4

InfoPath 2010 K96W8-67RPQ-62T9Y-J8FQJ-BT37T

OneNote 2010 Q4Y4M-RHWJM-PY37F-MTKWH-D3XHX

Outlook 2010 7YDC2-CWM8M-RRTJC-8MDVC-X3DWQ

PowerPoint 2010 RC8FX-88JRY-3PF7C-X8P67-P4VTT


6 09/08/2010 00:39


3/6

Project Professional 2010 YGX6F-PGV49-PGW3J-9BTGG-VHKC6

Project Standard 2010 4HP3K-88W3F-W2K3D-6677X-F9PGB

Publisher 2010 BFK7F-9MYHM-V68C7-DRQ66-83YTP

Word 2010 HVHB3-C6FV7-KQX9W-YQG79-CRY7T

Visio

Visio Premium 2010 D9DWC-HPYVV-JGF4P-BTWQB-WX8BJ

Visio Professional 2010 7MCW8-VRQVK-G677T-PDJCM-Q8TCP

Visio Standard 2010 767HD-QGMWX-8QTDB-9G3R2-KHFGJ

MAK activation issues

This section contains MAK activation issues and how to resolve them.

MAK activation fails with Windows XP

Relevant error code: 0x8007001

If you have daemon tools installed, such as CD emulation software, a registry key is preventing the hardwareID from being acquired. The workaround is as follows:

On the Start menu, click Run, and then type regedit.1.

In Registry Editor, search for the following registry key: HKLM\SYSTEM\CURRENTCONTROLSET\CONTROL\CLASS\{4D36E967-E325-11CE-BFC1-08002BE10318}

2.

Look for UpperFilters, which is of type REG_MULTI_SZ.3.

Double-click UpperFilters, and then under Value data, add PartMgr to the top of the list. Click OK.4.

Restart the computer.5.

Start any Office 2010 application and follow the prompts to activate.

Important:

If you want to activate by using VAMT or the Office Software Protection Platform script(ospp.vbs), you must first start an Office 2010 application so that the OSPP service is started.

6.

For information about how to resolve this issue, see Microsoft Knowledge Base article 916180: You tried to set

up your Xbox 360 console as a Media Center Extender, but the Setup program did not start [http://go.microsoft.com/fwlink/?LinkId=184076 ] (http://go.microsoft.com/fwlink/?LinkId=184076).

Note:

Although Knowledge Base article 916180 [ http://go.microsoft.com/fwlink/?LinkId=184076 ] describesa fix that is not specific to Office and activation, the fix is relevant to Windows XP and applies to thisissue.

The Office 2010 client does not activate when it is connected to the network through anauthenticated proxy

Independent MAK activation requires an Internet connection. If the Office 2010 client is connected to the

Internet through an authenticated proxy, you must activate the client over the telephone. For moreinformation about how to resolve this issue, see Knowledge Base article 921471: Activation fails when you tryto activate Windows Vista or Windows Server 2008 over the Internet [ http://go.microsoft.com/fwlink

/?LinkId=183044 ] (http://go.microsoft.com/fwlink/?LinkId=183044).

KMS activation issues


6 09/08/2010 00:39


4/6

This section contains KMS activation issues and how to resolve them.

The Office 2010 KMS client does not activate

There might be several reasons why the Office 2010 Key Management Service (KMS) client is not 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 the KMS clients can be activated. For more information, seePrepare and configure the KMS host [ http://technet.microsoft.com/en-us/library/ee624357.aspx ] in Deployvolume activation of Office 2010 [ http://technet.microsoft.com/en-us/library/ee624357.aspx ] . You mustrun KeyManagementServiceHost.exe, which you can download at Microsoft Office 2010 KMS Host License Pack[ http://go.microsoft.com/fwlink/?LinkID=169244 ] (http://go.microsoft.com/fwlink/?LinkID=169244). Then,you enter the Office 2010 KMS host key and activate the KMS host.

If you use slmgr.vbs, you must activate the KMS host within the command and include the following Office2010 activation ID:

cscript slmgr.vbs /ato bfe7a195-4f8f-4f0b-a622-cf13c7d16864

The client activation request count on the KMS host is not high enough for client computers toactivate


The Office 2010 KMS host must receive activation requests from at least five Office 2010 KMS clients beforeKMS clients on that network can be activated. If the KMS host does not receive more than five requests, KMSclients will not be activated. If you deploy Office 2010 to more than five computers, their initial activationrequests will be used to build up the count. If activation fails, the computers will attempt activation two hourslater. At that time, if the KMS host has a sufficient count, activation will be successful. To trigger activationmanually on the KMS client, run ospp.vbs /act. For more information about the ospp.vbs script, see Tools toconfigure client computers in Office 2010 [ http://technet.microsoft.com/en-us/library/ee624350.aspx ] .

To determine the current count on the KMS host, at the command prompt (with administrator permissions),run the following command:

cscript slmgr.vbs /dlv bfe7a195-4f8f-4f0b-a622-cf13c7d16864

The current count displayed must be 5 or greater for KMS clients to be activated. The output should resemblethe following:


6 09/08/2010 00:39


5/6

Name: Mi cr osof t Of f i ce 2010, KMSHost edi t i onDescr i pt i on: Mi cr osof t Of f i ce 2010 KMS, VOLUME_KMS channelAct i vat i on I D: bf e7a195- 4f 8f - 4f 0b- a622- cf 13c7d16864Appl i cat i on I D: 59a52881- a989- 479d- af 46- f 275c6370663Ext ended PI D: 55041- 00096- 199- 000004- 03- 1033- 7600. 0000- 3632009I nst al l at i on I D: 008585014214769124199722184000850026888810090785321136Processor Cer t i f i cat e URL: ht t p: / / go. mi crosof t . com/ f wl i nk/ ?Li nkI D=88342Machi ne Cer t i f i cat e URL: ht t p: / / go. mi crosof t . com/ f wl i nk/ ?Li nkI D=88343Use Li cense URL: ht t p: / / go. mi cr osof t . com/ f wl i nk/ ?Li nkI D=88345Product Key Cer t i f i cat e URL: ht t p: / / go. mi cr osof t . com/ f wl i nk/ ?Li nkI D=88344

Par t i al Product Key: RP3HHLi cense St at us: Li censedRemai ni ng Wi ndows r ear m count : 1

Tr ust ed t i me: 12/ 29/ 2009 1: 45: 54 PM

Key Management Ser vi ce i s enabl ed on t hi s comput erCur r ent count : 0Li st eni ng on Por t : 1688DNS publ i shi ng enabl edKMS pr i or i t y: Normal

Key Management Ser vi ce cumul at i ve r equest s r ecei ved f r om cl i ent sTot al r equest s r ecei ved: 0Fai l ed r equest s r ecei ved: 0Requests wi t h Li cense St at us Unl i censed: 0

Requests wi t h Li cense St at us Li censed: 0Request s wi t h Li cense St at us I ni t i al gr ace per i od: 0Requests wi t h Li cense St at us Li cense expi r ed or Hardware out of t ol erance: 0

Request s wi t h Li cense St atus Non- genui ne grace peri od: 0Request s wi t h Li cense St at us Not i f i cat i on: 0

The operating system that the KMS clients run under determines how the KMS clients send activationrequests.

For Office 2010 KMS clients that run under Windows Vista, Windows 7, Windows Server

2008, or Windows Server 2008 R2 After Office 2010 is installed, the Office Software

Protection Platform (OSPP) service automatically sends activation requests to the KMS host everytwo hours until activation occurs, regardless of whether Office 2010 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 are not on the corporate network (at home, for example) become

activated as soon as they connect to the network.

For Office 2010 KMS clients that run under Windows XP or Windows Server 2003 An

activation request is sent when the computer is connected to the corporate network and an Office

2010 application is started. Starting an Office 2010 application starts the OSPP service, which

continues to run until the computer is restarted. Although the OSPP service is running, an

activation request is automatically sent every two hours during the 30-day grace period. If these

KMS clients connect to the corporate network, and no Office 2010 application is started, no

activation requests are sent to the KMS host. There are two ways to manually send an activation

request to the KMS host to increase the current count. On each KMS client, perform either of the

following while connected to the corporate network:

Launch an Office 2010 application. This sends an activation request and starts the

OSPP service.

From the command line (with administrator permissions), run cscript ospp.vbs

/act. For more information about the ospp.vbs script, see Tools to configure client

computers in Office 2010 [ http://technet.microsoft.com/en-us/library

/ee624350.aspx ] .

The KMS host cannot be reached


If you want the KMS clients to use auto-discovery of the KMS host, review the Windows Volume Activation


6 09/08/2010 00:39


6/6

Deployment Guide [ http://go.microsoft.com/fwlink/?LinkId=183043 ] (http://go.microsoft.com/fwlink/?LinkId=183043) to make sure that the DNS configuration is correct. Ensure that the KMS host has networkconnectivity, 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 computername. 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 hostname after the test is completed.

See Also

Concepts

Volume activation overview for Office 2010 [ http://technet.microsoft.com/en-us/library/ee624349.aspx ]Plan volume activation of Office 2010 [ http://technet.microsoft.com/en-us/library/ee624358.aspx ]Deploy volume activation of Office 2010 [ http://technet.microsoft.com/en-us/library/ee624357.aspx ]Tools to configure client computers in Office 2010 [ http://technet.microsoft.com/en-us/library

/ee624350.aspx ]Other Resources

Office 2010 Volume Activation forum [ http://go.microsoft.com/fwlink/?LinkId=180346 ]Office 2010 forums [ http://go.microsoft.com/fwlink/?LinkId=180345 ]

Change History

Date Description Reason

May 12, 2010 Initial publication


Troubleshoot Volume Activation for Office 2010

Documents

Transcript of Troubleshoot Volume Activation for Office 2010