Campbell Scientific LoggerNet Datalogger Support Software - Manual (Page 40)

Section 2. Installation, Operation and Backup Procedures
If computer system power is lost while the LoggerNet server is writing data to
the active files, the files can become corrupted, making the files inaccessible to
the server.
While loss of power won’t always cause a file problem, having files backed up
as described above will allow you to recover if a problem occurs. If a file does
get corrupted, all of the server’s working files need to be restored from backup
to maintain the synchronization in the server state.
2.3.4 Program Crashes
If the communication server crashes, there is a possibility that files can be
corrupted (note, however, that corruption is much less likely with a program
crash than during a power loss, since the computer operating system remains in
control and can close the files left open by the failed program). If, after a
program crash, the server does not run properly, you may need to restore the
data from backup.
If you have problems restarting the LoggerNet server after a program crash or
it crashes as soon as it starts, make sure that the LoggerNet server has not left a
process running. You can check this by going to the Windows Task Manager
and selecting the Process tab. In the list of processes look for the Toolbar or
one of the client applications. If one of these processes exists but the Toolbar
is not running, select this process and click “End Process”; you will be asked to
confirm the end process.
2.4 Installing/Running LoggerNet as a Service
If you have LoggerNet Admin, you can install and run LoggerNet as a service.
The advantage of running a software application as a service is that the
software will run even when no user is logged in to the computer system. Some
users may desire to run LoggerNet as a service, so that in the event of a loss of
computer system power LoggerNet will resume data collection and scheduled
task activities when power is restored to the computer and it “boots up”.
LoggerNet Admin includes LoggerNet Service Manager, which is used to
install and control LoggerNet when running as a service. The LoggerNet
Service Manager is opened from the Windows Start menu (Start | Programs |
Campbell Scientific | LoggerNet | LoggerNet Service Manager). The
LoggerNet Service Status box at the top of the LoggerNet Service Manager
window indicates whether or not LoggerNet is installed as a service and
whether or not the service is running. When you first open the LoggerNet
Service Manager, if LoggerNet has not been installed as a service you will
need to select the Install button. Note that LoggerNet must be closed to install
it as a service. If it is opened, you will be prompted to close it before you can
continue.
Once LoggerNet is installed as a service, you can use LoggerNet Service
Manager to Start the service (or Stop it if it is enabled). The LoggerNet service
can be uninstalled by selecting the Uninstall button.
One caveat to running LoggerNet as a service is if LoggerNet uses system
resources (such as a COM port that is continuously open waiting for datalogger
call-back attempts) these resources will be unavailable to other applications
until the service is stopped.
2-8