0xC004F038 The software Licensing Service reported that the computer could not be activated. The count reported by your Key Management Service (KMS) is insufficient. Please contact your system administrator.

0xC004F038 The software Licensing Service reported that the computer could not be activated. The count reported by your Key Management Service (KMS) is insufficient. Please contact your system administrator.

  • Comments 7
  • Likes

Issue:

0xC004F038
The software Licensing Service reported that the computer could not be activated. The count reported by your Key Management Service (KMS) is insufficient. Please contact your system administrator.

Possible Causes:
This issue occurs because the KMS server has not received 5 unique requests for activation.
The KMS server must have requests for 5 machines that have unique computer IDs.

Resolution:
Ensure that 5 unique machines have requested activation against the KMS server. If you have used sysprep in your environment it is possible Office was not rearmed prior to the image creation and as such machines may have the same Office CMID.
If you have had more than 5 machine attempt activation and you are still seeing this, check the Key Management Service Host log, in eventvwr on the KMS server. You will see entries like so:

0x0,5,Ignite1.ignite.local,930bd202-a335-4c7e-bd9d-7305361f0d37,2010/6/10 19:34,0,5,0,6f327760-8c5c-417c-9b61-836a98287e0c
0x0,5,Ignite2.ignite.local,2f362dd3-fb39-4d18-94e6-de1d30dd27d5,2010/6/10 19:33,0,5,0,6f327760-8c5c-417c-9b61-836a98287e0c
0x0,5,Ignite5.ignite.local,930bd202-a335-4c7e-bd9d-7305361f0d37,2010/6/10 19:32,0,5,0,6f327760-8c5c-417c-9b61-836a98287e0c

Notice in my case Ignite5 and ignite1 have the same CMID (930bd202-a335-4c7e-bd9d-7305361f0d37).

This indicates that while the base OS image may have been generalized, the Office re-arm was skipped.

*Note*
When preparing Windows images that will contain Office 2010, please ensure that you run \%Program Files%\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform\ospprearm.exe prior to sysprepping the image to ensure a unique Office CMID.

http://technet.microsoft.com/en-us/library/ee624357.aspx#section4
Rearm the Office 2010 installation

There is a 25-day grace period from the time of installation of KMS clients before notifications to activate are displayed to the user. If you want to deploy an image, you must rearm your Office 2010 installation before you capture the image. Rearming is important for these reasons:

o The grace timer is reset to 30 days of grace.
o The grace timer is frozen. 
      o If you do not rearm, users see notification dialog boxes at the time that the image is deployed, instead of 25-days after deployment. The 25-day grace period allows ample time for a KMS host to be found and activation to succeed. If activation is successful, users do not see notifications to activate.

o The client machine ID (CMID) is reset. 
      o The KMS host counts the number of unique clients based on the CMID. 
      o Use the command ospp.vbs /dcmid to check the CMID.

Rearm is also recommended for MAK deployment. If you are deploying Office 2010 configured for MAK activation, and you did not remotely activate for end-users through VAMT 2.0 or ospp.vbs, users will see an activation dialog box the first time that an Office 2010 application starts. The activation dialog box is slightly different 25 days after installation. Also, users might immediately see a red title bar if Office 2010 had not been rearmed before image capture.

To rearm your Office 2010 installation

1. Make sure all Office 2010 applications are closed.
2. Open an elevated command prompt.
3. Go to <installdrive>\%Program Files%\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform. If you installed the 32-bit edition of Office 2010 on a 64-bit operating system, %Program Files% is the Program Files (x86) folder.
4. Run ospprearm.exe. If you see a message that indicates success, you are ready for image capture.

clip_image001Important:
Do not open an Office application, ospp.vbs, or anything related to Office 2010. Doing so starts the grace timer.

5. Capture the image or save the VM.

If you are in a situation where you have already deployed your OS image to machines, but the Office Rearm was not done during the imaging process you may be in a state now where all the machines are being used and they all have the same unique ID for Office. Here is a startup script that you could push out to those machines to rearm Office for you and generate new unique Office IDs. This will work on 32bit and 64bit flavors of Office 2010.

@echo off

:OSPP
reg query HKLM\Software\Microsoft\Office\14.0\Common\OSPPREARM
if %errorlevel%==1 (goto RUN) else (goto END)

:RUN
set ProgramFilesPath=%ProgramFiles%
"%ProgramFilesPath%\Common Files\microsoft shared\OfficeSoftwareProtectionPlatform\OSPPREARM.EXE"
C:\Windows\system32\cscript.exe "%ProgramFilesPath%\Microsoft Office\Office14\ospp.vbs" /act
set ProgramFilesPath=%ProgramFiles(x86)%
"%ProgramFilesPath%\Common Files\microsoft shared\OfficeSoftwareProtectionPlatform\OSPPREARM.EXE"
C:\Windows\system32\cscript.exe "%ProgramFilesPath%\Microsoft Office\Office14\ospp.vbs" /act
REG ADD "HKLM\Software\Microsoft\Office\14.0\Common\OSPPREARM"

:END
Exit

Comments
  • Hello,

    sorry but I haven't any OfficeSoftwareProtectionPlatform\OSPPREARM.EXE. What's wrong? how can I fix this trouble?

    <ADMIN RESPONSE>

    If you have Office 2010 installed, you should have it in one of these two locations:

    If X64
    C:\Program Files\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform

    If X86
    C:\Program Files (x86)\Common Files\microsoft shared\OfficeSoftwareProtectionPlatform

    Please check both locations.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment