Network traffic crashing built application; services to disable?

[Matthew_Williams]

We have a deployed application built with 7.0/7.1 LV.

One computer, out of 100 or so, has frequent (1-2/day) crashes of the application.

The machine has been rebuilt from the OS (XP) up.  Our hypothesis is that something
on the network was causing the crash, so we inserted a NAT'ing router in front, which helped
but caused other problems.  The network has lots of non-LV traffic, and is really beyond our
control.

After removing the router, the crashes resumed.  We added the following tokens to our
application.ini file:

server.tcp.enabled=false
server.ole.enabled=false
Webserver.enabled=false

which helped significantly with the crashes (none for many weeks).  Now the crashes
are starting again.  Any suggestions for other services that can be disabled with .ini
settings, or some other way?  We have captured traffic but have been unable to identify
the specific culprit.

Any suggestions for other things to look for?

Thanks.

Matt

[Hillary_C_E]

Hi Matt,

What is your application doing? Is it interfacing with the network? If you aren't interfacing the network you might want to consider setting your LabVIEW so no one else has access. You can do this by going to Tools»Options»VI Server: Machine Access and deny or allow access accordingly.

[Matthew_Williams]

Hi Hillary.  Thanks for the response.  We are making .vi server calls out from the PC to FieldPoint controllers running RT,
but there are no incoming (to the PC) .vi server calls.  I expected that setting server.tcp.enabled=false would disable the
vi server; is that not correct?  Can I accomplish your suggestion with:

server.tcp.access=""
server.vi.callsEnabled=false
server.vi.propertiesEnabled=false

in the .ini file?  This is a regulated application, so re-compiling is a major (weeks of work) undertaking, but we can get
away with .ini file changes.

Are there any other services I can disable through the .ini file?  I'll happily turn everything off, then turn on just enough to
make our app work again 😉

Thanks for your help.

Matt

edit:  my original post wasn't clear; this is one workstation in one network environment with this problem.  None of the other,
properly running, workstations are on the same network.


Message Edited by Matthew Williams on 04-22-2008 08:30 PM

[Hillary_C_E]

Hi Matt,

Can you clarify what you mean by crashing? Are you getting an error message? Have you checked the memory usage on your computer when you are seeing this crash? Why do you think it is the network and not settings on the computer? Have you tried turning off your firewall or anti-virus? I'd see if you can isolate what is different for this computer versus the other computers.

[Matthew_Williams]

Hi Hillary.  When our application crashes, it just disappears.  None of our shutdown code is executed.  There are sometimes messages
in the system error logs about .NET runtime 2.0 errors, or our application performing an illegal operation.  We have re-installed all of
our code, including the run-time engine, and we have also completely replaced the computer, same results.  They manually update
the OS, applying all critical or security updates.

When we replaced the computer, we left the old one on the network running our code but not doing any network activity; it crashed just as before.

Memory usage has been consistent with other installations, which frequently run for weeks before being manually shut down for backups, etc.

We have turned off everything we can on the PC, including firewall and AV for testing, nothing except the .ini tokens to shut down services or
the NATing router has had any positive effect.

We have a documented setup process for the computers, so we have a high confidence that this computer is setup just like all the others, but that
is not a guarantee once it is in the field.  They have disabled auto-updates, remote access, etc.

SR 7176298; I think I will have to call and ask that it be reopened.

Any suggestions are welcome.

Thanks.

Matt