Agreed Troy! Add the .exe to the path name. I ran into this very
same issue 'assuming' the extension would otto-magically be added. So
much for assuming
Erich
On Jan 19, 2007, at 12:40 AM, Troy Daniels wrote:
Hi Scott,
I might be completely wrong but have you tried to append .exe
This is what you said Erich Prinz
Agreed Troy! Add the .exe to the path name. I ran into this very
same issue 'assuming' the extension would otto-magically be added. So
much for assuming
Erich
On Jan 19, 2007, at 12:40 AM, Troy Daniels wrote:
Hi Scott,
I might be completely wrong
Scott Ruckh wrote:
Possibly the environment/context that the Bacula FD runs under is
different then the user I am using to run the .BAT file. The security on
the actual files appears to be correct for the SYSTEM user, which is what
I believe is the context for the Bacula FD.
In another
On Friday 19 January 2007 16:30, Scott Ruckh wrote:
This is what you said Erich Prinz
Agreed Troy! Add the .exe to the path name. I ran into this very
same issue 'assuming' the extension would otto-magically be added. So
much for assuming
Erich
On Jan 19, 2007, at 12:40 AM,
On Thu, 18 Jan 2007 20:23:38 -0700 (MST), Scott Ruckh said:
Importance: Normal
I am trying to call a .BAT file using ClientRunBeforeJob. The config used
to work fine before upgrading the Windows FD 2.0.1.
It looks like the syntax in my bacula-dir.conf file is correct. It looks
like the
This is what you said Martin Simmons
On Thu, 18 Jan 2007 20:23:38 -0700 (MST), Scott Ruckh said:
Importance: Normal
I am trying to call a .BAT file using ClientRunBeforeJob. The config
used
to work fine before upgrading the Windows FD 2.0.1.
It looks like the syntax in my bacula-dir.conf
On Friday 19 January 2007 22:55, Martin Simmons wrote:
On Thu, 18 Jan 2007 20:23:38 -0700 (MST), Scott Ruckh said:
Importance: Normal
I am trying to call a .BAT file using ClientRunBeforeJob. The config used
to work fine before upgrading the Windows FD 2.0.1.
It looks like the
I am trying to call a .BAT file using ClientRunBeforeJob. The config used
to work fine before upgrading the Windows FD 2.0.1.
It looks like the syntax in my bacula-dir.conf file is correct. It looks
like the .BAT file is being called, and for some reason there is a problem
with the .BAT file.
Hi Scott,
I might be completely wrong but have you tried to append .exe to the
ntbackup command?
On my systems at least the full path is c:\WINDOWS\system32\ntbackup.exe
Microsoft normally tries to be nice and append the .exe extension
automatically, but something may have changed in the
On Friday 19 January 2007 04:23, Scott Ruckh wrote:
I am trying to call a .BAT file using ClientRunBeforeJob. The config used
to work fine before upgrading the Windows FD 2.0.1.
Are you saying that this worked in version 2.0.0 and is broken in 2.0.1?
There was a change in the finding the
10 matches
Mail list logo