topic Re: ISE 3.2 - Getting "An unexpected error occurred." in Network Access Control

ISE 3.2 - Getting "An unexpected error occurred."

vgaur — Wed, 20 Sep 2023 10:26:23 GMT

Hello Everyone,

While trying to generate certificate using Certificate Provisioning Portal, I'm getting the following error :

I thought I might be running into bug : https://bst.cisco.com/bugsearch/bug/CSCwa03797
But even the workarounds aren't working, not sure what could be the issue. Any help is greatly appreciated.

Re: ISE 3.2 - Getting "An unexpected error occurred."

ahollifield — Wed, 20 Sep 2023 13:45:22 GMT

I've had this issue as well. Re-generating the ISE root CA solved the issue for me. You can also attempt to generate the certificate using the pxGrid workflow as well.

Re: ISE 3.2 - Getting "An unexpected error occurred."

vgaur — Thu, 21 Sep 2023 05:39:49 GMT

Tried doing that, still getting the error.

Re: ISE 3.2 - Getting "An unexpected error occurred."

ahollifield — Thu, 21 Sep 2023 14:52:57 GMT

The same exact error? What ISE version and patch?

Re: ISE 3.2 - Getting "An unexpected error occurred."

vgaur — Thu, 21 Sep 2023 15:14:36 GMT

Yup! same error, ISE version 3.2 Patch 3

Re: ISE 3.2 - Getting "An unexpected error occurred."

ahollifield — Thu, 21 Sep 2023 18:39:01 GMT

I would suggest opening a TAC case.

Re: ISE 3.2 - Getting "An unexpected error occurred."

rafaelsalvinos — Sun, 04 Feb 2024 19:09:50 GMT

Hi @vgaur

I solve this probleme, following this step:

Choose Administration > System > Certificates > Certificate Management > Certificate Signing Requests.

Click Generate Certificate Signing Requests (CSR).

choose ISE Root CA no Certificate(s) will be used for a lista suspensa

Click Replace ISE Root CA Certificate Chain .

https://www.cisco.com/c/pt_br/support/docs/security/identity-services-engine-30/217161-ca-service-and-est-service-on-ise.html

Re: ISE 3.2 - Getting "An unexpected error occurred."

vgaur — Mon, 05 Feb 2024 05:18:02 GMT

Hello @rafaelsalvinos - Thanks for the info, although I ended up rebuilding the node from scratch by deleting the old node and creating a new instance on AWS which fixed the issue.

It was a fairly new deployment so this was an option but if I run into this issue again (fingers crossed) I'll try your method.