Anonymous_User Absent Member.
Absent Member.
4355 views

"Synchronization failed because a path is too long"

iFolder 2.1.8 running on NetWare 6.5 SP6. User logs into iFolder and
gets "iFolder synchronization failed because a path is too long."

Thoughts?
Labels (1)
0 Likes
8 Replies
Anonymous_User Absent Member.
Absent Member.

Re: "Synchronization failed because a path is too long"

Doug Black,
> iFolder 2.1.8 running on NetWare 6.5 SP6. User logs into iFolder and
> gets "iFolder synchronization failed because a path is too long."
>

And that just happens for one user? Right away, or when syncing a
certain file?

- Anders Gustafsson, Engineer, CNE6, ASE
NSC Volunteer Sysop
Pedago, The Aaland Islands (N60 E20)

Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement

Using VA 5.51 build 315 on Windows 2000 build 2600

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: "Synchronization failed because a path is too long"

Anders Gustafsson,

>> iFolder 2.1.8 running on NetWare 6.5 SP6. User logs into iFolder and
>> gets "iFolder synchronization failed because a path is too long."
>>

> And that just happens for one user? Right away, or when syncing a
> certain file?
>


Yes, only for one user. I *think* it happens when he first logs in, but
I'll verify that.

I looked at the error log and found this:

07/18/07 13:15:27 LOCATE_SERVER user02 authentication failure

where "user02" is the user having problems. I don't know if this has
any bearing on the problem or not.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: "Synchronization failed because a path is too long"

Doug Black,
> 07/18/07 13:15:27 LOCATE_SERVER user02 authentication failure
>
> where "user02" is the user having problems. I don't know if this has
> any bearing on the problem or not.


Well it certainly does not look right. Has the user's password expired
perhaps? IFolder does not do grace logins.

- Anders Gustafsson, Engineer, CNE6, ASE
NSC Volunteer Sysop
Pedago, The Aaland Islands (N60 E20)

Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement

Using VA 5.51 build 315 on Windows 2000 build 2600

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: "Synchronization failed because a path is too long"

Anders Gustafsson wrote:
> Doug Black,
>> 07/18/07 13:15:27 LOCATE_SERVER user02 authentication failure
>>
>> where "user02" is the user having problems. I don't know if this has
>> any bearing on the problem or not.

>
> Well it certainly does not look right. Has the user's password expired
> perhaps? IFolder does not do grace logins.
>


He's in the office, so he wouldn't be logging into his PC if his NDS
password was expired. I see other failed logins, but they are worded a
bit differently, viz:

07/18/07 13:41:17 weil01/home: machId:1 - Login authentication
failure (ldap time = 3 secs)

The "LOCATE_SERVER" wording makes me wonder if this is a DNS issue
specific to that client. I'm checking that avenue now.

Thanks,

Doug
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: "Synchronization failed because a path is too long"

Doug Black,
> The "LOCATE_SERVER" wording makes me wonder if this is a DNS issue
> specific to that client. I'm checking that avenue now.
>

Ah, yes. That message is from iFolder when a client logs in and iFolder
asks itself "What server is this user on". Is there and IP address or
DNS name somewhere?

- Anders Gustafsson, Engineer, CNE6, ASE
NSC Volunteer Sysop
Pedago, The Aaland Islands (N60 E20)

Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement

Using VA 5.51 build 315 on Windows 2000 build 2600

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: "Synchronization failed because a path is too long"

Anders Gustafsson,

>> The "LOCATE_SERVER" wording makes me wonder if this is a DNS issue
>> specific to that client. I'm checking that avenue now.
>>

> Ah, yes. That message is from iFolder when a client logs in and iFolder
> asks itself "What server is this user on". Is there and IP address or
> DNS name somewhere?
>


I don't know, where would I look?

The user just removed and reinstalled iFolder on his PC and got the same
thing immediately after logging into iFolder. I'm thinking there may be
a corrupted item in his iFolder store on the server.

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: "Synchronization failed because a path is too long"

Doug Black,
> I don't know, where would I look?
>

On the same screen. Anyway, can you try an LDAP trace when that user
logs in?

- Anders Gustafsson, Engineer, CNE6, ASE
NSC Volunteer Sysop
Pedago, The Aaland Islands (N60 E20)

Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement

Using VA 5.51 build 315 on Windows 2000 build 2600

0 Likes
madolph1 Absent Member.
Absent Member.

Re: "Synchronization failed because a path is too long"

My iFolder Client running on a Windows XP notebook did this repeatedly.
I uninstalled and reinstalled iFolder Client multiple times, including deleting everything in the C:/Program Files/Novell/iFolder folder. Didnt help.

Then I ran a Registry Cleaner program by Uniblue (RegistryBooster2) and repaired or deleted bad registry items, and did a registry defrag. I went into McAfee antivirus and set iFolder as an exclusion program from intruder recognition. I also went to the Windows Security Center and allowed "port 80" as an exception.

I reloaded iFolder Client and a sync began! I discovered that the sychronization interruption would then only occur when I opened a C: drive iFolder item while iFolder Client synchronization was simultaneously occuring. I then logged out of iFolder Client and re-loggedin and to my surprise sync-ing occurred as long as I was not opening an iFolder item. My plan is to logout of iFolder Client when I am using iFolder items, and login to iFolder Client in order for syncing to occur when I am finished using files in the iFolder. This only occurs on my laptop, not on two desktops I have. This occurs whether I am on the LAN by ethernet cable, wireless networking, or Verizon USB broadband. I dont know what specifically helped, but this workaround has allowed me to sync at least intermittently. Our iFolder server administrator Doug Black has posted items about this on the forums and no clear answers otherwise yet to his posts.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.