1

Hello!!

I have a McAfee ePO setup where we use SQL for database.

I noticed few monitors/say tables are not displaying properly in dashboards. .

When I went through the sql logs I found below errors.

Could these errors be a reason for not seeing the tables getting populated ?

2022-03-21 02:00:26.35 spid16s SQL Server has encountered 808 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [T:\TempDB\tempdb_df4.ndf] in database [tempdb] (2). The OS file handle is 0x0000000000000C30. The offset of the latest long I/O is: 0x00000215ce0000

2022-03-21 02:00:26.35 spid16s SQL Server has encountered 807 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [T:\TempDB\tempdb_df5.ndf] in database [tempdb] (2). The OS file handle is 0x0000000000000C34. The offset of the latest long I/O is: 0x00000215c60000

2022-03-21 02:00:26.35 spid16s SQL Server has encountered 805 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [T:\TempDB\tempdb_df3.ndf] in database [tempdb] (2). The OS file handle is 0x0000000000000C0C. The offset of the latest long I/O is: 0x00000215c20000

2022-03-21 02:00:26.35 spid16s SQL Server has encountered 811 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [T:\TempDB\tempdb_df6.ndf] in database [tempdb] (2). The OS file handle is 0x0000000000000C14. The offset of the latest long I/O is: 0x00000215bb0000

2022-03-21 02:00:26.35 spid16s SQL Server has encountered 815 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [T:\TempDB\tempdb_df2.ndf] in database [tempdb] (2). The OS file handle is 0x0000000000000C08. The offset of the latest long I/O is: 0x00000215c10000

2022-03-21 02:00:26.35 spid16s SQL Server has encountered 806 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [T:\TempDB\tempdb_df7.ndf] in database [tempdb] (2). The OS file handle is 0x0000000000000C3C. The offset of the latest long I/O is: 0x00000215c80000

2022-03-21 02:00:26.35 spid16s SQL Server has encountered 809 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [T:\TempDB\tempdev.mdf] in database [tempdb] (2). The OS file handle is 0x0000000000000B90. The offset of the latest long I/O is: 0x00000215eb0000

2022-03-21 02:00:26.35 spid16s SQL Server has encountered 808 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [T:\TempDB\tempdb_df8.ndf] in database [tempdb] (2). The OS file handle is 0x0000000000000C40. The offset of the latest long I/O is: 0x00000215c90000

2022-03-21 02:00:26.35 spid16s SQL Server has encountered 14 occurrence(s) of I/O requests taking longer than 15 seconds to co

8 Spice ups
2

I don’t know what McAfee epo is, but my guess is that this is more of a product question than SQL.

It does sound like you’ve got some trouble with that temp db though. It is hard to tell if that’s a cause or effect or completely unrelated.

3

This should be posted under McAfee (I’ll get it changed), while the errors are SQL related, the problem is with your ePO Database.

@dsentelle ​ McAfee ePO is the central console for all McAfee enterprise products.

@spiceuser-hkef7 ​ you really need to be contacting McAfee or your reseller, if you don’t have support, you need it.

Do any of your servers, ePO or SQL have snapshots/checkpoints running, are they heavily loaded or under-spec?
You haven’t mentioned anything about your ePO, version, build, what products you have checked-in, what OSes are in use, what SQL version, virtual or physical systems, shared or dedicated boxes.
Please provide some background

1 Spice up
4

Those errors are all relating to tempdb too, have you tried restarting SQL or the SQL server?

TempDB will be flushed on restart, but if you are running heavy McAfee queries or reports, this will need to be investigated, do you run any indexing or scheduled maintenance on your SQL either directly or through the ePO console?

Having too many columns on a view can cause massive workloads for an SQL server too, so perhaps reduce how many visible columns are on your system tree.

5

The error seems to indicate your underlying storage is bogged down, your SQL is overloaded or both.

6

What are the server specs - particularly disk set up - where are your database files…user db’s as well as tempdb?

When is the last time indexes and statistics were maintained?

What are your top waits?

7

Firewall?