Page History
...
| Note | ||||||
|---|---|---|---|---|---|---|
When using direct WMI you must have RPC port 135 opened for WMI request initiation access. You must have permissions configured on each SQL instance to allow for remote access to WMI, using a Windows account. Other high-end ports opened may be required in firewall to allow WMI to communicate. The following article explains how to set a fixed port for WMI:
|
- Required permissions for direct WMI collection
...
For more information about using a direct WMI connection, see the Microsoft document,
| Newtablink | ||||
|---|---|---|---|---|
|
- Configure WMI to run out-of-process
...
To configure the WMI timeout value:
- NAvigate Navigate to the SQL Diagnostic Manager install directory
- Open SQLdmCollectionService.exe.Config
- Modify the <CollectionService> node under the <Services> node
- Add wmiQueryTimeOut="300" as a parameter to this node
- Save and close file
- Restart the collection service
Sample configuration entry:
...
- OLE Automation Procedures Disabled: Select the Collect Operating System data using OLE Automation option to enable OLE Automation procedures.
- OLE Automation Procedures Unavailable: The stored procedures associated with OLE Automation are missing on the SQL Server instance. SQL Diagnostic Manager cannot capture OS metrics until these stored procedures are available on the SQL Server instance.
- WMI Service Not Running: The WMI Service on the monitored SQL Server instance may not be running. SQL Diagnostic Manager cannot collect OS metrics until this service is started.
- Lightweight Pooling Enabled: This is an advanced feature used in symmetric multiprocessing environments in SQL Server. SQL Diagnostic Manager cannot collect OS metrics until this option is disabled on your monitored SQL Server instances.