03-09-2011 11:29 AM - edited 03-19-2019 02:31 AM
Start > Programs > Cisco Unified Personal Communicator
8.5, I don't get a a username/login at bottom of screen. We are using LDAP profiles. How can I turn on client debug if I can't get tot settings or h
elp?
Screen show show how client starts but doesn't do anything. Just hangs here until I end task or exit.
03-09-2011 11:40 AM
Hi Jason,
Do you have any antivitus installed (ie AVG ?) Can you remove it for a test
Can you try disabling ipv6 if you have it enabled ?
In any case and since this might be useful here are the instructions on how to set and collect detailed logs even though the client doesn't start
1. Make sure CUPC.exe and CUCSF.exe are stopped.
2. Edit userData.properties file.
Windows XP
C:\Documents and Settings\knicgabh\Application Data\Cisco\Unified
Communications\Client Services Framework\Config\userData.properties
Windows 7
C:\Users\
Services Framework\Config\userData.properties
3. Change the following parameter to true.
CcClient-CUPCDetailedLogging=True
4. Start CUPC.
To launch the Problem Report Tool (PRT), execute ProblemReportingTool.exe.
Start -> Run -> "C:\Program Files\Common Files\Cisco Systems\Client
Services Framework\prt\ProblemReportingTool.exe"
-or-
Start -> All Programs -> CUPC 8 -> Create Problem Report
If the PRT does not work for some reason, the logs we need are in the
following locations, zip and send them all:
Windows 7
C:\Users\
Services Framework\Logs
Windows XP
C:\Documents and Settings\
Data\Cisco\Unified Communications\ Client Services Framework\Logs
HTH
Christos
03-09-2011 11:43 AM
Is there a Bug ID or a Support Forums article that has more information about the problem?
03-09-2011 11:57 AM
We are LDAP integrated, would something wrong in the CUPS LDAP Profile cause this to happen? Or is this just a client bug unrelated to the LDAP Profile configured in CUPS
?
03-09-2011 12:00 PM
I don't think so. You are not even reaching the point where you authenticate anyway.
I believe this is local to your PC
Something goes wrong while the client initializes.
Regards,
Christos
02-01-2012 03:44 AM
Hi Jason,
Just seen this thread on the forums. I am also experiencing this behaviour with some CUPC clients running 8.5.5. Did you ever establish the cause?? Any help appreciated.
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