WatchDirectory home page
WatchDirectory Startseite (Deutsche Version)
Site WatchDirectory (Français)
  Welcome, Guest. Please Login or Register
YaBB - Yet another Bulletin Board
   
  HomeHelpSearchLoginRegister  
 
Page Index Toggle Pages: 1
Error code 64 (Read 21108 times)
Ruud
YaBB Newbies
*
Offline



Posts: 18
Kruiningen
Error code 64
Jan 23rd, 2014 at 10:23am
 
We having the following error in a task  which is using the fast monitoring event

after the second message the system stops trying to connect we have set the attempt on 1000 reconnects so it.
Logging:
2014-01-22 13:05:54;W;Can not get status of directory, error message: Error Code: 64 Description: The specified network name is no longer available. ;
2014-01-22 13:05:54;W;Directory monitor has encountered a problem, will retry after 1000 seconds.;
2014-01-22 13:22:34;I;Starting to monitor the directory;

2014-01-22 13:22:34;I;Will fire filenew/dirnew events for all files;
2014-01-22 13:35:25;W;Can not get status of directory, error message: Error Code: 64 Description: The specified network name is no longer available. ;
2014-01-22 13:35:47;E;Error watching directory Error code =   Error Code: 0 Description: The operation completed successfully. ;

and then the task is hanging.
Is there a solution for this issue?

Kind regards,

Ruud
Back to top
 

Kind regards,

Ruud
 
IP Logged
 
Gert
YaBB Administrator
*****
Offline



Posts: 2233
The Netherlands
Re: Error code 64
Reply #1 - Jan 23rd, 2014 at 12:27pm
 
Is this a network drive? If you are running this task as a service you need to set a userid/password for the service, see http://blog-en.gdpsoftware.com/2010/04/watchdirectory-tasks-as-windows-service.h...
Back to top
 

Gert Rijs - gert (at) gdpsoftware (dot) com
Blog: http://blog-en.gdpsoftware.com/
End Alzheimer's: http://www.alz.org&&...
WWW WWW GdPSoftware  
IP Logged
 
Ruud
YaBB Newbies
*
Offline



Posts: 18
Kruiningen
Re: Error code 64
Reply #2 - Jan 23rd, 2014 at 1:27pm
 
Hi we are running the task as a service and we have set the userid and password in the config file.

The task is running fine until we got some network issues then this issue occurred I would expect that the task is retrying to activated the task again a 1000 times.
Back to top
 

Kind regards,

Ruud
 
IP Logged
 
Dirk
YaBB Administrator
*****
Offline



Posts: 659
South Germany
Re: Error code 64
Reply #3 - Jan 23rd, 2014 at 1:47pm
 
The Task will retry when you configure it to do so.
Back to top
 

screenshot_001.png (62 KB | 209 )
screenshot_001.png

Viele Grüße / Best regards
Dirk - GdP Software

dirk [at] gdpsoftware [dot] com
http://blog-de.gdpsoftware.com
Webseite: http://www.gdpsoftware.com
WWW WWW  
IP Logged
 
Ruud
YaBB Newbies
*
Offline



Posts: 18
Kruiningen
Re: Error code 64
Reply #4 - Jan 23rd, 2014 at 1:52pm
 
We have set this option see attachment
Back to top
 


Kind regards,

Ruud
 
IP Logged
 
Dirk
YaBB Administrator
*****
Offline



Posts: 659
South Germany
Re: Error code 64
Reply #5 - Jan 23rd, 2014 at 1:54pm
 
So you only have  to wait 1000 seconds between each attemp to reconnect. 1000 seconds are ~ 16 minutes.

Maybe you want to lower that....
Back to top
 

Viele Grüße / Best regards
Dirk - GdP Software

dirk [at] gdpsoftware [dot] com
http://blog-de.gdpsoftware.com
Webseite: http://www.gdpsoftware.com
WWW WWW  
IP Logged
 
Ruud
YaBB Newbies
*
Offline



Posts: 18
Kruiningen
Re: Error code 64
Reply #6 - Jan 23rd, 2014 at 2:13pm
 
Please have a look at the logging I added in the original post.  After the last line

2014-01-22 13:35:47;E;Error watching directory Error code =   Error Code: 0 Description: The operation completed successfully. ;

the task is stopped working even do the status in the control center is green(running) No new files are processed any more.
This task is part of a critical interface so it should not stop running without any signal
Back to top
 

Kind regards,

Ruud
 
IP Logged
 
Dirk
YaBB Administrator
*****
Offline



Posts: 659
South Germany
Re: Error code 64
Reply #7 - Jan 23rd, 2014 at 2:41pm
 
If your network drive get lost because of a network error, the task stays green and try to reach the network again after the time period you have configured.

In your case:

Quote:
2014-01-22 13:05:54;W;Can not get status of directory, error message: Error Code: 64 Description: The specified network name is no longer available. ;
2014-01-22 13:05:54;W;Directory monitor has encountered a problem, will retry after 1000 seconds.;


at 13:05:54 the problem occured,
and at 13.22.34 - this is exactly 16,5minutes = 1000 seconds later -  the next try found the Network resource reachable again and was able to watch the directory again:

Quote:
2014-01-22 13:22:34;I;Starting to monitor the directory;


Everthing looks good as you have configured it this was.


Now you need to know that if you use the Fast Monitoring Method Windows at the watched computer informs WatchDirectory about the detected changes. When the network connection is dropped, this notification can get lost, so WatchDirectory never knows about the Change - and does not process anything.

I recommend to change the monitor method into "polling" with an reasonable intervall. With this setting WatchDirectory itself will scan the target and found the changes happened during the network connection was interupted.

Back to top
 

Viele Grüße / Best regards
Dirk - GdP Software

dirk [at] gdpsoftware [dot] com
http://blog-de.gdpsoftware.com
Webseite: http://www.gdpsoftware.com
WWW WWW  
IP Logged
 
Ruud
YaBB Newbies
*
Offline



Posts: 18
Kruiningen
Re: Error code 64
Reply #8 - Jan 23rd, 2014 at 2:46pm
 
We where using the Fast Monitoring Method.
That the event could be lost I understand but new events are not triggered even do there are new files created.

I would except the task to reconnect to the drive again..
Back to top
 

Kind regards,

Ruud
 
IP Logged
 
Dirk
YaBB Administrator
*****
Offline



Posts: 659
South Germany
Re: Error code 64
Reply #9 - Jan 23rd, 2014 at 2:50pm
 
The task does reconnect to the network drive, the log you send confirms this:

Quote:
2014-01-22 13:22:34;I;Starting to monitor the directory;


Please try the polling method to see if it solves the problem.
Back to top
 

Viele Grüße / Best regards
Dirk - GdP Software

dirk [at] gdpsoftware [dot] com
http://blog-de.gdpsoftware.com
Webseite: http://www.gdpsoftware.com
WWW WWW  
IP Logged
 
Gert
YaBB Administrator
*****
Offline



Posts: 2233
The Netherlands
Re: Error code 64
Reply #10 - Jan 24th, 2014 at 8:10am
 
Dirk is correct.

When you use the "Default" or "Fast" monitoring method monitoring a network drive, you have a very complex situation.
computer-1 (running WD)
network
computer-2 (host of the network drive)

The default and fast methods need all 3 parts (comp-1 & 2 and the network) to reliably inform WD of any events. In the above case, the task *CAN NOT* detect if something is wrong when computer-2 disconnects its handle and will "forever" wait on its local handle (on comp-1) for new event info.

The "polling" and "file age" monitoring methods work in a totally different way and can detect those kind of issues (and restart to monitor).

Back to top
 

Gert Rijs - gert (at) gdpsoftware (dot) com
Blog: http://blog-en.gdpsoftware.com/
End Alzheimer's: http://www.alz.org&&...
WWW WWW GdPSoftware  
IP Logged
 
Ruud
YaBB Newbies
*
Offline



Posts: 18
Kruiningen
Re: Error code 64
Reply #11 - Jan 24th, 2014 at 8:12am
 
Thanks for the explanation I will change it to polling.

Best regards,

Ruud
Back to top
 

Kind regards,

Ruud
 
IP Logged
 
Page Index Toggle Pages: 1