-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parameter is not correct - Pri.LongPath.Directory.BeginFind #58
Comments
My library stated 2.0.0-beta, I'm updating to the latest and will see if they can reproduce it. |
Updating to latest Pri.LongPath, the user still hits this issue. Same stack trace. |
The user manually tried going to the folder that had issues. Note, this folder name (1234_5678-110) was already returned from parentFolder.GetDirectories(), and the code is now iterating on each of these child folders with child.GetDirectories(). The user, when he navigates Windows Explorer to the parentFolder, can see the list of directories underneath. (Note this is a network drive). Then when user double-clicks on 1234_5678-110, an error message appears in windows: |
One more side note, somewhat related. The same person has a shared network folder with paths like: When he goes home, and isn't connected to network, the following throws an exception: |
I haven't been able to repo this; but is the user using Sync Center or some other method of offline files? |
Hi, |
I'm unfortunately using a version of Pri.LongPath that is a year or two old, so I'm not sure if this is still an issue. It is tough to reproduce though. I have a customer that hits this issue about once a week.
You can see below the stacktrace, and a mention of "System.IO.IOException - The parameter is incorrect" inside of Pri.LongPath.Directory.BeginFind().
At this point I do not have any additional information that could help in debugging this. Do you know where, within BeginFind(), I could maybe add some additional information to log files on this?
The text was updated successfully, but these errors were encountered: