Allway Sync Service Configuration

First of all, note that the options under Job -> Properties -> Automatic Synchronization don't setup synchronizer service. Currently the service is configured via the command line only.

Step 1. Make sure that the synchronizer service is installed and running. You should have synchronizer version 11.7.0 or higher and should turn the "Install service for synchronizer" option on during installation or update. To check whether the service is running, perform the following actions:

  • Use Start button -> Run or Win+R shortcut.
  • Type "services.msc" and hit Enter.
  • Find the "Botkind Service" in the list and make sure its status is "Started".

Step 2. Run the command prompt as an Administrator. For this:

  • Use Start button -> All Programs -> Accessories.
  • Right-click the "Command Prompt" and choose "Run as administrator".
  • Click "Yes" in the User Account Control prompt window.

Step 3. In the command prompt navigate to the Bin folder located inside installation directory of Allway Sync (usually "C:\Program Files\Allway Sync").

Step 4. Firstly you should add a user account to run synchronizer on its behalf. Use the following command for this:

syncservice.exe add_user -l "username" -p "password"

You should add a real user account that exists in your system.

Step 5. Now you can add new events. The service provides three types of events:

  • A drive event is triggered when a removable drive is connected. You should specify at least one of drive characteristics (size, serial number or label) to add the event. This event type accepts the following arguments:

    syncservice.exe drive_event
    <-l user account>
    <-p password>
    <-j job name>
    <-label drive label>
    <-size total drive size in bytes>
    <-id drive serial number>
  • A timer event is triggered on timer. You should specify the period for this event (minutes, hours, days, etc are available). This event type accepts the following arguments:

    syncservice.exe timer_event
    <-l user account>
    <-p password>
    <-j job name>
    <-period period in one of the next formats>
      [Nm - N minutes]
      [Nh - N hours]
      [Nd - N days]
      [daily - every day]
      [weekly <1..7>- every specified day of week]
      [monthly <1..31 | last> - every specified day of month]
    <-d begin date (dd.mm.yyyy)>
    <-t begin time (hh:mm)>
  • A file event is triggered when the modifications are detected in a specified directory. You should specify a directory path and the period to add this event. This event type accepts the following arguments:

    syncservice.exe file_event
    <-l user account>
    <-p password>
    <-j job name>
    <-path absolute path to monitoring directory>
    <-period period in one of the next formats>
      [Nm - N minutes]
      [Nh - N hours]
      [Nd - N days]
      [daily - every day]
      [weekly <1..7>- every specified day of week]
      [monthly <1..31 | last> - every specified day of month]
    <-d begin date (dd.mm.yyyy)>
    <-t begin time (hh:mm)>
Please note the following rules:
  • A username, password and job name are required arguments for each command.
  • It is recommended to double-quote all arguments (e.g. -l "justy")
  • The user accounts may have different configuration of the sync jobs. Make sure that the job you specify does exist under that user account.
  • A file event does work for local file systems only. It won't work with the network directories, removable devices and remote servers (FTP, WebDAV, cloud storages, etc).

Here is an example of command for adding of a file event:

syncservice.exe file_event -l "username" -p "password" -j "Test job" -path "C:\Users\justy\Desktop\source" -period "10m"

Step 6. To check whether your event has been added successfully you can use the "enum_event" command:

syncservice.exe enum_event -l "username" -p "password" -id event_ID

The event ID is an incrementing number of added events. You can also list all event ids using the "enum_events_id" command.

You can learn more about configuration and usage of the service in "How to... Use sync service" help topic (menu item Help -> Help Topics in synchronizer).

Troubleshooting tips

1. All synchronizer service activity can be viewed via the system Event Viewer. Follow the steps below to open it:

  • In the Control Panel, open "Administrative Tools", then "Event Viewer".
  • On the left panel choose "Windows Logs", then "Application".
  • On the "Actions" panel (far right) choose "Filter Current Log".
  • In the opened window set the value of "Event source" field to "BotkindSyncService" and click OK.
  • Now you'll see all actions performed by synchronizer service.

Also, on the left panel you can switch to "Security" section instead of "Application" to view all log on/logo ff actions performed by the service.

2. Enable saving log into the file to view all actions performed by synchronizer when it is ran by the service. To do this use a menu item View -> Options, switch to "Event log" section, turn on "Save log in file" option and set "Log conciseness" to "Verbose". The log file is located in the following directory:

C:\Users\[USERNAME]\AppData\Roaming\Sync App Settings\_SYNCAPP\

3. The service does run the jobs on behalf of the user account that you specify using "-l" and "-p" arguments for the commands. So make sure that the job you specify does exist under that user account.

4. The user account that you run synchronization on behalf of should have "Log on as a batch job" privileges. To grant these privileges to the user using the Local Security Policy, follow these steps:

  • In the Control Panel, open "Administrative Tools", then "Local Security Policy".
  • Beneath "Security Settings", open "Local Policies" and highlight "User Rights Assignment".
  • Locate "Log on as a batch job". Open the properties and add your user account to the list.
  • When finished, save your changes and close the Local Security Settings window.

5. If you get the following error message:

The function CreateProcessAsUser has done with error (522h): A required privilege is not held by the client.
look at this Microsoft forum thread for solution.