[Box Backup] Failed to setup location

E.W. Peter Jalajas boxbackup@fluffy.co.uk
Fri, 31 Aug 2007 14:11:29 -0700 (PDT)


Hi Chris,

We just discovered the same problem on another client server (with Box Backup 1781 installed on
Windows Server 2003; we can't backup from a share, with the same error messages re "No such file
or directory").  As we flailed around on it, we got these messages in the Event Viewer (I may have
pasted the first two events in the wrong order below):

Event Type:	Warning
Event Source:	Box Backup (bbackupd)
Event Category:	None
Event ID:	1
Date:		8/31/2007
Time:		2:09:21 PM
User:		N/A
Computer:	SERVER2000
Description:
Failed to stat location: Z:\Admin: Permission denied 

Event Type:	Warning
Event Source:	Box Backup (bbackupd)
Event Category:	None
Event ID:	1
Date:		8/31/2007
Time:		2:09:21 PM
User:		N/A
Computer:	SERVER2000
Description:
Failed to open 'Z:\Admin': The network name cannot be found. (67) 

Event Type:	Warning
Event Source:	Box Backup (bbackupd)
Event Category:	None
Event ID:	1
Date:		8/31/2007
Time:		2:09:21 PM
User:		N/A
Computer:	SERVER2000
Description:
Exception thrown: CommonException(OSFileError) at BackupDaemon.cpp(1703) 

At another customer, we have a version 784 client backing up from a remote share no problem, so
something broke sometime after 784.   

We tried changing the remote share Path line in bbackupd.conf to lowercase, we started getting
some weird network errors (109, 67).  Are you handling case correctly when parsing the Path line? 


(We of course can write to the Z: drive and open it in Windows Explorer.  Box Backup is running as
a Domain Admin with Full Control on the share.)

(We tried various combinations of Box Backup on Windows 2000/Windows 2003 with the shared drive on
those same OSs, but didn't learn anything.  The one that is working happens to have version 784
running on Win2K backing up from a share on Win2K3.)

Maybe this is a DNS/NetBIOS problem?  We stumbled across this page:
http://support.microsoft.com/kb/875441
See the section on "Method 1: Increase the value of the LmhostsTimeout registry entry"
If you think it might help, let me know and we can try to experiment with that.

Sorry, but I think that this is a showstopper for 0.11 (if it's not simply operator error on my
part).

Thanks, Chris.
Pete

--- "E.W. Peter Jalajas" <pjalajas@tebucosafe.com> wrote:

> Hi Chris, 
> 
> Did you get this one:
> http://lists.warhead.org.uk/pipermail/boxbackup/2007-August/003731.html
> 
> Thanks,
> Pete