|
UC Blogs... |
|
 |
|
|
How to enable Logging for Microsoft Office Communicator 2007? |
Enable Communicator File
Tracing on the client side (Where office communicator is installed)
-
You can enable
Communicator File Tracing by doing the following Registry keys on your client.
-
HKCU\Software\Microsoft\Tracing\uccp\Communicator
-
Inside the folder
there is a key called EnableFileTracing. By default it will be 0. Change
it to 1.
-
Also there is
a FileDirectory path where the log files get stored. By default this is in
the %USERNAME% directory. You can change it according to your preference.
-
After you make
the above changes.
-
Exit out of
the registry
-
Re-launch the
office communicator (after the above setting you need to kill communicator process
and re-launch it.)
-
Reproduce the
issue you want to capture
-
Go to your user
profile. There should be a folder "tracing" inside that. This folder has the uccp
log.
Note:
For Office Communicator enable the following key as mentioned above:
\HKEY_Current_user\software\microsoft\tracing\uccp\communicator
enablefiletracing 1
For Conferencing issues use this key:
\HKEY_Current_user\software\microsoft\tracing\uccp\Confapi
enablefiletracing 1
For Live Meeting Issues use this key:
\HKEY_Current_user\software\microsoft\tracing\uccp\livemeeting
enaablefiletracing 1

Note: There is a
tool "snooper.exe" in the OCS 2007 resource kit. you can use this tool to analyse
the uccp log generated after the above steps. Open the uccp log in snooper.exe and
analyze it. (Pretty much useful!)
|
|
|
|
Copyright, OCSpedia.com. Microsoft, MS-DOS, Windows, Windows 2000, Windows XP,
Windows Server 2003, Windows NT, Windows 98, Windows 95 are either registered trademarks
or trademarks of Microsoft Corporation in the U.S.A. and other countries. All other
names are registered trademarks of their respective companies. Should any right
be ran afoul, it is totally unintentional. Send us an e-mail and we will promptly
and gladly rectify it. All external sites will open in a new browser. Ocspedia.com
does not endorse external sites and is not responsible for their content. For broken
links, site problems or any feedback - please send at uc@ocspedia.com |