Hi everybody,
I don't understand, this error. Do you have an idea about this problem ?
NetPerfMon Service Error: Exception in Service Timer Tick - 0
Thanks in advance
Well, restarting the "Solarwinds Network Performance Monitor" service resolved both of my errors, but I'll keep watching it.
So far, I'm not getting the second error listed above when trying to open the system manager yet, but it is taking a long time to open.
I have seen this error in the past and as I recall it was due at least in part to time synchronization issues between the Orion polling server and the database server. I have been told by SW support that Orion is not very tolerant when it cannot communicate with the database. Time differentials as little as 30 seconds can be a problem.
Can anyone at SolarWinds re-verify if this is still an issue?
Is anyone seeing this issue with a local SQL installation?
Borgan and others - Yes, the time synchronization between the Orion Polling Engine and the Database Server can indeed cause issues (Most notably the Polling Engine Status in the Admin section of the web console) - Will continually show "down" or "warning" and have the "Last Database Update" off by the seconds or minutes of the discrepancy between the two servers...
Simply put - make sure they are in sync.
I have not seen the Timer Tick on databases that are local to the Polling Engine Server.
yes i have always this problem with :
Package | Orion NPM v9 SLX |
Version | 9.1.0 |
Release | Orion Version 9.1.0 - October 2008 |
I use a local sql 2000 installation).
This problem that I have no graphics since sunday. I have too errors with dcom.
I'm getting this error again and not sure why. Both of our servers (polling and database) are domain members and are both in sync with the DCs. The systray clocks show the same time, so from what I can tell, the servers are in time sync.
Even i had a problem with timer tick '0' in the event log (solarwinds)
The support found this while troubleshooting one of our problem . Below is the response i got form them . This really was meaning full and helped.
There are previous similar cases where timer tick '0' exist in the event log which is related to duplicated IPs/ nodes in the nodes in the database.
Locate any duplicate IP Addresses in the Nodes table:
select IP_Address, count(*)
from Nodes
Group by IP_Address
HAVING count(*) > 1
Locate any Mangled IP Addresses in the Nodes Table - this will lcoate IP Addresses that have less than 4 octets, more than 4 octets, are "Unknown", Null, or blank.
select NodeID, IP_Address, Caption
From Nodes
Where IP_Address not like '%.%.%.%' or IP_Address like '%.%.%.%.%'
FIND DUPLICATE NODES - E.G SAME NODE DISCOVERED UNDER DIFFERENT IPS
===========================================
1) Find out if there are any duplicate nodes with different IP Address/Caption. Checking this on Sysname
Select Sysname, count(*)
from Nodes
Group by Sysname
HAVING count(*) > 1
2) If there are duplicates showing up, this will display all details about those entries - the original and duplicate entries included. Customer can right-click and "Delete Selected Rows" on the entries that are deemed as the duplicates. Sysname is the 12th column in.
Select * from nodes where Sysname IN (select Sysname
from Nodes
group by Sysname
HAVING count(*) > 1)
ORDER BY sysname
do let us know if you find duplicates. And also if removing the same helped in solving the problem . Thanks!
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 195,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.