Everything Milesef needs to run the biometric attendance system: fixing the empty-report problem, every common error, full feature usage, and a sorted library of video + blog references.
Why this exists
One place to solve attendance & device problems
eTimeTrackLite is powerful but unintuitive — most "broken" reports trace back to a missing shift, an un-processed log, or a database driver. This guide turns those into 5-minute fixes with step-by-step instructions and verified tutorials, so anyone on the team can resolve it without waiting on support.
10Common issues documented with fixes
9Feature areas with full usage steps
20+Curated video tutorials, sorted
12FAQ entries with solutions
Jump in
📉
The Attendance IssueLogs download but the monthly report is empty — full diagnosis & fix.
Video LibraryEvery tutorial, sorted by setup, fixes & reports.
Tip: Use the filter box in the sidebar to jump straight to a topic. Each error page links the exact video that demonstrates the fix.
Start Here / The Attendance Issue
Logs download, but the report shows no attendance
The exact problem Milesef hit: both devices reported ~1039 logs downloaded, yet the Monthly Status Report came back mostly Absent / blank for the month.
Root cause in one line
Downloading logs ≠ computing attendance
"Logs Downloaded: 1039/1039" only means punches reached the DeviceLogs table. Marking Present/Absent is a separate computation into AttendanceLogs, and it only runs when punches are processed, every employee has an assigned shift, and device User IDs match the software Emp Codes.
Fix in order
1 · Assign a shift to every employee most likely cause
Without a shift the engine has no IN/OUT window, so it can't decide what counts as Present. A shift assigned for a single day produces the classic "P on day 1, blank after" pattern.
Open Masters → Employees, pick the employee, go to the Shift tab, assign a shift (e.g. General 09:00–18:00), Save.
For everyone at once use Masters → Employee Shift or set a Fixed Shift in Master Settings.
Confirm the schedule covers the whole month, not just one date.
Run the Daily Attendance Register / Punch Report for the month first — what you see points straight to the cause.
What you see in Punch Report
What it means
Go to
Punches present for all days
Processing or shift problem
Steps 1 & 2 of the Attendance Issue
No punches at all
Emp Code / device mapping issue
Step 3 of the Attendance Issue
Punches only on day 1
Shift assigned for one day, or device clock / duplicate logs
Step 1 (roll shift forward)
Can't even open the report
Menu disabled or DB driver error
"Menus greyed out" / "ACE.OLEDB" pages
Fastest first move: assign a Fixed Shift to all employees, re-calculate the month, regenerate. That clears the majority of empty-report cases.
Common Issues / Empty report
Logs OK, monthly report blank
The headline issue — fully covered on its own page with ordered fixes and videos.
➡️
Open the full diagnosis & fixShift assignment → re-calculate → Emp Code mapping → generate.
Common Issues / Device connection
Device won't connect / "Unable to connect"
The software can't reach the biometric terminal, so logs never download. Often shows as Error code -2.
CAUSE
Network, comm key, or unregistered device
"Unable to connect device" · Error code -2Fix
Ping the device IP from the server PC; confirm both are on the same subnet and the LAN cable/Wi-Fi is live.
In Device Management → Device Details verify the device IP, port (4370) and Comm Key match what's set on the terminal (Menu → Comm → Ethernet / Security).
Temporarily disable Windows Firewall / antivirus to rule out a blocked port.
If everything matches but it still fails, the device serial may be missing from eSSL's registration database — share the serial number with eSSL support to have it registered.
Legacy units (e.g. X990): repeated failures despite correct settings are usually the un-registered-serial case above.
"Microsoft.ACE.OLEDB.12.0 provider not registered"
The software can't open its Access/Excel database because the OLEDB driver is missing or the bitness (32/64) doesn't match.
CAUSE
Missing Microsoft Access Database Engine
'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machineFix
Install the Microsoft Access Database Engine (AccessDatabaseEngine).
Match the bitness: a 32-bit eTimeTrackLite needs the 32-bit (x86) engine even on 64-bit Windows. Use the /quiet switch if a conflicting Office install blocks it.
Quick answers with links to the matching video where useful.
Downloading only fills DeviceLogs. You must assign a shift to every employee, then Utilities → Re-Calculate Attendance for the date range. See the full page under "The Attendance Issue." Shift video ↗
Set a Fixed Shift in Master Settings, or use Masters → Employee Shift and select all. Fixed-shift video ↗
Check IP/port 4370/Comm Key match, ping the device, disable firewall. If still failing, the serial may be unregistered with eSSL — contact support to register it. Connection video ↗
Install the Microsoft Access Database Engine matching the software bitness (usually 32-bit). Fix video ↗
Install/repair .NET Framework 4.0 and run as Administrator. Video ↗
Their shift was assigned for one date. Re-assign the shift across the whole month and re-calculate.
Manage Attendance → View Log Records → Add Manual Entry with Direction (IN/OUT) and Date/Time, then re-calculate. Video ↗
Add Public Holidays and Leave Entries in Masters so those days mark H / L instead of A, then re-calculate.
Install/repair the Report Viewer runtime + VC++ redistributables and .NET 4.0. Video ↗
Configure Device Management → Schedule Downloader and keep the service running / PC awake.
Utilities → Backup Database to a safe path (ideally off the server PC). Also enable Auto Backup in Master Settings.
Set "Minimum difference between two punches" and/or "Consider only First & Last Punch" in Master Settings, then re-calculate.