Path name too long, being sent to .tonidocache instead

Support for FileCloud: On-Premises, Business File Sharing Software for SMBs, Enterprises, ISPs
Rogue75
Rookie Tonidoid
Rookie Tonidoid
Posts: 1
Joined: Mon Apr 14, 2014 12:08 pm

Path name too long, being sent to .tonidocache instead

Postby Rogue75 » Mon Apr 14, 2014 12:27 pm

Hello,

We are in the middle of testing the Filecloud trial for our company. One issue we noticed is that the Windows Desktop client doesn't want to sync certain folders/files as the path name is too long. Now here's the strange part. The path where it should go is...

C:\Focussync\FileCloud\Shared with Me\projects\etc...


But instead of going straight there, it seems to be going through a temporary directory which makes it's path too long...

C:\Users\Focus\AppData\Roaming\FileCloudSyncData\client\.tonidocache\Shared with Me\projects\etc..

As you can see this is extra characters being temporarily wasted and preventing the sync.
Previously with dropbox we had this path...

C:\Companies\Dropbox (Focus xxxxxxx xxxxxx)\projects\etc...


which is even longer than what FileCloud's path should be in the first path above. Any ideas as to why it has to go through this "tonidocache" before going into C:\Focussync? Can we move where this temporary cache is so that we don't hit this character limit?

Thanks ahead of time.

User avatar
madhan
Admin Tonidoid
Admin Tonidoid
Posts: 8617
Joined: Tue Dec 30, 2008 12:13 am
Location: Austin, TX, USA
Contact:

Re: Path name too long, being sent to .tonidocache instead

Postby madhan » Mon Apr 14, 2014 11:24 pm


rydgaze
Tonido Team
Tonido Team
Posts: 1354
Joined: Wed Jan 28, 2009 11:26 pm

Re: Path name too long, being sent to .tonidocache instead

Postby rydgaze » Tue Apr 15, 2014 11:25 am

which is even longer than what FileCloud's path should be in the first path above. Any ideas as to why it has to go through this "tonidocache" before going into C:\Focussync? Can we move where this temporary cache is so that we don't hit this character limit?


The sync app will commit only full "set" of changes. So it will get all the files of a "change set" and once it is complete, then it will commit (basically move it to your final sync folder).

alexon
Rookie Tonidoid
Rookie Tonidoid
Posts: 1
Joined: Fri May 30, 2014 11:00 am

Re: Path name too long, being sent to .tonidocache instead

Postby alexon » Fri May 30, 2014 11:02 am

Hi,
I am getting path too long error and that is why I cannot delete some files on my PC,
I came across Long Path Tool, is it ok solution for my problem?
Did anybody had similar experience?

User avatar
madhan
Admin Tonidoid
Admin Tonidoid
Posts: 8617
Joined: Tue Dec 30, 2008 12:13 am
Location: Austin, TX, USA
Contact:

Re: Path name too long, being sent to .tonidocache instead

Postby madhan » Mon Jun 02, 2014 6:23 pm

Nice idea, we might want to set up a FC community page with these kinds of nifty scripts.

alina--
Rookie Tonidoid
Rookie Tonidoid
Posts: 1
Joined: Tue Jan 27, 2015 2:55 am

Re: Path name too long, being sent to .tonidocache instead

Postby alina-- » Tue Jan 27, 2015 3:00 am

alexon wrote:Hi,
I am getting path too long error and that is why I cannot delete some files on my PC,
I came across Long Path Tool, is it ok solution for my problem?
Did anybody had similar experience?


I use Long Path Tool Alexon, First I had doubt but when I tried it , It has solved my path too long issues.

jesicca wonyta
Rookie Tonidoid
Rookie Tonidoid
Posts: 1
Joined: Tue Mar 10, 2015 12:02 pm

Re: Path name too long, being sent to .tonidocache instead

Postby jesicca wonyta » Tue Mar 10, 2015 12:05 pm

Use Long Path Tool, Long Path Tool can simplify and probably end your problems in unlocking, managing and renaming files that appear to have a long filename.


Return to “FileCloud”

Who is online

Users browsing this forum: No registered users and 2 guests