Hi everybody,
I don't understand, this error. Do you have an idea about this problem ?
Thanks in advance
Interfaces turns grey: Solved!
I had a problem that interfaces on some nodes turn grey and unknown. I use snmp v3, don't know if that has anything to do with it.
The solution was to enable 64-bit counters on that node. That could only be done from the web interface. Then I restarted the Network Performance Monitor Service. (Don't know if I had to do that but it fastend the process.)
Peace!
No idea ????
My windows application log is filling up with this error. It all started yesterday - no updates or maintenance was done to the server at all.
I'll bet we need to open tickets!
I'm also getting this error when trying to open the Orion NPM System Manager while on the polling server:
I'm leary that a restart of the service will fix this, so I guess I'm going to open a support ticket.
All - Please open tickets so we can see if there is a common issue we need to address.
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 :
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(*)
Group by Sysname
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
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!
Hey,
We're having the same problem and I've tried everything, including the solutions found on this thread... Opening up a ticket just now.
The tick-problem appears almost always within a week from rebooting the server, at random times. Usually it takes a couple of days though. When the crash occurs, Windows application monitor log starts spamming the "NetPerfMon Service Error: Exception in Service Timer Tick - 0-error" every 5 seconds until the Solarwinds Network Performance Monitor -service is restarted (or the server is rebooted). Also, when the error occurs, I can't access the System Manager because of the compatibility error (pic in jlintner's reply).
We're running a 64-bit Win2008SP2 with SQL2008 Express on the same server (Borgan). The problem occurred with versions 9.5.0SP4 and 9.5.1, can't confirm if it did it with 9.5.0 without the SP4.
Anyone had this on non-64-bit or pre-2008 system?
- L -
I have this problem also in one place. There we have a 64-bit Win2008SP2 with SQL2008 Express.
I "solved" it by using the win 2008 scheduler. In that you can make a rule to trigger on "NetPerfMon Service Error: Exception in Service Timer Tick" in the windows event log. If that occures I run a bat-script to restart all Orion services.
It's notpretty but it works. I can see in the logg that the alert has run the bat script a few times.
