Lookout 6.2 Beta

[erblock]

It appears that a Lookout 6.1 client process cannot display Hypertrend trace data generated by Lookout 6.2 Beta server process.

Existing server 6.1 database was off-line copied to new Lookout 6.2 directory on same server.  Two issues notices so far:

1.  On  Lookout 6.2 Server machine, sqlservr.exe hogs ~50% CPU for over an hour now.....  Restart....same.  This did not happen with Lookout 6.1 &  DSC 8.5 configuration.

2.  Lookout 6.1 client hypertrends are not updating with server's Lookout 6.2 generated data.  History from database is fine.  Just in case... turned firewall OFF on both client and server....no change.

Ed

[erblock]

Removed all NI software.  Reinstalled 6.2 Beta, archived 6.1 data to 6.2 with MAX.

All OK.  I did NOT copy the SQL files.

Hypertrend traces on 6.1 client now contiguous and sqlservr.exe is behaving fine....

Not sure if the original 6.2 install on top of 6.1 (w/ 8.5 DSC) went bad?  May have just been directory change to Lookout 6.2 that messed everything up...

One thing I did notice after the uninstal of all NI software and subsequent reinstall of Lookout 6.2, the Lookout 6.1 service is still listed in services.  This should have gone away, right?

Ed

[Mike@DTSI]

Had a similar issue with 6.0.  SQL server could not create a database, cause high CPU usage and Lookout trends took a long time to load.

Havent installed the 6.2 yet, but those expressions look to add a nice new feature 🙂

Mike

[Ryan.S]

Thank you for testing Lookout.

Both case 1 and 2 should not happen.

Next time you see the 50% cpu usage of sqlservr.exe, close Lookout, and stop Citadel service, then check if it is still 50%. If it goes down, the problem is related to Citadel or Lookout, otherwise the problem is something else. You can also check if there are any abnormal event about SQL Server in Event Viewer.

We did some tests with Lookout 6.2 install upon previous version, but didn't see the similar problem.  But from your description about the second issue, the Citadel may have something wrong after the install of 6.2.  Before you install 6.2, lookout 6.1 and dsc 8.5 already installed on the same computer?

By the way, if it is a dual core cpu, 50% means full usage of one core. It is critical.

The Lookout 6.1 service problem is a bug. We are working on it.

[Mike@DTSI]

Feature Request/Improvement:  On the TextEntry Object add a small icon to bring up the Virtual Keyboard.  Touchscreens dont have "right click", and using the left click requirement is "confusing" for some operators. 

Vector graphics would still be welcome 😉

Mike

[Mike@DTSI]

Cant edit post, found the feature request thread 🙂  disregard this one.

[Ryan.S]

Mike, Thank you for the advice. Actually we determined the features of Lookout 6.2 before we started that new feature thread, so in Lookout 6.2, you may not see the features mentioned in that thread, but we will surely consider them in future development or updates.

[erblock]

Hi Ryan,

What are you doing up at this time???  😉

Are you visiting Austin?

Cheers,

Ed

[Ryan.S]

working 🙂
far away from austin...

[erblock]

It seems the bug reports don't get read too often so I will first list the problem here....

Citadel crashes when server system is taken off net.  In my case, we had some switch problems twice in the last few weeks and each time a network switch was replaced, Nicitdl5.exe crashed and locked up Lookout.  At the bottom,  is one of the crash logs.

This is repeatable on two separate Win2k8 32-bit Hyper-V virtual machines, each time network is lost.  Note that this fault has only been seen with a client accessing data on the server at time of network interruption.  I cannot confirm yet that the crash also happens if there are no client connections.  Server process consists of lots of serial ASCII objects.

Please advise....

 --------------------------

Problem signature from one machine:

Problem signature:
  Problem Event Name: APPCRASH
  Application Name: nicitdl5.exe
  Application Version: 5.6.0.49153
  Application Timestamp: 485bba50
  Fault Module Name: nicitdl5.exe
  Fault Module Version: 5.6.0.49153
  Fault Module Timestamp: 485bba50
  Exception Code: c0000005
  Exception Offset: 000ac40d
  OS Version: 6.0.6001.2.1.0.272.7
  Locale ID: 1033
  Additional Information 1: 1b41
  Additional Information 2: a170e74464a133453b2bd7d7631e8573
  Additional Information 3: 15e8
  Additional Information 4: 6308a5a7bbe3a7fb8471e8398e132d04

 --------------------------------

Event log from another machine:

Log Name:      Application
Source:        Application Error
Date:          10/6/2008 8:42:14 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xxx.mit.edu
Description:
Faulting application nicitdl5.exe, version 5.6.0.49153, time stamp 0x485bba50, faulting module nicitdl5.exe, version 5.6.0.49153, time stamp 0x485bba50, exception code 0xc0000005, fault offset 0x000ac40d, process id 0x490, application start time 0x01c91cd60b20d7c1.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-10-07T00:42:14.000Z" />
    <EventRecordID>6695</EventRecordID>
    <Channel>Application</Channel>
    <Computer>xxx.mit.edu</Computer>
    <Security />
  </System>
  <EventData>
    <Data>nicitdl5.exe</Data>
    <Data>5.6.0.49153</Data>
    <Data>485bba50</Data>
    <Data>nicitdl5.exe</Data>
    <Data>5.6.0.49153</Data>
    <Data>485bba50</Data>
    <Data>c0000005</Data>
    <Data>000ac40d</Data>
    <Data>490</Data>
    <Data>01c91cd60b20d7c1</Data>
  </EventData>
</Event>