Avatar of bullfrog264
bullfrog264

asked on 

Errors with KMS Activation

Recently my KMS host on windows server 2012 quit issuing licenses.  I followed the MS procedure for my new KMS clients but they return an error stating they are unable to contact the KMS host.  I verifed the software protection services is running, the firewall is turned off(temporarily), and i verified the proper DNS records are present.  I can successfully check the license status of all my clients using the Volume Activation Management Tool and change product keys as well.  Any suggestions?
Microsoft Legacy OSMicrosoft Server OSWindows Server 2012

Avatar of undefined
Last Comment
bullfrog264
Avatar of Rich Weissler
Rich Weissler

Triple checking, just because I'd say there's a fair chance it something you already know, but is getting overlooked.
(1) "i verified the proper DNS records are present"
With apologies, lets check one more time from the client.  In nslookup on one of the clients which is exhibiting the problem... open up nslookup, and tell it to 'set type=all'.  Then '_vlmcs._tcp'
Hopefully you'll get your SRV record.  Close nslookup, and Ping the <srv hostname> that was returned... (and it's possible you're filtering icmp... no big deal, I'd really care that the exact name resolve the way you expect on that machine.)
(2) 'telnet <svr hostname> <port>' from that same client.  (You may need to install the telnet client on that workstation.)  If you get back nothing useful, but at least connect... that counts as success.  If you get connection refused... this is the path we'll need to pursue.
Avatar of bullfrog264
bullfrog264

ASKER

I just ran the nslookup and it did return the SRV record.  I ran telnet from one of the clients and I don't get a connection refused it just sits at connecting until i hit the escape characters.
Avatar of Rich Weissler
Rich Weissler

Well shoot.  That takes out all the easy fixes.  :-)  The error message says KMS isn't available, and it obviously is.

On the KMS server, in Event Viewer, "Application and Services Logs", "Key Management Service" -- what are the recent records?  (I.e. do you have ANY informational messages that "An activation request has been processed. [...]"?  Any errors/warnings?)

On the client, check the application error log, is there an event ID 12288 registered that might have more error information?
Avatar of bullfrog264
bullfrog264

ASKER

There is an event I'd for on the client for 12288 but it says the exact same error message.  The Kms host shows activation requests in the event viewer but none from my client.
SOLUTION
Avatar of Rich Weissler
Rich Weissler

Blurred text
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Avatar of bullfrog264
bullfrog264

ASKER

I did that and it successfully added the KMS but now I get a similiar error.  Running the slui.exe command tells me the same thing.  The KMS host is unavailable.
kms-error.png
Avatar of Rich Weissler
Rich Weissler

Okay, now we're into odd possibilities:
Is the time on the client terribly off the time on the server?
The activation requests which are being processed by KMS successfully -- are they the same client version as the client which is having difficulty?
When you do a ping <kms servername> from the problem client, does it resolve to an IPv6 address?
If you do a tracert <kms servername>, does the request follow a path you expect?
ASKER CERTIFIED SOLUTION
Avatar of Cliff Galiher
Cliff Galiher
Flag of United States of America image

Blurred text
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Avatar of bullfrog264
bullfrog264

ASKER

I did install the proper updates and the proper keys.  I was able to correct the issue by reactivating the host in KMS.  After that I was able to reapply the automatic virtual machine activation key.  They are activating properly.  I moved all of the VMs to another host and they activated with no issue.
Microsoft Server OS
Microsoft Server OS

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.

59K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
Ask the experts
Read over 600 more reviews

TRUSTED BY

IBM logoIntel logoMicrosoft logoUbisoft logoSAP logo
Qualcomm logoCitrix Systems logoWorkday logoErnst & Young logo
High performer badgeUsers love us badge
LinkedIn logoFacebook logoX logoInstagram logoTikTok logoYouTube logo