Forum Discussion

Spencer_Simpson's avatar
Spencer_Simpson
Level 4
13 years ago

Error 1314 running powershell script as a post command

It seems simple enough: I'd like to run a PowerShell script as a post job command.   The script does what it should, but when I make it a post job command, Backup Exec refuses to run it, with the following message in the job history:

Error: Could not start Post Job Command < C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -nologo -noninteractive -file "blah.ps1" -test >. Error (1314): A required privilege is not held by the client.

I've searched around and found various suggestions in Symantec support and Technet, none of which seem to make a difference.  I'm backing up a user defined share because there's no way to put a remote agent on the remote server. This also means the media server's remote agent service has to run as a domain user to connect.

The post job command is configured to run on the backup exec media server.     The system logon account is a domain user, and all of the sevices run as te same account on the media server.

I'm not seeing any failure messages in the security log in Windows Event viewer, and the server is configured to audit all such failures.

Backing Up
Backup and Recovery
Backup Exec
Configuring
Troubleshooting
  • Backup_Exec1's avatar
    Backup_Exec1
    13 years ago
    Hi Q This also means the media server's remote agent service has to run as a domain user to connect. Remote agent service never should be ran on domain account ,it should always use local system account to run, so in your case it seems you running it on domain account ,please change it to local system account and try job again Thanks.
  • Backup_Exec1's avatar
    Backup_Exec1
    Level 6
    13 years ago
    Hi Q This also means the media server's remote agent service has to run as a domain user to connect. Remote agent service never should be ran on domain account ,it should always use local system account to run, so in your case it seems you running it on domain account ,please change it to local system account and try job again Thanks.
  • pkh's avatar
    pkh
    Moderator
    13 years ago

    I'm backing up a user defined share because there's no way to put a remote agent on the remote server.

    I don't understand.

    1) what OS is the remote server running that you cannot put a remote agent on it?  It is a NAS?

    2) What version of BE are you running?

    3) What is your Powershell script doing?

    4) If you are using your script to backup the share, why can't you backup the share in BE using its FQDN.

    5) Can you run the Powershell script when you are logged on as the BESA?

     

  • VJware's avatar
    VJware
    Level 6
    13 years ago

    Have you looked at this KB - http://www.symantec.com/business/support/index?page=content&id=TECH70754

  • Backup_Exec1's avatar
    Backup_Exec1
    Level 6
    13 years ago

    Hi

     

    I have already mention it quiet before, to run remote agent service using local system account.

     

    Thanks

  • VJware's avatar
    VJware
    Level 6
    13 years ago

    Yes, I did see that, however I intended to point out the KB article (the OP had mentioned he had looked at several posts/articles, was just checking if he checked Symwise as well or not)..

  • Spencer_Simpson's avatar
    Spencer_Simpson
    Level 4
    13 years ago

    1) It's a NAS (EMC VNXe). The granular access to the backup gained from backing up as a user defined share trumps the speed benefits of NDMP.

    2) 2012 but it also hapened in 2010 R3

    3) The script deletes the contents of the shared folder it just backed up (no agent, so no backup and delete jobs), taking care not to delete things that would corrupt the shared folder if they were deleted.

    4) N/A. I'm content to let Backup Exec do the backing up.

    5) Yes, it works perfectly.  A Technet article suggested editing local security policy to allow the BESA to "log on as part of the operating system"

  • Spencer_Simpson's avatar
    Spencer_Simpson
    Level 4
    13 years ago

    Yes, I saw that, but the script isn't for controlling Backup Exec.   I thought maybe changing the execution policy for CurrentUser would solve the problem but it didn't.

  • pkh's avatar
    pkh
    Moderator
    13 years ago

    @spencer - How about trying to run this simple script as a post-command?

    import-module "\program files\symantec\backup exec\modules\bemcli\bemcli"

    get-bejobhistory -fromlastjobrun -jobtype backup > C:\ps-output.txt

  • Spencer_Simpson's avatar
    Spencer_Simpson
    Level 4
    13 years ago

    Exactly the same error.  The system doesn't want to let the Remote Agent run powershell at all, never mind what's in the script.