Skip to content

SQL LogScout v6.24.11.02
Compare
Choose a tag to compare
@PiJoCoder PiJoCoder released this 02 Nov 16:24
· 3 commits to main since this release
v6.24.11.02
13b9575
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Download

Scroll down to the bottom of this page and find the Assets section. Expand it and select SQL_LogScout_v6.24.11.02_Signed.zip to download it

Verify downloaded file:

You can verify the download by computing the hash of the SQL_LogScout_v6.24.11.02_Signed.zip file, using this command:

certutil -hashfile SQL_LogScout_v6.24.11.02_Signed.zip SHA512

Compare to this:

f6a6e0e66e4dfb02e44541ebf5b5aa4c44bcdfd4932390762b3d38e6ab59dfa1f302aff2a46a94037d04afebad12b66abffad856ec27643944fe3039789ea6fa

Known Issue(s)

Issue 1: Detailed scenario through GUI omits some xevent actions

When invoking SQL_LogScout for the Detailed scenario and use the GUI, some events in the xevent may be omitted such as showplan_xml.

Cause:

The reason is that the UI code was using the Xevent list for the General scenario instead of the Detailed.

Workaround:

To workaround this issue, do not use the GUI and instead use the command line interface.

Resolution

Fixed in 6.25.04.25

Issue 2: SQL Error Log, Agent Log and Full-Text Search log collection will fail on default failover cluster Instances

When you invoke SQL_LogScout with Basic scenario or any other scenario that contains the Basic against a default FCI (clustered) instance, the SQLErrorLogs_AgentLogs_SystemHealth_MemDumps_FciXel collector fail with following messages:

INFO	Executing Collector: SQLErrorLogs_AgentLogs_SystemHealth_MemDumps_FciXel 
WARN	The registry key for ERRORLOG path is not valid. Continuing with other collectors. 
INFO	Executing Collector: FullTextSearchMetadata 
INFO	Executing Collector: FullTextSearchLogFiles 
WARN	The registry key for ERRORLOG path is not valid. Continuing with other collectors.

Cause:

A recent code change doesn't account for the fact that registry key stores MSSQLSERVER for any default instance including FCI instances

Workaround:

To workaround this issue collect the ERRORLOG and SQL Agent logs manually.

Resolution

Fixed in 6.25.04.25

Fixes

This release fixes the following two issues that were reported in release 6.24.10.10. This package also includes all enhancements and fixes from the previous release. For the full list of these enhancements and fixes see Release 6.24.10.10

  • Fix error "Could not Connect to SQL Server" SSL Security error that occurs on some machines with older OS versions (Win 2012 R2, Win 2016)
  • Fix error for some scripts which would fail with "The multi-part identifier "COLUMN" could not be bound" on case sensitive instances
Assets 3
Loading