Hypertrend stopping and restarting at random

[jbesselm]

Lookout 6.02  Hypertrends seem to stop after a few minutes to hours and then restart. After replacing the computer on a system that has been working fine for over a year, this behavior has started with the new computer. The OS is Windows XP SP2. The trend data is not visible in MAX. I've tried starting with a new database but the symptoms persist. In the past whenI've seen something similar it was related to either windows or symantec automatic updates. These are off. Any ideas?

Jim

[Ryan.S]

Is this new computer the Lookout server or client?

If it's the server, and the database is on the local computer, try to view the data in MAX when the hypertrend stops displaying trends. If no data in MAX, it means the data logging has something wrong. Check if nicitdl5.exe is running or not. Check if the National Instruments Citadel service is Started or not in Windows Services. The Citadel should not stop randomly and restart after a while.

If the new computer is the client software, the database is on remote computer, check the networking, especially the firewall. Also, check the database in MAX. If the data is not in the database, the networking or firewall is not the issue. There might be something on the server computer that interrupts the Citadel.

[jbesselm]

Ryan;

The server and client processes are on the same computer. The data is not visible in MAX, the citadel service is running. Attached are screen shots of the hypertrend, the MAX hypertrend, and the windows processes. I suspect another windows process that is interfering with citadel. If this is the case do you have any ideas on how to isolate it. My first thought is to turn off the AVG antivirus software. Between the old computer and the new computer that is the only item that might have changed versions. Prior to us replacing the computer the Lookout installation has worked fine for over a year.

[jbesselm]

Problem Resolved.

After watching the symptoms and examining the windows event log. I noticed the following:
7/13/2008    7:04:52 AM    Tcpip    Information    None    4201    N/A    STC-WWCONTROL    The system detected that network adapter \DEVICE\TCPIP_{002F9391-B5AE-46DE-9909-D87BE5FC035C} was connected to the network, and has initiated normal operation over the network adapter.
7/13/2008    7:04:48 AM    E1000    Information    None    26    N/A    STC-WWCONTROL    Intel(R) PRO/1000 MT Network Connection Link has been established.
7/13/2008    7:04:47 AM    E1000    Warning    None    27    N/A    STC-WWCONTROL    Intel(R) PRO/1000 MT Network Connection Link has been disconnected.
7/12/2008    3:08:46 PM    Tcpip    Information    None    4201    N/A    STC-WWCONTROL    The system detected that network adapter \DEVICE\TCPIP_{002F9391-B5AE-46DE-9909-D87BE5FC035C} was connected to the network, and has initiated normal operation over the network adapter.
7/12/2008    3:08:46 PM    E1000    Information    None    26    N/A    STC-WWCONTROL    Intel(R) PRO/1000 MT Network Connection Link has been established.
7/12/2008    3:08:47 PM    BROWSER    Information    None    8033    N/A    STC-WWCONTROL    The browser has forced an election on network \Device\NetBT_Tcpip_{002F9391-B5AE-46DE-9909-D87BE5FC035C} because a master browser was stopped.
7/12/2008    3:08:45 PM    E1000    Warning    None    27    N/A    STC-WWCONTROL    Intel(R) PRO/1000 MT Network Connection Link has been disconnected.
In this instance the trending stopped at 3:08 and resumed at 7:04. The same events occured each morning at approximately 7:00 AM.  If you looked at the connection status under network properties it was showing the connection had been on for several days.

Installing a new network card in the computer stopped the erratic trending and now everything is back to normal. The problem was hardware or Lookouts interaction with the hardware.

Ryan - Why would this be? In our application Lookout was not using the networking capabilities of the computer. We have either 4 or 5 processes running.