1314: A required privilege is not held by the client

[Charles Braun]

This is actually happening on a 2003 server, but there is not 2003 server
group, so I hope this is a good place for the question:

I have a 2003 server that I am trying to backup with Veritas Backup Exec
9.1. Because of services running on other servers that I backup, I use pre
and post backup commands within Veritas. Before any server is backed up,
Veritas runs c:\prebackup.bat and after the job is complete Veritas runs
c:\postbackup.bat on each server. These batch files are on the local C drive
of every server in my environment. Many of these contain commands to stop
and start Oracle services and other DB services that can't be running while
the backup is happening. For those servers without services needing to be
stopped and started, the batch files only contain an exit command.

This works very well on all my NT4 and 2000 servers. We have 1 2003 server
in our data center and this just does not work on this one server. The error
I get is "Error: Could not start Pre Job Command < c:\prebackup.bat >. Error
(1314): A required privilege is not held by the client."

The file definately exists and the Backup Exec service account is a member
of Domain Admins.

Any thoughts on what the problem might be? Please reply to the group (for
everyone's benefit), but also via e-mail if you would as we block NNTP. (I
had to open it up just long enough to post this question)

Thanks

 

[Pegasus \(MVP\)]

This is actually happening on a 2003 server, but there is not 2003 server
group, so I hope this is a good place for the question:

I have a 2003 server that I am trying to backup with Veritas Backup Exec
9.1. Because of services running on other servers that I backup, I use pre
and post backup commands within Veritas. Before any server is backed up,
Veritas runs c:\prebackup.bat and after the job is complete Veritas runs
c:\postbackup.bat on each server. These batch files are on the local C drive
of every server in my environment. Many of these contain commands to stop
and start Oracle services and other DB services that can't be running while
the backup is happening. For those servers without services needing to be
stopped and started, the batch files only contain an exit command.

This works very well on all my NT4 and 2000 servers. We have 1 2003 server
in our data center and this just does not work on this one server. The error
I get is "Error: Could not start Pre Job Command < c:\prebackup.bat >. Error
(1314): A required privilege is not held by the client."

The file definately exists and the Backup Exec service account is a member
of Domain Admins.

Any thoughts on what the problem might be? Please reply to the group (for
everyone's benefit), but also via e-mail if you would as we block NNTP. (I
had to open it up just long enough to post this question)

Thanks

The message simply means that the account under
which you run the batch file has insufficient privileges
to execute either the batch file itself, or one of the
commands inside the batch file. To resolve the issue,
do this:
- Identifiy which command throws up the message.
- Execute the batch file in the foreground to see if
the problem still occurs.
- If it no longer occurs, consider the difference between
running the job in the foreground and in the background.

 

[dcdon]

Pegasus,

How's the ole hammer hanging buddy.(I grew up in a family of
developer/builders)(Could said how's the ole mouse working)

Forgive me, remember the Saturday you got snokered, well, I'm glad I have a spell
checker tonight.

Sure do miss getting to follow behind you guys and for the little good I've done in
here.

Just wanted to say hello.
Thanks again for the privilege of you guys letting me play in your sandbox.

friend,
don

This is actually happening on a 2003 server, but there is not 2003 server
group, so I hope this is a good place for the question:

I have a 2003 server that I am trying to backup with Veritas Backup Exec
9.1. Because of services running on other servers that I backup, I use pre
and post backup commands within Veritas. Before any server is backed up,
Veritas runs c:\prebackup.bat and after the job is complete Veritas runs
c:\postbackup.bat on each server. These batch files are on the local C drive
of every server in my environment. Many of these contain commands to stop
and start Oracle services and other DB services that can't be running while
the backup is happening. For those servers without services needing to be
stopped and started, the batch files only contain an exit command.

This works very well on all my NT4 and 2000 servers. We have 1 2003 server
in our data center and this just does not work on this one server. The error
I get is "Error: Could not start Pre Job Command < c:\prebackup.bat >. Error
(1314): A required privilege is not held by the client."

The file definately exists and the Backup Exec service account is a member
of Domain Admins.

Any thoughts on what the problem might be? Please reply to the group (for
everyone's benefit), but also via e-mail if you would as we block NNTP. (I
had to open it up just long enough to post this question)

Thanks

The message simply means that the account under
which you run the batch file has insufficient privileges
to execute either the batch file itself, or one of the
commands inside the batch file. To resolve the issue,
do this:
- Identifiy which command throws up the message.
- Execute the batch file in the foreground to see if
the problem still occurs.
- If it no longer occurs, consider the difference between
running the job in the foreground and in the background.

 

[Charles Braun]

The message simply means that the account under
which you run the batch file has insufficient privileges
to execute either the batch file itself, or one of the
commands inside the batch file. To resolve the issue,
do this:
- Identifiy which command throws up the message.
- Execute the batch file in the foreground to see if
the problem still occurs.
- If it no longer occurs, consider the difference between
running the job in the foreground and in the background.

Pegasus,

As I mentioned in my original message, the account under which the batch
files is being run is a Domain Admin account.

The batch file in question is one of those that is null in that it only
contains only a single command: "exit" a command that even a "Guest" can
run. This is because I have told Backup Exec to run the pre and post
commands on every server and if the command fails then to discontinue the
backup job because corruption can occur on those server which I am backing
up databases should the services not stop properly. For servers without
databases etc being backed up, such as this Windows 2003 server, the batch
file has only the exit command.

Any other thoughts?

BTW, I can log in locally and run the batch file.

 

[Pegasus \(MVP\)]

NNTP.

Pegasus,

As I mentioned in my original message, the account under which the batch
files is being run is a Domain Admin account.

The batch file in question is one of those that is null in that it only
contains only a single command: "exit" a command that even a "Guest" can
run. This is because I have told Backup Exec to run the pre and post
commands on every server and if the command fails then to discontinue the
backup job because corruption can occur on those server which I am backing
up databases should the services not stop properly. For servers without
databases etc being backed up, such as this Windows 2003 server, the batch
file has only the exit command.

Any other thoughts?

BTW, I can log in locally and run the batch file.

I'm puzzled. Here are a few thoughts - just a stab in the
dark:
- Have you checked the access permissions for the folder
where your one-line batch job resides?
- Do you fully qualify the drive, folder and name of your
batch file?
- When you run gpedit.msc, there is an item somewhere
that says something like "log on as a batch job". I would
play with that one.
- I would also run some other command to see if the
restriction applies to batch files only, or to any file.
For example, you could run this command, then check
the result:
c:\winnt\system32\attrib.exe +h c:\winnt\system32\attrrib.exe

 

[Charles Braun]

I'm puzzled. Here are a few thoughts - just a stab in the
dark:
- Have you checked the access permissions for the folder
where your one-line batch job resides?
- Do you fully qualify the drive, folder and name of your
batch file?
- When you run gpedit.msc, there is an item somewhere
that says something like "log on as a batch job". I would
play with that one.
- I would also run some other command to see if the
restriction applies to batch files only, or to any file.
For example, you could run this command, then check
the result:
c:\winnt\system32\attrib.exe +h c:\winnt\system32\attrrib.exe

Pegasus,

Thank you for your suggestions and trying to help. I got an e-mail today
from Veritas though and they had the answer. Turns out the remote agent
service on the server being backed up was running as the domain admin
account when it should have been running under the local system account. I
made that change and it works now.

Thanks again.