No data in hypertrends: logging buffer full

[tommy_scharmann]

I have set up hypertrends to log pots and waveform objects and yes I have
logged to historical database. I am also getting "logging buffer full" alarms.
I am running Lookout 4.0.1 Build 51 on Win NT 4.00.1381 SR 5. Has anyone
seen this and is there a simple fix or am I missing the big picture?

Tommy

[Trey Hamilton]

Thomas,
There is a Knowledge Base entry that addresses this issue. Here is a link
to the KB:http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/862567530005f09e862567c700746a65?OpenDocument
(or you can search in the KB on logging and buffer).

Lookout logs first to a buffer and this buffer dumps the data to the historical
database. In Lookout 4.0.1b51, it is easier (than the 3.8 builds) to fill
this logging buffer. If the instructions in the KB do not help, you might
double check the deviation on the pots. Make sure you are only logging as
is necessary. For example, if you are logging temperature, you probably
do not need to log every 0.001 change in temperature.


"Thomas Scharmann" wrote:
>>I have set up hypertrends t
o log pots and waveform objects and yes I have>logged
to historical database. I am also getting "logging buffer full" alarms.>I
am running Lookout 4.0.1 Build 51 on Win NT 4.00.1381 SR 5. Has anyone>seen
this and is there a simple fix or am I missing the big picture?>>Tommy

[tommy_scharmann]

The problem turned out to be this:
If I installed Lookout on my 😧 drive (hard drive partition in Windows NT
4.0 Build 1381 Service Pack 5) I could not see hypertrend data not matter
what I did. If I unistalled Lookout from the D:drive partition and reinstalled
it on th C: drive my hypertrends worked. The only thing I can figur is, in
my case, it seems Lookout needs to be on the same partition has the OS. Does
anyone have any insight to this problem?
Thank-you and regards,
Tommy Scharmann

[Peter Marcotte]

Here's some speculation:

Was the installation on the 😧 drive the same directory where you had previous
versions of Lookout installed? It's possible that some old INI settings were
pointing to the wrong machine, so that Lookout couldn't connect to the database
server, which would result in the error message you saw. Uninstalling and
installing to the same directory wouldn't clean the INI file, so every installation
in that directory would have the same result. When you installed to the C:
drive, the Lookout.INI file wasn't already in that directory, so a new default
one was created with the correct settings.

If this is the case, you should be able to install to the 😧 drive by uninstalling
Lookout, deleting the D:\Lookout4 directory, or wherever y
ou put it, then
trying the install again.

[tommy_scharmann]

Thanks for your reply. I did delete the Lookout directory after uninstalling
Lookout. This still did not work.

You have provided me with some insight into the lookout.ini file. Thank-you.

Regards,
Tommy Scharmann

[JPhillips]

Thank God I found this post. I just got two new computers with 2 separate hard drives(C: and D:).
I installed Lookout on the 😧 drive and have been having all kind of trouble with my trends.

The source of the problem seemed to be that even though I was telling Lookout to copy my database to the D:, another database was eventually created on the C:. I called NI and they suggested I tell Lookout to copy my database to the C: and so I did that and then a database was automatically created on the D:.

I'm not sure what's happening here but I think this might be why I am not getting any trends (although I was able to get a trend one time when I went into edit mode, brought up the trend properties, and then hit ok - but I wasn't going
to go thru 200 trends doing that). Plus, some of my runtime computers will lose their connection to the master computer.

Tommorrow I am going to install Lookout to the C: and see if the problem goes away.

Have you noticed another database on your C: even though you have Lookout installed on your D:?

Hope this sheds some light on your problem.

Jason Phillips