From 3b7f615d0074b019badc06ea3ec4f62773e80062 Mon Sep 17 00:00:00 2001 From: sevend2 <77822529+sevend2@users.noreply.github.com> Date: Fri, 19 Apr 2024 15:13:13 +0800 Subject: [PATCH 1/8] Update .openpublishing.redirection.developer.json --- .openpublishing.redirection.developer.json | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/.openpublishing.redirection.developer.json b/.openpublishing.redirection.developer.json index d6dab1f18f..2f5776e7ed 100644 --- a/.openpublishing.redirection.developer.json +++ b/.openpublishing.redirection.developer.json @@ -4694,6 +4694,26 @@ "source_path": "support/developer/visualstudio/installation/visual-studio-requires-computer-newer-version-windows.md", "redirect_url": "/previous-versions/troubleshoot/visualstudio/install/visual-studio-requires-computer-newer-version-windows", "redirect_document_id": false + }, + { + "source_path": "support/sql/general/sql-base-diagnostics-collector.md", + "redirect_url": "/troubleshoot/sql/tools/sql-support-troubleshooting-diagnostic-tools", + "redirect_document_id": true + }, + { + "source_path": "support/sql/general/rs-diagnostics-collector-information.md", + "redirect_url": "/troubleshoot/sql/tools/sql-support-troubleshooting-diagnostic-tools", + "redirect_document_id": false + }, + { + "source_path": "support/sql/general/connectivity-diagnostics-collector.md", + "redirect_url": "/troubleshoot/sql/tools/sql-support-troubleshooting-diagnostic-tools, + "redirect_document_id": false + }, + { + "source_path": "support/sql/general/setup-data-collection-diagnostic-tool.md", + "redirect_url": "/troubleshoot/sql/tools/sql-support-troubleshooting-diagnostic-tools", + "redirect_document_id": false } ] } From 59e3f747312db2468e0328856227e90c5bf1f3af Mon Sep 17 00:00:00 2001 From: sevend2 <77822529+sevend2@users.noreply.github.com> Date: Fri, 19 Apr 2024 15:13:52 +0800 Subject: [PATCH 2/8] Update .openpublishing.redirection.developer.json --- .openpublishing.redirection.developer.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.openpublishing.redirection.developer.json b/.openpublishing.redirection.developer.json index 2f5776e7ed..dffa5d4002 100644 --- a/.openpublishing.redirection.developer.json +++ b/.openpublishing.redirection.developer.json @@ -4698,7 +4698,7 @@ { "source_path": "support/sql/general/sql-base-diagnostics-collector.md", "redirect_url": "/troubleshoot/sql/tools/sql-support-troubleshooting-diagnostic-tools", - "redirect_document_id": true + "redirect_document_id": false }, { "source_path": "support/sql/general/rs-diagnostics-collector-information.md", From 8a018057e2d13086acac9cd7c83fb97cfc1a248c Mon Sep 17 00:00:00 2001 From: sevend2 <77822529+sevend2@users.noreply.github.com> Date: Fri, 19 Apr 2024 15:14:42 +0800 Subject: [PATCH 3/8] Delete support/sql/general/sql-base-diagnostics-collector.md --- .../general/sql-base-diagnostics-collector.md | 442 ------------------ 1 file changed, 442 deletions(-) delete mode 100644 support/sql/general/sql-base-diagnostics-collector.md diff --git a/support/sql/general/sql-base-diagnostics-collector.md b/support/sql/general/sql-base-diagnostics-collector.md deleted file mode 100644 index d252c50106..0000000000 --- a/support/sql/general/sql-base-diagnostics-collector.md +++ /dev/null @@ -1,442 +0,0 @@ ---- -title: SQL Base Diagnostics Collector -description: This article describes the information that may be collected from a computer when the SQL Base Diagnostics Collector tool is running. -ms.date: 11/11/2020 -ms.custom: sap:General -ms.reviewer: ramakoni, dansha ---- -# SQL Base Diagnostics Collector for Windows Server - -This article describes the information that may be collected from a computer when the SQL Base Diagnostics Collector tool is running. - -_Original product version:_   SQL Server -_Original KB number:_   2696886 - -## Summary - -The SQL Base Diagnostics Collector for Windows Server collects diagnostic information that is useful in troubleshooting a broad class of issues that involve the Microsoft SQL Server engine. The SQL Base Diagnostics collector also collects limited diagnostic information for SQL Server Analysis Services. - -The SQL Base Diagnostics Collector supports the SQL Server and SQL Server Analysis Services. - -## Prerequisite software - -There are different prerequisites to run diagnostic packages, depending on the operating system of the target computer. The diagnostic will automatically check your computer for these prerequisites and start executing if they are already installed. Or, you are prompted to install the prerequisites if they are not already available on the computer. The Microsoft Automated Troubleshooting Service (MATS) may also install required software for you. For example, if Windows PowerShell is not present on the target computer, MATS will install it automatically. For more information, see [Information about Microsoft Automated Troubleshooting Services and Support Diagnostic Platform](https://support.microsoft.com/help/2598970). - -## Required Windows rights - -The SQL Server Base Diagnostics Collector must be run by a user who has administrative rights on the computer where the SQL Base Diagnostics Collector is executed. - -## SQL Server security requirements - -The SQL Base Diagnostics Collector discovers all instances of SQL Server that are installed on the computer where the diagnostics tool is run. As part of the data collection process, the SQL Base Diagnostics Collector will try to connect to each instance of SQL Server that the diagnostic tool discovers to collect information about the current SQL Server configuration and server "state." Database connections are made by using Windows authentication. The user who is executing the SQL Base Diagnostics Collector must have a Windows logon that is a member in the sysadmin fixed server role for the following diagnostic collection tasks to succeed: - -- SQL Server Always On Configuration Collection -- SQLDIAG Data Collection Scripts - -## Support for Windows failover clusters - -The SQL Base Diagnostics Collector is cluster-aware and will collect cluster-specific information when the diagnostic tool is run against a Windows Server Failover Cluster. - -To diagnose SQL Server Always On Availability Group failovers, or SQL Server cluster resource failovers, you may have to run the SQL Base Diagnostic collector against more than one cluster node to collect all the necessary troubleshooting information: - -- Run the SQL Base Diagnostic Collector against the cluster node that currently owns the SQL Server Always On Availability Group or SQL Server cluster resource that experienced the failover. This is necessary as the information that is collected for SQL Server and SQL Server Always On resides on the cluster disk resource, and is failed over with the Always On Availability Group or SQL Server cluster resource to the new owning node. - -- Run the SQL Base Diagnostic Collector against the node where the failure occurred. This enables the collection of the cluster log from the cluster node where the failure occurred. - -## Information that is collected - -- System event log - - > [!NOTE] - > The SQL Base Diagnostics Collector collects events from the last 30 days. - - |Description|File name| - |---|---| - |System event log in TXT, CSV, and EVT or EVTX formats| __ evt_System.csv_
__ evt_System.txt_
__ evt_System.(evt or evtx)_| - -- Application event log - - > [!NOTE] - > The SQL Base Diagnostics Collector collects events from the last 30 days. - - |Description|File name| - |---|---| - |Application event log in TXT, CSV, and EVT or EVTX formats| __ evt_Application.csv_
__ evt_Application.txt_
__ evt_Application.(evt or evtx)_ | - -- Registry information that is related to Session Manager and to debugging - - |Description|File name| - |---|---| - |Collect Registry Key - HKLM\Software\Microsoft\Windows NT\CurrentVersion\AEDebug| __Recovery_Registry.txt_| - |Collect Registry Key - HKLM\Software\Microsoft\DrWatson| __Recovery_Registry.txt_ | - |Collect Registry Key - HKLM\System\CurrentControlSet\Services\i8042prt\Parameters| __Recovery_Registry.txt_ | - |Collect Registry Key - HKLM\System\CurrentControlSet\Control| __Recovery_Registry.txt_ | - |Collect Registry Key - HKLM\System\CurrentControlSet\Control\Session Manager| __Recovery_Registry.txt_| - -- Existing Dr. Watson log files and Windows error reporting memory dumps for the SQL Server process - - |Description|File Name| - |---|---| - |Report that contains information about memory dumps and about computer settings that are related to memory dumps in htm and txt formats| __DumpReport.htm_
__DumpReport.txt_ | - |Windows error reporting memory dump files for SQL Server process that are at most 30 days old and less than or equal to 25 MB| __ _DMP_(Date).zip

| - -- Information about all services that are installed on the destination computer - - |Description|File Name| - |---|---| - |Collect information about services that are installed on the target computer| __SC_Services_Output.txt_ | - -- Information about filter drivers that are installed on the destination computer - - |Description|File Name| - |---|---| - |Upper and lower filter drivers enumerated by the fltrfind.exe utility| __ _FltrFind.txt| - -- Report of mini-filter drivers - - |Description|File Name| - |---|---| - |Enumerate mini-filter drivers by using Fltmc.exe| __Fltmc.TXT_| - -- Information about all the running processes and driver details together with their file versions - - |Description|File Name| - |---|---| - |%programfiles%\*.sys| __sym_ProgramFiles_SYS.CSV_ | - |%programfiles%\*.sys| __sym_ProgramFiles_SYS.TXT_ | - |Running Drivers| __sym_RunningDrivers.CSV_ | - |Running Drivers| __sym_RunningDrivers.TXT_ | - |%windir%\system32\drivers\*.*| __sym_Drivers.CSV_| - |%windir%\system32\drivers\*.*| __sym_Drivers.TXT_ | - |%SystemRoot%\System32\iscsi*.*| __sym_MS_iSCSI.CSV_ | - |%SystemRoot%\System32\iscsi*.*| __ _sym_MS_iSCSI.TXT* | - |Running Processes| __sym_Process.CSV_ | - |Running Processes| __sym_Process.TXT_ | - |%SystemRoot%\System32\*.DLL| __sym_System32_DLL.CSV_ | - |%SystemRoot%\System32\*.DLL| _sym_System32_DLL.TXT* | - |%SystemRoot%\System32\*.EXE| __sym_System32_EXE.CSV_ | - |%SystemRoot%\System32\*.EXE| __sym_System32_EXE.TXT_ | - |%SystemRoot%\System32\*.SYS| __sym_System32_SYS.CSV_ | - |%SystemRoot%\System32\*.SYS| __sym_System32_SYS.TXT_ | - |%SystemRoot%\SysWOW64\*.dll| __sym_SysWOW64_DLL.CSV_ | - |%SystemRoot%\SysWOW64\*.dll| __sym_SysWOW64_DLL.TXT_ | - |%SystemRoot%\SysWOW64\*.exe| __sym_SysWOW64_EXE.CSV_ | - |%SystemRoot%\SysWOW64\*.exe| __sym_SysWOW64_EXE.TXT_ | - |%SystemRoot%\SysWOW64\*.sys| __sym_SysWOW64_SYS.CSV_ | - |%SystemRoot%\SysWOW64\*.sys| __sym_SysWOW64_SYS.TXT_ | - -- Performance-related information that is captured from the destination computer - - |Description|File Name| - |---|---| - |One-minute basic perfmon capture of overall system performance from Windows Server 2008 and later versions| __Performance Counter.blg_ | - |One-minute basic perfmon capture of overall system performance from Windows Server 2003| *_Perfmon_(DateAndTime).blg* | - |System performance report that is generated from the collected perfmon log| __report.html_| - -- Information about the networking configuration of the destination computer - - |Description|File Name| - |---|---| - |This report outputs the number of unique local TCP ports in use (above the starting port) for each IP address and process on the target computer| __PortUsage.txt_| - |SMB Basic Information| __SMB-Info.txt_| - |TCP/IP Basic Information| __TcpIp-Info.txt_| - |DNS Client Hosts file| __DnsClient_HostsFile.TXT_| - |IPCONFIG /DISPLAYDNS command output| __DnsClient_ipconfig-displaydns.TXT_| - |NETSH DNSCLIENT SHOW STATE command output

> [!NOTE]
> This command not valid on Windows Server 2003| __DnsClient_netsh_dnsclient-show-state.TXT_| - |DNS Client Registry Entries| *_DnsClient_reg_.TXT*| - -- List of updates that are installed on the destination computer - - |Description|File Name| - |---|---| - |List of updates that are installed on the target computer in CSV, TXT, and HTM format| __Hotfixes.CSV_
__Hotfixes.TXT_
__Hotfixes.HTM_| - -- Information about scheduled tasks that are configured on the destination computer - - |Description|File Name| - |---|---| - |Scheduled tasks list in CSV and TXT format| __schtasks.csv_
__schtasks.txt_| - -- Boot configuration data for the destination computer - - |Description|File Name| - |---|---| - |Output from Bcdedit.exe

> [!NOTE]
> Only collected from Windows 7, Windows Server 2008 R2, Windows Server 2008, and Windows Vista| __BCDEdit.TXT_| - |Output from Bcdedit.exe

> [!NOTE]
> Only collected from Windows 7, Windows Server 2008 R2, Windows Server 2008, and Windows Vista| __BCD-Backup.BKP_| - |Boot.ini

> [!NOTE]
> Only collected on Windows Server 2003| __Boot.ini_| - -- Registry backup and text dump files of CurrentControlSet and SQL Server registry hives - - |Description|File Name| - |---|---| - |HKLM\System\CurrentControlSet\SessionManagers| __ _CurrentControlSet_Reg.txt| - |HKLM\SYSTEM\CurrentControlSet\Control\Lsa| __ _CurrentControlSet_Reg.txt| - |HKLM\SYSTEM\CurrentControlSet| __ _CurrentControlSet_Reg.hiv| - |HKLM\SOFTWARE\Microsoft\Microsoft SQL Server|_REG_SQL.TXT| - |HKLM\SOFTWARE\Microsoft\MSSQLServer| __REG_SQL.TXT_| - |HKLM\SOFTWARE\Microsoft\Microsoft SQL Server 2005 Redist| __REG_SQL.TXT_| - |HKLM\Software\Microsoft\MSFTESQLInstMap| _REG_SQL.TXT| - |HKLM\SOFTWARE\Microsoft\Microsoft SQL Native Client| __REG_SQL.TXT_| - |HKLM\SOFTWARE\Microsoft\OLAP Server| __REG_SQL.TXT_| - |HKLM\SOFTWARE\Microsoft\SNAC| __REG_SQL.TXT_| - |HKLM\SOFTWARE\Microsoft\SQLXML4| __REG_SQL.TXT_| - |HKLM\Software\Microsoft\Vsa| __REG_SQL.TXT_| - |HKLM\SOFTWARE\ODBC|__REG_SQL.TXT_| - |HKLM\SOFTWARE\Microsoft\MSDTS| __REG_SQL.TXT_| - |HKLM\SOFTWARE\Microsoft\MSXML 6.0 Parser and SDK|__REG_SQL.TXT_| - |HKLM\SOFTWARE\Microsoft\MSXML60| __REG_SQL.TXT_| - |HKCU\Software\Microsoft\Microsoft SQL Server| __REG_SQL.TXT_| - |HKLM\SOFTWARE\Microsoft\Microsoft SQL Server| __REG_SQL.TXT_| - |HKLM\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server| __Wow6432Node_REG_SQL.TXT_| - |HKLM\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer| __Wow6432Node_REG_SQL.TXT_| - |HKLM\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server 2005 Redist| _Wow6432Node_REG_SQL.TXT| - |HKLM\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Native Client| __Wow6432Node_REG_SQL.TXT_| - |HKLM\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Native Client 10.0| __Wow6432Node_REG_SQL.TXT_| - |HKLM\SOFTWARE\Wow6432Node\Microsoft\SNAC| __Wow6432Node_REG_SQL.TXT_| - |HKLM\SOFTWARE\Wow6432Node\Microsoft\SQLXML4| __Wow6432Node_REG_SQL.TXT_| - |HKLM\Software\Wow6432Node\Microsoft\Vsa| __Wow6432Node_REG_SQL.TXT_| - |HKLM\SOFTWARE\Wow6432Node\ODBC| __Wow6432Node_REG_SQL.TXT_| - |HKLM\SOFTWARE\Wow6432Node\Microsoft\MSDTS| __Wow6432Node_REG_SQL.TXT_| - |Backup of HKLM\SOFTWARE\Microsoft\Microsoft SQL Server key in HIV format| __Microsoft_SQL_Server.HIV_| - -- Output of PSTAT utility - - |Description|File Name| - |---|---| - |Output from PSTAT.EXE| __PStat.txt_| - -- Windows firewall information - - |Description|File name| - |---|---| - |Windows Firewall Advanced Security event log in TXT, CSV, and EVTX formats

> [!NOTE]
> Available only on Windows 7 and Windows Server 2008 R2| *_evt_WindowsFirewallWithAdvancedSecurity-Firewall_evt_.csv*

*_evt_WindowsFirewallWithAdvancedSecurity-Firewall_evt_.txt*

*_evt_WindowsFirewallWithAdvancedSecurity-Firewall_evt_.evtx*| - |Output of NETSH ADVFIREWALL SHOW command together with various options| __Firewall_netsh_advfirewall.TXT_

| - |Output of NETSH advfirewall consec show rule name=all

| __Firewall_netsh_advfirewall-consec-rules.TXT_| - |Output of netsh advfirewall export| __Firewall_netsh_advfirewall-export.wfw_| - |Output of netsh advfirewall firewall show rule name=all

| __Firewall_netsh_advfw-firewall-rules.TXT_| - |HKLM\SOFTWARE\Policies\Microsoft\WindowsFirewall| *_Firewall_reg_.TXT*| - |HKLM\SYSTEM\CurrentControlSet\Services\BFE| *_Firewall_reg_.TXT*| - |HKLM\SYSTEM\CurrentControlSet\Services\IKEEXT| *_Firewall_reg_.TXT*| - |HKLM\SYSTEM\CurrentControlSet\Services\MpsSvc| *_Firewall_reg_.TXT*| - |HKLM\SYSTEM\CurrentControlSet\Services\SharedAccess"| *_Firewall_reg_.TXT*| - -- Basic Information that is collected when the SQL Base Diagnostics Collector is run on a Windows failover cluster - - |Description|File name| - |---|---| - |Cluster logs that are generated by Get-ClusterLog Windows PowerShell cmdlet| __cluster.log_| - |Cluster Properties| __ClusterProperties.txt_| - |Cluster Dependency Report| __ag_DependencyReport.mht_| - |Names and versions of clustering binaries| __sym_Cluster.CSV_| - |Names and versions of clustering binaries| __sym_Cluster.TXT_| - |Failover Cluster Manager Administrative event log in TXT, CSV, and EVTX formats



> [!NOTE]
> Available only on Windows Server 2008 R2 failover cluster nodes| __evt_FailoverClusteringManager-Admin.csv_

__evt_FailoverClusteringManager-Admin.txt_

__evt_FailoverClusteringManager-Admin.evtx_| - |Failover Cluster Operational Eventlog in TXT, CSV, and EVTX formats

> [!NOTE]
> Available only on Windows Server 2008 R2 failover cluster nodes| __evt_FailoverClustering-Operational.csv_

__evt_FailoverClustering-Operational.txt_

__evt_FailoverClustering-Operational.evtx_

| - -- Windows cluster registry keys - - |Description|File name| - |---|---| - |HKLM\System\CurrentControlSet\services\CluDisk| __reg_ClusDisk.txt_| - |HKLM\System\CurrentControlSet\services\ClusSvc| __reg_ClusSvc.txt_| - |HKLM\Cluster| __reg_Cluster.hiv_| - -- Information about user rights assignments on the destination computer - - |Description|File name| - |---|---| - |Local User Rights Assignments| __UserRights.txt_| - -- Information about the domain the destination computer is joined to - - |Description|File name| - |---|---| - |Information about the domain the target computer is joined to| __DSMisc.txt_| - -- Information about the operating system and whether the destination computer is a VM - - |Description|File name| - |---|---| - |Reports virtualization status of target VM| __Virtualization.htm_| - |Reports virtualization status of target VM| __Virtualization.TXT_| - -- Information about Active Directory Group Policies that are applied to the destination computer - - |Description|File name| - |---|---| - |Information about group policies that are applied to the target computer| __GPResult.txt_| - |Information about group policies that are applied to the target computer| __GPResult.htm_| - -- Autorun information - - > [!NOTE] - > For more information about the Autorun utility, see [Autoruns for Windows v13.98](/sysinternals/downloads/autoruns). - - |Description|File name| - |---|---| - |Autorun information in .htm format| __Autoruns.htm_| - |Autorun information in .xml format| __Autoruns.XML_| - -- Kerberos tickets and TGT - - |Description|File name| - |---|---| - |Kerberos tickets and TGT| __ Kerberos_klist.txt_| - -- Information about the Windows Volume Shadow Copy Service configuration on the destination computer - - |Description|File name| - |---|---| - |Windows Volume Shadow Copy Service information| __VSSAdmin.TXT_| - -- SQL Server error logs - - The SQL Base Diagnostics Collector will collect up to 20 SQL Server error logs for each discovered instance that meets the following criteria: - - - Each error log file size must be 200 MB or less. - - The maximum total uncompressed size of all collected error log files cannot exceed 250 MB. When the 250-MB limit is reached, no additional error logs are collected for the instance of SQL Server. - - |Description|File name| - |---|---| - |Collects SQL Server error logs for all instances that are installed on the computer on which the diagnostic tool is executed.| Named instance:
___1033_ERRORLOG[.n]_

Default instance:
__MSSQLSERVER_ERRORLOG[.n]_| - - > [!NOTE] - > When the SQL Base Diagnostics Collector is executed against a Windows failover cluster, SQL Server error logs are only collected if they are stored on a drive that is "owned" and "online" to the target cluster node. - -- SQL Server Agent logs - - The SQL Base Diagnostics Collector will collect up to 20 SQL Server Agent logs for each discovered instance that meets the following criteria: - - - Each SQL Server Agent log file size must be 200 MB or less. - - The maximum total uncompressed size of all collected SQL Server Agent log files cannot exceed 250 MB. When the 250-MB limit is reached, no additional SQL Server Agent log files are collected for the instance of SQL Server. - - |Description|File name| - |---|---| - |Collects SQL Server Agent logs for all instances that are installed on the computer on which the diagnostic tool is executed.| Named instance:
`__1033_SQLAGENT.[OUT|n]`
Default instance:
`_MSSQLSERVER__1033_SQLAGENT.[OUT|n]`| - - > [!NOTE] - > When the SQL Base Diagnostics Collector is executed against a Windows failover cluster, SQL Server Agent logs are only collected if they are stored on a drive that is "owned" and "online" to the target cluster node. - -- SQL Server minidump files - - The SQL Base Diagnostics Collector will collect up to 10 SQL Server minidump files for each discovered instance of SQL Server. The files are collected in descending order, based on the creation date of the minidump file. This means that the most recently generated files are collected first. The collected files must meet the following criteria: - - - Each minidump file size must be 250 MB or less. - - Each minidump file must be 30 days old or less. - - The maximum total uncompressed size of all collected minidump files for a given instance of SQL Server cannot exceed 300 MB. When the 300-MB limit is reached, no additional minidump files are collected for the instance of SQL Server - - > [!NOTE] - > All the files for a given instance are compressed into a zip archive before they are collected. - - |Description|File name| - |---|---| - |SQL Server minidump files| Named instance:
___1033_SqlMiniDumps.zip_

Default instance:
__MSSQLSERVER_1033_SqlMiniDumps.zip_| - |A dump inventory report is generated and collected for each discovered instance of SQL Server| Named instance:
___DumpInventory.log_

Default Instance:
__MSSQLSERVER_DumpInventory.log_| - - > [!NOTE] - > When the SQL Base Diagnostics Collector is executed against a Windows failover cluster, SQL Server minidump files are only collected if they are stored on a drive that is "owned" and "online" to the target cluster node. - -- SQLDIAG data collection script - - The SQLDIAG data collection script will be executed against each instance of SQL Server that has a service status of "RUNNING." The script output is redirected to a file and collected by the diagnostic. - - |Description|File name| - |---|---| - |SQLDIAG script output| Named instance:
___1033_sp_sqldiag_Shutdown.OUT_

Default Instance:
__MSSQLSERVER_1033_sp_sqldiag_Shutdown.OUT_| - -- SQL Server Always On configuration information - - > [!NOTE] - > The SQL Server Always On configuration information is only collected from SQL Server 2012 instances. - - |Description|File name| - |---|---| - |SQL Server Always On configuration information| Named instance:
___1033_AlwaysOn.OUT_

Default Instance:
__MSSQLSERVER_1033_AlwaysOn.OUT_| - -- SQL Server Always On health logs - - SQL Server Always On health session logs are collected from each SQL Server 2012 instance that is installed on the destination computer. The files are collected and compressed into "instance specific" zip archives. - - The maximum number of SQL Server Always On Health logs that will be collected for each discovered instance is 20. The files are collected in descending order, based on the creation date of the file. - - |Description|File name| - |---|---| - |SQL Server Always On health logs| Named instance:
___AlwaysOn_health_XeLogs.zip_

Default Instance:
__MSSQLSERVER_AlwaysOn_health_XeLogs.zip_| - - > [!NOTE] - > When the SQL Base Diagnostics Collector is executed against a Windows failover cluster, SQL Server Always On health logs are only collected if they are stored on a drive that is "owned" and "online" to the target cluster node. - -- SQL Server failover cluster health logs - - SQL Server failover cluster health logs are collected from each "clustered" SQL Server 2012 instance that is installed on the destination computer. The files are collected and compressed into "instance specific" zip archives. - - The maximum number of failover cluster health logs that will be collected for each instance is 20. The files are collected in descending order, based on the creation date of the file. - - |Description|File name| - |---|---| - |SQL Server failover cluster health logs| Named instance:
___FailoverCluster_health_XeLogs.zip_

Default Instance:
__MSSQLSERVER_FailoverCluster_health_XeLogs.zip_| - - > [!NOTE] - > The SQL Server failover cluster health logs are only collected if they are stored on a drive that is "owned" and "online" to the target cluster node. - -- SQL Server default system health logs - - SQL Server default system health logs are collected from each SQL Server 2012 instance that is installed on the destination computer. The files are collected and compressed into "instance specific" ZIP archives - - |Description|File name| - |---|---| - |SQL Server default system health logs| Named instance:
___system_health_XeLogs.zip_

Default Instance:
__MSSQLSERVER_system_health_XeLogs.zip_| - - > [!NOTE] - > When the SQL Base Diagnostics Collector is executed against a Windows failover cluster, SQL Server default system health logs are only collected if they are stored on a drive that is "owned" and "online" to the target cluster node. - -- SQL Server Analysis Services configuration file - - The SQL Server Analysis Services configuration file will be collected for each Analysis Services instance that is discovered on the destination computer. - - |Description|File name| - |---|---| - |SQL Server Analysis Services configuration file| ___1033_msmdsrv.ini_| - - > [!NOTE] - > When the SQL Base Diagnostics Collector is executed against a Windows failover cluster, SQL Server Analysis Services configuration files are only collected if they are stored on a drive that is "owned" and "online" to the target cluster node. - -- SQL Server Analysis Services registry keys - - |Description|File name| - |---|---| - |HKLM:\SOFTWARE\Microsoft\Microsoft SQL Server\| __reg_HKLM_OLAP_IntanceRoot_all.txt_
| - |HKCR:\MSOLAP
HKCR:\MSOLAP.2
HKCR:\MSOLAP.3
HKCR:\MSOLAP.4| __reg_HKCR_MSOLAP_all.txt_

| - |HKLM:\System\CurrentControlSet\Services\| __reg_HKLM_CurrentControlSet_Services_OLAP.txt_| - -- SQL Server Analysis Services log file - - The SQL Server Analysis Services log file will be collected for each Analysis Services instance that is discovered on the destination computer. - - |Description|File name| - |---|---| - |SQL Server Analysis Services log file| __msmdsrv.log_| - -- SQL Server Analysis Services Flight Recorder traces - - The SQL Server Analysis Services flight recorder traces will be collected for each Analysis Services instance that is discovered on the destination computer - - |Description|File name| - |---|---| - |Current SQL Server Analysis Services Flight recorder| _-_FlightRecorderCurrent.trc_| - |Previous SQL Server Analysis Services Flight recorder| _-_FlightRecorderBack.trc_| - -- SQL Server Analysis Services minidump files - - The SQL Base Diagnostics Collector will collect up to 10 SQL Server Analysis Services minidump files for each discovered instance of SQL Server Analysis Service. The files are collected in descending order, based on the creation date of the minidump file. This means that the most recently generated files are collected first. The collected files must meet the following criteria: - - - Each minidump file size must be 250 MB or less. - - Each minidump file must be 30 days old or less. - - The maximum total uncompressed size of all collected minidump files for a given instance of SQL Server cannot exceed 300 MB. When the 300-MB limit is reached, no additional minidump files are collected for the instance of SQL Server Analysis Services. - - > [!NOTE] - > All the files for a given instance are compressed into a zip archive before they are collected. - - |Description|File name| - |---|---| - |SQL Server Analysis Services minidump files|Named instance:
___1033_ASMiniDumps_
.zip

Default instance:
__MSSQLSERVER_1033_ASMiniDumps .zip_| - |A dump inventory report is generated and collected for each discovered instance of SQL Server Analysis Services|Named instance:
___DumpInventory.log_

Default Instance:
__MSSQLSERVER_DumpInventory.log_| From 047613479cb477c1a42a6330db4109aa49434add Mon Sep 17 00:00:00 2001 From: sevend2 <77822529+sevend2@users.noreply.github.com> Date: Fri, 19 Apr 2024 15:15:45 +0800 Subject: [PATCH 4/8] Update toc.yml --- support/sql/general/toc.yml | 8 -------- 1 file changed, 8 deletions(-) diff --git a/support/sql/general/toc.yml b/support/sql/general/toc.yml index 003e822000..76aa38f595 100644 --- a/support/sql/general/toc.yml +++ b/support/sql/general/toc.yml @@ -1,18 +1,10 @@ items: -- name: Connectivity Diagnostics Collector - href: connectivity-diagnostics-collector.md - name: Detours or similar techniques cause issues href: issue-detours-similar-techniques.md - name: End of support for SQL Server 2008 href: end-support-sql-server-2008.md - name: Issues when upgrading to SQL Server 2022 href: issues-upgrading-sql-server-2022.md -- name: RS Diagnostics Collector collects information - href: rs-diagnostics-collector-information.md -- name: Setup data collection diagnostic tool - href: setup-data-collection-diagnostic-tool.md -- name: SQL Base Diagnostics Collector - href: sql-base-diagnostics-collector.md - name: SQL Server in Windows operating system href: use-sql-server-in-windows.md - name: Support policy for hardware virtualization product From 13601a83072045d513a5769fc26817bf025a48e3 Mon Sep 17 00:00:00 2001 From: sevend2 <77822529+sevend2@users.noreply.github.com> Date: Fri, 19 Apr 2024 15:16:06 +0800 Subject: [PATCH 5/8] Delete support/sql/general/setup-data-collection-diagnostic-tool.md --- .../setup-data-collection-diagnostic-tool.md | 327 ------------------ 1 file changed, 327 deletions(-) delete mode 100644 support/sql/general/setup-data-collection-diagnostic-tool.md diff --git a/support/sql/general/setup-data-collection-diagnostic-tool.md b/support/sql/general/setup-data-collection-diagnostic-tool.md deleted file mode 100644 index 1ce609f25b..0000000000 --- a/support/sql/general/setup-data-collection-diagnostic-tool.md +++ /dev/null @@ -1,327 +0,0 @@ ---- -title: Setup data collection diagnostic tool -description: This article describes the information that may be collected from a computer when the SQL Server Setup data-collection diagnostic tool is running. -ms.date: 08/19/2020 -ms.reviewer: amitban, dansha, shonh -ms.topic: article ---- -# SQL Server Setup data-collection diagnostic tool - -This article describes the information that may be collected from a computer when the SQL Server Setup data-collection diagnostic tool is running. - -_Original product version:_   SQL Server 2008 -_Original KB number:_   2621109 - -## Summary - -The SQL Server Setup Data Collector for Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1 and Windows Server 2012 R2 collects diagnostic information that is useful in troubleshooting setup-related issues for Microsoft SQL Server 2008, for SQL Server 2008 R2, and for SQL Server 2012. - -SQL Server features are categorized as Instance Features or as Shared Features. - -## Instance Features - -The Instance Features are as follows: - -- Database Engine Features (SQL Server Replication, Full-text, and Semantics Extractions search, Data Quality Services) -- Analysis Services -- Reporting Services - Native - -## Shared Features - -The Shared Features are as follows: - -- Reporting Services - SharePoint -- Reporting Services Add-in for SharePoint Products -- Business Intelligence Development Studio -- Client Tools Connectivity -- Integration Services -- Client Tools Backward Compatibility -- Client Tools SDK -- SQL Server Books Online -- Management Tools - Basic (Management Tools - Complete) -- SQL Client Connectivity SDK -- Microsoft Sync Framework -- Data Quality Client -- Master Data Services -- Distributed Replay Controller -- Distributed Replay Client - -The SQL Server Setup Data Collector is cluster-aware and will collect cluster-specific information when the SQL Server Setup Data Collector is run against a clustered instance of SQL Server. When you troubleshoot a Setup failure that occurred on a Windows cluster, the SQL Server Setup Data Collector should be run against the cluster node at which the Setup failure occurred. To troubleshoot multiple Setup failures on multiple nodes that are joined to the same cluster, the SQL Server Setup Data Collector must be run against each node at which the failure occurred. - -The SQL Server Setup Data Collector should be run under the security context of the account that was used to run Setup. Also, the SQL Server Setup Data Collector must be run by a user who has administrative rights on the computer on which the data collector will be run. - -## Information that is collected - -- **All event logs** - - |Description|File name| - |---|---| - |System log - Evtx format| _ComputerName_System.evtx_| - |Application log - Evtx format| _ComputerName_Application.evtx_| - |Security log - Evtx format| _ComputerName_Security.evtx_| - |FailoverClustering-Operational - Evtx format| _ComputerName_FailoverClustering-Operational.evtx_| - - > [!NOTE] - > Failover Clustering event logs will be collected only on servers that have Failover Clustering configured. - -- **Registry information that is related to Session Manager and Debugging** - - |Description|File name| - |---|---| - |Collect Registry Key - `HKLM\Software\Microsoft\Windows NT\CurrentVersion\AEDebug`| _ComputerName_ _Recovery_Registry.TXT_| - |Collect Registry Key - `HKLM\Software\Microsoft\DrWatson`| _ComputerName __Recovery_Registry.TXT_| - |Collect Registry Key - `HKLM\System\CurrentControlSet\Services\i8042prt\Parameters`| _ComputerName_ _Recovery_Registry.TXT_| - |Collect Registry Key - `HKLM\System\CurrentControlSet\Control`| _ComputerName __Recovery_Registry.TXT_| - |Collect Registry Key - `HKLM\System\CurrentControlSet\Control\Session Manager`| _ComputerName_ _Recovery_Registry.TXT_| - -- **Existing Dr. Watson logs files and memory dump reports and files** - - |Description|File name| - |---|---| - |Memory dump report| _ComputerName_DumpReport.htm_| - |Memory dump report| _ComputerName_ DumpReport.txt_| - |Memory dump file (minidumps)| *ComputerName _DMP_{Date}.zip*| - -- **Information about all services that are installed on the operating system** - - |Description|File name| - |---|---| - |Collect information about all OS services| _ComputerName_SC_Services_Output.txt_| - -- **Information about all filter drivers that are active on the computer** - - |Description|File name| - |---|---| - |Upper and lower filters information that uses fltrfind.exe utility| _ComputerName_ FltrFind.txt_| - -- **Information about all the running processes and driver details together with their file versions** - - |Description|File name| - |---|---| - |`%programfiles%\*.sys`| _ComputerName_sym_ProgramFiles_SYS.CSV_| - |`%programfiles%\*.sys`| _ComputerName_sym_ProgramFiles_SYS.TXT_| - |`%windir%\system32\drivers\*.*`| _ComputerName_sym_Drivers.CSV_| - |`%windir%\system32\drivers\*.*`| _ComputerName_sym_Drivers.TXT_| - |`%windir%\system32\*.exe`| _ComputerName_sym_System32_exe.CSV_| - |`%windir%\system32\*.exe`| _ComputerName_sym_System32_exe.TXT_| - |`%windir%\system32\*.sys`| _ComputerName_sym_System32_sys.CSV_| - |`%windir%\system32\*.sys`| _ComputerName_sym_System32_sys.TXT_| - |Running processes| _ComputerName_sym_Process.CSV_| - |Running processes| _ComputerName_sym_Process.TXT_| - |Running drivers| _ComputerName_sym_RunningDrivers.CSV_| - |Running drivers| _ComputerName_sym_RunningDrivers.TXT_| - -- **Performance-related information for the operating system** - - |Description|File name| - |---|---| - |System processor basic information| _ComputerName_ Processor_Details.txt_| - |System processor performance information| _ComputerName_ OS_Perf_Details.txt_| - |System performance statistics| _ComputerName_ OS_Perf_Statistics.txt_| - -- **Information about the network configuration of the computer** - - |Description|File name| - |---|---| - |TCP/IP basic information| _ComputerName_TcpIp-Info.txt_| - |SMB basic information| _ComputerName_SMB-Info.txt_| - -- **Output of the NetDiag utility** - - |Description|File name| - |---|---| - |Networking diagnostic output that uses the NetDiag.exe utility| _ComputerName_NetDiag.txt_| - - > [!NOTE] - > NetDiag is a diagnostic tool that helps isolate networking and connectivity problems by performing a series of tests to determine the state of the network client. - -- **Information about Windows scheduled tasks that are configured on the computer** - - |Description|File name| - |---|---| - |Scheduled tasks list| _ComputerName_schtasks.csv_| - |Scheduled tasks list| _ComputerName_schtasks.txt_| - -- **Boot configuration data of the computer** - - |Description|File name| - |---|---| - |Output from Bcdedit.exe utility| _ComputerName_BCDEdit.txt_| - |Output from Bcdedit.exe utility| _ComputerName_BCD-Backup.bak_| - -- **Servicing information for the computer** - - |Description|File name| - |---|---| - |Component-Based Servicing logs that are located at `%windir%\Logs\CBS`| *ComputerName _CBS\*.log*| - |DPX Setup Act log that is located at `%windir%\logs\DPX`| _ComputerName_setupact.log_| - |Pending Operations Queue Exec log that is located at `%windir%\winsxs`| _ComputerName_poqexec.log_| - |Windows Side-by-Side Pending Bad log that is located at `%windir%\ winsxs`| _ComputerName_pending.xml.bad_| - |Windows Side-by-Side Pending log that is located at `%windir%\ winsxs`| _ComputerName_pending.xml_| - -- **Operating system SetupAPI logs** - - |Description|File name| - |---|---| - |SetupAPI logs that are located in `%windir%\inf` folder| _ComputerName_SetupApi.app.log_

_ComputerName_SetupApi.evt.log_

_ComputerName_SetupApi.offline.log_

_ComputerName_SetupApi.Dev.log_| - -- **Information about all hotfixes that are applied on the computer** - - |Description|File name| - |---|---| - |Installed updates and hotfixes| _ComputerName_Hotfixes.CSV_

_ComputerName_Hotfixes.Txt_

_ComputerName_Hotfixes.HTM_| - -- **Backup of CurrentControlSet and SQL Server registry hives** - - |Description|File name| - |---|---| - |`HKLM\System\CurrentControlSet\SessionManagers`| _ComputerName_CurrentControlSet_Reg.txt_| - |`HKLM\SYSTEM\CurrentControlSet\Control\Lsa`| _ComputerName_CurrentControlSet_Reg.txt_| - |`HKLM\SYSTEM\CurrentControlSet`| _ComputerName_CurrentControlSet.Hiv_| - |`HKLM\SOFTWARE\Microsoft\Microsoft SQL Server`| _ComputerName_REG_SQL.TXT_| - |`HKLM\SOFTWARE\Microsoft\MSSQLServer`| _ComputerName_REG_SQL.TXT_| - |`HKLM\SOFTWARE\Microsoft\Microsoft SQL Server 2005 Redist`| _ComputerName_REG_SQL.TXT_| - |`HKLM\Software\Microsoft\MSFTESQLInstMap`| _ComputerName_REG_SQL.TXT_| - |`HKLM\SOFTWARE\Microsoft\Microsoft SQL Native Client`| _ComputerName_REG_SQL.TXT_| - |`HKLM\SOFTWARE\Microsoft\OLAP Server`| _ComputerName_REG_SQL.TXT_| - |`HKLM\SOFTWARE\Microsoft\SNAC`| _ComputerName_REG_SQL.TXT_| - |`HKLM\SOFTWARE\Microsoft\SQLXML4`| _ComputerName_REG_SQL.TXT_| - |`HKLM\Software\Microsoft\Vsa`| _ComputerName_REG_SQL.TXT_| - |`HKLM\SOFTWARE\ODBC`| _ComputerName_REG_SQL.TXT_| - |`HKLM\SOFTWARE\Microsoft\MSDTS`| _ComputerName_REG_SQL.TXT_| - |`HKLM\SOFTWARE\Microsoft\MSXML 6.0 Parser and SDK`| _ComputerName_REG_SQL.TXT_| - |`HKLM\SOFTWARE\Microsoft\MSXML60`| _ComputerName_REG_SQL.TXT_| - |`HKCU\Software\Microsoft\Microsoft SQL Server`| _ComputerName_REG_SQL.TXT_| - |`HKLM\SOFTWARE\Microsoft\Microsoft SQL Server`| _ComputerName_Microsoft_SQL_Server.HIV_| - -- **Output of MSINFO32** - - |Description|File name| - |---|---| - |Microsoft System Information report| _ComputerName_MSINFO32.NFO_

_ComputerName_MSINFO32.TXT_| - -- **Output of PStat utility** - - |Description|File name| - |---|---| - |PStat.exe output| _ComputerName_Pstat.txt_| - - > [!NOTE] - > PStat is a character-based tool that lists all running threads and displays their status. - -- **Backup of cluster-related registry keys** - - |Registry key|File name| - |---|---| - |`HKLM\Software\Microsoft\Windows NT\CurrentVersion`
`HKLM\Software\Microsoft\Windows\CurrentVersion`| _ComputerName_reg_CurrentVersion.TXT_| - |`HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall`| _ComputerName_reg_Uninstall.TXT_| - |`HKLM\SYSTEM\CurrentControlSet\Control\ProductOptions`| _ComputerName_reg_ProductOptions.TXT_| - |`HKLM\System\MountedDevices`| *ComputerName _reg_MountedDevices.\**| - |`HKLM\System\CurrentControlSet\Control\CrashControl`
`HKLM\System\CurrentControlSet\Control\Session Manager`
`HKLM\System\CurrentControlSet\Control\Session Manager\Memory Management`
`HKLM\Software\Microsoft\Windows NT\CurrentVersion\AeDebug`
`HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options`
`HKLM\Software\Microsoft\Windows\Windows Error Reporting`
`HKLM\Software\Policies\Microsoft\Windows\Windows Error Reporting`| _ComputerName_reg_Recovery.TXT_| - |`HKCU\Software\Microsoft\Windows\CurrentVersion\Run`
`HKCU\Software\Microsoft\Windows\CurrentVersion\Runonce`
`HKCU\Software\Microsoft\Windows\CurrentVersion\RunonceEx`
`HKCU\Software\Microsoft\Windows\CurrentVersion\RunServices`
`HKCU\Software\Microsoft\Windows\CurrentVersion\RunServicesOnce`
`HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\Run`
`HKLM\ Software\Microsoft\Windows\CurrentVersion\Run`
`HKLM\Software\Microsoft\Windows\CurrentVersion\Runonce`
`HKLM\Software\Microsoft\Windows\CurrentVersion\RunonceEx`
`HKLM\Software\Microsoft\Windows\CurrentVersion\RunServices`
`HKLM\Software\Microsoft\Windows\CurrentVersion\RunServicesOnce`
`HKLM\Software\Microsoft\Windows\CurrentVersion\ShellServiceObjectDelayLoad`
`HKCU\Software\Microsoft\Windows NT\CurrentVersion\Load`
`HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows\Run`
`HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\Run`
`HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\UserInit`| _ComputerName_reg_Startup.TXT_| - |`HKLM\SYSTEM\CurrentControlSet\Control\Print`| _ComputerName_reg_Print.HIV_| - |`HKCU\Software\Policies`
`HKLM\Software\Policies`
`HKCU\Software\Microsoft\Windows\CurrentVersion\Policies`
`HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies`| _ComputerName_reg_Policies.txt_| - |`HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation`
`HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones`| _ComputerName_reg_TimeZone.txt_| - |`HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server`
`HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server`
`HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server Web Access`
`HKLM\SYSTEM\CurrentControlSet\Services\TermService`
`HKLM\SYSTEM\CurrentControlSet\Services\TermDD`| _ComputerName_reg_TermServices.txt_| - |`HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer`
`HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation`
`HKLM\SYSTEM\CurrentControlSet\Services\MRxSmb`
`HKLM\SYSTEM\CurrentControlSet\Services\SMB`
`HKLM\SYSTEM\CurrentControlSet\Services\MRxSmb10`
`HKLM\SYSTEM\CurrentControlSet\Services\MRxSmb20`| _ComputerName_reg_SMB.txt_| - |`HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters`| _ComputerName_reg_TCPIPParameters_| - |`HKLM\SYSTEM\CurrentControlSet\Services\VSS`| _ComputerName_reg_VSS.TXT_| - |`HKLM\SYSTEM\CurrentControlSet\Services\iScsiPrt`
`HKLM\SOFTWARE\Microsoft\iSCSI Target`
`HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\iSCSI`| _ComputerName_reg_iSCSI.TXT_| - |`HKLM\System\CurrentControlSet\Control\MPDev`
`HKLM\System\CurrentControlSet\Control\iSCSIPrt`
`HKLM\System\CurrentControlSet\Services\MSiSCSI`
`HKLM\System\CurrentControlSet\Services\MSDsm`
`HKLM\System\CurrentControlSet\Services\MPIO`
`HKLM\System\CurrentControlSet\Control\Class\{4d36e97b-e325-11ce-bfc1-08002be10318}`
`HKLM\System\CurrentControlSet\Services\Tcpip`| _ComputerName_reg_Storage.TXT_| - |`HKLM\SYSTEM\CurrentControlSet\Enum`| _ComputerName_reg_Enum.TXT_| - |`HKLM\System\CurrentControlSet\services\ClusSvc`
`HKLM\System\CurrentControlSet\services\CluDisk`| _ComputerName_reg_ClusSvc.TXT_| - |`HKLM\Cluster`| _ComputerName_Cluster.hiv_| - - > [!NOTE] - > This information will be collected if the SQL Server Setup data-collection diagnostic tool detects that the computer on which the tool is running is a cluster. - -- **Basic information about Windows Failover Cluster** - - The data that is collected includes the following: - - - Cluster logs - - Shared volume information - - Cluster resource properties - - Cluster reports folder - - Cluster resource dependency - - Cluster validation report - - |Description|File name| - |---|---| - |Cluster logs that are generated by Get-ClusterLog Windows PowerShell cmdlet| _ComputerName_Cluster.Log_| - |Cluster MPS Tool (clusmps.exe) output| _ComputerName_Cluster_MPS_Information.txt_| - |Cluster validation reports files that are located at `\Windows\Cluster\Reports\*.mht`| *ComputerName _\*.mht*| - |Cluster reports XML files that are located at `\Windows\Cluster\Reports\*.xml`| *ComputerName _\*.xml*| - |Cluster validation log files from `\Windows\Cluster\Reports\Validate*.log`| *ComputerName _Validade\*.log*| - |Cluster resources properties that use the Windows PowerShell Get-ClusterResource cmdlet| _ComputerName_ClusterProperties.txt_| - |Cluster Dependency Report that is generated by the Get-ClusterResourceDependencyReport Windows PowerShell cmdlet| _ComputerName_DependencyReport.mht_| - |Cluster Shared Volume information - HTML format| _ComputerName_CSVInfo.htm_| - |Cluster basic Validation Report that is generated by the Test-Cluster Windows PowerShell cmdlet| _ComputerName_ValidationReport.mht_| - - > [!NOTE] - > This information will be collected if the SQL Server Setup data-collection diagnostic tool detects that the computer on which the tool is running is a cluster. - -- **Information about SQL Server instances that are installed on the computer** - - |Description|File name| - |---|---| - |MSI Installer information for SQL Server products| _ComputerName_FindSQLInstalls.txt_| - -- **Information about TCP/IP ports that are used on the computer** - - |Description|File name| - |---|---| - |TCP/IP port usage information| _ComputerName_PortUsage.txt_| - -- **Information about User Rights Assignments** - - |Description|File name| - |---|---| - |Local User Right Assignments| _ComputerName_userrights.txt_| - -- **Backup of the Setup Bootstrap folder for SQL Server installations** - - |Description|File name| - |---|---| - |Compressed directory `%programfiles%\ Microsoft SQL Server\90\Setup Bootstrap\Log`| _ComputerName_SQL90_Bootstrap.Cab_| - |Compressed directory `%programfiles%\ Microsoft SQL Server\100\Setup Bootstrap\Log`| _ComputerName_SQL100_Bootstrap.Cab_| - |Compressed directory `%programfiles%\ Microsoft SQL Server\110\Setup Bootstrap\Log`| _ComputerName_SQL110_Bootstrap.Cab_| - -- **SQL Server error logs for all instances of SQL Server that are installed on the computer** - - |Description|File name| - |---|---| - |Collects SQL Server error logs for all instances that are installed on the computer on which the diagnostic tool is executed. The number of files that are collected is determined by how many error logs exist on the file system.|Named instance:
_ComputerName_ instance_name _.errorlog_
Default instance:
*ComputerName _MSSQLSERVER_.errorlog*| - - > [!NOTE] - > The SQL Server Setup data-collection diagnostic tool will collect error logs for a clustered instance only if the shared drive that is storing the error log is currently owned by the server on which the utility is being executed. - -## More information - -In addition to the files that are collected and listed here, this troubleshooter can detect one or more of the following situations: - -- The computer is running in a virtual environment. -- The cluster service of a FailoverCluster node is not running. -- The state of any of the cluster nodes is Offline. -- Any of the cluster groups is offline. -- There is a problem in obtaining cluster information. - -## Applies to - -- SQL Server 2008 Enterprise -- SQL Server 2008 Developer -- SQL Server 2008 Express -- SQL Server 2008 Express with Advanced Services -- SQL Server 2008 Web -- SQL Server 2008 Workgroup -- SQL Server 2008 Standard -- SQL Server 2008 Standard Edition for Small Business -- SQL Server 2008 R2 Datacenter -- SQL Server 2008 R2 Developer -- SQL Server 2008 R2 Enterprise -- SQL Server 2008 R2 Express -- SQL Server 2008 R2 Express with Advanced Services -- SQL Server 2008 R2 Standard -- SQL Server 2008 R2 Workgroup -- SQL Server 2008 R2 Standard Edition for Small Business -- SQL Server 2008 R2 Web From 1bb3d7acfaefe27221e4c23ebfe98e56113cbc1b Mon Sep 17 00:00:00 2001 From: sevend2 <77822529+sevend2@users.noreply.github.com> Date: Fri, 19 Apr 2024 15:16:29 +0800 Subject: [PATCH 6/8] Delete support/sql/general/connectivity-diagnostics-collector.md --- .../connectivity-diagnostics-collector.md | 352 ------------------ 1 file changed, 352 deletions(-) delete mode 100644 support/sql/general/connectivity-diagnostics-collector.md diff --git a/support/sql/general/connectivity-diagnostics-collector.md b/support/sql/general/connectivity-diagnostics-collector.md deleted file mode 100644 index c4f04e6e3b..0000000000 --- a/support/sql/general/connectivity-diagnostics-collector.md +++ /dev/null @@ -1,352 +0,0 @@ ---- -title: Connectivity Diagnostics Collector -description: This article describes the information that is collected by the SQL Server Connectivity Diagnostics Collector. -ms.date: 08/19/2020 -ms.topic: article ---- -# Information is collected by the SQL Server Connectivity Diagnostics Collector - -This article describes the information that is collected by the SQL Server Connectivity Diagnostics Collector. - -_Original product version:_   SQL Server 2012, SQL Server 2008, SQL Server 2008 R2, SQL Server 2005 -_Original KB number:_   2871695 - -## Summary - -The Microsoft SQL Server Connectivity Diagnostics Collector for Windows Server 2003 R2, Windows Vista, Windows Server 2008, Windows Server 2008 R2, Windows 7, Windows 8, Windows 8.1, Windows Server 2012 and Windows Server 2012 R2 collects diagnostic information that is useful in troubleshooting a broad class of connectivity issues with SQL Server. The SQL Server Connectivity Diagnostics Collector also collects limited diagnostic information for SQL Server Analysis Services. - -The SQL Server Connectivity Diagnostics Collector supports the following versions of SQL Server: - -- SQL Server 2005 -- SQL Server 2008 -- SQL Server 2008 R2 -- SQL Server 2012 - -## Prerequisite software - -There are different prerequisites to run diagnostic packages, depending on the operating system of the destination computer. The diagnostic will automatically check your computer for these prerequisites and start executing if they are already installed. Or, you are prompted to install the prerequisites if they are not already available on the computer. The Microsoft Automated Troubleshooting Service (MATS) may also install required software for you. For example, if Windows PowerShell is not present on the destination computer, MATS will install it automatically. For more information, see [Information about Microsoft Automated Troubleshooting Services and Support Diagnostic Platform](https://support.microsoft.com/help/2598970). - -## Required Windows rights - -The SQL Server Connectivity Diagnostics Collector must be run by a user who has administrative rights on the computer on which the SQL Server Connectivity Diagnostics Collector is running. - -## SQL Server security requirements - -The SQL Server Connectivity Diagnostics Collector discovers all instances of SQL Server that are installed on the computer on which the diagnostics tool is run. As part of the data-collection process, the SQL Server Connectivity Diagnostics Collector tries to connect to each instance of SQL Server that the diagnostic tool discovers to collect information about the current SQL Server configuration and server "state". Database connections are made by using Windows authentication. For the following diagnostic collection tasks to succeed, the user who is executing the SQL Server Connectivity Diagnostics Collector must have a Windows logon that is a member of the sysadmin fixed server role: - -- SQL Server Always On Configuration Collection -- SQLDIAG Data Collection Scripts - -## Support for Windows failover clusters - -To diagnose SQL Server Always On Availability Group connectivity or clustered SQL Server connectivity, you may have to run the SQL Server Connectivity Diagnostic Collector against more than one cluster node to collect all the necessary troubleshooting information as follows: - -- Run the SQL Server Connectivity Diagnostic Collector against the cluster node that currently owns the SQL Server Always On Availability Group or SQL Server cluster resource that is experiencing the connectivity issue. - -- Run the SQL Server Connectivity Diagnostic Collector against the node where a connectivity failure occurred previously. This enables the collection of various logs from the cluster node where the failure occurred previously. - -## Information that is collected - -- **General information** - - | Description| File name | - |---|---| - |Basic system information. This includes computer name, service pack number, computer model, and processor name and speed.|__ System_Information.txt_| - |Virtualization information, and so on.|__ DiscoveryReport.xml_| - |List of roles and features that are installed on server media. (Windows Server 2008 R2 and later versions)|__ ResultReport.xml_| - -- **System log** - - > [!NOTE] - > The SQL Server Connectivity Diagnostics Collector collects events from the past 15 days. - - | Description| File name | - |---|---| - |System log in TXT, CSV, and EVT or EVTX formats|__ evt_System.csv_
__ evt_System.txt_
__ evt_System.evt_ or
__ evt_System.evtx_| - -- **Application log** - - > [!NOTE] - > The SQL Server Connectivity Diagnostics Collector collects events from the past 15 days. - - | Description| File name | - |---|---| - |Application log in TXT, CSV, and EVT or EVTX format|__ evt_Application.csv_
__ evt_Application.txt_
__ evt_Application.evt_ or
__ evt_Application.evtx_| - -- **Information about user and system environment variables on the destination computer** - - | Description| File name | - |---|---| - |Information about user and system environment variables in the context of the current user on the destination computer in XML and TXT format|__ EnvironmentVariables.xml_
__ EnvironmentVariables.txt_| - -- **Information about all services that are installed on the destination computer** - - | Description| File name | - |---|---| - |Information about services that are installed on the destination computer|__SC_Services_Output.xml_| - -- **Information about filter drivers that are installed on the destination computer** - - | Description| File name | - |---|---| - |Enumerate upper and lower filter drivers by using Fltrfind.exe|__FltrFind.txt_| - -- **Report of mini-filter drivers** - - | Description| File name | - |---|---| - |Enumerate mini-filter drivers by using Fltmc.exe|__Fltmc.txt_| - -- **Information about all the running processes and driver details together with their file versions** - - | Description| File name | - |---|---| - |Running drivers|__sym_RunningDrivers.csv_| - |Running drivers|__sym_RunningDrivers.txt_| - |`%windir%\system32\drivers\*.*`|__sym_Drivers.csv_| - |`%windir%\system32\drivers\*.*`|__sym_Drivers.txt_| - |Running processes|__sym_Process.csv_| - |Running processes|__sym_Process.txt_| - -- **Information about the networking configuration of the destination computer** - - | Description| File name | - |---|---| - |Basic SMB configuration information such as output of net.exe subcommands such as net share, net sessions, net use, net accounts, and net config.|__SMB-Info.txt_| - |Basic TCP/IP and networking configuration information such as TCP/IP registry key and outputs from ipconfig, netstat, nbtstat, and netsh commands.|__TcpIp-Info.txt_| - |DNS Client hosts file|__DnsClient_HostsFile.txt_| - | IPCONFIG/DISPLAYDNS command output|__DnsClient_ipconfig-displaydns.txt_| - | NETSH DNSCLIENT SHOW STATE command output

**NOTE** This command is not valid on Windows Server 2003|__DnsClient_netsh_dnsclient-show-state.TXT_| - |DNS Client registry entries|*_DnsClient_reg_.txt*| - |TCP/IP parameters registry key `HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters`

|__TcpIp_Parameters_Registry.xml_| - |Network adapter properties|__NetworkAdapterConfigurations.xml_| - -- **Registry backup and text dump files of CurrentControlSet and SQL Server registry hives** - - | Description| File name | - |---|---| - |`HKLM\System\CurrentControlSet\SessionManagers`|__CurrentControlSet_Reg.txt_| - |`HKLM\SYSTEM\CurrentControlSet\Control\Lsa`|__CurrentControlSet_Reg.txt_| - |`HKLM\SYSTEM\CurrentControlSet`|__CurrentControlSet_Reg.hiv_| - |`HKLM\SOFTWARE\Microsoft\Microsoft SQL Server`|__REG_SQL.txt_| - |`HKLM\SOFTWARE\Microsoft\MSSQLServer`|__REG_SQL.txt_| - |`HKLM\SOFTWARE\Microsoft\Microsoft SQL Server 2005 Redist`|__REG_SQL.txt_| - |`HKLM\Software\Microsoft\MSFTESQLInstMap`|__REG_SQL.txt_| - |`HKLM\SOFTWARE\Microsoft\Microsoft SQL Native Client`|__REG_SQL.txt_| - |`HKLM\SOFTWARE\Microsoft\OLAP Server`|__REG_SQL.txt_| - |`HKLM\SOFTWARE\Microsoft\SNAC`|__REG_SQL.txt_| - |`HKLM\SOFTWARE\Microsoft\SQLXML4`|__REG_SQL.txt_| - |`HKLM\Software\Microsoft\Vsa`|__REG_SQL.txt_| - |`HKLM\SOFTWARE\ODBC`|__REG_SQL.txt_| - |`HKLM\SOFTWARE\Microsoft\MSDTS`|__REG_SQL.txt_| - |`HKLM\SOFTWARE\Microsoft\MSXML 6.0 Parser and SDK`|__REG_SQL.txt_| - |`HKLM\SOFTWARE\Microsoft\MSXML60`|__REG_SQL.txt_| - |`HKCU\Software\Microsoft\Microsoft SQL Server`|__REG_SQL.txt_| - |`HKLM\SOFTWARE\Microsoft\Microsoft SQL Server`|__REG_SQL.txt_| - |`HKLM\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server`|__Wow6432Node_REG_SQL.txt_| - |`HKLM\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer`|__Wow6432Node_REG_SQL.txt_| - |`HKLM\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server 2005 Redist`|__Wow6432Node_REG_SQL.txt_| - |`HKLM\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Native Client`|__Wow6432Node_REG_SQL.txt_| - |`HKLM\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Native Client 10.0`|__Wow6432Node_REG_SQL.txt_| - |`HKLM\SOFTWARE\Wow6432Node\Microsoft\SNAC`|__Wow6432Node_REG_SQL.txt_| - |`HKLM\SOFTWARE\Wow6432Node\Microsoft\SQLXML4`|__Wow6432Node_REG_SQL.txt_| - |`HKLM\Software\Wow6432Node\Microsoft\Vsa`|__Wow6432Node_REG_SQL.txt_| - |`HKLM\SOFTWARE\Wow6432Node\ODBC`|__Wow6432Node_REG_SQL.txt_| - |`HKLM\SOFTWARE\Wow6432Node\Microsoft\MSDTS`|__Wow6432Node_REG_SQL.txt_| - |`Backup of HKLM\SOFTWARE\Microsoft\Microsoft SQL Server key in HIV format`|__Microsoft_SQL_Server.hiv_| - -- **Output of the PSTAT utility** - - | Description| File name | - |---|---| - |Output from PSTAT.EXE|__PStat.txt_| - -- **Windows firewall information** - - | Description| File name | - |---|---| - |Output of the netsh advfirewall show command together with various options|__Firewall_netsh_advfirewall.txt_| - |Output of netsh advfirewall consec show rule name=all|__Firewall_netsh_advfirewall-consec-rules.txt_| - |Output of netsh advfirewall export|__Firewall_netsh_advfirewall-export.wfw_| - |Output of netsh advfirewall firewall show rule name=all|__Firewall_netsh_advfirewall-firewall-rules.txt_| - |Output of netsh wfp show netevents|__Firewall_netsh_wfp-show-netevents.txt_| - |`HKLM\SOFTWARE\Policies\Microsoft\WindowsFirewall`|*_Firewall_reg_.txt*| - |`HKLM\SYSTEM\CurrentControlSet\Services\BFE`|*_Firewall_reg_.txt*| - |`HKLM\SYSTEM\CurrentControlSet\Services\IKEEXT`|*_Firewall_reg_.txt*| - |`HKLM\SYSTEM\CurrentControlSet\Services\MpsSvc`|*_Firewall_reg_.txt*| - |`HKLM\SYSTEM\CurrentControlSet\Services\SharedAccess`|*_Firewall_reg_.txt*| - -- **Information about user rights assignments on the destination computer** - - | Description| File name | - |---|---| - |Local user rights assignments|__UserRights.txt_| - -- **Information about the domain to which the destination computer is joined** - - | Description| File name | - |---|---| - |Information about the domain to which the destination computer is joined.|__DSMisc.txt_| - -- **Kerberos tickets and TGT** - - | Description| File name | - |---|---| - |Kerberos tickets and TGT|__ Kerberos_klist.txt_| - -- **Kerberos, LSA, and SChannel registry keys on the destination computer** - - | Description| File name | - |---|---| - |`HKLM:\System\CurrentControlSet\Control\Lsa`
`HKLM:\System\CurrentControlSet\Control\Lsa\MSV1_0`
`HKLM:\System\CurrentControlSet\Control\Lsa\Kerberos\Parameters`
`HKLM:\System\CurrentControlSet\Services\LanmanServer\Parameters`
`HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL`|__ Authentication_Registry.xml_| - -- **Server network configuration of all instances of SQL Server on the destination computer** - - | Description| File name | - |---|---| - |SQL Server network configurations (TCP/IP, NP, Shared Memory, and so on) for all instances of SQL Server. Also, (Database Engine) instances on the destination computer. This includes both 64-bit and 32-bit instances on a 64-bit computer.|__ SqlServer_Network_Configurations.xml_| - -- **Active Directory properties and SPNs of SQL Server service accounts on the destination computer** - - | Description| File name | - |---|---| - |Active directory properties and SPNs of SQL Server service accounts on the destination computer|__ SqlServiceAccounts_SPN_ADProperties.xml_
__ SQLInstances_Spn_Summary.xml_| - -- **SQL Server error logs** - - The SQL Server Connectivity Diagnostics Collector will collect up to 20 SQL Server error logs for each discovered instance that meets the following criteria: - - - The size of each error log file must be 200 MB or less. - - The maximum total uncompressed size of all collected error log files cannot exceed 250 MB. When the 250-MB limit is reached, no additional error logs are collected for the instance of SQL Server. - - | Description| File name | - |---|---| - |Collects SQL Server error logs for all instances that are installed on the computer on which the diagnostic tool is executed.| Named instance:
___1033_ERRORLOG[.n]_

Default instance:
__MSSQLSERVER_ERRORLOG[.n]_| - - > [!NOTE] - > When the SQL Server Connectivity Diagnostics Collector is executed against a Windows failover cluster, SQL Server error logs are only collected if they are stored on a drive that is "owned" and "online" to the destination cluster node. - -- **SQL Server Agent logs** - - The SQL Server Connectivity Diagnostics Collector will collect up to 20 SQL Server Agent logs for each discovered instance that meets the following criteria: - - - The size of each SQL Server Agent log file must be 200 MB or less. - - The maximum total uncompressed size of all collected SQL Server Agent log files cannot exceed 250 MB. When the 250-MB limit is reached, no additional SQL Server Agent log files are collected for the instance of SQL Server. - - | Description| File name | - |---|---| - |Collects SQL Server Agent logs for all instances that are installed on the computer on which the diagnostic tool is executed.| Named instance:
*__1033_SQLAGENT.[OUT \| n]*

Default instance:
*_MSSQLSERVER__1033_SQLAGENT.[OUT \|n]*| - - > [!NOTE] - > When the SQL Server Connectivity Diagnostics Collector is executed against a Windows failover cluster, SQL Server Agent logs are only collected if they are stored on a drive that is "owned" and "online" to the destination cluster node. - -- **SQL Server minidump files** - - The SQL Server Connectivity Diagnostics Collector will collect up to 10 SQL Server minidump files for each discovered instance of SQL Server. The files are collected in descending order, based on the creation date of the minidump file. This means that the most recently generated files are collected first. The collected files must meet the following criteria: - - - The size of each minidump file must be 100 megabytes (MB) or less. - - Each minidump file must be 30 days old or less. - - The maximum total uncompressed size of all collected minidump files for a given instance of SQL Server cannot exceed 200 MB. When the 200-MB limit is reached, no additional minidump files are collected for the instance of SQL Server. - - > [!NOTE] - > All the files for a given instance are compressed into a zip archive before they are collected. - - | Description| File name | - |---|---| - |SQL Server minidump files| Named instance:
___1033_SqlMiniDumps.zip_

Default instance:
__MSSQLSERVER_1033_SqlMiniDumps .zip_| - |A dump inventory report is generated and collected for each discovered instance of SQL Server.| Named instance:
___DumpInventory.log_

Default Instance:
__MSSQLSERVER_DumpInventory.log_| - - > [!NOTE] - > When the SQL Server Connectivity Diagnostics Collector is executed against a Windows failover cluster, SQL Server minidump files are only collected if they are stored on a drive that is "owned" and "online" to the destination cluster node. - -- **SQLDIAG data-collection script** - - The SQLDIAG data-collection script will be executed against each instance of SQL Server that has a service status of "RUNNING." The script output is redirected to a file and collected by the diagnostic. - - | Description| File name | - |---|---| - |SQLDIAG script output| Named instance:
___1033_sp_sqldiag_Shutdown.out_

Default Instance:
__MSSQLSERVER_1033_sp_sqldiag_Shutdown.out_| - -- **SQL Server Always On configuration information** - - > [!NOTE] - > The SQL Server Always On configuration information is collected only from instances of SQL Server 2012. - - | Description| File name | - |---|---| - |SQL Server Always On configuration information| Named instance:
___1033_AlwaysOn.out_

Default Instance:
__MSSQLSERVER_1033_AlwaysOn.out_| - -- **SQL Server Always On health logs** - - SQL Server Always On health session logs are collected from each instance of SQL Server 2012 that is installed on the destination computer. The files are collected and compressed into "instance specific" compressed archives. - - The maximum number of SQL Server Always On Health logs that will be collected for each discovered instance is 20. The files are collected in descending order, based on the creation date of the file. - - | Description| File name | - |---|---| - |SQL Server Always On health logs| Named instance:
___AlwaysOn_health_XeLogs.zip_

Default Instance:
__MSSQLSERVER_AlwaysOn_health_XeLogs.zip_| - - > [!NOTE] - > When the SQL Server Connectivity Diagnostics Collector is executed against a Windows failover cluster, SQL Server Always On health logs are collected only if they are stored on a drive that is "owned" and "online" to the destination cluster node. - -- **SQL Server failover cluster health logs** - - SQL Server failover cluster health logs are collected from each "clustered" instance of SQL Server 2012 that is installed on the destination computer. The files are collected and compressed into "instance specific" compressed archives. - - The maximum number of failover cluster health logs that will be collected for each instance is 20. The files are collected in descending order, based on the creation date of the file. - - | Description| File name | - |---|---| - |SQL Server failover cluster health logs| Named instance:
___FailoverCluster_health_XeLogs.zip_

Default Instance:
__MSSQLSERVER_FailoverCluster_health_XeLogs.zip_| - - > [!NOTE] - > The SQL Server failover cluster health logs are collected only if they are stored on a drive that is "owned" and "online" to the destination cluster node. - -- **SQL Server default system health logs** - - SQL Server default system health logs are collected from each instance of SQL Server 2012 that is installed on the destination computer. The files are collected and compressed into "instance specific" compressed archives. - - | Description| File name | - |---|---| - |SQL Server default system health logs| Named instance:
___system_health_XeLogs.zip_

Default Instance:
__MSSQLSERVER_system_health_XeLogs.zip_| - - > [!NOTE] - > When the SQL Server Connectivity Diagnostics Collector is executed against a Windows failover cluster, SQL Server default system health logs are collected only if they are stored on a drive that is "owned" and "online" to the destination cluster node. - -## Applies to - -- SQL Server 2012 Business Intelligence -- SQL Server 2012 Developer -- SQL Server 2012 Enterprise -- SQL Server 2012 Express -- SQL Server 2012 Parallel Data Warehouse -- SQL Server 2012 Standard -- SQL Server 2012 Web -- SQL Server 2012 Enterprise Core -- SQL Server 2008 Developer -- SQL Server 2008 Enterprise -- SQL Server 2008 Express -- SQL Server 2008 Standard -- SQL Server 2008 Standard Edition for Small Business -- SQL Server 2008 Web -- SQL Server 2008 Workgroup -- SQL Server 2008 Express with Advanced Services -- SQL Server 2008 R2 Datacenter -- SQL Server 2008 R2 Developer -- SQL Server 2008 R2 Enterprise -- SQL Server 2008 R2 Express -- SQL Server 2008 R2 Express with Advanced Services -- SQL Server 2008 R2 Parallel Data Warehouse -- SQL Server 2008 R2 Standard -- SQL Server 2008 R2 Standard Edition for Small Business -- SQL Server 2008 R2 Web -- SQL Server 2008 R2 Workgroup -- SQL Server 2005 Developer Edition -- SQL Server 2005 Enterprise Edition -- SQL Server 2005 Enterprise X64 Edition -- SQL Server 2005 Evaluation Edition -- SQL Server 2005 Express Edition -- SQL Server 2005 Express Edition with Advanced Services -- SQL Server 2005 Standard Edition -- SQL Server 2005 Standard X64 Edition -- SQL Server 2005 Workgroup Edition From c7d443ba8c6f22466bb7f1d919ee10dc591a8c38 Mon Sep 17 00:00:00 2001 From: sevend2 <77822529+sevend2@users.noreply.github.com> Date: Fri, 19 Apr 2024 15:16:50 +0800 Subject: [PATCH 7/8] Delete support/sql/general/rs-diagnostics-collector-information.md --- .../rs-diagnostics-collector-information.md | 161 ------------------ 1 file changed, 161 deletions(-) delete mode 100644 support/sql/general/rs-diagnostics-collector-information.md diff --git a/support/sql/general/rs-diagnostics-collector-information.md b/support/sql/general/rs-diagnostics-collector-information.md deleted file mode 100644 index 08850f271f..0000000000 --- a/support/sql/general/rs-diagnostics-collector-information.md +++ /dev/null @@ -1,161 +0,0 @@ ---- -title: RS Diagnostics Collector collects information -description: This article describes the information that may be collected from a computer when the SQL RS Diagnostics Collector tool is running. -ms.date: 08/19/2020 -ms.reviewer: ramakoni -ms.topic: article ---- -# Information that is collected by SQL RS Diagnostics Collector - -This article describes the information that may be collected from a computer when the SQL RS Diagnostics Collector tool is running. - -_Original product version:_   Microsoft SQL Server 2012, SQL Server 2008, SQL Server 2008 R2, SQL Server 2005 -_Original KB number:_   2773194 - -## Summary - -The SQL RS Diagnostics Collector for Windows Server 2003 R2, Windows Vista, Windows Server 2008, Windows Server 2008 R2, Windows 7, Windows 8, Windows 8.1, Windows Server 2012, and Windows Server 2012 R2 collects diagnostic information that is useful in troubleshooting a broad class of issues that involve SQL Server Reporting Services (SSRS). This collector is used to collect information for both the Native mode and the SharePoint mode of SSRS. - -The SQL RS Diagnostics Collector supports the following versions of SQL Server: - -- SQL Server 2005 -- SQL Server 2008 -- SQL Server 2008 R2 -- SQL Server 2012 - -## Prerequisite software - -There are different prerequisites to run diagnostic packages, depending on the operating system of the destination computer. The diagnostic package will automatically check your computer for these prerequisites, and then start if the prerequisites are already installed. If the prerequisites are not already available on the computer, you are prompted to install them. The Automated Troubleshooting Service (MATS) can also install the required software for you. For example, if Windows PowerShell is not present on the destination computer, MATS will install it automatically. For more information, see [Information about Microsoft Automated Troubleshooting Services and Support Diagnostic Platform](https://support.microsoft.com/help/2598970). - -## Required Windows rights - -You must have administrative rights on the computer from which you execute the SQL RS Diagnostics Collector. - -## Steps that are involved - -The SQL RS Diagnostics Collector must be manually run on all computers that are involved in the SSRS configuration. For example if the SSRS is a scale-out deployment, then the SQL RS Diagnostics Collector should be manually run on all computers that are involved in the scale-out configuration. Similarly, on a SharePoint-integrated mode, the SQL RS Diagnostics Collector should be run on SharePoint. - -## SQL Server security requirements - -The SQL RS Diagnostics Collector discovers all instances of reporting services that are installed on the computer where the diagnostics tool is run. As part of the data collection process, the SQL RS Diagnostics Collector tries to connect to each SSRS catalog database server to which the SSRS instances connect, and then collects information from the ReportServer catalog database. Database connections are made by using Windows authentication. In order to start the SQL RS Diagnostics Collector, you must have a Windows logon that is a member in the sysadmin fixed server role. - -## SharePoint security requirements - -The SQL RS Diagnostics Collector discovers all instances of reporting services that are installed on the computer. If the computer hosts just the SharePoint software that SSRS integrates to, then the SQL RS Diagnostics Collector collects information about the SharePoint configuration, installed websites, and so on. In order to execute the SQL RS Diagnostics Collector, you must have a Windows logon that is a member of the administrator group on the computer. - -## Information that is collected by the SQL RS Diagnostics Collector - -- **System event log** - - > [!NOTE] - > The SQL RS Diagnostics Collector collects events from the previous 30 days. - - |Description|File name| - |---|---| - |System event log in TXT, CSV, and EVT or EVTX formats| _ _ evt_System.csv_
_ _ evt_System.txt_
_ _ evt_System.(evt or evtx)_| - -- **Application event log** - - > [!NOTE] - > The SQL RS Diagnostics Collector collects events from the previous 30 days. - - |Description|File name| - |---|---| - |Application event log in TXT, CSV, and EVT or EVTX formats| _ _evt_Application.csv_
_ _ evt_Application.txt_
_ _evt_Application.(evt or evtx)_| - -- **Registry information that is related to reporting services configuration** - - |Description|File name| - |---|---| - |Collect registry key and child keys under `HKLM:\System\CurrentControlSet\Services\TCPIP\Parameters`.| _ _RS_Registry.XML_| - |Collect registry key and child keys under `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa`.| _ _RS_Registry.XML_| - -- **Information from all services that are installed on the destination computer** - - |Description|File name| - |---|---| - |Collect information about services that are installed on the destination computer.| _ _MiscProperties.XML_| - -- **Information from the ULS logs from the SharePoint instance on the destination computer** - - |Description|File name| - |---|---| - |Collect the ULS logs from the SharePoint that is installed on the destination computer.| _. _Date.log_| - -- **Information from the SSRS Logs from all SSRS instances on the destination computer** - - |Description|File name| - |---|---| - |Collect the SSRS logs from the SSRS instances that are installed on the destination computer.| _. _ReportServerService_GUID.log_| - -- **Information from the SSRS ReportServer.Config file from all SSRS instances on the destination computer** - - |Description|File name| - |---|---| - |Collect the _RSReportServer.Config_ file from the SSRS instances that are installed on the destination computer.| _. _RSReportserver.config_| - -- **Information from the Web.config file from all SSRS instances on the destination computer** - - |Description|File name| - |---|---| - |Collect the _Web.config_ file from the ReportServer and ReportManager directories from all SSRS instances that are installed on the destination computer.| _. _web.config_| - -- **Information from the SSRS configuration for all SSRS instances on the destination computer** - - |Description|File name| - |---|---| - |Collect the configuration information that is stored in the SSRS Catalog database for all SSRS instances that are installed on the destination computer.| _. ConfigInfo.XML_| - -- **Information from the execution information for all SSRS instances on the destination computer** - - |Description|File name| - |---|---| - |Collect the execution information that is stored in the SSRS Catalog database for all SSRS instances that are installed on the destination computer.| _. ExecutionInfo.XML_| - -- **Information from the SPN configuration for all SSRS instances on the destination computer** - - |Description|File name| - |---|---| - |Collect the SPN configuration information for the SSRS service account that is running the SSRS instance. (if the server is running SharePoint)| _ _RS_SPN.XML_| - -- **Information from the HTTP error logs on the destination computer** - - |Description|File name| - |---|---| - |Collect the HTTP error logs on the destination computer.| _.httperrX.log_| - -- **Information from the HTTP logs for all SSRS instances on the destination computer** - - |Description|File name| - |---|---| - |Collect the HTTP logs that are generated if the attribute is turned on the SSRS _Reportserver.config_ files.| _. _Http.log_| - -## Applies to - -- SQL Server 2012 Developer -- SQL Server 2012 Enterprise -- SQL Server 2012 Enterprise Core -- SQL Server 2012 Express -- SQL Server 2012 Web -- SQL Server 2008 Developer -- SQL Server 2008 Enterprise -- SQL Server 2008 Express -- SQL Server 2008 Standard -- SQL Server 2008 Web -- SQL Server 2008 Workgroup -- SQL Server 2008 R2 Datacenter -- SQL Server 2008 R2 Developer -- SQL Server 2008 R2 Enterprise -- SQL Server 2008 R2 Express -- SQL Server 2008 R2 Parallel Data Warehouse -- SQL Server 2008 R2 Standard -- SQL Server 2008 R2 Web -- SQL Server 2008 R2 Workgroup -- SQL Server 2005 Developer Edition -- SQL Server 2005 Enterprise Edition -- SQL Server 2005 Enterprise X64 Edition -- SQL Server 2005 Evaluation Edition -- SQL Server 2005 Express Edition -- SQL Server 2005 Standard Edition -- SQL Server 2005 Standard X64 Edition -- SQL Server 2005 Workgroup Edition From 23b2e048b96d511b1d3659b5f7c259fe62402d03 Mon Sep 17 00:00:00 2001 From: sevend2 <77822529+sevend2@users.noreply.github.com> Date: Fri, 19 Apr 2024 15:26:49 +0800 Subject: [PATCH 8/8] Update .openpublishing.redirection.developer.json --- .openpublishing.redirection.developer.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.openpublishing.redirection.developer.json b/.openpublishing.redirection.developer.json index dffa5d4002..9c06ad589e 100644 --- a/.openpublishing.redirection.developer.json +++ b/.openpublishing.redirection.developer.json @@ -4707,7 +4707,7 @@ }, { "source_path": "support/sql/general/connectivity-diagnostics-collector.md", - "redirect_url": "/troubleshoot/sql/tools/sql-support-troubleshooting-diagnostic-tools, + "redirect_url": "/troubleshoot/sql/tools/sql-support-troubleshooting-diagnostic-tools", "redirect_document_id": false }, {