I have installed IM and Presence 10.x (System version: 10.0.1.10000-26) as a Subs and Cisco Sync Agent does not Start. I tried restart the services but never start.
Is there any bug for this version?
Thanks in Advance for help!
Please try the following steps
1.Remove all UC Service and Service Profile
3.Add UC Service and Service Profile manually
4.Start UP Sync agent
Let us know if it helps.
I have not configured any UC Service (on CUCM>User Management>User Settings>UC service) and also Service profile (on CUCM>User Management>User Settings>service Profile).
I did restart the Cisco Tomcat and then Sync Agent but no luck!, still Sync Agent is not running.
Anyway, thanks your info.
Looks like IM and Presence 10.1 hitting some kind of Bug that's why Sync Agent never starts.
Anyway I did install 10.5 Version and it is working fine and Sync Agent UP and Running , no issues.
Thanks for your reply Uddin.
So did you upgrade CUCM to 10.5 then upgrade CUP to 10.5 after?
Will there be any license issue?
I can't believe CUP 10.1 is just not working...
I am having the same issue.
I actually just did a fresh installation, this is the first IM node in the cluster, however while I went through the installation process it was always saying "this is not the first node of the cluster".
After installation, the Cisco Sync Agent and Cisco XCP Directory Service are both not running.
Tried restart, same issue
Could anybody help me out? thanks a lot
Hi Uddin and everybody facing the issue,
There are couple of defects with IM and Presence version 10.5.1 and 10.5.2 affecting your issue. Check these: CSCup88194 and CSCut52781. Both of them have a workaround which needs TAC intervention (to be implemented in root of the server).
Also, collect the Cisco Sync Agent logs from the IM and Presence server, before approaching Cisco TAC. You can collect those through the IMnP server CLI using the commands:
file list activelog /epas/trace/epassa/log4j
file view activelog /epas/trace/epassa/log4j/<file name from list> --- to view the contents of the file on CLI itself
file get activelog /epas/trace/epassa/log4j
As of now, most of the cases end up (specially with version 10.5.2) end up rebuilding the server, but can also be worked out as per the defect details.
Hope this helps!