Good afternoon: I'm having some issues activating Office 2013 via KMS server.  My environment is: KMS Server: 

• Windows 2012, Volume Activation role added
• Hosting KMS for Windows 2012/8, Office 2013 and (hopefully) 2010

KMS Clients

• Windows 8, 7
• Windows 2012, 2008
• Office 2010
• Office 2013

Currently, my KMS server can Activate Windows OS correctly.  It can also activate Office 2010.  I need it to be able to activate 2013 as well, but after configuring it for 2010, 20013 broke. Here are the steps I followed to break it:

1. Installed Windows 2012 and added the Volume Activation role
2. Added KMS key for Windows Server; activated.  Verified with my 2012 machines that this worked properly.
3. Installed KMS Host for Office 2013 (not the preview)
4. Added Office 2013 KMS key and activated.  Verified that activations were working on my 2013 clients.
5. Installed Office 2010 KMS host per the instructions in the following Microsoft Article:
   http://blogs.technet.com/b/odsupport/archive/2012/10/29/how-to-install-the-office-2010-kms-host-license-pack-on-windows-8-or-windows-server-2012.aspx
6. Verified 2010 clients were activating properly

At this point, 2013 clients stopped activating when I used VAMT to force a KMS activation to this server.  Instead of activating, they immediately fail with the following error: A licensing provider for the specified product cannot not be found Parameter name: product To resolve the issue, I have tried the following:

• Reinstall the 2013 KMS host on the KMS server.  
  When I do this, I'm prompted for a key, but the activate radio button is grayed out.  However, I can manually activate the key fine.
• I've attempted to delete the product key for 2010 -- still can't activate 2013.
• Remove the Volume Activation role, restarted, re-added the role and then added all of my keys back (they didn't appear to have actually been removed)

I have a feeling that the 2010 install overwrote some important files for 2013, and now it doesn't fully recognize the 2013 product.  I believe my fix will be to remove the product information for 2010 and 2013, but I don't know where the product information is stored or how to uninstall it. Any help is *greatly* appreciated.

Got same message: A licensing provider for the specified product cannot not be found

Parameter name: product

/KMS Hosting on Windows 2008 R2/

I am running into this same issue....

I have yet to find a solution or a FIX for this...

Really wanted to start ROLLING out Office 2013 but this is a MAJOR issue....

I have faced the same issues. We have activated the CSVLK license for Office 2013 (we have office 2010 CSVLK in the same box) already but not able to activate via Volume Activation Management tool or activated from client. It will show the below errors A licensing provider for the specified product cannot not be found

Parameter name: product

Can any expert help on this issues?

Thanks,

The current count is 0. Is it the root cause? I think we may have at least 5 clients to be in the network and send the request to KMS before they can be activated.

Name: Office 15, KMSHostVL edition
Description: Office 15, VOLUME_KMS channel
Activation ID: 
Application ID: 
Extended PID: 
Installation ID: 
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88342
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88343
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88345
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88344
Partial Product Key: 
License Status: Licensed
Remaining Windows rearm count: 3
Trusted time: 20-11-2012 4:32:37 PM

Key Management Service is enabled on this machine
    Current count: 0
    Listening on Port: 1688
    DNS publishing enabled
    KMS priority: Normal

Key Management Service cumulative requests received from clients
    Total requests received: 0
    Failed requests received: 0
    Requests with License Status Unlicensed: 0
    Requests with License Status Licensed: 0
    Requests with License Status Initial grace period: 0
    Requests with License Status License expired or Hardware out of tolerance: 0

    Requests with License Status Non-genuine grace period: 0
    Requests with License Status Notification: 0

The current count is 0. Is it the root cause? I think we may have at least 5 clients to be in the network and send the request to KMS before they can be activated.

Name: Office 15, KMSHostVL edition
Description: Office 15, VOLUME_KMS channel
Activation ID: 
Application ID: 
Extended PID: 
Installation ID: 
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88342
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88343
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88345
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88344
Partial Product Key: 
License Status: Licensed
Remaining Windows rearm count: 3
Trusted time: 20-11-2012 4:32:37 PM

Key Management Service is enabled on this machine
    Current count: 0
    Listening on Port: 1688
    DNS publishing enabled
    KMS priority: Normal

Key Management Service cumulative requests received from clients
    Total requests received: 0
    Failed requests received: 0
    Requests with License Status Unlicensed: 0
    Requests with License Status Licensed: 0
    Requests with License Status Initial grace period: 0
    Requests with License Status License expired or Hardware out of tolerance: 0

    Requests with License Status Non-genuine grace period: 0
    Requests with License Status Notification: 0

the Office KMShost will not begin issuing activations until 5 clients have contacted the KMShost to request activation.

Office2010 KMShost and Office2013 KMShost, when installed on the same server, each maintain independent counts, so you will need 5 x Office2010 clients and also 5 x Office2013 clients

Don,

So you are saying that this works ? Because i am waitng to do it in my production envirement. Can someone confirm that it works.

fract

Don,

So you are saying that this works ? Because i am waitng to do it in my production envirement. Can someone confirm that it works.

fract

@Fract - yes, there are guys in the Office2013 Setup forum who have confirmed they have it working.
there are also guys in the forum who are having trouble.
some guys seem to be having trouble when they are hosting KMS on SRV2012 and put Office2010kmshostpack on *after* putting Office2013kmshostpack on. although there is no documentation which advises on any particular order in which to co-host, I tend to always apply products/patches in the oldest-to-newest order.

so if you are building a KMShost and need to co-host, I would do this:
a) setup and activate Windows KMShost
b) install and activate Office2010 KMShostpack
c) install and activate Office2013 KMShostpack

Personally, I have not yet added Office2013KMShostpack to my primary KMShost (which is Windows 2008R2 KMS+ Office2010 KMS). I'm about to do that (since I now have my change manager's appro

Have you tested with VAMT 3.0?

Below is a link on how to install and configure VAMT 3.0

http://technet.microsoft.com/en-us/library/hh825211.aspx

Doak[MSFT]

Don,

Did you have any luck with getting Office 2010 and 2013 KMS on the same box?  I'm still having the original problem that started this thread.  

I have since created yet another box 2012 box to host the licenses.  I installed the 2010 pack, activated it and verified it was activating clients properly.   After I add the 2013 pack, it will not activate 2013.  I get the same message as I did in the original post.

I figured I'd abandon 2012 and go back to 2008 R2, and I'm getting the same results.  Install KMS, make sure it activates Windows.  Install 2010, make sure it activates clients, and then install 2013 -- fails every time with 

A licensing provider for the specified product cannot be found
Parameter Name: product

I am testing with VAMT 2.0.  I'm assuming this will work for Office 2013, as it's just telling the client to talk to the server and showing me the results...

Did you have any luck with getting Office 2010 and 2013 KMS on the same box?  I'm still having the original problem that started this thread.

Yep, mine is all fine. I don't have enough Office2013 clients to kickoff yet (only 3), but it looks ok so far.
Are you using the original office2010kmshostlicensepack.exe or the newer release?
http://www.microsoft.com/en-us/download/details.aspx?id=2509

Any hints outside of your post above?  What OS are you hosting KMS on?

I've tried a combination of all of the KMS hosts.  

I started with 2012 and the old 2010 host (with the updated vbs from the MS Blogs) -- activates 2010 fine.  Installed 2013 host, can't get them to activate.

Built a new 2012 Server, installed the new 2010 host and it activates 2010.  Installed 2013 host, can't get 2013 clients to activate.

Built a new 2008 R2 server, installed new 2010 host and it activates 2010.  Installed 2013 host, can't get 2013 clients to activate.

I have not published my server to DNS as my current production KMS server is activating clients fine, but it's running 2003 so I can't do Office 2013 or Win8/2012.  My intent is to build this new server and replace the old 2003 box once I can get clients to activate.  

My test is to discover the client in VAMT (2.0).  I right click the Office 2013 entry for the client and then choose to KMS activate.  I specify my new server and get the error message from above:

A licensing provider for the specified product cannot not be found

Parameter name: product

VAMT 2.0 does not support activating Office 2013 clients so you will need to use VAMT 3.0

Doak[MSFT]

Excellent information; thanks!

Do you know how to make VAMT 3.0 use an alternate KMS sever similar to VAMT 2.0?  I would like to do this to test the server out before I promote it to production.  If 2.0 doesn't work, than that is most likely my problem from the start.

Any hints outside of your post above?  What OS are you hosting KMS on?

we're using SRV2008R2 for all of our KMShosts (we have several isolated networks, since we are a hoster/service-provider/Telco as well as a 50,000 seat enterprise)

our main box was first setup as Windows KMShost, then added Office2010 pack to it, then added the hotfixes and pack for Win8/SRV2012 to it, then added Office2013 to it.
No issues with it at all to date. We have only 3 Office2013 clients so far, so it isn't yet ticking over fully, for Office2013. We are trialling O365 (Office2013 edition), so depending on how that goes we may not see a great need for KMS-Office2013.

In some Cases the active firewall on the system can cause KMS procedure failes ; First disable system firewalls & ....( hope to success:-) )