A Windows Vista forum. Vista Banter

Welcome to Vista Banter.

You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today!

If you have any problems with the registration process or your account login, please contact contact support.

Go Back   Home » Vista Banter forum » Microsoft Windows Vista » Installation and Setup of Vista
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Installation and Setup of Vista Installation problems and questions using Windows Vista. (microsoft.public.windows.vista.installation_setup)

KMS Client Activation returns 0xC004F039 error



 
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old January 29th 07, 04:23 PM posted to microsoft.public.windows.vista.installation_setup
William Luo
external usenet poster
 
Posts: 2
Default KMS Client Activation returns 0xC004F039 error

I created a KMS host with a volume license key for MS partner.
But when I tried to active any KMS client in my intranet with the following
command:
C:\Windows\System32cscript slmgr.vbs -ato
I saw the error:
0xC004F039 The computer could not be activated. The Key Management Service
could not be reached.

Why is it not the 0xC004F038 error (n-count is not enough)?


  #2 (permalink)  
Old January 29th 07, 08:37 PM posted to microsoft.public.windows.vista.installation_setup
Darrell Gorter[MSFT]
external usenet poster
 
Posts: 685
Default KMS Client Activation returns 0xC004F039 error

Hello William,
The KMS server machine is not activated. Until the machine that is running
the KMS Server service, is activated you will get this message.
Once you activate that machine against the Activation servers, then the KMS
clients will be able to communicate to the KMS server. At which point you
will start getting the 0xc004f038 messages until the n-count hits 25.
Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
|From: "William Luo"
|Subject: KMS Client Activation returns 0xC004F039 error
|Date: Tue, 30 Jan 2007 00:23:29 +0800
|Lines: 11
|X-Priority: 3
|X-MSMail-Priority: Normal
|X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
|X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
|X-RFC2646: Format=Flowed; Original
|Message-ID:
|Newsgroups: microsoft.public.windows.vista.installation_setup
|NNTP-Posting-Host: 219.144.141.130
|Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSF TNGP02.phx.gbl
|Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.vista.installation_setup: 3556
|X-Tomcat-NG: microsoft.public.windows.vista.installation_setup
|
|I created a KMS host with a volume license key for MS partner.
|But when I tried to active any KMS client in my intranet with the
following
|command:
|C:\Windows\System32cscript slmgr.vbs -ato
|I saw the error:
|0xC004F039 The computer could not be activated. The Key Management
Service
|could not be reached.
|
|Why is it not the 0xC004F038 error (n-count is not enough)?
|
|
|

  #3 (permalink)  
Old January 30th 07, 01:04 AM posted to microsoft.public.windows.vista.installation_setup
William Luo
external usenet poster
 
Posts: 2
Default KMS Client Activation returns 0xC004F039 error


Sorry that I didn't mention that I ran slmgr.vbs -ato at the KMS host,
the KMS host was successfully activated by itself.

So, there must be other reason for this problem.
Any other hints?

P.S.
I run telnet mykms:1688 from a Windows XP and the error is:
Could not open the connection to the host, on port 1688: Connect failed.
So I guess the Software Licensing service has some problem.
But I can see from the Services management panel that the
Software Licensing service is of Started status.


""Darrell Gorter[MSFT]"" wrote in message
...
Hello William,
The KMS server machine is not activated. Until the machine that is
running
the KMS Server service, is activated you will get this message.
Once you activate that machine against the Activation servers, then the
KMS
clients will be able to communicate to the KMS server. At which point you
will start getting the 0xc004f038 messages until the n-count hits 25.
Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
|From: "William Luo"
|Subject: KMS Client Activation returns 0xC004F039 error
|Date: Tue, 30 Jan 2007 00:23:29 +0800
|Lines: 11
|X-Priority: 3
|X-MSMail-Priority: Normal
|X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
|X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
|X-RFC2646: Format=Flowed; Original
|Message-ID:
|Newsgroups: microsoft.public.windows.vista.installation_setup
|NNTP-Posting-Host: 219.144.141.130
|Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSF TNGP02.phx.gbl
|Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.vista.installation_setup: 3556
|X-Tomcat-NG: microsoft.public.windows.vista.installation_setup
|
|I created a KMS host with a volume license key for MS partner.
|But when I tried to active any KMS client in my intranet with the
following
|command:
|C:\Windows\System32cscript slmgr.vbs -ato
|I saw the error:
|0xC004F039 The computer could not be activated. The Key Management
Service
|could not be reached.
|
|Why is it not the 0xC004F038 error (n-count is not enough)?
|
|
|



  #4 (permalink)  
Old February 9th 07, 12:21 AM posted to microsoft.public.windows.vista.installation_setup
bsimon
external usenet poster
 
Posts: 1
Default KMS Client Activation returns 0xC004F039 error

Hi Darrell,
I am wondering can we reduce the number of client since I have to run the
test before I can roll out the Vista. Since, I dont have 25 machine on the
test environment. Is there any way to reduce the client count on KMS host
for testing purpose first? it is really hard for us for do the testing.

Simon

""Darrell Gorter[MSFT]"" wrote:

Hello William,
The KMS server machine is not activated. Until the machine that is running
the KMS Server service, is activated you will get this message.
Once you activate that machine against the Activation servers, then the KMS
clients will be able to communicate to the KMS server. At which point you
will start getting the 0xc004f038 messages until the n-count hits 25.
Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
|From: "William Luo"
|Subject: KMS Client Activation returns 0xC004F039 error
|Date: Tue, 30 Jan 2007 00:23:29 +0800
|Lines: 11
|X-Priority: 3
|X-MSMail-Priority: Normal
|X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
|X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
|X-RFC2646: Format=Flowed; Original
|Message-ID:
|Newsgroups: microsoft.public.windows.vista.installation_setup
|NNTP-Posting-Host: 219.144.141.130
|Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSF TNGP02.phx.gbl
|Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.vista.installation_setup: 3556
|X-Tomcat-NG: microsoft.public.windows.vista.installation_setup
|
|I created a KMS host with a volume license key for MS partner.
|But when I tried to active any KMS client in my intranet with the
following
|command:
|C:\Windows\System32cscript slmgr.vbs -ato
|I saw the error:
|0xC004F039 The computer could not be activated. The Key Management
Service
|could not be reached.
|
|Why is it not the 0xC004F038 error (n-count is not enough)?
|
|
|


  #5 (permalink)  
Old February 22nd 07, 06:58 PM posted to microsoft.public.windows.vista.installation_setup
[email protected]
external usenet poster
 
Posts: 1
Default KMS Client Activation returns 0xC004F039 error

Did you have any luck getting past this? I am in a similar
situation. I ran the cscript slmgr.vbs -ipk volume license key and
that worked but when I tried to then activate the machine using the -
ato option, it always failed. So, I activated it using the MAK
license we own and that seemed to work (its activated) but it is not
receiving any kms requests from our clients and appears to be dead.

On Jan 29, 8:04 pm, "William Luo" wrote:
Sorry that I didn't mention that I ran slmgr.vbs -ato at theKMShost,
theKMShost was successfully activated by itself.

So, there must be other reason for this problem.
Any other hints?

P.S.
I run telnet mykms:1688 from a Windows XP and the error is:
Could not open the connection to the host, on port 1688: Connect failed.
So I guess the Software Licensing service has some problem.
But I can see from the Services management panel that the
Software Licensing service is of Started status.

""Darrell Gorter[MSFT]"" wrote in message

...

Hello William,
TheKMSserver machine is not activated. Until the machine that is
running
theKMSServer service, is activated you will get this message.
Once you activate that machine against the Activation servers, then the
KMS
clients will be able to communicate to theKMSserver. At which point you
will start getting the 0xc004f038 messages until the n-count hits 25.
Thanks,
Darrell Gorter[MSFT]


This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
|From: "William Luo"
|Subject:KMSClient Activation returns 0xC004F039 error
|Date: Tue, 30 Jan 2007 00:23:29 +0800
|Lines: 11
|X-Priority: 3
|X-MSMail-Priority: Normal
|X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
|X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
|X-RFC2646: Format=Flowed; Original
|Message-ID:
|Newsgroups: microsoft.public.windows.vista.installation_setup
|NNTP-Posting-Host: 219.144.141.130
|Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSF TNGP02.phx.gbl
|Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.vista.installation_setup: 3556
|X-Tomcat-NG: microsoft.public.windows.vista.installation_setup
|
|I created aKMShost with a volume license key for MS partner.
|But when I tried to active anyKMSclient in my intranet with the
following
|command:
|C:\Windows\System32cscript slmgr.vbs -ato
|I saw the error:
|0xC004F039 The computer could not be activated. The Key Management
Service
|could not be reached.
|
|Why is it not the 0xC004F038 error (n-count is not enough)?
|
|
|



  #6 (permalink)  
Old February 18th 09, 01:42 PM posted to microsoft.public.windows.vista.installation_setup
Vespera[_3_]
external usenet poster
 
Posts: 1
Default KMS Client Activation returns 0xC004F039 error


The first thing I would try is ensure that name resolution is working to
the internet, so that it can reach the KMS servers...

The second thing would be to go to the below link for some solutions
given.
http://forums.techarena.in/operating...ms/1125683.htm


--
Vespera
------------------------------------------------------------------------
Vespera's Profile: http://forums.techarena.in/members/vespera.htm
View this thread: http://forums.techarena.in/vista-set...all/669067.htm

http://forums.techarena.in

  #7 (permalink)  
Old May 5th 10, 04:20 PM posted to microsoft.public.windows.vista.installation_setup
mcscotty
external usenet poster
 
Posts: 2
Default KMS Client Activation returns 0xC004F039 error


I had the same problem with the 0xC004F039 error

After some poking around, I discovered that enabling the KMS server
process DOES NOT automatically open the port in the firewall that allows
the server to accept activation requests (on a 2008 R2 server at
least).

Looking in the firewall config, there was a "Key Management Service"
rule, but it was not activated, so the firewall was blocking all KMS
requests. Once I activated the firewall rule, allowing KMS traffic
through, everything worked properly.

I bet half of the people having trouble with a new KMS server trip over
this same problem.


--
mcscotty
Posted via http://www.vistaheads.com

  #8 (permalink)  
Old May 5th 10, 04:20 PM posted to microsoft.public.windows.vista.installation_setup
mcscotty
external usenet poster
 
Posts: 2
Default KMS Client Activation returns 0xC004F039 error



I had the same problem with the 0xC004F039 error

After some poking around, I discovered that enabling the KMS server
process DOES NOT automatically open the port in the firewall that allows
the server to accept activation requests (on a 2008 R2 server at
least).

Looking in the firewall config, there was a "Key Management Service"
rule, but it was not activated, so the firewall was blocking all KMS
requests. Once I activated the firewall rule, allowing KMS traffic
through, everything worked properly.

I bet half of the people having trouble with a new KMS server trip over
this same problem.


--
mcscotty
Posted via http://www.vistaheads.com

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT. The time now is 01:55 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.Search Engine Optimization by vBSEO 3.0.0 RC6
Copyright ©2004-2024 Vista Banter.
The comments are property of their posters.