Re: Error watching for changes in directory
@leoslg: Is there anything special about the "my/path"? Is it a plain local drive? Or a network drive? Or something else?
- martin
Post a reply
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
Topic review
- leoslg
Error watching for changes in directory
Error watching for changes in directory
*my/path/*
----------------------------------------
System Error. Code: 1.
Incorrect Function.
----------------------------------------
I reached this error, and I have no idea what this function means.
- Pada
OK, thanks for the reply.
I think I'll resort to 2 WinSCP instances. One for watching the changes on my computer, which then copies the files to the local WinXP machine, and then another WinSCP instance for watching & updating the remote server.
I think I'll resort to 2 WinSCP instances. One for watching the changes on my computer, which then copies the files to the local WinXP machine, and then another WinSCP instance for watching & updating the remote server.
- martin
OK, anyway, I haven't found anything I can change in WinSCP to make it working for you. I'm Sorry.
- Pada
No problem.
I find that strange that the Window was open a few minutes after that. It might be that I've left the error message open to try and copy the Windows crash report.
I've now rerun the same debugging application again and this time I quickly closed the error window.
New trace log (zipped) is attached.
If you want me to run certain debugging/tracing applications I would be more than glad to do that. I'm not a reverse engineer, but I'm a quite capable Java/C# programmer.
Thanks for all your time & effort that you've put into this problem.
Regards
Chris
I find that strange that the Window was open a few minutes after that. It might be that I've left the error message open to try and copy the Windows crash report.
I've now rerun the same debugging application again and this time I quickly closed the error window.
New trace log (zipped) is attached.
If you want me to run certain debugging/tracing applications I would be more than glad to do that. I'm not a reverse engineer, but I'm a quite capable Java/C# programmer.
Thanks for all your time & effort that you've put into this problem.
Regards
Chris
- martin
Sorry for delay. In the log I can see that WinSCP was running yet minutes after that. So do you say that the WinSCP window disapeared from your desktop?
- Pada
OK, I've ran the winscp424pada build. With that build it managed to get further than the other stable/development builds. It even showed "Watching for changes in 92 directories...", which it weren't able to do previously. HOWEVER, it's immediately crashing right after it showed that in the status listbox.
The trace log file has been uploaded here: <invalid hyperlink removed by admin>
The trace log file has been uploaded here: <invalid hyperlink removed by admin>
- Pada
Yes, I did receive the email. I was just too busy with my project at the time.
I've ran the debugging version, replicated the error and uploaded the log file to:
<invalid hyperlink removed by admin>
I've ran the debugging version, replicated the error and uploaded the log file to:
<invalid hyperlink removed by admin>
- martin
Re: System Error. Code: 1. Incorrect function when using SAMBA
@Pada: I've sent you a debug version, did you get it?
- Pada
System Error. Code: 1. Incorrect function when using SAMBA
Hi,
I'm getting exactly the same error as @Jens P.:
I know it's the same error, because I've worked in Germany for a few months and I've been to Prague :)
Anyways, I have tried WinSCP 3.8.2, 4.1.8 & 4.2.3 beta and they all give the same error. I'm trying to "Keep remote directory up to date", where my local directory is a SAMBA share on Ubuntu. I'm actually running Windows XP as the guest OS & Ubuntu as the host OS using VirtualBox.
Using Debug 2 level, it is showing:
I guess its impossible to fix WinSCP since it's an underlaying error of Windows / SAMBA shares?
Regards
Chris Kistner
I'm getting exactly the same error as @Jens P.:
System Error. Code: 1.
Incorrect function
I know it's the same error, because I've worked in Germany for a few months and I've been to Prague :)
Anyways, I have tried WinSCP 3.8.2, 4.1.8 & 4.2.3 beta and they all give the same error. I'm trying to "Keep remote directory up to date", where my local directory is a SAMBA share on Ubuntu. I'm actually running Windows XP as the guest OS & Ubuntu as the host OS using VirtualBox.
Using Debug 2 level, it is showing:
. 2009-10-22 22:43:22.830 Session upkeep
. 2009-10-22 22:43:22.830 Looking for network events
. 2009-10-22 22:43:22.830 Timeout waiting for network events
. 2009-10-22 22:43:23.311 Session upkeep
. 2009-10-22 22:43:23.311 Looking for network events
. 2009-10-22 22:43:23.311 Timeout waiting for network events
. 2009-10-22 22:43:23.812 Session upkeep
. 2009-10-22 22:43:23.812 Looking for network events
. 2009-10-22 22:43:23.812 Timeout waiting for network events
. 2009-10-22 22:43:24.453 Session upkeep
. 2009-10-22 22:43:24.453 Looking for network events
. 2009-10-22 22:43:24.453 Timeout waiting for network events
. 2009-10-22 22:43:24.813 Session upkeep
. 2009-10-22 22:43:24.813 Looking for network events
. 2009-10-22 22:43:24.813 Timeout waiting for network events
I guess its impossible to fix WinSCP since it's an underlaying error of Windows / SAMBA shares?
Regards
Chris Kistner
- Vacilando
Re: cannot auto update on Novell
Perhaps it is configurable?
I can formulate a question for a Novell discussion forum or their support people. What should I ask them about -- what signal / process / flag is it, technically speaking, that WinSCP needs to know in order to register a change in a directory?
- martin
Re: cannot auto update on Novell
@tjfulopp: If the Novell drive does not support the notification, I cannot do anything about it. Perhaps it is configurable?
- tjfulopp
cannot auto update on Novell
Ahoj Martin,
The "Keep remote directory up to date" does not work if the source is on Novell server. This has been a serious problem for me since there are several people who need access to the source files. In this forum, I see other WinSCP users need it as well.
Do you have plans to introduce this functionality in the coming release of WinSCP? I understand Novell may work differently than Windows but I can imagine there are ways to achieve it.
Thanks for the amazing software -
Tom
The "Keep remote directory up to date" does not work if the source is on Novell server. This has been a serious problem for me since there are several people who need access to the source files. In this forum, I see other WinSCP users need it as well.
Do you have plans to introduce this functionality in the coming release of WinSCP? I understand Novell may work differently than Windows but I can imagine there are ways to achieve it.
Thanks for the amazing software -
Tom
- martin
Re: Same Problem
@Jens: Your Novell network probably does not support the "change notification" functionality.
- Jens P.
Same Problem
Hi,
I am on Windows 2000 and files are stored at a Novell network directory!
The webserver is a Linux machine
I think Unzulässige Funktion in English is illegal or forbidden?!
What can be the reasons?
Greetz
I am on Windows 2000 and files are stored at a Novell network directory!
The webserver is a Linux machine
Error watching for changes in directory 'R:\Data\_CurrentProject\abwesenheit_test':
System Error. Code: 1.
Unzulässige Funktion
I think Unzulässige Funktion in English is illegal or forbidden?!
What can be the reasons?
Greetz
- martin
BTW, 500 is limit imposed by WinSCP.
- FodderMK
Yes, actually, it was on a network drive. So for testing I mirrored everything relevant on the network to my local machine and tried it again. The error did not occur. So it seems like the solution (for me) is to work on my local machine.
To answer your other question, there are 406 folders, 1540 files. Another project I work on contains 802 folders, 4925 files. For that project I get the following error when attempting to use the "Keep remote directory up to date" feature:
But at least that error code makes sense to me and I'll be able to work around it. Thanks for your help!
To answer your other question, there are 406 folders, 1540 files. Another project I work on contains 802 folders, 4925 files. For that project I get the following error when attempting to use the "Keep remote directory up to date" feature:
Cannot watch for changes in more then 500 directories and subdirectories
But at least that error code makes sense to me and I'll be able to work around it. Thanks for your help!
- martin
It seems that there is some system limit on number of directories being watched. If this is true, I can hardly do anything about that. BTW, is the directory you are watching on network drive?
What is approximate number of subdirectories in the directory?
What is approximate number of subdirectories in the directory?
- FodderMK
I get the error as well:
The directory it has problems with isn't always necessarily the same. I do seem to notice a correlation between this error and the number of files/directories though. If I tell WinSCP to monitor a relatively empty directory then everything works fine. If I tell it to monitor a directory with many files and subdirectories then I get this error.
I'm using WinSCP 3.7.5 (Build 294) on a fully-patched WinXP system. The settings I have checked in the "Keep remote directory up to date" window are "Update subdirectories", "Existing files only" and "No confirmations". If I uncheck "Update subdirectories" then WinSCP also works correctly, reinforcing the "trouble with lots of directories" theory.
If you'd like me to run any more tests just let me know. I don't have any control over the remote box, however, so the testing I can do there is limited.
System Error. Code: 56.
The network BIOS command limit has been reached
The directory it has problems with isn't always necessarily the same. I do seem to notice a correlation between this error and the number of files/directories though. If I tell WinSCP to monitor a relatively empty directory then everything works fine. If I tell it to monitor a directory with many files and subdirectories then I get this error.
I'm using WinSCP 3.7.5 (Build 294) on a fully-patched WinXP system. The settings I have checked in the "Keep remote directory up to date" window are "Update subdirectories", "Existing files only" and "No confirmations". If I uncheck "Update subdirectories" then WinSCP also works correctly, reinforcing the "trouble with lots of directories" theory.
If you'd like me to run any more tests just let me know. I don't have any control over the remote box, however, so the testing I can do there is limited.
- daftbusker
Nothing yet
No, nothing yet. I spent a few hours looking around and couldn't turn up anything. I don't have the time to poke around too much right now, but if I figure out a solution I'll post it here. Opening a few winscp's at once won't kill me.
Thanks again for the software and your help,
- Daft
Thanks again for the software and your help,
- Daft
- martin
Re: Whoops
Have you found anything?
- daftbusker
Whoops
OK that makes sense, the error is:
This article:
<invalid hyperlink removed by admin>
Mentions using the latest Service Pack for w2000 but I have 4 installed... I'm gonna check the Samba settings.
System Error. Code: 56.
The network BIOS command limit has been reached
This article:
<invalid hyperlink removed by admin>
Mentions using the latest Service Pack for w2000 but I have 4 installed... I'm gonna check the Samba settings.
- martin
Are you sure you have used the version linked from my post? You should have
I'm leaving for one week now, so please do not expect another reply soon.
"more" button on the message to show additional info. Like:
---------------------------
Error
---------------------------
Error watching for changes in directory 'D:\XXX'.
---------------------------
System Error. Code: 2.
Cannot find the path specified.
---------------------------
OK
---------------------------
I'm leaving for one week now, so please do not expect another reply soon.
- daftbusker
Thanks for the help.
It now says the problem is with a directory inside the directory reported in the previous error.
(If you compare the new error message to the one in my last post, you'll see the directory names are slightly different because I'd typed (not c&p'ed) the old error, but I was pretty close.)
The new error:
I double-checked the permissions, etc., but I still don't see anything funny.
It now says the problem is with a directory inside the directory reported in the previous error.
(If you compare the new error message to the one in my last post, you'll see the directory names are slightly different because I'd typed (not c&p'ed) the old error, but I was pretty close.)
The new error:
---------------------------
Error
---------------------------
Error watching for changes in directory 'M:\home\daft\project\project-dev\root\user_scripts\root_tables'.
---------------------------
OK
---------------------------
I double-checked the permissions, etc., but I still don't see anything funny.
- martin
Re: Error watching for changes in directory
I have improved error reporting for this case. Please download updated version and try again with it. Then post the full error message (do not forget to press "More" button or copy full error message using
Ctrl+C). Thanks.
- daftbusker
Error watching for changes in directory
Hi,
First, I'd like to thank you for the software, it's great. I'm using 3.7.4
I'm trying to use the 'Keep remote directory up to date' and it's chokes on one sub-directory. The error is
Error watching for changes in directory 'M:\home\daft\project\project-files\admin\user-scripts\'
M: is a samba share on a Linux server, winscp is on windows 2000.
I went in and recursively chmoded and chowned the whole directory in case it was a permission problem but to no avail. I also did a lsattr but I didn't see anything. There are sub directories in the user-scripts directory, but I have done other transfers with a larger number subdirectories (5 I think)
What was particularly strange was that if I go into the admin folder (in the above example) and then run the command, I don't get an error... My work around is to open several instances of winSCP but it's kind of clumsy.
Thanks for any help.
First, I'd like to thank you for the software, it's great. I'm using 3.7.4
I'm trying to use the 'Keep remote directory up to date' and it's chokes on one sub-directory. The error is
Error watching for changes in directory 'M:\home\daft\project\project-files\admin\user-scripts\'
M: is a samba share on a Linux server, winscp is on windows 2000.
I went in and recursively chmoded and chowned the whole directory in case it was a permission problem but to no avail. I also did a lsattr but I didn't see anything. There are sub directories in the user-scripts directory, but I have done other transfers with a larger number subdirectories (5 I think)
What was particularly strange was that if I go into the admin folder (in the above example) and then run the command, I don't get an error... My work around is to open several instances of winSCP but it's kind of clumsy.
Thanks for any help.