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: 56 upon starting task (Read 6905 times)
chadcarpenter
YaBB Newbies
*
Offline



Posts: 6
Error Code: 56 upon starting task
Feb 23rd, 2006 at 10:34pm
 
Hi,

I am currently evaluating the WatchDirectory software and have quite a few tasks set up to make sure this software will do what we need to do before buying a couple of pro licenses.

I have WatchDirectory setup with 17 tasks all monitoring folders on a networked computer.  I currently have 10 of them running and they seem to be working just fine.  However, when I go to start another one, it gives me the below error message and immediately closes.

DMD - Can not monitor directory \\Networked Directory path CD: Error Code: 56
Description: The network BIOS command limit has been reached.

This happens seemingly independent of the order I open them in, so it appears I simply have too many connections open to the networked computer or something.  Is my assesment correct?  Is there a way around this?

Thanks for any help,
Chad
Back to top
 
 
IP Logged
 
Gert
YaBB Administrator
*****
Offline



Posts: 2239
The Netherlands
Re: Error Code: 56 upon starting task
Reply #1 - Feb 24th, 2006 at 5:49am
 
I believe this is part of some limitation that Microsoft has build into their non-server products (limit the number of incoming connections).
Perhaps [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;810886 this knowledge base article[/url] helps?

A future plugin for watchDirectory will allow you to combine tasks that monitor the same directory into 1 task. That may help to limit the number of connections (if your tasks watch the same directory on the network).

Gert
Back to top
« Last Edit: Feb 24th, 2006 at 7:32am by Gert »  

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
 
chadcarpenter
YaBB Newbies
*
Offline



Posts: 6
Re: Error Code: 56 upon starting task
Reply #2 - Feb 24th, 2006 at 3:18pm
 
Thanks for the response.  I checked out the article you linked to, but the registry keys mentioned in it do not exist on the three computers (including our Server2003 machine) that we have here, so I couldn't get anything useful out of it.

Do you know of a set max number of connections that Watch Directory can have to a networked computer, or does it change from situation to situation?  I currently have some tasks running with the "fast" monitor method and others using "default" simply because I don't really know the difference and when I wasn't allowed to run any more with fast monitoring, it did seem to allow some with default.

I guess my possible solutions are as follows:

- Put WD on the local computer with the directories to be monitored instead of monitoring over the network.
- Or try to combine tasks so I have fewer tasks running overall.
- Or try running all tasks on default monitoring.

Any other suggestions?

Thanks again,
Chad
Back to top
 
 
IP Logged
 
Gert
YaBB Administrator
*****
Offline



Posts: 2239
The Netherlands
Re: Error Code: 56 upon starting task
Reply #3 - Feb 24th, 2006 at 6:36pm
 
I would think that the Fast and Default methods put the same "burden" on network resources. One possible exception is that if you let WD monitor for directory and file events (on this page), the Fast method will have 2 network connections. The Default method always uses 1 connection.

Quote:
- Put WD on the local computer with the directories to be monitored instead of monitoring over the network.

If you have that option, it is the best. It also is the least burden on your network.

Quote:
Any other suggestions?


Depends on what your tasks are doing. If you don't want that info "public", feel free to e-mail me (gert at watchdirectory dot net) the details.

Gert

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
 
chadcarpenter
YaBB Newbies
*
Offline



Posts: 6
Re: Error Code: 56 upon starting task
Reply #4 - Feb 24th, 2006 at 8:30pm
 
I'm actually just trying to use WD to do stuff that Sorenson Squeeze is supposed to do for me.  Because of some odd Squeeze bugs, I'm having to use WD to sort video files into different watch folders for Squeeze to encode.  Then I'm using WD to ftp the output to my Windows Server 2003.

The reason I've kept WD on another computer is because Squeeze is processor intensive and I didn't want anything to interfere with it.  But now that I've run into this problem with connections and WD, I may have to move WD over to the same computer.

While typing this, I've just thought of a simple way to combine a bunch of the tasks I have into one by using the Sort task.  I'll go and try that and see how it works.
Back to top
 
 
IP Logged
 
Gert
YaBB Administrator
*****
Offline



Posts: 2239
The Netherlands
Re: Error Code: 56 upon starting task
Reply #5 - Feb 25th, 2006 at 5:17am
 
When you use the Fast monitoring method, WD runs extremely efficient. It doesn't need to scan the disk to find new/changed files as Windows will inform WD of the exact change. The polling and default methods always need to scan the disk.

So, if you compare remote access using the Default method with local access using the Fast method, you will probably find that Sorenson Squeeze is impacted more by the remote "WD" than by a local "WD".

An overview of the monitoring methods is available here: http://www.watchdirectory.net/wdhelp/help/wdnewconfigpage3.html

Gert
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
 
Page Index Toggle Pages: 1