Search the Community

Showing results for tags 'bugs'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Resilio Sync
    • Sync General Discussion
    • Sync Troubleshooting
    • Sync for NAS (Network Attached Storage)
    • Sync Stories
    • Developers
    • Feature Requests

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 4 results

  1. Applies to: BTSync v.2.3.3 (296) Windows 7, 8/8.1, Windows 10 -- Home and Professional. BTSync prompts to install as a service -- but doesn't follow Windows service account conventions as other programs do, (IIS, MySQL, SQL Server, etc). Issues: Software Defect: Some installations, (like BitTorrent Sync), will not install the Windows Service -- unless a regular user account is specified. Expected Behavior: Should automatically provide the correct NT Service account identity, or at least allow the user too. Security Issue: The user is forced to create another regular user account, [which as a best practice, should never be done]. Workaround: After the Appropriate Service Account is specified, this temporary user account should be deleted. References Windows does not use "Service Accounts" -- in the Linux sense, but rather "Virtual Accounts" and "Managed Service Accounts, (for machines participating in an LDAP environment. Service Account Naming Convention: By Naming Convention, it appears that the virtual accounts should follow the form, "Command Name" - [Extension] + "svc" "btsync.exe" becomes "NT Service\btsyncsvc" Creating the Virtual "NT Service" Account: Open up the Local Services snap-in, "services.msc" Navigate to the desired service, (btsync), right-click "Properties". Select the "Log On" tab. Select the option to specify a user. Enter the "Conventional" service name, described above: (without quotes). NT Service\btsyncsvc REMOVE the passwords. Save - Apply Restart the Service. Setting Folder Permissions: Set folder permissions -- using the full account name: "NT Service\btsyncsvc", (using quotes may or may not be required depending on the context ...) ... It is not necessary for the btsyncsvc to have execute permissions, so remove if you like -- otherwise, full control. Error - Service Fails to Start due to "No Mapping Between Account Names and Security IDs": For example, this error will occur if you specify, "NT Service\btsync" rather than "NT Service\btsyncsvc" ... The following command will return the list of current service account names. Using PowerShell, (PS), Verify the list against the one you have specified to use for "Log On": PS > get-service | foreach {Write-Host NT Service\$($_.Name)} Error - Service Fails to Start because the Account has not been Granted Log On as a Service Permissions: This error can occur if you have specified the incorrect "Conventional Name", or if the permissions really are missing -- though will be automatically assigned if the correct convention is used. In Windows 10 Home, the User will not be able to use the local security policy snap-in to configure this, (secpol.msc) -- and must be done manually, through PowerShell, or other utility. PowerShell Scripts: To fix this, it is possible to use PowerShell. "Grant-Log-on-as-a-service PowerShell Script, from Technet Gallery": If PowerShell reports an "ExecutionPolicy Error", it may be necessary to change the ExecutionPolicy: PS > Set-ExecutionPolicy RemoteSigned ... May Result in a signing error -- And then changed to: PS > Set-ExecutionPolicy Unrestricted And then use the Script to assign the permission: PS > .".\Add Account To LogonAsService.ps1" "NT Service\btsyncsvc" Reset the ExecutionPolicy if desired: PS > Set-ExecutionPolicy Restricted Hope this Helps!
  2. Downloaded the program, chose to share a folder using email, and got the following dialogs. As is apparant there is absolutely no real text showing except the dummy text for the templates. Not too professional :-/ If this works for other users, my guess is that it is related to localization. Perhaps there were no strings found for the "no" (Norwegian) locale, and instead of resorting to English, it spit out dummy text
  3. I don't know if anyone has been stuck on just one file yet, but I have a windows x64 box trying to move files to a linux x64. Everyone goes smoothly until one last file (which I don't know how to identify) refuses to transfer over to the linux box. Any help would be appreciated. Logs show no record of initiation of a transfer as far as I can tell.
  4. Hi, After updating on all my Macs to 1.0.130 I have noticed a couple of new issues, compared to 1.0.116: 1. Constant and high CPU utilization on all my macs. Even if sync paused it uses around 20-40% of CPU on every mac I have around here (from core2duo to i7) 2. Sync to read-only clients is very slow in some cases. Not sure if this is due slow transfer or slow detection of updated files, but some clients reported 8-12 hours delay from the moment I populate a new file. With 1.0.116 it was almost instant. Could be due a mix of version, maybe those clients run on 1.0.116, no sure.