eTimeTrackLite Not Syncing Attendance? Complete Fix Guide

Device Communication Errors

Device communication errors are the most common cause of sync failures.

Common Error Messages:

• "Device Not Responding"
• "Cannot Connect to Device"
• "Communication Timeout"
• "Device Offline"

Troubleshooting Steps:

1. Check Device Power:
   • Ensure device is turned on
   • Check power indicator light
   • Try power cycle: Off 30 seconds, then On
2. Check Network Connection:
   • Verify network cable connected to device
   • Check cable for physical damage
   • Try different network port
   • Test with different cable
3. Verify Device IP:
   • Press Mode button on device
   • Check IP address on LCD screen
   • Should be in same subnet as server
   • Example: Server 192.168.1.100, Device 192.168.1.101
4. Test Network Connectivity:
   • Open Command Prompt on server computer
   • Type: ping [device-ip-address]
   • Example: ping 192.168.1.101
   • Should show replies (not "Request timed out")
5. Restart eTimeTrackLite Service:
   • Go to Settings → Services
   • Stop eTimeTrackLite Service
   • Wait 10 seconds
   • Start Service again

SQL Connection Problems

Error: "Cannot Connect to SQL Server"

Solutions:

1. Verify SQL Server is Running:
   • Open SQL Server Management Studio
   • Check Connection Status
   • If not running, restart service
2. Check Database Connection Settings:
   • Tools → Settings → Database
   • Verify Server Name
   • Verify Database Name (usually "eTimeTrackLite")
   • Verify Username and Password
3. Test Connection:
   • Click "Test Connection" button
   • Should show "Connection Successful"
   • If fails, check credentials
4. SQL Server Authentication:
   • Ensure SQL Server uses "Mixed Mode" authentication
   • Check SQL user account has required permissions
   • Verify database ownership
5. Check Disk Space:
   • SQL Server needs free disk space
   • If C: drive full, sync will fail
   • Ensure minimum 1 GB free space
   • Archive old records to free space

IP Mismatch Issues

Problem: Device IP doesn't match software configuration

Scenarios:

• Device IP changed (DHCP assigned different IP)
• Network router restarted causing IP reassignment
• Device was moved to different network
• Software has wrong IP configured

Solutions:

1. Assign Static IP to Device:
   • Press Mode on device, note current IP
   • Go to device settings
   • Change from DHCP to Static IP
   • Assign IP like 192.168.1.101 (match your network)
   • Save settings and restart device
2. Update Software Configuration:
   • Open eTimeTrackLite software
   • Go to Tools → Device Management
   • Update device IP address
   • Click "Test Connection" to verify
3. Verify Network Subnet:
   • Server and Device must be on same subnet
   • Example: Server 192.168.1.x and Device 192.168.1.x
   • If different subnets, configure router to allow communication

Firewall Troubleshooting

Windows Firewall Blocking eTimeTrackLite

1. Allow Application Through Firewall:
   • Windows Security → Firewall → Allow app through firewall
   • Click "Change settings"
   • Find eTimeTrackLite in list
   • Check box for "Private" and "Public"
   • Click OK
2. Allow Port 5005:
   • Advanced Firewall Settings
   • Inbound Rules → New Rule
   • Port → TCP → Port 5005
   • Allow connection → Finish
3. Temporarily Disable Firewall (For Testing Only):
   • Windows Security → Firewall
   • Turn off Windows Defender Firewall
   • Test if sync works
   • If works, re-enable firewall and add exceptions

Third-Party Antivirus/Firewall:

• Norton, McAfee, Avast may block eTimeTrackLite
• Add eTimeTrackLite.exe to whitelist
• Allow port 5005 in antivirus settings
• Temporarily disable to test

Database Repair Steps

If Database is Corrupted:

1. Create Backup First:
   • Tools → Backup & Restore → Backup Database
   • Save backup to safe location
2. Repair Database:
   • Stop eTimeTrackLite service
   • Open SQL Server Management Studio
   • Right-click database → Integrity Check
   • Run repair if issues found
3. Rebuild Indexes:
   • Tasks → Maintain Indexes → Rebuild
   • Wait for process to complete
4. Restart Service:
   • Start eTimeTrackLite service
   • Try syncing again

Real-World Troubleshooting Examples

Case Study 1: Device Offline After Power Cut

Problem: Power failure caused device to go offline. After power restored, still not syncing.

Solution:

• Device IP changed due to DHCP
• Checked device IP: 192.168.1.105 (was 101)
• Updated software to new IP
• Sync resumed successfully
• Now using static IP to prevent future changes

Case Study 2: Attendance Showing But Not Syncing to Payroll

Problem: Device showing attendance, but not appearing in payroll module.

Solution:

• SQL Server disk space full (C: drive 100%)
• Archived old records to free 5 GB space
• Restarted SQL Server
• Sync worked after cleanup

Case Study 3: Random Sync Timeouts

Problem: Sync works sometimes, fails other times.

Solution:

• Network switch port flaky
• Changed network cable
• Changed switch port
• Assigned static IP for stability
• No more timeout issues

When to Contact Support

If after trying all above solutions sync still fails, contact Always Tech Solution:

• Email: support@alwaystechsolution.com
• Phone: +91-8925020661
• WhatsApp: https://wa.me/918925020661
• We provide remote support via TeamViewer

Conclusion

Most eTimeTrackLite sync issues can be resolved using these troubleshooting steps. Regular maintenance, static IP configuration, and proper backup ensure reliable attendance tracking for your business.