Long-running sleeping queries are left open to the SQL Server when 'Single System Troubleshooting' is used
Technical Articles ID:
KB93380
Last Modified: 2023-08-10 10:42:56 Etc/GMT
Environment
ePolicy Orchestrator (ePO) 5.10.x. 5.9.x
McAfee Agent (MA) 5.7.1, 5.7.0
Problem
When you use the Single System Troubleshooting feature in ePO, several different queries are executed against the ePO database. Sometimes, these queries are not closed correctly and are left open in a sleeping state.
The above can cause problems, such as tempdb growth.
You may see one or more of the following queries in a sleeping state:
Query 1
select AutoID, LeafNodeID, LdapOrgUnit from [EPOComputerLdapProperties] where LeafNodeID=<some integer>
Query 2
(@P0 nvarchar(4000),@P1 nvarchar(4000))SELECT pp.ParentID AS SystemId , ln.ModifiedPropsDate , ln.LastUpdate , pp.ProductCode , ps.SectionName , ps.SettingName , ps.Value FROM EPOLeafNode ln JOIN EPOProductProperties pp ON ln.AutoID = pp.ParentID JOIN EPOMetaSoftware ms ON ms.ProductCode = pp.ProductCode JOIN EPOProductSettings ps ON pp.AutoID = ps.ParentID WHERE (ms.ProductCode = @P0 OR ms.MetaProductID = @P1 ) AND ln.AutoID = <some integer>
Query 3
(@P0 int)select [EPOComputerProperties].ParentID, [EPOComputerProperties].ComputerName, [EPOComputerProperties].DomainName, [EPOComputerProperties].IPAddress, [EPOComputerProperties].OSType, [EPOComputerProperties].OSVersion, [EPOComputerProperties].OSServicePackVer, [EPOComputerProperties].OSBuildNum, [EPOComputerProperties].OSOEMID, [EPOComputerProperties].CPUType, [EPOComputerProperties].CPUSpeed, [EPOComputerProperties].NumOfCPU, [EPOComputerProperties].TotalPhysicalMemory, [EPOComputerProperties].FreeDiskSpace, [EPOComputerProperties].TotalDiskSpace, [EPOComputerProperties].TimeZone, [EPOComputerProperties].DefaultLangID, [EPOComputerProperties].NetAddress, [EPOComputerProperties].UserName, [EPOComputerProperties].CPUSerialNum, [EPOComputerProperties].OSPlatform, [EPOComputerProperties].FreeMemory, [EPOComputerProperties].IPHostName, [EPOComputerProperties].IPXAddress, [EPOComputerProperties].TheTimestamp, [EPOComputerProperties].TheHiddenTimestamp, [EPOComputerProperties].SubnetAddress, [EPOComputerProperties].SubnetMask, [EPOComputerProperties].Description, [EPOComputerProperties].IsPortable, [EPOComputerProperties].OSBitMode, [EPOComputerProperties].UserProperty1, [EPOComputerProperties].UserProperty2, [EPOComputerProperties].UserProperty3, [EPOComputerProperties].UserProperty4, [EPOComputerProperties].UserProperty5, [EPOComputerProperties].UserProperty6, [EPOComputerProperties].UserProperty7, [EPOComputerProperties].UserProperty8, [EPOComputerProperties].IPV6, [EPOComputerProperties].IPV4x, [EPOComputerProperties].LastAgentHandler, [EPOComputerProperties].SysvolFreeSpace, [EPOComputerProperties].SysvolTotalSpace, [EPOComputerProperties].IPSubnet, [EPOComputerProperties].IPSubnetMask, [EPOComputerProperties].ManagementType, [EPOComputerProperties].SystemDescription, EPOLeafNode.TenantId, [EPOComputerProperties].Vdi from [EPOComputerProperties] left join [EPOLeafNode] on [EPOComputerProperties].[ParentID]=[EPOLeafNode].[AutoID] where [EPOComputerProperties].[ParentID]= @P0
Workaround
To purge any current sleeping connections, restart the ePO application server service as follows:
- Press Windows+R.
- Type services.msc into the field and press Enter.
- Right-click on the following ePO service, and select Restart:
McAfee ePolicy Orchestrator #.#.# Application Server
- Close the services window.
|
