cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
440
Views
0
Helpful
1
Replies

ISE DATABASE PRIMING FAILED

AshkanKiani
Community Member

We have 2 ISE 3.3 servers, there was a odd problem during registering the secondary node, on Primary, It shows it is the Primary node, but there is no Secondary node, on the Secondary node, it displays it as secondary node and is in a deployment.
I performed a application-reset-config on the secondary it shows an error "ISE database PRIMING FAILED", and from then, this secondary node stuck in a complicated situation where its application server stuck in initializing state and there is some other logs in ise-psc.log syaing : 
2026-01-27 1:22:38,352 ERROR [main][[]] cpm.posture.runtime.visibility.VisibilityHandler -:::::- error in finding is this node standalone or pri-pan
com.cisco.epm.pap.api.exceptions.NoSuchHostConfigException: No such HostConfig with hostName [secondary-hostname]

is there any way to fix this issue?

1 Accepted Solution

Accepted Solutions

@AshkanKiani ,

 there are some old and new bugs related to this error, please take a look at: CSCwq11293 ISE 3.5 BH // New installation via VM fails with Database Priming Failed

 Two suggestions:

  • perform the application reset-config without keeping the Certificates
  • install the Secondary Node from scratch

 

Hope this helps !

 

View solution in original post

1 Reply 1

@AshkanKiani ,

 there are some old and new bugs related to this error, please take a look at: CSCwq11293 ISE 3.5 BH // New installation via VM fails with Database Priming Failed

 Two suggestions:

  • perform the application reset-config without keeping the Certificates
  • install the Secondary Node from scratch

 

Hope this helps !