Preface

There are some common issues that cause Clockings to stop coming through to your software, these issues are IT Related and we are happy to help with a support ticket if required.

You should also note FRD Can't be running and connecting to the clock in multiple locations. Once FRD Connects to a clock and gets the clockings it will remove them from the clock, if FRD is installed in two locations some clockings will be on one PC and other clockings will be on another PC which makes it look like clockings are missing or not coming through.

If the Data is stored on a server and clockings are usually on the server, it's best to check the Server when doing the steps detailed in this article.

Below are some ways to fix this issue but if you are uncomfortable doing these steps just open a ticket with support.

Figuring out the cause

Firstly, press the Windows Start button in the bottom left and search FRD.

You should see 'FRD Configuration' pop up, open up this application.

Above is a screenshot of the FRD Configuration Application.

Take note of the IP Address and the CSV File Path.

Checking the clock is online

A common reason is that the clock has changed IP or isn't responding.

You can confirm the clocks connectivity by opening up CMD Prompt and typing 'Ping {DeviceIP}' in this case it would be 'Ping 192.168.0.210'

In the picture below you will see the device is responding:

If the device does not respond, the device has likely been unplugged, the ethernet cable isn't connected to your router or the device has changed IP.

Checking the service that connects to the clock is running

Another common issue is that the 'FRD Service' is not running.

You can check this by clicking the Windows Icon (Start Menu) in the bottom left and typing Services and launching Services.

Pictured below we can see FRD Windows Service is running, if this is stopped please start the service.

Reviewing FRD Logs

FRD Logs can include some useful information about what is happening.

They are typically found in the following path: C:\Program Files\FRD comms\FRD Configuration\ExecutionLog

Each day a new log file will be generated (if the service is running) and you should be able to open these and read what's going on, they are not that verbose so finding relevant logs is quite easy.

One thing to look out for in these logs are looking for the word 'Denied' if you see that FRD is trying to write files and it's getting Denied it probably doesn't have Write permission on the folder that's set in FRD Configuration (under the CSV File Path Parameter) you will need to give permission to the service to write in this directory. The service typically runs under the 'Local Service' user.