CUCM 14 "Operation Completes by" Problem with 2023

[Ronny K.]

Hi everyone,

i am running a CUCM 14 SU2 and since 2023 started i have Issues Setting the CAPF "Operation Completes by" either via GUI as well as AXL. AXL throws a "UpgradeFinishTime format must be YYYY:MM:DD:HH or YYYY:MM:DD:HH:mm" at me, while the GUI says "Operation Completes By Invalid year/month/day/hour in date field" (see Screenshot).

The automatic CAPF Update via "CAPF Operation Expires in (days)" works just fine, its only the manual operations that have issues.

I also tried several YYYY:MM:DD combinations from in 3 Days, to 2 Weeks over to 6 Months in the future.

ntp is running and the time is correct:

admin:utils ntp status
ntpd (pid 29596) is running...

     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
+134.109.133.27  131.188.3.222    2 u  410 1024  377    0.238   -0.683   0.335
*134.109.133.24  192.150.70.56    2 u  381 1024  377    0.194    1.251   0.217
+134.109.6.1     144.76.43.40     4 u  846 1024  377    0.357    0.421   0.136
-134.109.133.17  60.114.215.234   3 u  814 1024  377    0.331    1.992   0.277


synchronised to NTP server (134.109.133.24) at stratum 3
   time correct to within 46 ms
   polling server every 1024 s

Current time in UTC is : Wed Feb  1 09:05:13 UTC 2023
Current time in Europe/Berlin is : Wed Feb  1 10:05:13 CET 2023

Does Anyone have an Idea? I only found complaints in this regard 

Thank you,
Ronny

[b.winter · Accepted solution]

Maybe because you entered the month in wrong format?
It says MM, but you only entered 1 digit according to your screenshot.

[Ronny K.]

OMG, this is embarrassing... why didn't i see this. I tried different combinations but always one of those numbers just had one digit.

Thank you for hitting me with the obvious!