PDF(75.3 KB) View with Adobe Reader on a variety of devices
ePub(72.9 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(66.9 KB) View on Kindle device or Kindle app on multiple devices
Updated:November 21, 2017
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes a procedure on how to collect Windows Server specific logs for Cisco Unified Contact Center Enterprise (UCCE) issue.
In certain scenarios, in order to troubleshoot Cisco UCCE issues, Cisco TAC engineer requires to collect Windows server logs. This document provides guidelines on what logs need to be collected and how to collect them.
Collect Windows Server Logs for Cisco UCCE Issue
This section gives a basic information about the Windows server operation - system information, network configuration, processes and sockets.
whoami > c:\temp\tac-ucce-techinfo.txt
systeminfo >> c:\temp\tac-ucce-techinfo.txt
netstat -ano >> c:\temp\tac-ucce-techinfo.txt
tasklist /v >> c:\temp\tac-ucce-techinfo.txt
netsh int tcp show global >> c:\temp\tac-ucce-techinfo.txt
netsh int ip show offload >> c:\temp\tac-ucce-techinfo.txt
wmic product get name,version > c:\temp\tac-ucce-sw-list.txt wmic qfe list >> c:\temp\tac-ucce-sw-list.txt
Launch Run tool, type ncpa.cpland click OK. Now press Alt key and navigate to Advanced > Advanced Settings. Make a screenshot. Ensure that the Public network interface is the first in the list followed by the Private network interface.
Add the output files to an archive and send it to Cisco TAC engineer.
Event Viewer Logs
Launch Run tool, type eventvwr and click OK. In the Event Viewer (Local) pane expand Windows Logs. Right click on Application and Save All Event As... Provide a file name and select Text Files as a file type. Save the file.
Note: In case if you need to collect Security, Setup, System log on top of the Application log right click on the appropriate file and follow the same steps.
You can filter the log based on the relevant day and time.
In order to filter the output right click on the log and click Filter Current Log... and set Logged: value to, for example, Last 7 days and click OK.
In order to save the filtered output right click on the log and select Save Filtered Log File As..., set Save as type parameter to Text (Tab delimited) value and click OK.
Launch Run tool, type regedit and click OK. Navigate to Computer > HKEY_LOCAL_MACHINE > SOFTWARE > Cisco Systems, Inc.. Right click on the Cisco Systems, Inc. folder and click Export. Provide a file name and select Text Files as a file type. Save the file.
SQL Database Server
Log in to Microsoft SQL Server Management Studio (SSMS) tool. In the Object Explorer window navigate to SQL Server Agent > Error Logs > right click on Current > select View Agent log. In the Select logs window, check SQL Server and SQL Server Agent menus and click Export. Save the log file.
In order to do basic domain controller health check, use these commands.