cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1091
Views
0
Helpful
2
Replies
Enthusiast

HTTP Status 500 Error on CUIC Login Page

Hello,

I have a pair of UCCX 10.6 nodes setup in HA using Finesse. When it goes into failover mode (primary down) and agents login to the secondary node they were seeing errors on all the widgets:

Though all the call features seemed to work and agents were able to go into Ready state and answer calls.

So next I attempted to login to the secondary server's CUIC page either via any of the URLs:
http://<IPAddress>:8081/ 
https://<IPAddress>:8444/
http://hostname.domain.com:8081/ 
https://hostname.domain.com:8444/
or the "Cisco Unified Contact Center Express Reporting" link on the UCCX main web page. Each time I am getting the following error:


Which reads the following:

HTTP Status 500 - 
type: Exception report 

message: 

description: The server encountered an internal error that prevented it from fulfilling this request. 

exception: 

BeanCreationException Error creating bean with name 'quartzSchedulerFactoryImpl' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Invocation of init method failed; nested exception is java.lang.IllegalArgumentException: Could not identify the local device in the database config. This could be a configuration problem. Checked for hostname: <hostname.domain.com>, fully qualified hostname: <hostname.domain.com>, hostname without domain name: <hostname>, address: <IPAddress>                

root cause: 

IllegalArgumentException Could not identify the local device in the database config. This could be a configuration problem. Checked for hostname: <hostname.domain.com>, fully qualified hostname: <hostname.domain.com>, hostname without domain name: <hostname>, address: <IPAddress>                

note: The full stack trace of the root cause is available in the logs. 

 

I checked the services and they are all running on both servers. Checked DBReplication and it's good all around.

Wasn't able to find any details on these errors anywhere.

 

Any help would be greatly appreciated!

 

2 REPLIES 2
Beginner

Did you ever manage to

Did you ever manage to resolve this issue?

I am having a similar issue.

Highlighted
Enthusiast

Yes, I had to involve Cisco

Yes, I had to involve Cisco TAC as root level access and changes to the servers are required. The TAC engineer updated a couple tables and files on both servers to resolve this issue.

 

Cisco TAC involvement is necessary to resolve this.

CreatePlease to create content
Content for Community-Ad
July's Community Spotlight Awards