1. The "Product Update" is the correct task to select. The update is actually done through the agent, not VirusScan.
2. For the locking issue. You will need to find out what query is actually doing the blocking. In the Activity Monitor, you can see the "Blocking" column, find the blocking SPID and right click, select "Details" and you can see the T-SQL code. This should give some indication of what is going on.
Hope this helps!
That really helps. I didn't know about details and seeing the SQL statement.
So I used the activity monitor and looked at my sql and found the following
There are two open transactions (=1)
1) PID 177 is sleeping and the last transaction was
(@P0 int)select AutoID, Type, NodeName, ParentID, AgentPlatform, ResortEnabled, AgentGUID, SequenceErrorCount, SequenceErrorCountLastUpdate, SuperAgent from [EPOLeafNode] where [EPOLeafNode]."AutoID"= @P0
2) PID 345 the other is suspended and was
select AutoID, Type, NodeName, ParentID, AgentPlatform, ResortEnabled, AgentGUID, SequenceErrorCount, SequenceErrorCountLastUpdate, SuperAgent from [EPOLeafNode] where AgentGUID='4DD7AE50-1F5F-4DCB-AB92-C4842B1B20B3'
Pid 345 is blocked waiting on PID 177 (the first select)
Both of these the application is jTDS
Do you have any scheduled tasks to run reports?
No I don't have any scheduled tasks for reports. I just added my virusscan policies on Friday and had just started to manually add a few systems that had different policies.
It's definitely hanging on the select for the group that has the most clients (like 25) wherehas if I click in my system tree and look at groups with just a couple of clients then all is okay.
This looks like something that we will need to diagnose further with the DB. I would suggest calling in to support so we can look at this closer.
I hate to jinx myself, but the lockup problem mysteriously went away on Monday night (KNOCK ON WOOD). So I will contact support if it happens again.