08-08-2013 09:13 AM - edited 03-16-2019 06:45 PM
I installed Cisco unity connection 7.x successfully
I can reach the webpage ( 10.10.210.13)
But after clicking on the link i receive the message
If i remove cuadmin and put ccmadmin i'm able to get to the serviceability page and activate services.
But when i go to administration webpage this will not work.
What could be the cause??
Any help will be appeciate!
I attached a file
Solved! Go to Solution.
11-04-2019 07:17 AM
This process worked for 12.5.1 SU1 Unity as well. Thanks for the tip.
08-11-2014 12:35 PM
Tried all solutions mentioned to no avail. I have reinstalled CUC 4 times now, fresh install each time. No Joy..... I am installing on a Cisco UCSC-C220-M3SBE server that had the following servers preloaded (or at least the *.OVA was loaded):
Cisco Prime Collaboration Provisioning
Cisco Unified Communications Manager
Cisco Unified Contact Center Express
CUCM IM and Presence Server
We had purchased the Unity portion of the server but for some reason it had not been preloaded. I proceeded after bringing all 4 other servers online to load the .ova file for CUC and then load the .iso. I have successfully loaded the .ova and .iso all four times without any visible errors. The main website for the given IP address x.x.x.x comes up with the selection of the License Server and the Cisco Unity Connection server but when you select the CUC it throws the "HTTP Status 404 - /cuadmin/home.do" error saying the requested resource is not available. However the Licensing portal/portion of the main page has worked flawlessly from the beginning. I can log into it from the originating x.x.x.x web page and see it fine.
The other Cisco instances on the VM server work great so far and I have had no problems with any of them. Real weird. Cisco Tech support has been stummped so far by this one. Anyone have any additional ideas?
08-12-2014 04:34 PM
With a BE6K the server should be in the inventory alreayd. I suggest you start a new thread for your issues.
04-25-2017 10:50 AM
I also had this issue. Event those the Cisco Tomcat Service said started, I would get the related error.
Turns out I just wasn't being patient. It came back 5 - 10 minutes after I noticed Tomcat had started.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide