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

UCCX 7 Very Slow Admin Access, Usually None At All

planetmaker
Level 1
Level 1

Hi,

can anyone suggest why CRS admin access and Editor access maybe failing?

The admin page comes up with "waiting for.." status while the page loads for a very long time. It usually times out and if you do get the log in screen logging on juist goes on and on and fails.

I don't want to restart any services that maybe service affecting i.e. knock the Agents off (by the way they are operating fine) unless its out of core hours.

Any help would be gratefully recieved !

1 Reply 1

joesnyde
Cisco Employee
Cisco Employee

Hi,

Try restarting the CCX Administration service. This will not affect the agents in any whay. This is the service used for the CCX appadmin page. Another thought is to check that NIC bidning is setup properly. See page 3-6 of the installation guide,

http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/crs/express_7_0/installation/guide/uccx70ig.pdf

If you have to change the NIC binding you will need to restart the server for the application CCX to update the change. You also might be hitting the following bug;

CSCsu22366
Symptom:
AppAdmin Page will not load, "Page can not be displayed" message on the  browser.
--World Wide Publishing Service stuck in stopping status if IIS attempted to be restarted.

Conditions:
1.Open Browser
2. Type the following url http:///appadmin
3. Receive page can not be displayed or blank page

If you attempt to restart IIS at this time, the only workaround is to reboot  the server.
4. Go to services (start-run-services.msc)
5. Try restarting IIS services, restart will cause worldwide publishing  service
(co-dependent on IIS service) to be stuck in stopping status

Workaround:
Do not attempt to restart IIS . Instead, do the following steps -
1. Open Internet Explorer and type http://crsIPAddress:6293/appadmin/
2. Login to appadmin and go to Control Center page.
3. Select the CRS Administration process radio button and click the "Restart" button.
4. Exit the browser and launch appadmin normally from the Start Menu.
Alternatively, if this is an HA setup, login to appadmin from the 2nd node, go to the
Control Center page, select the broken node, and restart its CRS Administration process

Regards

Joe