Forum Discussion

ScottDuncan's avatar
ScottDuncan
Icon for Contributor rankContributor
26 days ago
Solved

SQL Server discovery issue

I'm trying to get a SQL Server instance discovered by SL1 which refuses to even determine SQL Server is installed. All the discovery does is return this message:

SQL Server discovery returned empty from SqlAppCollectionInstance data collector

The Windows device seems to have no issues. SQLPS is installed and working. SQL Server permissions have been granted as required (but it doesn't appear to be getting as far as logging in to the instance - it simply doesn't recognize SQL Server is installed).

I've tried rerunning winrm_configuration_wizard_v3.4.ps1, which worked for another machine that was returning the same sort of error.

I've tried removing the SQL DAs and realigning via pre-defined template & credentials (which work perfectly fine for other servers in the domain).

I'd rather not have to delete the Windows device and perform complete discovery from scratch; this shouldn't be necessary.

Ideas?

Full log from discovery session:

1.    Collector Task session registered...
2.    Collector is working...
3.    Collector is working...
4.    Collector is working...
5.    Collector is working...
6.    Collector is working...
7.    Collector is working...
8.    Process Started on Collector
9.    Collecting for App ID: 1270 from Device ID: 192379 on Collector ID: 359
10.    Python version 3.6.8 (default, May 24 2024, 06:39:46)
11.    [GCC 8.5.0 20210514 (Red Hat 8.5.0-21.0.1)]
12.    Assigned collector: 359; Root collector: None; This collector: 359
13.    Collector affinity: [4] Root device collector affinity mode specified, device does not have a DCM root device. Using assigned collector.
14.    Skipping scheduling of non-collectable Discovery and Label (Config Group) objects: [12550, 12551]
15.    Object 12549 is enabled for collection
16.    Object 12552 is enabled for collection
17.    Using credential: 1216
18.    Created an app object: AID: 1270 [SNIPPET CONFIG] / DID: 192379
19.    Created a device object: 192379
20.    Will use 10.155.210.18 as IP for device
21.    Precollect for app returned True
22.    Oids to collect:
23.    GROUP: 1 obj_id: 12549 OID: name NAME: Name
24.    GROUP: 1 obj_id: 12552 OID: unique_id NAME: ID
25.    Starting collect
26.    Running Snippet 1458
27.    /opt/em7/lib/python3/requests/__init__.py:104: RequestsDependencyWarning: urllib3 (1.26.6) or chardet (5.0.0)/charset_normalizer (2.0.4) doesn't match a supported version!
28.    RequestsDependencyWarning)
29.    Reading config as a prod env
30.    Reading config as a prod env
31.    powershell_pywinrm_transport.connect: service: HTTP, target device: 10.155.210.18
32.    callPywinrmFunction: processing output and error for Python 3
33.    SqlAppCollectionInstance:_collect_data: No SQL Server instances found (standalone or clustered)
34.    Snippet 1458 ran successfully
35.    collected objects: {1: {12549: {'object_type': 'DynamicAppObject', 'enum': '', 'error_msg': '', 'factor': '', 'monitor_config': 0, 'name': 'Name', 'oid': 'name', 'oid_time': '0', 'oid_type': 1458, 'class': 10, 'prime': 0, 'result': [], 'std_enable': 0, 'std_min': 0, 'string_type': 0, 'trend_col': '', 'wm_walk_length': '', 'formula': ''}, 12552: {'object_type': 'DynamicAppObject', 'enum': '', 'error_msg': '', 'factor': '', 'monitor_config': 0, 'name': 'ID', 'oid': 'unique_id', 'oid_time': '0', 'oid_type': 1458, 'class': 10, 'prime': 0, 'result': [], 'std_enable': 0, 'std_min': 0, 'string_type': 0, 'trend_col': '', 'wm_walk_length': '', 'formula': ''}}}
36.    AID: 1270 [SNIPPET CONFIG] / DID: 192379 thinks it was collected properly
37.    AID: 1270 [SNIPPET CONFIG] / DID: 192379 had 0 bad oids (out of 1): []
38.    ================================================================================
39.    Ingestion Metadata
40.    ================================================================================
41.    Collected: True
42.    Collection time: 2.165022611618042 seconds
43.    Found Collection Objects: []
44.    Number of Bad OIDS: []
45.    Error Message: N/A
46.    Internal Alert 518: did: 192379, message: "[App ID 1270]: SQL Server discovery returned empty from SqlAppCollectionInstance data collector."
47.    ================================================================================
48.    Raw Ingested Data:
49.    ================================================================================
50.    Group    RawIndex    ObjID    ObjName    RawValue       ElapsedTime(ms)
51.    -------  ----------  -------  ---------  -------------  -----------------
52.    1        N/A         12552    ID         -- NO DATA --  N/A
53.    1        N/A         12549    Name       -- NO DATA --  N/A
54.    ================================================================================
55.    Configuration Data for Storage:
56.    ================================================================================
57.    Group    Index    ObjID    ObjName    Value          PrevValue        Added    Changed    Removed
58.    -------  -------  -------  ---------  -------------  ---------------  -------  ---------  ---------
59.    1        N/A      12552    ID         -- NO DATA --  -- UNCHANGED --
60.    1        N/A      12549    Name       -- NO DATA --  -- UNCHANGED --
61.    ================================================================================
62.    Configuration Change Alerts:
63.    ================================================================================
64.    -- NO CHANGE ALERTS --
65.    ================================================================================
66.    Processing app alerts...
67.    ================================================================================
68.    Triggered alerts:
69.    0 triggered
70.    ================================================================================
71.    DCM Component Records extracted from Configuration Data:
72.    ================================================================================
73.    ========================================
74.    Discovered component records:
75.    ========================================
76.    device_name    unique_identifier    distinguished_name    uuid    guid    previous_unique_ids    organization    class_identifier_1    class_identifier_2    mac_address    availability
77.    -------------  -------------------  --------------------  ------  ------  ---------------------  --------------  --------------------  --------------------  -------------  --------------
78.    ========================================
79.    Vanished components (by unique_id):
80.    ========================================
81.    --NO VANISHED DEVICES--
82.    Dynamic App Execution Complete
83.    /opt/em7/lib/python3/paramiko/transport.py:33: CryptographyDeprecationWarning: Python 3.6 is no longer supported by the Python core team. Therefore, support for it is deprecated in cryptography and will be removed in a future release.
84.    from cryptography.hazmat.backends import default_backend
85.    /opt/em7/lib/python3/requests/__init__.py:104: RequestsDependencyWarning: urllib3 (1.26.6) or chardet (5.0.0)/charset_normalizer (2.0.4) doesn't match a supported version!
86.    RequestsDependencyWarning)
87.    Process Completed on Collector
  • Thought I'd left a reply covering the solution, but apparently it didn't save. It was some sort of permissions issue, only resolved by making the service account used by ScienceLogic PowerShell account a local admin. A message in the Windows Security Event Log indicated it was due to not having "Act as part of the operating system" rights, but those rights weren't sufficient. I suspect some sort of Group Policy interfering with things, but without knowing exactly what rights the service account is expected to have and the rats nest of GPOs, I don't have time to dig further.

2 Replies

  • Well, I bit the bullet and removed/rediscovered the Windows device anyway. Still getting the same error for SQL discovery: SQL Server discovery returned empty from SqlAppCollectionInstance data collector

  • Thought I'd left a reply covering the solution, but apparently it didn't save. It was some sort of permissions issue, only resolved by making the service account used by ScienceLogic PowerShell account a local admin. A message in the Windows Security Event Log indicated it was due to not having "Act as part of the operating system" rights, but those rights weren't sufficient. I suspect some sort of Group Policy interfering with things, but without knowing exactly what rights the service account is expected to have and the rats nest of GPOs, I don't have time to dig further.