Not activated

[SKILHUNT]

Use instrucrion but get this log and system not activeted.

Fri, 07 Feb 2025 12:29:24 INFO Connection accepted: 192.168.1.43:50322
Fri, 07 Feb 2025 12:29:24 INFO RPC bind request received.
Fri, 07 Feb 2025 12:29:24 INFO RPC bind acknowledged.
Fri, 07 Feb 2025 12:29:24 INFO Received activation request.
Fri, 07 Feb 2025 12:29:24 INFO Received V6 request on Fri Feb 07 12:29:24 2025.
Fri, 07 Feb 2025 12:29:24 WARNING With count = 26, activated client could be detected as not genuine !
Fri, 07 Feb 2025 12:29:24 INFO Machine Name: DESKTOP-FI4NPDI
Fri, 07 Feb 2025 12:29:24 INFO Client Machine ID: 68b66080-8f6f-4574-a489-73d5f39fb7cb
Fri, 07 Feb 2025 12:29:24 INFO Application ID: Windows
Fri, 07 Feb 2025 12:29:24 INFO SKU ID: Windows 10/11 Professional
Fri, 07 Feb 2025 12:29:24 INFO License Status: Notifications Mode
Fri, 07 Feb 2025 12:29:24 INFO Request Time: 2025-02-07 08:29:21 CET (UTC+0100)
Fri, 07 Feb 2025 12:29:24 INFO Connection closed: 192.168.1.43:50322

[Hobbabobba]

I have the same problem. My docker-compose.yml

name: "kms"
services:
  kms:
    image: "11notes/kms:646f476"
    container_name: "kms"
    environment:
      TZ: "Europe/Berlin"
    volumes:
      - "var:/kms/var"
    ports:
      - "1688:1688/tcp"
    restart: "always"
  kms-gui:
    image: "11notes/kms-gui:latest"
    container_name: "kms-gui"
    environment:
      TZ: "Europe/Berlin"
    volumes:
      - "var:/kms/var"
    ports:
      - "8081:8080/tcp"
    restart: "always"
volumes:
  var:

My logfile:

2025-02-07T12:40:32.000Z 2025-02-07T12:40:32.000Z 2025-02-07T12:40:32.000Z 2025-02-07T12:40:32.000Z 2025-02-07T12:40:32.000Z 2025-02-07T12:40:32.000Z 2025-02-07T12:40:32.000Z 2025-02-07T12:40:32.000Z 2025-02-07T12:40:32.000Z 2025-02-07T12:40:32.000Z 2025-02-07T12:40:32.000Z 2025-02-07T12:40:32.000Z 2025-02-07T12:40:32.000Z 2025-02-07T12:40:32.000Z 2025-02-07T12:40:32.000Z 2025-02-07T12:40:32.000Z type=INF 2025-02-07T12:40:32.000Z 2025-02-07T12:40:32.000Z 2025-02-07T12:40:32.000Z 2025-02-07T12:40:32.000Z 2025-02-07T12:40:32.000Z 2025-02-07T12:40:32.000Z 2025-02-07T12:40:32.000Z 2025-02-07T12:40:32.000Z 2025-02-07T12:40:32.000Z 2025-02-07T12:40:32.000Z 2025-02-07T12:40:32.000Z 2025-02-07T12:40:32.000Z 2025-02-07T12:40:32.000Z 2025-02-07T12:40:32.000Z 2025-02-07T12:40:32.000Z 2025-02-07T12:40:32.000Z type=INF msg=starting kms v646f476
Fri, 07 Feb 2025 13:40:32 WARNING  IPv4 [0.0.0.0] can't be dualstack
Fri, 07 Feb 2025 13:40:32 INFO     TCP server listening at 0.0.0.0 on port 1688
Fri, 07 Feb 2025 13:40:32 INFO     HWID: 8706299C48714246
Fri, 07 Feb 2025 13:41:18 INFO     Connection accepted: 192.168.0.131:57814
Fri, 07 Feb 2025 13:41:18 INFO     RPC bind request received.
Fri, 07 Feb 2025 13:41:18 INFO     RPC bind acknowledged.
Fri, 07 Feb 2025 13:41:18 INFO     Received activation request.
Fri, 07 Feb 2025 13:41:18 INFO     Received V6 request on Fri Feb 07 13:41:18 2025.
Fri, 07 Feb 2025 13:41:18 WARNING  Too many clients ! Fixed with 10
Fri, 07 Feb 2025 13:41:18 INFO     Machine Name: LAPTOP-14LAC5FN
Fri, 07 Feb 2025 13:41:18 INFO     Client Machine ID: 5bbea8ee-7e91-41f9-bb36-652e4bc96fe3
Fri, 07 Feb 2025 13:41:18 INFO     Application ID: Office 15 (2013) / 16 (2016) / 17 (2019)
Fri, 07 Feb 2025 13:41:18 INFO     SKU ID: Office Standard 2019
Fri, 07 Feb 2025 13:41:18 INFO     License Status: Activated
Fri, 07 Feb 2025 13:41:18 INFO     Request Time: 2025-02-07 12:41:18 CET (UTC+0100)
Fri, 07 Feb 2025 13:41:18 INFO     Connection closed: 192.168.0.131:57814

On the clientside i get this error message:

C:\Program Files\Microsoft Office\Office16>cscript ospp.vbs /act
Microsoft (R) Windows Script Host, Version 5.812
Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten.

---Processing--------------------------
---------------------------------------
Installed product key detected - attempting to activate the following product:
SKU ID: 6912a74b-a5fb-401a-bfdb-2e3ab46f4b02
LICENSE NAME: Office 19, Office19Standard2019VL_KMS_Client_AE edition
LICENSE DESCRIPTION: Office 19, VOLUME_KMSCLIENT channel
Last 5 characters of installed product key: 9D9HK
ERROR CODE: 0xC004F074
ERROR DESCRIPTION: The Software Licensing Service reported that the product could not be activated. No Key Management Service (KMS) could be contacted. Please see the Application Event Log for additional information.
To view the activation event history run: cscript ospp.vbs /dhistorykms
NOTICE: A KB article has been detected for activation failure: 0xC004F074
FOR MORE INFORMATION PLEASE VISIT: https://support.microsoft.com/kb/2870357#Error0xC004F074
---------------------------------------
---------------------------------------
---Exiting-----------------------------

[boblapo]

KMS can activate both physical computers and virtual machines, but a network must meet or exceed the activation threshold (minimum number of computers that KMS requires) of 25.
from
https://py-kms.readthedocs.io/en/latest/Documentation.html#understanding-key-management-service

read,
https://woshub.com/how-to-increase-kms-server-current-count/

[boblapo]

Relates to bug
Py-KMS-Organization/py-kms#117

Python is 3.12.8 in the container which makes py-kms "looks" ok but it's just not working.

[ajgon]

Downgrading to python 3.11.11 solved issue for me.

Edit: Setting --build-arg APP_VERSION=next also did the trick (without need to downgrade).

[11notes]

Downgrading to python 3.11.11 solved issue for me.

Edit: Setting --build-arg APP_VERSION=next also did the trick (without need to downgrade).

❤️❤️❤️❤️❤️ thank you. I'm not a Python coder so I just assumed upgrading to 3.12 does no harm. Will rebuild with 3.11 but I have to first make an Alpine package since on 3.21 of Alpine there is only 3.12.

I did not check the next branch of py-kms yet since there is no documentation about it. Do you know what the next branch is supposed to be?

[ajgon]

@11notes I'm not a python dev as well, so no clue - but according to comparision between master and next - they didn't change much. I assume next working on python 3.12 is byproduct of that :)

Edit: I think, you can always freeze APP_VERSION to the current next commit: 465f4d14. So when they start messing things up, it won't break your build.

[SKIYET]

@11notes also reproduced the issue. Hope to see a perfect solution from you.

[didotb]

I did not check the next branch of py-kms yet since there is no documentation about it. Do you know what the next branch is supposed to be?

the next branch fixes a bunch of stuff, but IMO the most important is the EPID generation, and I highly recommend using that branch instead. There are also some added KMS ID from the KmsDatabase.

[11notes]

@SKIYET @ajgon @didotb @boblapo this issue is now resolved by switchting to next branch but keeping python 3.12. I try to use a new base image this week based on 11notes/python:3.12 to ditch the 11notes/alpine:stable for a better workflow and add also the automatic rebuild of kms-gui on updates of this repo. Hope that helps. I have seen though that the next kmsdb does not contain all IDs so I will try to add all missing ones as well as Office keys.