0x1f ntbackup

[Evan Camilleri]

ntbackup returned code 0x1f when running from scheduler

when running from ntbackup it works but asks for prompts!

Evan Camilleri

[Miha Pihler]

Hi Evan,

this error usually means that destination folder can't be accessed (e.g. due
to permissions or destination folder does not exist).

Make sure that account that will run the backup has sufficient permissions
on the folder (write permissions on folder and e.g. share) where the backup
will be stored and make sure that destination folder (or share) actually
exists...

Mike

"Evan Camilleri" <[email protected]> wrote in message
news:%[email protected]...
> ntbackup returned code 0x1f when running from scheduler
>
> when running from ntbackup it works but asks for prompts!
>
> Evan Camilleri
>

[Evan Camilleri]

thanks, i found in the log file that ntbackup was trying to find backup
definition xyz.bkf, where the name was 'abc xyz.bkf'.

I think it is a bug in scheduler with backup where there is a space in bkf
name!!!


Evan Camilleri


"Miha Pihler" <[email protected]> wrote in message
news:%23Ncx%[email protected]...
> Hi Evan,
>
> this error usually means that destination folder can't be accessed (e.g.
> due to permissions or destination folder does not exist).
>
> Make sure that account that will run the backup has sufficient permissions
> on the folder (write permissions on folder and e.g. share) where the
> backup will be stored and make sure that destination folder (or share)
> actually exists...
>
> Mike
>
> "Evan Camilleri" <[email protected]> wrote in message
> news:%[email protected]...
>> ntbackup returned code 0x1f when running from scheduler
>>
>> when running from ntbackup it works but asks for prompts!
>>
>> Evan Camilleri
>>
>
>

[Miha Pihler]

Evan,

If you use spaces in names you have to put them in brackets. E.g. c:\My
Folder\Daily Backup\Friday BKF file would then be "c:\My Folder\Daily
Backup\Friday BKF file". If you don't do it, system will look for location
c:\My

Mike

"Evan Camilleri" <[email protected]> wrote in message
news:%[email protected]...
> thanks, i found in the log file that ntbackup was trying to find backup
> definition xyz.bkf, where the name was 'abc xyz.bkf'.
>
> I think it is a bug in scheduler with backup where there is a space in bkf
> name!!!
>
>
> Evan Camilleri
>
>
> "Miha Pihler" <[email protected]> wrote in message
> news:%23Ncx%[email protected]...
>> Hi Evan,
>>
>> this error usually means that destination folder can't be accessed (e.g.
>> due to permissions or destination folder does not exist).
>>
>> Make sure that account that will run the backup has sufficient
>> permissions on the folder (write permissions on folder and e.g. share)
>> where the backup will be stored and make sure that destination folder (or
>> share) actually exists...
>>
>> Mike
>>
>> "Evan Camilleri" <[email protected]> wrote in message
>> news:%[email protected]...
>>> ntbackup returned code 0x1f when running from scheduler
>>>
>>> when running from ntbackup it works but asks for prompts!
>>>
>>> Evan Camilleri
>>>
>>
>>
>
>

[Evan Camilleri]

i did, and it took the last part!


"Miha Pihler" <[email protected]> wrote in message
news:uqPYi%[email protected]...
> Evan,
>
> If you use spaces in names you have to put them in brackets. E.g. c:\My
> Folder\Daily Backup\Friday BKF file would then be "c:\My Folder\Daily
> Backup\Friday BKF file". If you don't do it, system will look for location
> c:\My
>
> Mike
>
> "Evan Camilleri" <[email protected]> wrote in message
> news:%[email protected]...
>> thanks, i found in the log file that ntbackup was trying to find backup
>> definition xyz.bkf, where the name was 'abc xyz.bkf'.
>>
>> I think it is a bug in scheduler with backup where there is a space in
>> bkf name!!!
>>
>>
>> Evan Camilleri
>>
>>
>> "Miha Pihler" <[email protected]> wrote in message
>> news:%23Ncx%[email protected]...
>>> Hi Evan,
>>>
>>> this error usually means that destination folder can't be accessed (e.g.
>>> due to permissions or destination folder does not exist).
>>>
>>> Make sure that account that will run the backup has sufficient
>>> permissions on the folder (write permissions on folder and e.g. share)
>>> where the backup will be stored and make sure that destination folder
>>> (or share) actually exists...
>>>
>>> Mike
>>>
>>> "Evan Camilleri" <[email protected]> wrote in message
>>> news:%[email protected]...
>>>> ntbackup returned code 0x1f when running from scheduler
>>>>
>>>> when running from ntbackup it works but asks for prompts!
>>>>
>>>> Evan Camilleri
>>>>
>>>
>>>
>>
>>
>
>

[Miha Pihler]

Evan,

If it doesn't work, can you post whole command that you use to perform
Backup...

Mike

"Evan Camilleri" <[email protected]> wrote in message
news:%[email protected]...
>i did, and it took the last part!
>
>
> "Miha Pihler" <[email protected]> wrote in message
> news:uqPYi%[email protected]...
>> Evan,
>>
>> If you use spaces in names you have to put them in brackets. E.g. c:\My
>> Folder\Daily Backup\Friday BKF file would then be "c:\My Folder\Daily
>> Backup\Friday BKF file". If you don't do it, system will look for
>> location c:\My
>>
>> Mike
>>
>> "Evan Camilleri" <[email protected]> wrote in message
>> news:%[email protected]...
>>> thanks, i found in the log file that ntbackup was trying to find backup
>>> definition xyz.bkf, where the name was 'abc xyz.bkf'.
>>>
>>> I think it is a bug in scheduler with backup where there is a space in
>>> bkf name!!!
>>>
>>>
>>> Evan Camilleri
>>>
>>>
>>> "Miha Pihler" <[email protected]> wrote in message
>>> news:%23Ncx%[email protected]...
>>>> Hi Evan,
>>>>
>>>> this error usually means that destination folder can't be accessed
>>>> (e.g. due to permissions or destination folder does not exist).
>>>>
>>>> Make sure that account that will run the backup has sufficient
>>>> permissions on the folder (write permissions on folder and e.g. share)
>>>> where the backup will be stored and make sure that destination folder
>>>> (or share) actually exists...
>>>>
>>>> Mike
>>>>
>>>> "Evan Camilleri" <[email protected]> wrote in message
>>>> news:%[email protected]...
>>>>> ntbackup returned code 0x1f when running from scheduler
>>>>>
>>>>> when running from ntbackup it works but asks for prompts!
>>>>>
>>>>> Evan Camilleri
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

[Evan Camilleri]

do not worry

i replaced space with _ and now it works

Thanks anyway for the help


Evan

"Miha Pihler" <[email protected]> wrote in message
news:%[email protected]...
> Evan,
>
> If it doesn't work, can you post whole command that you use to perform
> Backup...
>
> Mike
>
> "Evan Camilleri" <[email protected]> wrote in message
> news:%[email protected]...
>>i did, and it took the last part!
>>
>>
>> "Miha Pihler" <[email protected]> wrote in message
>> news:uqPYi%[email protected]...
>>> Evan,
>>>
>>> If you use spaces in names you have to put them in brackets. E.g. c:\My
>>> Folder\Daily Backup\Friday BKF file would then be "c:\My Folder\Daily
>>> Backup\Friday BKF file". If you don't do it, system will look for
>>> location c:\My
>>>
>>> Mike
>>>
>>> "Evan Camilleri" <[email protected]> wrote in message
>>> news:%[email protected]...
>>>> thanks, i found in the log file that ntbackup was trying to find backup
>>>> definition xyz.bkf, where the name was 'abc xyz.bkf'.
>>>>
>>>> I think it is a bug in scheduler with backup where there is a space in
>>>> bkf name!!!
>>>>
>>>>
>>>> Evan Camilleri
>>>>
>>>>
>>>> "Miha Pihler" <[email protected]> wrote in message
>>>> news:%23Ncx%[email protected]...
>>>>> Hi Evan,
>>>>>
>>>>> this error usually means that destination folder can't be accessed
>>>>> (e.g. due to permissions or destination folder does not exist).
>>>>>
>>>>> Make sure that account that will run the backup has sufficient
>>>>> permissions on the folder (write permissions on folder and e.g. share)
>>>>> where the backup will be stored and make sure that destination folder
>>>>> (or share) actually exists...
>>>>>
>>>>> Mike
>>>>>
>>>>> "Evan Camilleri" <[email protected]> wrote in message
>>>>> news:%[email protected]...
>>>>>> ntbackup returned code 0x1f when running from scheduler
>>>>>>
>>>>>> when running from ntbackup it works but asks for prompts!
>>>>>>
>>>>>> Evan Camilleri
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

[=?Utf-8?B?WWlrZQ==?=]

OK, I'll supply my command line, in the hopes it will help me and others in
the future:

C:\WINDOWS\system32\ntbackup.exe backup "@d:\masters\usdewilco1r01.bks" /d
"DIFF tape #1 - Treasury cluster shared disk" /v:no /r:no /rs:no /hc:on /m
differential /j "DIFF shares backup" /l:s /a /t "DIFF tape #1 - Treasury
cluster shared disk"

Just to recap my similar situation. I have a backup job that I want to run
every morning. If I enter the above at the command line, the backup job
kicks off and runs no problem. I am a local admin on this box. When I try
to schedule this same job, using my account or another local administrator on
the box, I get the 0x1f last result.

Like you, I figure this is some sort of permissions issue, but it won't run
- even when I set the job to use my account credentials. I guess something
must be wrong with the scheduled job, but I cannot tell what.

Any ideas?

"Miha Pihler" wrote:

> Evan,
>
> If it doesn't work, can you post whole command that you use to perform
> Backup...
>
> Mike
>
> "Evan Camilleri" <[email protected]> wrote in message
> news:%[email protected]...
> >i did, and it took the last part!
> >
> >
> > "Miha Pihler" <[email protected]> wrote in message
> > news:uqPYi%[email protected]...
> >> Evan,
> >>
> >> If you use spaces in names you have to put them in brackets. E.g. c:\My
> >> Folder\Daily Backup\Friday BKF file would then be "c:\My Folder\Daily
> >> Backup\Friday BKF file". If you don't do it, system will look for
> >> location c:\My
> >>
> >> Mike
> >>
> >> "Evan Camilleri" <[email protected]> wrote in message
> >> news:%[email protected]...
> >>> thanks, i found in the log file that ntbackup was trying to find backup
> >>> definition xyz.bkf, where the name was 'abc xyz.bkf'.
> >>>
> >>> I think it is a bug in scheduler with backup where there is a space in
> >>> bkf name!!!
> >>>
> >>>
> >>> Evan Camilleri
> >>>
> >>>
> >>> "Miha Pihler" <[email protected]> wrote in message
> >>> news:%23Ncx%[email protected]...
> >>>> Hi Evan,
> >>>>
> >>>> this error usually means that destination folder can't be accessed
> >>>> (e.g. due to permissions or destination folder does not exist).
> >>>>
> >>>> Make sure that account that will run the backup has sufficient
> >>>> permissions on the folder (write permissions on folder and e.g. share)
> >>>> where the backup will be stored and make sure that destination folder
> >>>> (or share) actually exists...
> >>>>
> >>>> Mike
> >>>>
> >>>> "Evan Camilleri" <[email protected]> wrote in message
> >>>> news:%[email protected]...
> >>>>> ntbackup returned code 0x1f when running from scheduler
> >>>>>
> >>>>> when running from ntbackup it works but asks for prompts!
> >>>>>
> >>>>> Evan Camilleri
> >>>>>
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >
> >
>
>
>

[=?Utf-8?B?WWlrZQ==?=]

OK, I'll supply my command line, in the hopes it will help me and others in
the future:

C:\WINDOWS\system32\ntbackup.exe backup "@d:\masters\usdewilco1r01.bks" /d
"DIFF tape #1 - Treasury cluster shared disk" /v:no /r:no /rs:no /hc:on /m
differential /j "DIFF shares backup" /l:s /a /t "DIFF tape #1 - Treasury
cluster shared disk"

Just to recap my similar situation. I have a backup job that I want to run
every morning. If I enter the above at the command line, the backup job
kicks off and runs no problem. I am a local admin on this box. When I try
to schedule this same job, using my account or another local administrator on
the box, I get the 0x1f last result.

Like you, I figure this is some sort of permissions issue, but it won't run
- even when I set the job to use my account credentials. I guess something
must be wrong with the scheduled job, but I cannot tell what.

Any ideas?

"Miha Pihler" wrote:

> Evan,
>
> If it doesn't work, can you post whole command that you use to perform
> Backup...
>
> Mike
>
> "Evan Camilleri" <[email protected]> wrote in message
> news:%[email protected]...
> >i did, and it took the last part!
> >
> >
> > "Miha Pihler" <[email protected]> wrote in message
> > news:uqPYi%[email protected]...
> >> Evan,
> >>
> >> If you use spaces in names you have to put them in brackets. E.g. c:\My
> >> Folder\Daily Backup\Friday BKF file would then be "c:\My Folder\Daily
> >> Backup\Friday BKF file". If you don't do it, system will look for
> >> location c:\My
> >>
> >> Mike
> >>
> >> "Evan Camilleri" <[email protected]> wrote in message
> >> news:%[email protected]...
> >>> thanks, i found in the log file that ntbackup was trying to find backup
> >>> definition xyz.bkf, where the name was 'abc xyz.bkf'.
> >>>
> >>> I think it is a bug in scheduler with backup where there is a space in
> >>> bkf name!!!
> >>>
> >>>
> >>> Evan Camilleri
> >>>
> >>>
> >>> "Miha Pihler" <[email protected]> wrote in message
> >>> news:%23Ncx%[email protected]...
> >>>> Hi Evan,
> >>>>
> >>>> this error usually means that destination folder can't be accessed
> >>>> (e.g. due to permissions or destination folder does not exist).
> >>>>
> >>>> Make sure that account that will run the backup has sufficient
> >>>> permissions on the folder (write permissions on folder and e.g. share)
> >>>> where the backup will be stored and make sure that destination folder
> >>>> (or share) actually exists...
> >>>>
> >>>> Mike
> >>>>
> >>>> "Evan Camilleri" <[email protected]> wrote in message
> >>>> news:%[email protected]...
> >>>>> ntbackup returned code 0x1f when running from scheduler
> >>>>>
> >>>>> when running from ntbackup it works but asks for prompts!
> >>>>>
> >>>>> Evan Camilleri
> >>>>>
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >
> >
>
>
>