Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Version History
Date
Revision
TF Version
Author(s)
Oct 2012
Draft A
1.7.12
T. Sanerkin
Dec 2012
Rev 1.1
1.7.18
T. Sanerkin
Page 2 of 9
Contents
Version History........................................................................................................................................ 2
Contents .................................................................................................................................................. 3
Common start-up problems.................................................................................................................... 4
1.
Overview ......................................................................................................................................... 4
2.
3.
4.
Actions:- .................................................................................................................................. 8
6.
Actions:- .................................................................................................................................. 6
5.
Actions:- .................................................................................................................................. 5
Actions:- .................................................................................................................................. 8
Page 3 of 9
Overview
This guide describes how to troubleshoot common problems that prevent TriggerFish from startingup correctly. Most problems preventing TriggerFish from starting are related to the Hydra Server and
Hydra Proxy services or to the network configuration of the system; TriggerFish must be able to
access a network for any applications to run successfully.
2.
The following error messages are indicative of the Hydra Server not running or being incorrectly
configured.
Start-up error messages from Survey Editor, System Editor and Survey Manager
Page 4 of 9
2.1
Actions:-
Check that the Hydra Server service is running on the server machine and only on the server
machine, with the correct Network, User Name and Domain settings. Check that the firewall is
turned off or configured to allow the TriggerFish applications and Hydra Server process
(HydraServer.exe). Stop and re-start the service and then re-start the TriggerFish applications.
3.
The following errors and messages are indicative of the Hydra Proxy service not running or being
incorrectly configured.
Survey Editor reports connection error, and then starts with Survey not loaded reported in caption
bar.
Page 5 of 9
System Editor first reports connection error and then reports and access rights error.
Survey Manager starts with no data and no survey name in the caption bar
3.1
Actions:-
Check that the Hydra Proxy service service is running on the local machine with the correct Network
and Central Server Location settings (the central server is the machine running Hydra Server service).
Check that the firewall is turned off or configured to allow the TriggerFish applications and Hydra
Proxy process (HydraProxy.exe). Stop and re-start the service and then re-start the TriggerFish
applications.
Page 6 of 9
4.
The following errors are indicative of incorrect network settings, no network, network cable
unplugged, network switch not powered-up.
Survey Manager starts with no data and no survey name in the caption bar
Page 7 of 9
4.1
Actions:-
Check that the network adaptors used for the TriggerFish networks (windows client network &
sensor data network) are enabled and connected in the Windows control panel network connections
dialogue. Check that the firewall is turned off or configured to allow the Hydra Server, Hydra Proxy
and TriggerFish application processes. For remote machines (e.g. bridge) check that the server
machine is accessible (use ping command). Check that the networks defined in the Hydra Server and
Hydra Proxy configurations are correct. NOTE: - IP addresses should be selected from the browser
buttons in dialogue boxes of the Hydra Server and Hydra Proxy configuration, if the required
network adaptor cannot be seen in the browser window; it implies that there is some problem with
network access.
5.
The following errors are indicative of access rights problems with the Hydra system
5.1
Actions:-
If these errors are seen on the machine running the Hydra Server, and the correct Administrative
user is logged on to the machine, the following steps should be taken:Re-enter (clear the box and re-type the values) and apply the Username and Domain names. To
obtain the correct Username and Domain name run the utility TFishUser from the TriggerFish
Tools menu and cut and paste the values in the Hydra Server dialogue.
Page 8 of 9
Then stop Hydra Server and Hydra Proxy and un-tick Start process automatically. Restart the PC,
and then Hydra Server and Hydra Proxy.
6.
For Windecoder users, stop and start the Windecoder process (control panel) and ensure that
TriggerFish services and the Gravel Controller servlet are running. Note that serial com ports can
become blocked if another process (e.g. HyperTerminal) is using them. Sometimes a PC shutdown
and restart is required to unblock serial ports.
For GTU (Gravel Decoder Unit) user, check the network connection to the decoder cards using the
ping command from a DOS (CMD) window and check that TriggerFish Services and the Gravel
Controller servlet is running.
NB: - To monitor serial communications in the System Editor window, the Gravel Controller servlet
must be running (check for the green status panel, bottom right corner of the System Edit viewer
window) and also the show Card Debug and Show Raw Card Debug flags must be enabled.
Page 9 of 9