Updates Warning in Console (v4.5)

HI,

Looking at a SQL Profiler trace of what's going on, the dasboard data is fetched using the strored procedure:

dbo.ComputerDashboardDataGet

Depending on which subestate the data is being called for, it goes on to call either:

These essentially takes the subestate as a parameter and 2 time stamps.

The part of the query that fetches that update time is something like:

SELECT MAX(LastBinaryUpdate) AS FreshestSUMUpdate, ISNULL(MIN(LastBinaryUpdate), 0) AS StalestSUMUpdate
			FROM dbo.SDDMServers WITH (NOLOCK)
			WHERE ComputerID IN (SELECT ID FROM dbo.AliveComputersInSubestate( 1 ) WHERE Managed=1)
			AND LastBinaryUpdate != 0

I have added the 1 in the call to

AliveComputersInSubestate

 to represent the default subestate.

So essentially it's the oldest time of the column lastbinaryupdate in the table dbo.sddmservers.

This suggest that one of your SUMs hasn't updated or hasn't sent in a status message to report an update for a while.  Is there a SUM with the same "Last Updated" time?  

If you run:

sqlcmd -E -S .\sophos -d sophos45 -Q "select c.Name, c.LastMessageTime StatusRefreshedAt, LastBinaryUpdate, LastDataUpdate from dbo.SDDMServers as s left join dbo.ComputersAndDeletedComputers as c on c.ID = s.ComputerID" -o C:\windows\temp\out.txt -w 1000

 Which SUM has the same time as displayed in the dashboard?  Just considering the minutes and seconds should be enough if the timezones make the hours off.

I would suggest on that SUM machine:
1. Stop the SUM Service
2. Stop the Sophos Agent service.
3. Start the SUM Service

4. Start the Agent Service.
5. In SEC, check the computer details page of that SUM machine (endpoints view) and look at the last message time.  It should be very recent.

I would then force the SUM to update and then re-query the table after it completes its update routine.

Hope this helps.

Regards,

Jak

HI,

Looking at a SQL Profiler trace of what's going on, the dasboard data is fetched using the strored procedure:

dbo.ComputerDashboardDataGet

Depending on which subestate the data is being called for, it goes on to call either:

These essentially takes the subestate as a parameter and 2 time stamps.

The part of the query that fetches that update time is something like:

SELECT MAX(LastBinaryUpdate) AS FreshestSUMUpdate, ISNULL(MIN(LastBinaryUpdate), 0) AS StalestSUMUpdate
			FROM dbo.SDDMServers WITH (NOLOCK)
			WHERE ComputerID IN (SELECT ID FROM dbo.AliveComputersInSubestate( 1 ) WHERE Managed=1)
			AND LastBinaryUpdate != 0

I have added the 1 in the call to

AliveComputersInSubestate

 to represent the default subestate.

So essentially it's the oldest time of the column lastbinaryupdate in the table dbo.sddmservers.

This suggest that one of your SUMs hasn't updated or hasn't sent in a status message to report an update for a while.  Is there a SUM with the same "Last Updated" time?  

If you run:

sqlcmd -E -S .\sophos -d sophos45 -Q "select c.Name, c.LastMessageTime StatusRefreshedAt, LastBinaryUpdate, LastDataUpdate from dbo.SDDMServers as s left join dbo.ComputersAndDeletedComputers as c on c.ID = s.ComputerID" -o C:\windows\temp\out.txt -w 1000

 Which SUM has the same time as displayed in the dashboard?  Just considering the minutes and seconds should be enough if the timezones make the hours off.

I would suggest on that SUM machine:
1. Stop the SUM Service
2. Stop the Sophos Agent service.
3. Start the SUM Service

4. Start the Agent Service.
5. In SEC, check the computer details page of that SUM machine (endpoints view) and look at the last message time.  It should be very recent.

I would then force the SUM to update and then re-query the table after it completes its update routine.

Hope this helps.

Regards,

Jak