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

Section 14. Troubleshooting Guide
This section is provided as an aid to solving some of the common problems that might be
encountered using the LoggerNet software. This list is not comprehensive but should
provide some insight and ability to correct simple errors without a call to Campbell
Scientific technical support.
This section also includes descriptions of some of the tools such as Terminal Emulator and
Data Table Monitor that can be useful in troubleshooting LoggerNet problems.
14.1 What’s Changed?
When things stop working the most important thing to ask yourself is: “What’s
changed?” A new computer, new software (especially non-Campbell Scientific
software), different communication peripheral such as a new modem, new
datalogger program, etc., can all interrupt communications. If you can’t
deduce the nature of the problem, go back to the original configuration. If a
phone telecommunications or socket link starts to fail for no apparent reason,
ask someone else to try it from a different computer. Try swapping out
components – one at a time – from a link in the network that you know works
or from spare equipment that you are certain is functioning correctly.
Sometimes the smallest thing – a cable or a new PC utility program – can cause
widespread havoc. If using TCP/IP or cellular telephone communications,
check with the network administrator to see if anything changed that coincided
with the loss of communications.
14.2 LoggerNet Server Problems
The following sections identify problems that have been observed with
operation of the server. If you are experiencing problems with the server look
through the following conditions to see if any of these match the problem you
are having. If you find the problem listed, try the suggested remedies. If your
problem is not listed or the remedies don’t fix the problem, contact Campbell
Scientific for technical assistance.
14.2.1 Starting LoggerNet and Connecting to the Server
Problem: Cannot start LoggerNet on a laptop computer. (Error message
“LoggerNet was unable to start the communications server.” Socket Failure
creation 10047.”)
Remedy 1: If the computer is sometimes used on a computer
network and no network card is installed, TCP-IP services may not be
starting. Try starting the computer with the network adapter card
installed.
Remedy 2: If remedy 1 doesn’t work, you will need to configure a
non-existent dial-up service with a fixed IP address. There is a
description of this procedure in Section 1.2, Configuration of TCP/IP
Service.
14-1