PCCE 12.6(1) Inventory Error during configuration

[Kyle Sullivan]

I'm trying to get PCCE 12.6(1) running in my lab. I've been stuck for 4 days with Inventory file errors trying to configure in Simplex lab mode. I found one post regarding Certificate exchanges however all the Pre, Post and installation documentation/ videos I've watched haven't mentioned any thing about certificates at this point. I have copied the configuration error log:

Error occurred
Unable to create the inventory. Fix the errors below before continuing.
2023-05-08T11:31:40-04:00 - Job created
2023-05-08T11:31:40-04:00 - Job started
2023-05-08T11:31:40-04:00 - Processing line 1: Header
2023-05-08T11:31:40-04:00 - Processing line 2: operation=CREATE, name=pcce-rgr-a, machineType=CCE_ROGGER, publicAddress=192.168.30.237, publicAddressServices=, privateAddress=192.168.146.237
2023-05-08T11:31:40-04:00 - Processing line 3: operation=CREATE, name=pcce-aw-a, machineType=CCE_AW, publicAddress=192.168.30.232, publicAddressServices=type=DIAGNOSTIC_PORTAL&userName=pcceadmin@corp.company.com&password=********, privateAddress=
2023-05-08T11:31:40-04:00 - Processing line 4: operation=CREATE, name=pcce-pg1-a, machineType=CCE_PG, publicAddress=192.168.30.236, publicAddressServices=, privateAddress=192.168.146.236
2023-05-08T11:31:41-04:00 - Processing line 5: operation=CREATE, name=pcce-cvp-a, machineType=CVP, publicAddress=192.168.30.234, publicAddressServices=type=CVP_WSM&userName=pcceadmin@corp.company.com&password=********, privateAddress=
2023-05-08T11:31:41-04:00 - Processing line 6: operation=CREATE, name=hq-ucm125pub, machineType=CM_PUBLISHER, publicAddress=192.168.30.220, publicAddressServices=type=AXL&userName=pcce-pg1&password=********, privateAddress=
2023-05-08T11:31:41-04:00 - Processing line 7: operation=CREATE, name=pcce-cuic-a, machineType=CUIC_PUBLISHER, publicAddress=192.168.30.233, publicAddressServices=type=DIAGNOSTIC_PORTAL&userName=pcceadmin&password=********; type=IDS&userName=pcceadmin&password=********, privateAddress=
2023-05-08T11:31:41-04:00 - Processing line 8: operation=CREATE, name=pcce-fin-a, machineType=FINESSE, publicAddress=192.168.30.235, publicAddressServices=type=DIAGNOSTIC_PORTAL&userName=pcceadmin&password=********, privateAddress=
2023-05-08T11:31:41-04:00 - Error processing line 5: Unable to connect to the requested resource: https://192.168.30.234:8111
2023-05-08T11:31:41-04:00 - Error processing line 6: Cannot connect to the AXL service. https://192.168.30.220:8443/axl/
2023-05-08T11:31:41-04:00 - Error processing line 7: Can't connect to CUIC Diagnostic Portal Service, Unable to connect to the requested resource: https://192.168.30.233:8553
2023-05-08T11:31:41-04:00 - Job failed due to errors
2023-05-08T11:31:41-04:00 - 7 lines processed, 0 succeeded, 3 failed
2023-05-08T11:31:41-04:00 - No objects were created or updated

Any assistance would be appreciated.

Kyle

[Gerry O'Rourke]

Great - that all makes sense.
Glad you have it working now.
Gerry

[lliborio05]

Just for the info the failing of the Jtapi download from the CUCM 11.5 SU9 or up ended on a defect. Rigth now the only option is to upgrade the CUCM first.

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwi01998

Regards

Luis Liborio

[svaux]

Hi Luis, Great diagnostic, We just hit this ourselves today! 

[ptegan]

Hello all! Looking for guidance to see if I have the same issue as described above.

PCCE 12.6.2 & CUCM 11.5 SU9

I have the same error message in the SPOG which suggests that it's looking for something but unable to find it.

But looking in the CCBU logs I don't see a failed GET from the CUCM but a failed PUT to the PG:

0000004008: MKTMPRUCHDS01: Nov 07 2023 03:34:41.585 -0800: %CCBU_150-INVENTORYUPDATEASYNCTASK-3-REST_API_EXCEPTION: %[exception=com.cisco.ccbu.cce.unifiedconfig.api.error.CceDBDataNotFoundException: The specified URL does not exist.][message_string=Error 404 occurred while trying to PUT to https://10.25.210.40:443 ]: The REST API has caught an exception com.cisco.ccbu.cce.unifiedconfig.api.error.CceDBDataNotFoundException: The specified URL does not exist.

The account that I'm using can get to the URL if I try manually in a browser or in Postman.

Even if this is something else I know based on the great work done above that I'll hit this bug anyhow but was unsure if I'm already there or not

[lliborio05]

Hi Ptegan,

Check the CCBU Logs of the PG, because from what i remember you have a PUT on the AW towards the PG (the IP 10.25.210.40 is probably your PG) and then on the PG CCBU logs you should see the GET to the CUCM with the file that it is trying to download.

Regards

LL

[ptegan]

I'm not sure that I've ever been happier to confirm a bug. Well at least I can stop searching now

0000000170: MKTMPRUCPG01: Nov 07 2023 05:34:41.577 -0600: %CCBU_ajp-nio-127.0.0.1-8009-exec-10-6-REST_API_INFO: Response Got is GET https://10.25.210.10:8443/plugins/CiscoJTAPIx64-Windows.exe returned a response status of 404 Not Found

11.5.1 SU9 seems to have the issue. Do we know if SU10 or SU11 are the ones that introduces the .exe version of jtapi ?

[lliborio05]

It's the other way around.

"Starting from Release 11.5(1)SU9, and any subsequent SU or ES releases in this release train, Cisco JTAPI Client for Linux, and Windows will be available as the zip file (.zip) "

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/jtapi_dev/11_5_1/CUCM_BK_C04D9E75_00_jtapi-developers-guide_1151/CUCM_BK_C04D9E75_00_jtapi-developers-guide_1151_chapter_0100.html

From 11.5 SU9 onwards it's .zip, so you will have the same problem with SU10 and SU11, we actually had SU10 and to overcome this we had to upgrade the CUCM to the 12.5, (to maintain compatibility with the old CCE solution and in the end of the project we will have to upgrade the CUCM again to v14), since downgrades are not possible.

[ptegan]

> It's the other way around.

You know...I had considered that it was but then thought that it wasn't possible that Cisco made a change to Jtapi from 11.5 SU9 onwards but then reverted it in future releases!

TAC case opened but looks like it's time to dust down the CUCM 12.5 installation.