Restituisci
-
Titolo
Cannot access db2diag.log, SQL Server error log, or Oracle alert/log files on Windows – “A command shell connection could not be established” -
Descrizione
Database agents on Windows may fail to access the following log files:
- DB2: db2diag.log
- Oracle: alert.log and listener.log
- SQL Server: Error log
You may see errors like:
Failed to execute collection [DBO_Usability], reason=A command shell connection could not be establishedor
Failed to execute collection [DBO_Alert_Log], reason=A command shell connection could not be established -
Causa
The agent uses WMI or WinRM for OS-level log access. On Windows, these require elevated permissions that may not be granted by default. -
Risoluzione
Please see update at the end of the resolution before making changes.
To allow access, the OS user must have Full Control on these Windows registry keys:- 76A6415B-CB41-11d1-8B02-00600806D9B6
- 76a64158-cb41-11d1-8b02-00600806d9b6
- 72C24DD5-D70A-438B-8A42-98424B88AFB8
- 0D43FE01-F093-11CF-8940-00A0C9054228
Refer to the attached document or KB article 4229811 for step-by-step instructions on setting permissions on updating registry permissions.Note: There is no means at this time to bypass this error for the DB2 Error when adding a new DB2 agent using the wizard. Two Enhancement Requests have been logged to skip the OS monitoring or bypass the OS connectivity check.ER FGDB2-I-19 Skip OS check when adding a DB2 agent
ER FGDB2-I-26 Creating a DB2 agent wizard without OS information
UPDATE
Starting with WIndows Server 2019, Microsoft disabled SMBv1 by default s. This prevents automatic configuration of WinShell.WorkaroundYou can still use use WinShell over DCOM by manually setting permissions or running a script locally on the monitored server.See KB article 4294210 - "WMI over DCOM onserver with SMB 1.0 disabled" for details and script.