-
Troubleshooting: No Alerts are Generating
Problem No alerts are generating in Kaseya at all. Or no alerts of a single type are not generating, for example, no agent offline alerts. Cause The scheduled agent procedure Run Process Alarms has been removed from the schedule. This may happen after a patch or a maintenance event. Solution Navigate to the System > Server…
-
Agent status alarms are based on server time to agent time
Symptom When an agent goes offline and and email is sent the reported time is the Kaseya servers time not the Agents time, which creates confusion for agents that are in different time zones. Resolution You can change the reported time from server time to agent time <ata>
-
Multiple Alarm conditions don’t translate into multiple script executions
Multiple Alarm conditions don’t translate into multiple script executions Symptom With Kaseya classic monitoring, when an alarm condition is met you can chose to create an Alarm, Ticket, E-mail or Run script. If the alarm condition is met a number of times in a very short period of time you will receive multiple alerts (if…
-
How can I change the monitoring of certain counters without changing the whole monitor set
QUESTION I have configured a Kaseya Performance Monitor to monitor all the drives on a machine. However, I do not want certain drives to be monitored. How can I disable monitoring on some drives, but leave the others active - I don't want to have lots of different monitor sets? ANSWER Kaseya has a concept called…
-
ERROR 0x4019 occurred while processing managed file 'c:\kworking\KMonitorsets\KMON$null.xml
Symptom Errors found in the agent logs similar to this "ERROR 0x4019 occurred while processing managed file C:\kworking\KMonitorsets\KMON$null.xml" Resolution Delete the contents on this folder "C:\kworking\KMonitorsets" then perform a "Update Lists By Scan" ( Because it will reapply the monitoring) on the…
-
Perfmon continues to run after Kaseya Agent has been removed
PROBLEM After uninstalling the kasyea agent, performance counters continue to run and you see files such as KLOG$1234.csv being created in c:\kworking on the machine CAUSE When you configure Kaseya to collect Windows performance counter logs from a machine, kaseya sends instructions down to the machine that tells windows…
-
Event log collection error
PROBLEM Event log collection error in Event log settings page(Too many logs selected. Reduce the number of logs for this machine) CAUSE You can only assign 10 event logs per machine. The system won't allow you to go further from that. As soon as you assign ten event logs to a machine, it will give you an error message in…
-
Event Log collection has drastically increased per day after a fresh build and copying over the data
Symptom As part of an upgrade or change to new hardware you've built a new server and installed Kaseya then copied the files from the old server to the new one and Restored the database. Post the change you're database is growing fast. Further investigation After further investigation you've noticed that the even't logs…
-
Kaseya and machines without persistant disks such as Thin clients and Citrix PVS
Symptom While you're able to to install an agent on some machines without persistent disks such as Thin client and Citrix PVS, Various functions stop working. This is typically seen by performance counters not working as an example. Previous attempts to resolve While you may have resolved the issue yourself by following…
-
How Can I Identify Unresponsive Perfmon Counters in Classic Monitoring?
QUESTION In the VSA how can I identify which Monitor sets have unresponsive counters and are not reporting data? ANSWER There is no built-in report or functionality in the VSA that will identify these counters. For advanced users, you can run the following SQL command in SQL Management Studio. For monitor sets that have…