Troubleshooting
Could not start the UT-LabMan Server service on \\xxx. Error 0005: Access is denied.
Make sure that you are logged in to the NT server with administrative privileges or have the privilege for handling services and registry entries when you are trying to start UT-LabMan Server service.
Could not start the UT-LabManager service on \\xxx. Error 0002: The system cannot find the file specified.
Make sure the UT-LABMAN.EXE file is located in path that was specified in the destination path during the installation.
The station does not show on the LabMan Console after adding a new station in the station.cfg file.
- Make sure that the index number of the new station is unique.
- Make sure that the x and y coordinates of the new station are not identical to any station.
- Make sure you have stopped and restarted the server, or have restarted the computer.
This Waiting List machine is not defined by UT-LabMan.
Check to see if the WaitList machine's IP address is included in STATION.CFG. If not, add this machine's IP address into the list, then stop UT-LabMan service and start UT-LabMan service again.
UT-LabMan thinks the Max # of waiting users is 0.
Check to see if you have defined any workstation groups and that:
- you have checked the "Provides a Waiting List" option,
- you have checked the "Display group on UT-LabMan Wait List client." option.
Client Failure; Showing no connection on the clients' display.
- If this happens to only one workstation, make sure that the Ethernet cable is connected to the workstation properly. Check its value for name or IP address for UT-LabMan Server.
- If this happens to all workstations, make sure the UT-LabMan Server is still running and make sure that the Ethernet cable is connected properly to the UT-LabMan Server machine.
The clients are showing intermittent no connection on the clients' display.
- If this is restricted to the Mac OS X clients, update to version 4.1.2 or later.
- Use the UT-LabMan Server Configuration Tool to increase the Total Number of Client-Server Threads (see Figure 4.5).
- If this does not help, see if there is excess network traffic. You might need to reset your network hub, switch, or router.
