Hello All,

I have a KMS server setup on a 2008R2 server that's been running in a production environment for a couple of years now. It hands out all of my licenses internally and has given me no trouble until now.

Licenses it's providing without issue are:
Windows 7
Outlook 2010
Office 2010
Server 2008
Server 2008R2

I need to start issuing Excel 2013 Volume licenses now and I can't seem to make that happen. In VAMT when I try to force a KMS Activate I receive the message "A Licensing provider for the product cannot not be foundParametername: product"

What I've done so far:
Installed - Update for Windows Server 2008 R2 x64 Edition (KB2757817)
Installed - Update for Windows Server 2008 R2 x64 Edition (KB2885698)
Installed - Microsoft Office 2013 Volume License Pack
Installed - All Microsoft updates

When I install the "Microsoft Office 2013 Volume License Pack" it installs successfully and then asks if I want to add a Microsoft Office 2013 KMS host product key. I add the key provided for me from Microsoft Volume License Service Center and it accepts it without error. I also ran slmgr.vbs /ipk xxxxx-xxxxx-xxxxx-xxxxx-xx xxx without errors as well.

I called the Volume License Service Center to verify my  KMS key and the ISO image I downloaded to run my install from were correct. They said yes after looking at the KMS key and the Product ID number on one of the workstations I've installed Excel 2013 on.

Using VAMT if I look at my KMS server it shows "Office 15, KMSHost VL edition" - "CSVLK" - "Licensed"

I'm stuck. The Volume License Service Center can't help me any further. I thought I'd try a post before opening a support ticket.

Any help would be outstanding
Thanks
Eric

For Office KMShost, there's no distinction between "full suite" and "individual apps" - i.e. if you install the Office KMShost keys, that's applicable for individual Office VL apps too. On the KMSclient machine (where Excel2013 is installed), what does the output from "cscript ospp.vbs /dstatus" tell you?

You can alternatively use (on the KMSclient) to display all VL products: cscript slmgr.vbs /dli all

Thanks for the Reply Don,

Here's the output:

==================
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

---Processing--------------------------
---------------------------------------
SKU ID: f7461d52-7c2b-43b2-8744-ea958e0bd09a
LICENSE NAME: Office 15, OfficeExcelVL_KMS_Client edition
LICENSE DESCRIPTION: Office 15, VOLUME_KMSCLIENT channel
LICENSE STATUS:  ---OOB_GRACE---
ERROR CODE: 0x4004F00C
ERROR DESCRIPTION: The Software Licensing Service reported that the application is running within the valid grace period.
REMAINING GRACE: 29 days  (41780 minute(s) before expiring)
Last 5 characters of installed product key: 12345
    KMS machine name from DNS: kms.domain.com:1688
    KMS machine registry override defined: kms.domain.com:1688
    Activation Interval: 120 minutes
    Renewal Interval: 10080 minutes
    KMS host caching: Enabled
---------------------------------------
---------------------------------------
---Exiting-----------------------------
=====================

Thanks for the Reply Don,

Here's the output:

==================
Last 5 characters of installed product key: 12345

That looks very suspicious. (unless you redacted it) I don't believe any legitimate product key of any type would have 12345 in it.

The correct Office2013 KMSclient (GVLK) keys are here, and yours doesn't match at all...

Change your Office2013/Excel2013 KMSclient pkey to the correct key, and then try activation again.

https://technet.microsoft.com/en-us/library/dn385360%28v=office.15%29.aspx

On the client, use:

cscript ospp.vbs /inpkey:<correct pkey for your product>
cscript ospp.vbs /act

refer: https://technet.microsoft.com/en-us/library/1825df76-7e23-459b-a6c1-224dd6eab81e#sectio

Yes, sorry I redacted it, just trying to be careful. The correct number is "BG7GB" which is what I see on your link for Excel 2013.

hmm, ok, then I'd check the event logs on your KMShost (look for source-SPPSVC/SoftwareProtection, and event ID's in the range of 12288-12289-12290-etc

https://technet.microsoft.com/en-us/library/ee939272.aspx

Your KMShost is probably unhappy about something (key not registered/activated or below threshold/count).

Otherwise, I'd log a case for this, it doesn't seem to be the usual culprit.

Don,

I tried to add the KMS keys from the link you provided just for the heck of it, but everyone I try says it's invalid.

Any Idea?

Thanks
Eric

What log should I be checking? When I try to activate a KMS or Update Status I would think it would drop into the Key Management Services event log, but nothing does. I don't see anything dropping into the other logs either.

Thanks
Eric

Finally, got it working!

I decided to go back to the Volume License Service Center and re-download the ISO for Excel 2013. I then uninstalled the version that I had loaded and re-installed the version that I downloaded on the 5 PCs I've been working on. That did it, they immediately licensed like they should.

Even though I had 3 different support reps verify that my version was correct for the KMS key I was using, apparently something wasn't correct.

This would be so much easier if a KMS server and it's documentation weren't so obnoxiously vague. It might as well be a box full of magic Unicorn sparkles. Is a Console too much to ask for on the server side?

Anyway Thanks for the help Don
Eric

Finally, got it working!

I decided to go back to the Volume License Service Center and re-download the ISO for Excel 2013. I then uninstalled the version that I had loaded and re-installed the version that I downloaded on the 5 PCs I've been working on. That did it, they immediately licensed like they should.

Even though I had 3 different support reps verify that my version was correct for the KMS key I was using, apparently something wasn't correct.

This would be so much easier if a KMS server and it's documentation weren't so obnoxiously vague. It might as well be a box full of magic Unicorn sparkles. Is a Console too much to ask for on the server side?

Anyway Thanks for the help Don
Eric

Glad you got it sorted.
I'm curious that a re-download/change of the product installed, fixed it.

Originally, you were getting this output from the client:

SKU ID: f7461d52-7c2b-43b2-8744-ea958e0bd09a
LICENSE NAME: Office 15, OfficeExcelVL_KMS_Client edition
LICENSE DESCRIPTION: Office 15, VOLUME_KMSCLIENT channel

What does the output look like now ?

Looks the same to me.

Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

---Processing--------------------------
---------------------------------------
SKU ID: f7461d52-7c2b-43b2-8744-ea958e0bd09a
LICENSE NAME: Office 15, OfficeExcelVL_KMS_Client edition
LICENSE DESCRIPTION: Office 15, VOLUME_KMSCLIENT channel
LICENSE STATUS:  ---LICENSED---
REMAINING GRACE: 178 days  (257568 minute(s) before expiring)
Last 5 characters of installed product key: BG7GB
    KMS machine name from DNS: kms.server.com:1688
    KMS machine registry override defined: kms.server.com:1688
    Activation Interval: 120 minutes
    Renewal Interval: 10080 minutes
    KMS host caching: Enabled
---------------------------------------
---------------------------------------
---Exiting-----------------------------

Finally, got it working!

I decided to go back to the Volume License Service Center and re-download the ISO for Excel 2013. I then uninstalled the version that I had loaded and re-installed the version that I downloaded on the 5 PCs I've been working on. That did it, they immediately licensed like they should.

Even though I had 3 different support reps verify that my version was correct for the KMS key I was using, apparently something wasn't correct.

This would be so much easier if a KMS server and it's documentation weren't so obnoxiously vague. It might as well be a box full of magic Unicorn sparkles. Is a Console too much to ask for on the server side?

Anyway Thanks for the help Don
Eric

• Proposed as answer by DonPick 9 hours 47 minutes ago

Finally, got it working!

I decided to go back to the Volume License Service Center and re-download the ISO for Excel 2013. I then uninstalled the version that I had loaded and re-installed the version that I downloaded on the 5 PCs I've been working on. That did it, they immediately licensed like they should.

Even though I had 3 different support reps verify that my version was correct for the KMS key I was using, apparently something wasn't correct.

This would be so much easier if a KMS server and it's documentation weren't so obnoxiously vague. It might as well be a box full of magic Unicorn sparkles. Is a Console too much to ask for on the server side?

Anyway Thanks for the help Don
Eric

• Proposed as answer by DonPick Saturday, April 04, 2015 9:39 PM

Looks the same to me.

Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

---Processing--------------------------
---------------------------------------
SKU ID: f7461d52-7c2b-43b2-8744-ea958e0bd09a
LICENSE NAME: Office 15, OfficeExcelVL_KMS_Client edition
LICENSE DESCRIPTION: Office 15, VOLUME_KMSCLIENT channel
LICENSE STATUS:  ---LICENSED---
REMAINING GRACE: 178 days  (257568 minute(s) before expiring)
Last 5 characters of installed product key: BG7GB
    KMS machine name from DNS: kms.server.com:1688
    KMS machine registry override defined: kms.server.com:1688
    Activation Interval: 120 minutes
    Renewal Interval: 10080 minutes
    KMS host caching: Enabled
---------------------------------------
---------------------------------------
---Exiting-----------------------------

Hmm, my guess is that something wasn't quite right with the original download/installation - the SKU/License all looks identical. (sometimes, the unicorn sparkles just don't twinkle the right way ;)