Error Log in Live Sync - Finding specific error problem

A

AEngineer

I'm getting a message that there is a filename (I presume they mean path)
that is too long so one of my LiveSync folders on one machine won't sync -
they sync fine on other machines.

I've checked all the files in the synced folder and found that none exceed a
path length of 231. I'm therefore trying to search the error log to find the
specific reference. It's very large - multiple thousand lines.

Can anyone tell me how to search it to find a specific identification of a
too-long filename/path? I've tried "error" and "path" and "filename" without
much luck.
 

My Computer

K

KyongHwan Kim [MSFT]

The reason you are getting this error is because you probably have some files on your remote machine with path lengths pretty close
to 255. On this machine the library is getting mapped to a base path that is longer than the base path on the remote machine. This
causes some path lengths to exceed 255. One thing which would help (get rid of this and subsequent path length errors) would be to
map this library to a base path less than or equal in length to the base path on the remote machine – which would guarantee the file
paths to be less than 255.

Meanwhile, you could try following steps *on Remote machine* to indentify file/folder caused the issue
1. run cmd
2. cd to the folders which ran into the issue.
3. run "dir /b /s > c:\filelist.txt"
4. "notepad c:\filelist.txt"
5. search for long filename including path

Hope this helps.
Kyong

"AEngineer" <[email protected]> wrote in message news:[email protected]
I'm getting a message that there is a filename (I presume they mean path)
that is too long so one of my LiveSync folders on one machine won't sync -
they sync fine on other machines.

I've checked all the files in the synced folder and found that none exceed a
path length of 231. I'm therefore trying to search the error log to find the
specific reference. It's very large - multiple thousand lines.

Can anyone tell me how to search it to find a specific identification of a
too-long filename/path? I've tried "error" and "path" and "filename" without
much luck.
 

My Computer

Top