Hi,

I'm running Omada Software Controller 6.2.10.17 on Windows Server 2025 and seeing the following error repeating in the server.log at the start of each month:

Command failed with error 67 (CannotCreateIndex): 'namespace name generated from index name "omada_data.clienthistory_2026m06_t1s1.$site_1_type_1_last_seen_-1_associated_-1_port_1_guest_1_mac_1_radio_Id_1_multi_radio_Id_1" is too long (127 byte max)'

The error occurs when the controller tries to create its monthly clienthistory collection index. The auto-generated index name exceeds MongoDB's 127 byte namespace limit.

This might be a bug introduced in 6.2.10.17 as the index name is too long by design. The error repeats every second and fills the log.

Has anyone else encountered this and found a fix or workaround? Is there a planned fix from TP-Link?

Running:

• Omada Controller 6.2.10.17 on Windows Server 2025
• 2x EAP660HD APs ver. 1.1.5
• 1x EAP773 AP ve. 1.4.3

Thanks