Troubleshooting TimeStation Issues
On machines where they would typically only run TimeStation, please install TimeClock as well. The current version requires both TimeClock & TimeStation. If you do not want TimeClock on a particular computer, simply drag the shortcut into the recycle bin. Even with the shortcut available, the employee cannot access the admin piece without proper permissions.
Make sure your Windows operating system is up-to-date
When TimeStation is physically installed on a client workstation, it uses a local installation of the Firebird database engine as well as the Firebird database engine installed on the server/computer where the database (hrware.gdb) resides. If Firebird is not installed on the client or is not running on the client, TimeStation will [not] open.
Web TimeStation on the other hand, utilizes Microsoft IIS Server/Microsoft .NET Services for communication between it and the Gradience database. This is because it is essentially a web site that runs on your organizations intranet. We recommend running a Windows Update on the workstation(s) in question first.
Power Saving Mode
If you leave TimeStation running 24/7 = On the PC in question: Set the Control Panel > Power Options > Wireless Adapter Settings > Power Saving Mode to Maximum Performance. Also, Power Options > Hard disk to 0 Minutes or Never..
Locate your database file
If the issue remains; determine the name of the computer that contains your HRWARE.GDB database. You can determine [which] computer houses the database by opening a file named HRWARE.INI which is found on each computer that uses the software - the .INI file tells the software where to go to find the database. If you see "localhost" on the server= line, that is the main computer that houses the database. Note the name as you will need it.
•On XP or Windows server 2003 click Start > Run and enter hrware.ini and click OK to display the file contents.
•On Win 7 or Windows server 2008, go to C:\programdata\gradience to find it and open it. …Note: on Win 7 the programdata folder may be hidden.
At the top of the hrware.ini file, you will see three lines as shown below…
PATH=C:\Program Files\Gradience\Data\Hrware.gdb (Note: your path may differ.)
SERVER=Localhost (Note: You may see an IP Address or server name/computer name instead.)
Determine if you have a network problem
Once you determine the computer name or IP, you'll need to open a command prompt at the computer in question and ping the computer name/IP address. At the command line type PING and then the address or computer name. If the reply values are higher than 85-100+ there is a network issue between the workstations and the main computer/server. If the ping times are below 80ms; see the update section below for updating Gradience TimeClock version 11.
Secondly, you'll need to run a Trace Route (tracert). You can perform a simple trace route to yahoo.com for example. The lesser the hops the better the connection. These hops can consist of firewalls and routers.
Update your TimeClock software to the latest release
Make sure everyone is out-of-the-software and does not open the software until all updates are completed. Click here for update instructions.
Open the Database Monitor to make sure that all workstations running TimeClock are running the same full, multi-digit version number as the server
1. From the desktop click Start >
2. Click Connections (notice that there is a mix of release 11.0.1403 and 11.0.1306 connecting to the database. All workstations including the server must have the same release installed as the example below can lead to database corruption.)
Perform Database Maintenance
After updating, run DBMaintenance at the server/main computer that houses the database (make sure everyone is out-of-the-software until DBMaintenance is completed). Click here for DBMaintenance instructions.
Running the Database Maintenance Utility
Do this from the desktop of the computer/server where the database resides.
1. Have all users at client workstations, close Gradience (not minimize).
2. Click Start>
3. Click the Start button that appears on the Database Maintenance popup.
4. Click File > Exit when done. Ignore any Runtime error you may get.
Perform a Clean Installation
If after trying the options listed above; you still encounter issues, it is possible you may have a corrupted install. Please see the following instructions for performing a clean installation.