Schedule PS1 does not work 1

[spazman]

Okay I have a powershell script, it backs up an SQL DB to two locations. It has one command line parameter. If its set to "Midday" it only copies the backup to one location.

The script without parameter runs as a scheduled task. It I added the parameter it doesn't run.

If I run the same command powershell c:\PS_Scripts\backup-db.ps1 "Midday" from Start |Run or a batch file it works. If I schedule the batch file, or the powershell line it doesn't work.

I have tried

powershell C:\PS_Scripts\backup-db.ps1 "Midday"
powershell "C:\PS_Scripts\backup-db.ps1 "Midday""
powershell C:\PS_Scripts\backup-db.ps1 Midday

same line in the batch file, they all run manually but not in a sceduled task.

 

[Geates]

I can't remember why exactly but I read that powershell scripts may need to be run from a .vbs file. The Run dialog is more of a command interpreter. Perhaps, what's why it work there and not as a scheduled task.

scheduled task: 'backup.vbs'

set objShell = CreateObject("Wscript.Shell")
objShell.Run("powershell.exe -noexit c:\PS_Scripts\backup-db.ps1 Midday")

-Geates

 

[crobin1]

See if these blog posts from Sapien and post at Microsoft Discussion Groups help:

http://blog.sapien.com/index.php/2006/12/20/schedule-hidden-powershell-tasks/

http://blog.sapien.com/index.php/2006/12/26/more-fun-with-scheduled-powershell/

http://www.microsoft.com/communitie...ba8-9fdf-310605b16ace&lang=en&cr=US&sloc=&p=3

 

[spazman]

Thanks for the posts. I will check them out and keep you in the loop, plus there may be stars to hand out!

 

[spazman]

Nothing will work.

I wrote a batch file that has Powershell <ScriptName>.ps1 if I double click the batch file, it runs, if I schedule it it runs, doesn;t really run and never terminates.

 

[crobin1]

OK, I've done a couple of tests on a system here. I wrote a .BAT file with the following command:

powershell -command "& 'd:\is\powershell\export-ip.ps1'"

The PS1 script uses the Quest AD cmdlets to export some information from Active Directory to a CSV file.

I verified that PowerShell was in the PATH environment variable. I then scheduled a job using the credentials of an account that had access to AD, and had the Quest snap-in loaded in its PowerShell profile. The job ran successfully and produced the expected CSV file. I then changed the job to use the credentials of another account. This second account has access to AD, but does not have the Quest snap-in loaded in its PowerShell profile. The job ran and completed, but no CSV file was produced. I expected this since PowerShell wouldn't know the Quest command.

So, some questions for you:
1. In the batch file did you follow the syntax given above, using the -command switch?
2. Is PowerShell in the system-wide PATH environment variable? If not you will need to specify the full path to the PowerShell executable
3. Does the account used to run the scheduled task have the necessary permissions to SQL/file shares/backup devices/etc?
4. Does the PS1 script use only native PowerShell (or built-in Windows) commands/cmdlets, or does it rely on 3rd-party cmdlets? If it relies on 3rd-party commands, does the account used to run the job have that snap-in loaded in its PowerShell profile?

Scheduling PowerShell does work, we just need to figure out what's different/missing in your environment.

 

[crobin1]

Sorry, it would also help if I read your original post a little more closely. I missed that it only failed with the parameter. Try the following in your batch file:

powershell -command "& 'C:\PS_Scripts\backup-db.ps1' Midday"

or

powershell -command "& {C:\PS_Scripts\backup-db.ps1 Midday}"

 

[spazman]

I ended up using

powershell -command "& {C:\PS_Scripts\backup-db.ps1 Midday}" and it worked.

 

[SilviaS]

Have a look here

http://blog.meigh.eu/2010/02/24/running-powershell-script-as-scheduled-task.aspx

http://blog.meigh.eu

 

[58sniper]

I run a ton of PowerShell scripts as scheduled tasks. See my blog post at

http://www.ucblogs.net/blogs/exchan...g-PowerShell-scripts-via-Scheduled-Tasks.aspx

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/