Fix it now
Microsoft publishes 0xC004F074 as “no Key Management Service (KMS) could be contacted”, with five causes: a version mismatch between client and host, clocks more than four hours apart, sppsvc stopped on the host, TCP 1688 blocked, or a wrong or stale KMS record in DNS. For Office there is a sixth: the host has no Office licence pack.
cd "C:\Program Files\Microsoft Office\root\Office16"
cscript ospp.vbs /dstatus
nslookup -type=all _vlmcs._tcp
cscript ospp.vbs /act
- Read the channel in
/dstatusfirst. A KMS client reports a volume channel; MAK or retail means this machine was never going to talk to a host. - Read the nslookup answer. A host name and port 1688 means DNS is doing its job; a non-existent domain result means the record is missing or the client is searching the wrong DNS domain.
- If the record resolved, test the path before changing anything:
Test-NetConnection kms.contoso.local -Port 1688in PowerShell, and read TcpTestSucceeded. - If Windows activates against the host but Office does not, stop testing the client. That is the Office-specific cause and it is fixed on the host.
Do not open by pinning a host with /sethst:. It hides a broken DNS record rather than fixing it and leaves a machine that stops activating the day the host is renamed.
If /act completes you are done. If not, the next section works through the six causes and tells you which one you have.
Why it happens
Volume Office carries no key of its own worth typing. Microsoft’s position is that volume licensed versions install with a Generic Volume License Key, and that key exists to make the installation find and activate against a KMS host or Active Directory. 0xC004F074 is the licensing service reporting that it went looking and came back with nothing.
Discovery works the same way it does for Windows. The client asks DNS for a service record named _vlmcs._tcp in its own DNS domain, gets back a host name and a port, and opens a TCP session on 1688. If someone has pinned a host name, DNS is skipped and the stored name is used instead.
Microsoft’s own page for this code names five causes, and they are worth learning as a set because the error message points at none of them: a supported-version mismatch between client and host, a difference of more than four hours between the two system clocks, the Software Protection service stopped on the host, TCP 1688 blocked on the way, and an incorrect or stale KMS record in DNS. Time is compared in Coordinated Universal Time, so time zones are irrelevant.
Office adds a sixth that catches out most organisations. A working KMS host does not automatically activate Office. The host needs the Office Volume License Pack for the version you are deploying, and an Office KMS host key installed and activated. Until that happens the host will activate every copy of Windows on the network and answer nothing at all for Office, which from the client looks exactly like a host that is not there.
The KMS host has never been set up for Office
You have this one if Windows clients activate against the same host without complaint, and every Office client fails with the same code.
- On the host, run
slmgr /dlv alland look for an entry naming your Office version. If there is none, the host cannot serve Office. - Install the Office Volume License Pack for that version, named exactly that: Office LTSC 2024 Volume License Pack, Office LTSC 2021 Volume License Pack, and so on. Running it installs the pack and opens the Volume Activation Tools wizard.
- Enter the Office KMS host key when the wizard prompts, or install it afterwards with
slmgr /ipk, then activate the host withslmgr /ato. - Restart the licensing service on the host so it republishes:
net stop sppsvcthennet start sppsvc.
One host can serve several Office versions, but it must be running an operating system that supports KMS for each version you want to activate.
The service record is missing from DNS
You have this one if nslookup returns a non-existent domain result, and there is no _vlmcs entry under _tcp in the forward lookup zone.
- On the host, check the Application log for Event ID 12293, which records a failure to publish the KMS record to DNS. Successful publication logs 12294.
- Give the host write access to the DNS zone, or create the record by hand: service
_VLMCS, protocol_TCP, port 1688, pointing at the host’s fully qualified name. - Restart sppsvc on the host to force a republish attempt.
- On the client, run
ipconfig /flushdnsand retry.
The client cannot reach TCP 1688
You have this one if DNS resolves correctly and Test-NetConnection returns TcpTestSucceeded False from the client subnet.
- On the host, allow the Key Management Service through Windows Firewall, which is Microsoft’s documented way to open 1688 for it.
- Have the network team permit TCP 1688 from the client subnets, including any VLAN access lists.
- Confirm no endpoint protection product on the client blocks outbound 1688.
- Retry
cscript ospp.vbs /act.
Test from a client subnet. A port test that succeeds from the host’s own network tells you nothing about the machine that is failing.
The clocks are more than four hours apart
You have this one if DNS resolves, 1688 answers, and activation still fails with nothing in the message pointing at time.
- Run
w32tm /resyncon the client, then retry activation. Its documented parameters are /computer:, /nowait, /rediscover and /soft, and /force is not one of them. - Measure the offset against the host directly:
w32tm /stripchart /computer:kms.contoso.local. - Compare in UTC. Time zone settings on either machine are irrelevant to the comparison.
There is no KMS host, and there never was
You have this one if Nobody can name the host, nothing in DNS references _vlmcs, and the estate is small enough that no one built one.
- Count the Office devices. The host requires a minimum of five requests before it starts activating clients, so below that KMS is structurally the wrong mechanism.
- If the devices are domain-joined, look at Active Directory-based activation, which activates volume Office on domain-joined computers and needs no host and no port.
- Otherwise move those devices to MAK keys:
cscript ospp.vbs /inpkey:then/act.
Full reference
Which machine to run what on
| Command | Where | What it tells you |
|---|---|---|
cscript ospp.vbs /dstatus |
Client | The channel, the licence status and the KMS host and port in use |
cscript ospp.vbs /act |
Client | Attempts activation now |
cscript ospp.vbs /sethst:<name> and /setprt:<port> |
Client | Pins a host name and port, skipping DNS discovery |
cscript ospp.vbs /remhst |
Client | Clears the pinned host and resets the port to 1688 |
cscript ospp.vbs /dhistorykms |
Client | Displays the KMS client activation history |
nslookup -type=all _vlmcs._tcp |
Client | Whether the service record is published and where it points |
slmgr /dlv all |
Host | Licence information for all installed products, which is where an Office entry either is or is not |
slmgr /ato |
Host | Activates the host key against Microsoft |
The two DNS publishing values
| Value | Type | Effect |
|---|---|---|
DnsDomainPublishList |
Multi-string | One DNS domain per line. The host publishes its SRV record into each |
DisableDnsPublishing |
DWORD | 0 or absent: the host registers the record once every 24 hours. 1: it never registers automatically |
Both live under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform. A KMS host publishes into its own DNS domain only, which in a multi-domain forest leaves every other domain’s clients with nothing to find. DnsDomainPublishList is the supported answer; restart the licensing service after changing it, because that restart is what creates the records.
Creating the record by hand
- Open DNS Manager and expand Forward Lookup Zones.
- Right-click the
_tcpfolder in the domain and choose Other New Records. - Select Service Location (SRV), then Create Record.
- Enter service
_VLMCS, protocol_TCP, port number 1688, and the fully qualified name of the KMS host. - On a BIND 9 server the equivalent record is
_vlmcs._TCP, type SRV, priority 0, weight 0, port 1688, pointing at the host’s name.
How long a client can sit like this
| State | What Microsoft publishes |
|---|---|
| Licensed after a KMS activation | 180 days |
| Renewal attempt | Once every seven days by default |
| After 180 days without activation | Office enters the out-of-tolerance state for 30 days |
| First activation on a new client | Succeeds as long as the host has already received at least four prior requests |
The other three entries in this article
0x80072EE7 is documented: WinINet error 12007, ERROR_INTERNET_NAME_NOT_RESOLVED, “The server name could not be resolved.” It points squarely at name resolution. 0x4004F304 has no published description, and its severity bit is clear, which the documented HRESULT layout defines as a success result rather than a failure. Event ID 12294 is the one most often misquoted: Microsoft states that when publishing to DNS succeeds, the host logs 12294. The failure is 12293.
When a licence is the actual fix
If you already hold a volume agreement this costs nothing to fix: the entitlement exists and the work is repairing the host. If you have no host and do not want one, MAK activation is the straightforward alternative for smaller sites, and Active Directory-based activation is a genuinely free option for domain-joined devices, needing only the Office Volume License Pack on a domain controller and the host key you already hold. Where MAK is the right answer, Arco supplies Office LTSC 2024 Professional Plus MAK keys sized to your device count, and will check whether your existing agreement already entitles you to one before you buy anything.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0xC004F074 |
The computer could not be activated because no Key Management Service host could be contacted. Microsoft names five causes: version mismatch, clocks more than four hours apart, sppsvc stopped on the host, TCP 1688 blocked, and a wrong or stale DNS record | Microsoft Learn |
0x4004F304 |
Seen alongside during activation. No published description; its severity bit marks it a success result rather than a failure | not published by the vendor |
0x80072EE7 |
WinINet error 12007, ERROR_INTERNET_NAME_NOT_RESOLVED: the server name could not be resolved | Microsoft Learn |
Event ID 12294 |
Logged on the KMS host when publishing to DNS succeeds. The failure event is 12293 | Microsoft Learn |
Confirm the fix worked
cscript ospp.vbs /dstatuson the client reports a licensed status.- The KMS host name and port shown are the ones you intended.
- On the host,
slmgr /dlv alllists an Office entry with a count that is climbing. - The host’s Application log shows a 12294 rather than a 12293 after the last service restart.
- Reboot one client and confirm it stays activated without anyone touching it.
Questions people ask about this
Does activating Windows against the host prove Office will work?
No, and it is the single most common misunderstanding behind this code. The host needs the Office Volume License Pack for the version you are deploying and an Office KMS host key installed and activated before it can answer an Office client at all.
Is Event ID 12294 an error?
No. Microsoft states that when publishing to DNS is successful, the host logs Event ID 12294 in the Application log. The failure event is 12293, which reports that publishing the Key Management Service to DNS in a given domain failed.
Can I point Office at a KMS host in another domain?
Yes. Automatic discovery only searches the client’s own DNS domain, but a pinned host name accepts any reachable name as long as TCP 1688 is open. For more than a handful of machines, publish into the extra domains with DnsDomainPublishList instead.
How long before this becomes urgent?
A KMS-activated Office client is licensed for 180 days and renews every seven. After 180 days without activation it enters a 30-day out-of-tolerance state. A client that has never activated has much less margin.
Do I have to buy anything?
Usually not. This is nearly always an infrastructure fault on top of an entitlement you already hold. It becomes a purchasing question only if there is no volume agreement behind the Office installations, or the estate is too small for KMS.
