A Client connectivity problem will manifest as a “not
all data transmitted, logging request failed” message on the
Client.
If this occurs, check the events log. The events log is the primary
troubleshooting tool for connectivity issues. The events log lists
all the back end-specific
and Agentry-specific
error messages.
Login Request Failed
This error message
results when the client device is not communicating with the
Agentry
Server. To
troubleshoot the above error message:
- Make sure that the Agentry
Server is
running.
- If the Server is not started, you will see the logging in message
for a minute and eventually get this error.
- Check the events log to make sure that the Agentry
Server has
not lost its the back end connection.
Check for the following network issues:
- Time-outs
and TCP/IP issues: Troubleshoot network
- Wireless network issues: Troubleshoot wide area network
- Firewalls: Ensure that configured ports are open for the IP
addresses of the Clients
Incorrect User ID or Password
This
error is seen on the mobile device when an incorrect user ID or
password is used. View the error in the events.log file
located in the install directory of the Agentry
Server.
To
fix the problem, have the technician use the correct password.
Failure to Connect to the Server (3)
This error is received when the Agentry
Client fails
to connect to the Agentry
Server.
Because a connection to the server was not made, there will not
be an entry in the events.log file.
A common
cause of this error is that a Client’s network connection is not
established or is severed.
To fix the problem, re-establish
the computer’s network connection.
Communication Error (14)
This error is
received when the
Agentry
Client cannot
communicate with the
Agentry
Server. Because
there is a problem communicating with the Server, there is not an
entry in the
events.log file. Common causes of
this error are:
- The Agentry
Server service
is not started
- The network connection is not working properly
- The device has Production logic on it and is now trying to connect
to the Agentry Development Server.
This is shown in the events.log file.
To
fix the problem:
- Start the Agentry
Server service.
- Disconnect, then re-establish a network connection.