Im using version 4.6 and I create a batch job using Free File Sync. I need to
call this job using Real time Sync. I add it as a service on Windows server
2003 and start the service. Real time sync 'red' color icon appears in system
tray but in very dark 'red' color.When mouse pointer is on the icon it says
"Waiting for missing directories".... What could be it went wrong?
Please note I need to run this job without login in to Windows account & real
time. ..Thank you! [404, Invalid URL: http://www.freeimagehosting.net/scz1e]
[404, Invalid URL: http://www.freeimagehosting.net/dk65u]
"Waiting for missing directories&...
- Posts: 12
- Joined: 2 Jun 2011
- Posts: 12
- Joined: 2 Jun 2011
Screen shots
[404, Invalid URL: http://www.freeimagehosting.net/dk65u]
[404, Invalid URL: http://www.freeimagehosting.net/scz1e]
[404, Invalid URL: http://www.freeimagehosting.net/dk65u]
[404, Invalid URL: http://www.freeimagehosting.net/scz1e]
- Site Admin
- Posts: 7279
- Joined: 9 Dec 2007
"Waiting for missing directories" means, one of the directories listed in RTS
is not found at this very moment.
is not found at this very moment.
- Posts: 12
- Joined: 2 Jun 2011
what a quick reply....Thanks...Then shall I upgrade current version to newer
version or re install same thing?
version or re install same thing?
- Site Admin
- Posts: 7279
- Joined: 9 Dec 2007
Äh... it's probably a better idea to make sure the directory exists ;) Maybe
it's a spelling error. If the path names contain macro, you can check what it
resolves to by hovering over the name via mouse and see its tooltip.
it's a spelling error. If the path names contain macro, you can check what it
resolves to by hovering over the name via mouse and see its tooltip.
- Posts: 12
- Joined: 2 Jun 2011
Yes correct..My source directory is shared folder over the network. It seems
RTS & FFS can not read it. Isn't RTS support UNC paths? :(
RTS & FFS can not read it. Isn't RTS support UNC paths? :(
- Site Admin
- Posts: 7279
- Joined: 9 Dec 2007
UNC shouldn't be a problem. Are you able to open the folder via the very same
path in explorer?
Make sure you are running the tool under the correct user (which may affect
access permissions).
path in explorer?
Make sure you are running the tool under the correct user (which may affect
access permissions).
- Posts: 12
- Joined: 2 Jun 2011
Yes UNC path can open via explorer. I am running this tool as domain
administrator. I also map the folder to a drive letter but giving same error.
I create two test folders locally and test..It working fine.
administrator. I also map the folder to a drive letter but giving same error.
I create two test folders locally and test..It working fine.
- Site Admin
- Posts: 7279
- Joined: 9 Dec 2007
Strange. Can you send me a Process Monitor log (https://technet.microsoft.com/de-de/sysinternals/bb896645.aspx)? This should give some details on why it
doesn't find the path.
doesn't find the path.
- Posts: 12
- Joined: 2 Jun 2011
hi Zenju..log file can be downloaded from following link. Pls note I can open
this UNC path using Windows Explorer without any issue.
[404, Invalid URL: http://wikisend.com/download/387338/Logfile.rar]
this UNC path using Windows Explorer without any issue.
[404, Invalid URL: http://wikisend.com/download/387338/Logfile.rar]
- Site Admin
- Posts: 7279
- Joined: 9 Dec 2007
Thanks, the log makes it clear: RTS is run under the system account and trying
to access "shared\Organization Stuff\Documentation\" is denied. So the
solution is to make sure that the system account is granted access to this
directory.
\\192.168.104.160\NP shared\Organization Stuff\Documentation\ NT
AUTHORITY\SYSTEM ACCESS DENIED
There may be also a todo for RTS: Failure to access the directory is handled
as if the directory did not exist. A better behavior may be treat it as
existing but let it fail when starting directory monitoring with "access
denied".
to access "shared\Organization Stuff\Documentation\" is denied. So the
solution is to make sure that the system account is granted access to this
directory.
\\192.168.104.160\NP shared\Organization Stuff\Documentation\ NT
AUTHORITY\SYSTEM ACCESS DENIED
There may be also a todo for RTS: Failure to access the directory is handled
as if the directory did not exist. A better behavior may be treat it as
existing but let it fail when starting directory monitoring with "access
denied".