RealtimeSync Pogoplug Bug?

[eschepp]

I'm using:
Win7, Pogoplug
(with a usb drive connected) and the latest version of Pogoplug drive software
(Maps the pogoplug as a Windows drive).

When I run FreeFileSync bettween my C drive and P drive (Pogoplug Mapped
drive) it works perfectly.

Then I create a batch job from my FreeFileSync job to run it in RealtimeSync.
It starts fine (telling me it is scanning # of files) and then it dies with
the following error message.

Title: Error
Could not register device removal notifications:
Windows Error Code 1066: The service has returned a sevice-specific error
code.

This error "looks like" this one I found in the forums
viewtopic.php?t=977

Is this me or is there a problem with RealtimeSync?

[eschepp]

Did some more testing.
RealtimeSync calls FreeFileSync and the sync completes (I checked all changes
where synced).
I also checked the log file "Synchronization completed successfully!".
The error happens after the sync (might help to narrow it down where it
happens in RealtimeSync).

[eschepp]

Ran FreeFileSync from the command prompt. Works 100% correctly.
So the problem is in RealtimeSync.

[Zenju]

Thank you for the detailed problem description including error message texts!
Thous I was able to quickly fix this problem similar to the SAMBA issue:
[404, Invalid URL: http://www.file-upload.net/download-2942933/FreeFileSync_v3.12_beta2_setup.exe.html]
Is this working for you?

Regards, Zenju

[eschepp]

Thanks for the quick response.

I did download the file but ZoneAlarm scan failed the file.
Security Status:
ZoneAlarm Browser Security security scan has found this file is malicous.

So - for now I can't test it

the file

[Zenju]

Obviously a false positive:
http://www.virustotal.com/file-scan/report.html?id=0ee46d7560f6b330e7a17c5507c5ac2540686e51e3e858c345896391e520759a-1288822566

[eschepp]

Strange...Scanned it again - no more red flags.
Anyhow - installed it and ran RealtimeSync - works perfectly now!!!

[eschepp]

Zenju, do you know when FreeFileSync_v3.12 is scheduled to be released
(that will have this new fix)?

[Zenju]

>Anyhow - installed it and ran RealtimeSync - works perfectly now!!!
That's good to hear!

>do you know when FreeFileSync_v3.12 is scheduled to be released (that will
have this new fix)?
v3.12 is not yet scheduled for release, but it will probably take 2-3 weeks
from now. Until then the beta posted above is fully usable and despite its
name, has release-quality.

[eschepp]

Did some more detailed testing.
When RealtimeSync starts it automatically runs FreeFileSync once and both
drive are in sync (C:\subfolder - internal hard drive and my P:\subfolder
mapped Pogodrive) – all good.
RealtimeSync is monitoring C:\subfolder and P:\subfolder.
Every time I make changes in the subfolder on the C:\subfolder files get
synced – also all good.
All changes on P:\mysubfolder are not noticed by RealtimeSync. I tried
add/update/delete of files - nothing triggers RealtimeSync to run.
I made sure that the date and time of the folder on P:\mysubfolder change each
time I update files inside of it – and it is changing.
What else can I do to make it work?
I prefer running RealtimeSync instead of creating scheduled tasks so that the
sync only runs when needed.

[Zenju]

>All changes on P:\mysubfolder are not noticed by RealtimeSync
I don't know what the problem is in this case. In general if a drive is not
able to send file change notifications an error message is shown right at the
start that the drive does not support this function. If there is no error
message shown it should work....FFS in general is designed to never suppress
significant error situations.

[eschepp]

There are no error messages.
FFS works great - RealtimeSync doesn’t detect changes on the mapped PogoDrive
(This is an external Linux box with a hd(s) attached to it (looks like
P:\HD_Label1\YourFolderName).
What exactly is RealtimeSync looking for to trigger?
I need exact details so I can post it in the PogoDrive forum to see if they
have a solution.

[Zenju]

>What exactly is RealtimeSync looking for to trigger?
RTS is simply using the WinAPI function FindFirstChangeNotification:
https://msdn.microsoft.com/en-us/library/aa364417%28VS.85%29.aspx
If this call fails for whatever reason, it's error code is correctly processed
by RTS. If you don't see an error message this means that calling this
function succeeded, thous one can expect to receive change notifcations.

[enferal]

I have a problem using Realtime because I receive an error message as follows:
Execution of command failed...(path to batch file....) (error 193
:unknownerror c1)
I am using the beta version you advise in this post and before using Realtime
I have created the batch file with FFS in the menu Advanced/Create batch and
Save to Load in Realtime inits advanced menu.
Thanks in advance and regards.

[Zenju]

> Execution of command failed..
What's in the RTS commandline? Is the path to FFS correct?

[enferal]

Thanks for the quick answer. The path is
C:\Users\Enferal\Desktop\FFS\FreeFileSync.exe
"C:\Users\Enferal\Desktop\Copy\SyncJob.ffs_batch" where FFS is the folder
which has the program in Portable Mode. SyncJob.ffs_batch is the configuration
of a job which runs in FFS without problem.

[Zenju]

Error 193 seems to be "%1 is not a valid Win32 application." Maybe the
FreeFileSync.exe is currupted?

[enferal]

If FreeFileSync.exe is currupted, it wouldn't run when double click on it to
start... Perhaps the Beta has not solved the problem with RealtimeSync?

[Zenju]

Did you manually go into the directory that is referenced and start the
application? Is there a 64<->32 bit issue? When doing tests with specifing a
path to an invalid executable FFS responds with exactly error 193.

[siutsch]

Hi,

I had the same problem with FreeFileSync_v3.11, but with mounted Truecrypt
Volumes.

Inst. of FreeFileSync_v3.12_beta2 has fixed it. :)

Just wanted to say.

Siutsch.