Backup-GPO cmdlet errors in Task Scheduler

I have scheduled a simple script on my Windows Server 2012 domain controller to backup my group policies (separate from the System State backup). I ran the script manually, and it works as expected. I scheduled the script in Task Scheduler using a service
acct with domain admin privileges. Due to our domain policy settings, I had to select the "Do not store password" option on the job, otherwise the usual error regarding "no session" is presented. This means I have access to local resources
only (on the DC).
I also right-clicked the job and selected "run" and the job executes properly. However, when the job kicked off at the scheduled time on its own, it only ran partially. The date stamped backup folder was created, and it contained a partial "manifest.xml"
file which is created at every backup. The manifest only has the header in it, no other content such as GPO names and GUIDs.
In the Powershell transcript output, it generates an error when the Backup-GPO cmdlet runs:
Backup-Gpo : The system cannot open the device or file specified. (Exception from HRESULT: 0x8007006E)
The command is:
Backup-Gpo -All -Path $backup_dir\$date_stamp
And yes, I have selected to run the job without the user being logged in. Is it possible to backup domain GPOs without the credentials cached in the job? Are the GPOs considered a "local resource" on the domain controller?

Anna,
You are correct, if I disable that policy setting that I do not need to select "Do not store password" and the job runs fine.
However, the PowerShell script does run with the "Do not store password" option checked, it just normally fails when trying to access the policies to backup with a seemingly random error depending on the domain controller. Then, after 3 days of failures,
I checked this morning and it had run fine on two of three domain controllers. No changes to policy or the script or the job. It isn't cut and dried as to why it works or doesn't work.
I guess what I am ultimately looking for is a better description of what resources are still available using that setting ("Do not store password"); are ADDS related commands considered local resources on domain controllers, or do you always need a cached
credential?
Jim

Similar Messages

Issues with Backup-GPO Scheduled Task as a non-admin account

I'm having an issue trying to get a daily backup of domain GPO's from a non-administrative account. I'm using Powershell 2.0, the Backup-GPO cmdlet runs fine as a standard user, but when I run the same cmdlet with the same user, but with a scheduled task,
the backup does not produce valid output. The command I run is:
[batch file called by scheduled task]
powershell.exe d:\loj\psps.ps1
[psps.ps1]
import-module grouppolicy
backup-gpo -all -path d:\loj
The specific problem is, all other files created by the backup are created successfully except the 'gpreport.xml' file found directly under the folder identified by the backup ID. All of the subdirectories under DomainSysvol\GPO contain xml files with the
appropriate data, and the Backup.xml and bkupInfo.xml files are also created normally. The manifest.xml file is also created normally in the root directory.
The gpreport.xml file however is malformed. It contains only two bytes of data, FF FE.
The reason this is a problem is that the xml in the gpreport file can be used to restore whether the GPO is 'enforced' and also contains link data. Using this when restoring the GPO's makes the process a lot less painful.
Running the batch file while logged in interactively as the user removes the problem, without making them an administrator.
I've been using a test domain to investigate this, I tried adding the user in question to every local group except administrators, gave it full control to the destination folder for backups, the powershell executable, batch and ps1 files. Resultant set of
policy access has been granted (rsop.msc run-as the user tested fine). The scheduled task stores credentials (needs to run when the user is not already logged in) and runs with the highest privileges.
The only possibly related error I could find in the logs was this:
This error goes away if enough group memberships are added to the account or alternatively if this string is added to the security descriptor for the LanManServer service: (A;;GA;;;S-1-5-21-1191697313-1384311512-914143962-35706), which just adds
generic all to this account by referencing the SID. However, despite the fact that the error is no longer raised, the issue with the gpreport.xml file remains.
Does anyone have any ideas on why this is happening? At this point my best guess is something UAC related, since the gpreport.xml file is created like normal if the user is made an administrator on the local machine (I'd rather not do that in production).

Hi Fergubru,
Thanks for your posting.
To troubleshoot Task scheduled that a task ran, but the program that should have been executed did not run correctly.
As AZ said above, some programs require elevated privileges to run correctly. If a task is running a program that requires elevated privileges, ensure that the task runs with the highest privileges. You can set a task to run with the highest privileges
by changing the task's security options on the General tab of the Task Properties dialog box.
If a task program does not run correctly, check the history of the task for errors. For more information, see
View Task Properties and History.
For the Event ID 4656, this is an Audit log, This event will be Audit Success or Audit Failure depending on whether the user account under which the account is running has the requested permissions or not.
For more detailed information about Event ID 4656, please refer to this article:
http://www.ultimatewindowssecurity.com/securitylog/encyclopedia/event.aspx?eventid=4656
I hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Why won't this script run in task scheduler properly?

Hello,
I've created a script find all opened windows applications on the local computer. The script creates an html outfile to report the opened windows and who is logged in.
When I run this script from the Powershell ISE or from Powershell command line it works fine. When I schedule this script to run in windows Task Scheduler (either in Windows 7 or on Windows Server 2008) and I use 'Run only when user is logged in' the
script again runs fine and reports in the html file the opened windows.
But when I am logged into the server and I schedule this script to run in windows Task Scheduler (either in Windows 7 or on Windows Server 2008) and I use 'Run whether user is logged in or not' the script will run without error, it creates the html report,
but it does not list the opened windows applications That part of the report is missing.
Why would this happen? Do I need to change something in my script to make this script work whether or not someone is logged in?
Here is the script:
$a = "<style>"
$a = $a + "BODY{background-color:peachpuff;}"
$a = $a + "TABLE{border-width: 1px;border-style: solid;border-color: black;border-collapse: collapse;}"
$a = $a + "TH{border-width: 1px;padding: 0px;border-style: solid;border-color: black;background-color:thistle}"
$a = $a + "TD{border-width: 1px;padding: 0px;border-style: solid;border-color: black;background-color:PaleGoldenrod}"
$a = $a + "</style>"
get-wmiobject Win32_ComputerSystem | ConvertTo-HTML -head $a -body "<H2>Logged in UserID</H2>" -property username | Out-File C:\Powershell_Scripts\Test.htm ; Get-Process |where {$_.mainWindowTItle} |Select-Object name,mainwindowtitle | ConvertTo-HTML -head $a -body "<H2>Open Applications</H2>" | Out-File C:\Powershell_Scripts\Test.htm -Append
Thank you.

Its hard to get a full grasp of the errors from task scheduler. Try rewriting the Action portion of the Scheduled Task in a cmd prompt (with or without the elevated credentials). When the cmd line runs, the cmd host will convert to a black
powershell host and you will be able to read the errors.
C:\> powershell.exe -command { update-help }
or
C:\> powershell.exe -noprofile -file c:\scripts\dosomething.ps1
I solved a similar problem this week. When I ran my script from within powershell, all the required modules are normally present and the script ran fine. It was pretty clear which module I forgot to load at the beginning of the script once I could
watch it from start to finish
or, your script could dump the Error logs to a text file.
$Error | select * | out-file c:\errors.txt
Not the point. Look at the task scheduler history first. If the history is not enabled enable it. If it shows no error code then the script ran successfully but had an internal error.
There is only one place that an error can occur. This will trap it and set the exit code which will be visible in the event history:
$a=@'
<style>
BODY{
background-color:peachpuff;
TABLE{
border-width: 1px;
border-style: solid;
border-color: black;
border-collapse: collapse;
TH{
border-width: 1px;
padding: 0px;
border-style: solid;
border-color: black;
background-color:thistle;
TD{
border-width: 1px;
padding: 0px;
border-style: solid;
border-color: black;
background-color:PaleGoldenrod
</style>
Try{
$username=get-wmiobject Win32_ComputerSystem |%{$_.username}
$precontent="<H2>Logged in User: $username</H2><br/><H2>Open Applications</H2><br/>"
$html=Get-Process |where {$_.mainWindowTItle} -ErorAction Stop|
Select-Object name,mainwindowtitle |
ConvertTo-HTML -cssuri c:\scripts\style.css -preContent $precontent -body "<body bgcolor='peachpuff'/>"
$html | Out-File C:\Scripts\Test.htm -ErrorAction Stop
Catch{
exit 99
This is really an exercise in how to manage background tasks.
Using an error log is good assuming it is not the file system that you are having an issue with
¯\_(ツ)_/¯

Ability to "task schedule" via small utilities backup/optimize

Include small utilites with Lightroom that can be used with the system "task scheduler" that will perform catalogue backup and optimize on a user defined schedule.

(Replying to myself here no edit option) Is there a way to optimize the catalog via single command line or in a bat file with sqlite3.exe and/or Contig.exe?

Error when using Windows Task Scheduler in C#

I am using Windows Task Scheduler in my Visual C# application. I add the reference to C:\Windows\SysWOW64\taskschd.dll (on a 64-bit system), and Visual Studio creates a COM wrapper Interop.TaskScheduler.dll. Ths works fine on Windows 7. However, when
I run on Windows 8.1, I get the following error:
Unable to cast COM object of type 'System.__ComObject' to interface type 'TaskScheduler.IExecAction'.
This operation failed because the QueryInterface call on the COM component for the interface with IID
'{4C3D624D-FD6B-49A3-B9B7-09CB3CD3F047}' failed due to the following error:
No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).
I noticed that on Windows 7, the above GUID exists in the registry under HKEY_CLASSES_ROOT\Interface, with the value "IExecAction". But on Windows 8.1, there is no such GUID, and no key with value "IExecAction". I use IExecAction
in my code.
When I develop on Windows 8.1, the program compiles, but at runtime I get the above error.

Hello tomszms,
Here is a blog related to this issue and the troubleshoot steps of his error is very useful for your case, so please check for it:
http://blogs.msdn.com/b/smondal/archive/2012/10/02/unable-to-cast-com-object-of-type-system-comobject-to-interface-type-microsoft-visualstudio-ole-interop-iserviceprovider.aspx
Please try use the same way to track the logs and then try use the regsvr32
on your Win 8 machine to re-register that dll and see the result.
Best regards,
Barry
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Incremental and Full backups using WBADMIN and Task Scheduler in Server 2008 R2

I'd like to create an automated rotating schedule of backups using wbadmin and task scheduler, which would backup Bare Metal Recovery; System State; Drive C: and D: to a Network Share in a pattern like this:
Monday - Incremental, overwrite last Monday's
Tuesday - Incremental, overwrite last Tuesday's
Wednesday - Incremental, overwrite last Wednesday's
Thursday - Incremental, overwrite last Thursday's
Friday - Incremental overwrite last Friday's
Saturday - Full, overwrite last Saturday's
I need to use the wbadmin commands within the Task Scheduler and do not know any of the required Syntax to make sure everything goes smoothly, I do not want to do this through the CMD.

I know each backup for the previous corresponding day will be replaced, how do you figure I wont be able to do incremental backups...
Because incremental backup is based on Volume Shadow Copy (VSS) feature and due to Windows Server 2008 R2 limitations (this limitation is resolved in Windows 8) only one version of backed up data can be stored in a shared folder. So the
result is that every time you back up some data on a shared folder, you actually creating a full backup of them.
is it not supported through task scheduler?
The Task Scheduler is only a feature that does the tasks that you have defined for it. Actually it runs the
wbadmin command that runs on an operating system with the mentioned limitation.
I know you can do Incremental backups through Windows Server Backup, but my limitation using that is I cant setup multiple backups.
Yes, you are right. Windows Server Backup feature in Windows Server 2008/2008 R2 has not this functionality (although
ntbackup in Windows XP and Windows Server 2003 had this functionality). So, the only workaround to this limitation is through using Task Scheduler feature with wbadmin command. For more information see the following article:
http://blogs.technet.com/b/filecab/archive/2009/04/13/customizing-windows-server-backup-schedule.aspx
So are you saying that even though I want each backup to go to a different place on the Shared Folder that it will replace the previous backup anyways?
No and because of this I said in my previous post that with some modifications and additions you can do the scenario. For example, you back up to a shared folder with the name of Shared1 on Mondays. You also have been configured the backup feature to back
up data on another shared folder, named Shared2, on Wednesday. When you repeat the backup operation in Shared1, only the backed up data that resides on it will be affected, and the data on Shared2 remains intact.
Please feel free to let us know if you have any question or concern.
Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
the thread.
Hi R.Alikhani
Then do you know if wbadmin supports incremental backup in Windows 8? As you said the VSS issue is fixed in Win8. However, the wbadmin has less options then in windows server. I tried a bit but it seems it only supports full backup? ps, I use a network share
- will the incremental backup works if I define a ISCCI then? My remote backup PC is also running Win8.

Task Scheduler Won't Run WBADMIN Backup

After several weeks of trying, the backup (wbadmin) doesn't work from the task scheduler. When I enter the WBADMIN Start Backup command directly into a command prompt, it executes perfectly and backs up everything it's supposed to, but for some reason,
when that EXACT SAME COMMAND is executed from the task scheduler it starts, then immediately stops. I opened the Task Scheduler, clicked on "Task Scheduler Library" in the left pane, and looked at the backup job in the top window of the center pane.
The "Last Run Result" column simply showed, "(0xFFFFFFFF")". I also clicked on the job's History Tab, which showed 7 entries at the date/time the job is set to trigger, which indicated that the task started and completed, "successfully" within the same
second (i.e. 01:00:00), but absolutiely nothing is backed up, nor are there any entries for the trigger date on the backup drive.
This has happened four Sundays in a row, and each time, when I subsequently execute the WBADMIN command from a command prompt, it works correctly. Any ideas about what I'm missing and/or doing incorrectly
Creacon

Thanks Jeff, but unfortunately, I've already done all those things from advice in a previous thread. The task scheduler DOES schedule the task, and my History is not disabled. But when the Task Scheduler starts, it then stops immediately with two
log entries: 1) "Action Completed", and in the lower history window "Task Scheduler successfully completed the task ...", and 2) a log entry saying "Task Completed", and in the lower history window, "Task Scheduler successfully finished...", but NOTHING
is backed up. I've gone through the task scheduler settings for the task, and everything seems ok, but no dice. Yet, I can enter the EXACT SAME wbadmin command into a command prompt, and the backup works fine.
Here's the actual "SCHTASKS" command that I entered to schedule the job:
SCHTASKS /Create /SC WEEKLY /D SUN /TN CTServerWeeklyBackup /RL Highest /ST 01:00 /TR "WBADMIN START BACKUP -backupTarget:f: -allCritical -include:C:\,D:\CAB\,D:\Downloads\,D:\Extracts\,D:\SSLCert\,D:\Temp\,U:\CAB\,U:\Shares\,U:\Temp\ >
C:\backupLogs.txt"
The above command executed without incident, then I immediately checked the task scheduler, and the task was there, properly scheduled. When the trigger time/day occurred, the task simply started then immediately stopped, yet when I enter just
the WBADMIN command into a command prompt, it executes correctly, completely and without incident.
Creacon

Error if we schedule Backup in DB13

Hi Friends,
I am getting an error, if we schedule back up from DB13. It is saying "file size is greater than it can fit in an cpio header--limit is 32 bits". This error is occuring when PSAPDATA3\undo_1\undo.data1 file is in backup process. And undo.data1 file is 5GB in size. Is this could be problem or any other problem with settings in InitSID.sap. Please help me with your valuable solutions.
Regards,
Nageshwar

HI nageshwar,
Check the initSID.sap file for parameters CPio, dd that has mentioned. Change that according to your OS and the tape parameters also needed to be set based on your OS. After doing changes, try the backup.
Regards,
Maheswaran

Task License Validation Error Message/ Automatic Scheduling for Disk Defrag is not working.

I saw where I could possibly ask you for answers to the problems that I am having with Windows 8.1 pro. First of all I noticed that my disk defragmentation task which was set on daily wasn't operating. It indicated that the last time it ran all disks
for disk defrag was back on 4/20 and on the this morning of 4/26 there was the date 4/20 for all the disks. I went into the Administrator Tools section of Control Panel and found Schedule Tasks. When I opened Schedule Tasks I got the
error message that indicated a Task License Validation Error. It went on to read:The task XML contains a value which is incorrectly formatted or out of range. This is my question...are the two related...the inoperative automatic maintenance of disk defrag
and this error message from task scheduler? And how do I address each issue to solution. Thank you very much.
[email protected]

The MSDN Windows and Windows Phone app development forums are for developers to discuss writing their own Windows and Windows Phone apps.
For help using Windows please post on the Windows forums on
http://answers.microsoft.com .

Exchange 2013 mailbox auditing command with showdetails parameter in ps1 script is not working via task scheduler

Hi All ,
In my environment we are having exchange 2013 enterprise edition with SP1 which is installed in windows server 2012 standard edition.
We have enabled mailbox auditing for few mailboxes and also we have made simple powershell script with only the below mentioned commands .when i run the ps1 script in exchange management shell ,i can able to get the relevant output.
CMDLETS in powershell script :
Search-MailboxAuditLog -StartDate ((Get-Date).AddHours(-24)) -EndDate (Get-Date) -showdetails | fl >e:\output.txt
Note : we are having only the above commands in ps1 script , apart from that we don't have anything in it .
Sametime i have scheduled the same powershell script via task scheduler .But i cannot able to get the valid output ,instead of that i was getting a blank output file with no data in it .
Steps handled on my side to run the powershell script in task scheduler:
1.when i remove the parameter showdetails in the ps1 script ,i can able to get the output in the txt file .But in my scenario showdetails is the only parameter which will brought me more and in depth details about mailbox auditing.
The Difference what i have seen between exchange 2010 and exchange 2013
when in run the same powershell script via task scheduler in exchange 2010 enterprise environment installed in windows server 2008 r2 enterprise OS, i can able able to get the proper output without removing the showdetails parameter .
I am using the below methods to run the ps1 file via task scheduler in exchange 2013 environment .
program/script : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
Add arguments : -PSConsoleFile "E:\Program Files\Microsoft\Exchange Server\V15\Bin\exshell.psc1" -Command ". 'C:\scripts\MailboxAuditReport\test.ps1'"
I have mentioned the error below and that is the one what i have faced, when i try to run the PS1 script directly in windows powershell and not in exchange management shell .
Error message : "the requesting account does not have permission to access the audit log"
Please help me out to resolve this case .
Thanks
S.Nithyanandham

Hi All ,
In my environment we are having exchange 2013 enterprise edition with SP1 which is installed in windows server 2012 standard edition.
We have enabled mailbox auditing for few mailboxes and also we have made simple powershell script with only the below mentioned commands .when i run the ps1 script in
exchange management shell,i can able to get the relevant output.
CMDLETS in powershell script :
Search-MailboxAuditLog -StartDate ((Get-Date).AddHours(-24)) -EndDate (Get-Date) -showdetails | fl >e:\output.txt
Note : we are having only the above commands in ps1
script , apart from that we don't have anything in it .
In case, if i have scheduled the same powershell script via task scheduler .But i cannot able to get the valid output ,instead of that i was getting a blank output file with no data in it .
Steps
handled on my side to run the powershell script in task scheduler:
1.when i remove the parameter showdetails
in the ps1 script ,i can able to get the output in the txt file .But in my scenario showdetails is the only parameter which will brought me more and in depth details about mailbox auditing.
The
Difference what i have seen between exchange 2010 and exchange 2013
when in run the same powershell script via task scheduler in exchange 2010 enterprise environment installed in windows server 2008 r2 enterprise OS, i can able able to get the proper output without removing the showdetails parameter .
I
am using the below methods to run the ps1 file via task scheduler in exchange 2013 environment .
program/script : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
Add arguments : -PSConsoleFile "E:\Program
Files\Microsoft\Exchange Server\V15\Bin\exshell.psc1" -Command ". 'C:\scripts\MailboxAuditReport\test.ps1'"
I have mentioned the error below and that is the one what i have faced, when i try to run the PS1 script directly in windows powershell and not in exchange management shell .
Error message : "the requesting account does
not have permission to access the audit log"
Please help me out to resolve this case .
Thanks
S.Nithyanandham

Windows Task Scheduler executing old triggers even after recreating the task

I had this task working perfectly until I changed the schedule. After I changed the scheduled time 5 minutes earlier, I noticed that in the history, it still triggers the old schedule. I tried restarting the server, deleting the task and recreating it even
without a trigger and it's still executing the task with the old trigger. The attached screenshot shows that the task doesn't have a trigger but as you can see in the history it's still trying to execute the task. How does the Windows Task Scheduler work?
Is there a file or database that I can purge the old task?
I also tried applying this hotfix but it didn't seem to fix the issue:
http://support.microsoft.com/kb/2461249
NOTE: This is Windows 2008 R2 and the Error message in the history is: Task Scheduler failed to start "<the
name of my task>" task for user "<the
user>". Additional Data: Error Value: 2147750689.

Since batch job can be run manually without error, cmd.exe is not the problem.
I researched and found that the problem may be due to exhausted desktop heap and the solution is to increase the value.
Please try this step:
1. restart the server first and test again (a simple solution that may work)
2. if the first attempt fail, take a full backup first and attempt to increase desktop heap
http://www.symantec.com/business/support/index?page=content&id=TECH48099
Yes THAT WAS THE SOLUTION FOR THE ISSUE. !!
Now its working perfect!!
Why now its working and not before? Because after made the changes to the registry,
RESTART IS NECESSARY to apply the changes and I have done it yesterday night (this server is working 24x7, so its hard to find a moment to restart it).
Thanks for all to help me with this issue!!! I really,really ,really ,really apreciate !!!
THANKS !!!!!

Windows server backup crash vss errors

We're having an issue where every other day the system state fails. We use a 3rd party piece of software that uses WSB for the system state. We get the following in the eevnt logs:
Faulting application name: wbengine.exe, version: 6.1.7601.17514, time stamp: 0x4ce79951
Faulting module name: ntdll.dll, version: 6.1.7601.18229, time stamp: 0x51fb164a
Exception code: 0xc0000005
Fault offset: 0x0000000000055384
Faulting process id: 0x3560
Faulting application start time: 0x01d01197a2bdc7a1
Faulting application path: C:\Windows\system32\wbengine.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: d6f0610d-7d8f-11e4-a8f7-5cf3fc557333
and the following when running vssadmin list writers:
Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error
Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error
Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error
Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {7655da00-923b-441b-bc40-d64e3d44aaa9}
   State: [1] Stable
   Last error: No error
Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {0e9c9681-5e67-4748-900c-b32ff7ebd072}
   State: [5] Waiting for completion
   Last error: No error
Writer name: 'FRS Writer'
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {3e4d034d-b955-428e-952b-0581f8e05203}
   State: [5] Waiting for completion
   Last error: No error
Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {3ee8ab83-468c-4cfe-8613-6946976820fb}
   State: [5] Waiting for completion
   Last error: No error
Writer name: 'FSRM Writer'
   Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
   Writer Instance Id: {2975a331-2068-4a6e-a16f-4635f5ce2856}
   State: [5] Waiting for completion
   Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {43188986-6573-45a8-b871-4be3d189a45f}
   State: [1] Stable
   Last error: No error
Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {a9632f02-31e3-424c-8c87-69395dbf04e2}
   State: [1] Stable
   Last error: No error
Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {180f4d03-93aa-4947-b874-c2d0d7546ca0}
   State: [5] Waiting for completion
   Last error: No error
Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {231ceb2e-3b8c-40f1-8d02-22a4f263802d}
   State: [1] Stable
   Last error: No error
Writer name: 'TS Gateway Writer'
   Writer Id: {368753ec-572e-4fc7-b4b9-ccd9bdc624cb}
   Writer Instance Id: {60237974-e116-454e-b29c-6ffeffd1bd9d}
   State: [5] Waiting for completion
   Last error: No error
Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {440c5208-9d3a-4c84-884c-f9a3d8ad2c1e}
   State: [1] Stable
   Last error: No error
Writer name: 'NPS VSS Writer'
   Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
   Writer Instance Id: {d6ae39a4-2c8b-4e48-9f79-12247b9fac5b}
   State: [5] Waiting for completion
   Last error: No error
Writer name: 'Dhcp Jet Writer'
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {c616d312-5e21-47df-9e59-100cf6ac6f0e}
   State: [5] Waiting for completion
   Last error: No error
Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {8f945f3b-d50b-47b8-9085-1416d0b094e1}
   State: [5] Waiting for completion
   Last error: No error
Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {50c005a1-35e8-4bc1-a0c1-1bcdc9351322}
   State: [5] Waiting for completion
   Last error: No error
Writer name: 'MSSearch Service Writer'
   Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
   Writer Instance Id: {2bcebf65-9243-4ccd-bae2-6ae12efd9a51}
   State: [5] Waiting for completion
   Last error: No error
Writer name: 'Certificate Authority'
   Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
   Writer Instance Id: {4101713c-f207-431f-be52-1171f1227c0b}
   State: [5] Waiting for completion
   Last error: No error
Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {aa053355-2571-4e37-ba1d-501127ab2846}
   State: [5] Waiting for completion
   Last error: No error
Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {7645b18a-8aa4-49d3-abd1-5d7debd4b3f3}
   State: [1] Stable
   Last error: No error
as i said - this happens every other day, the 3rd party software provider say this is a microsoft issue but this doesnt happen when running a system state directly from WSB

Hi,
What third party software do you use? There is a similar thread, please try to restart Block Level Backup Engine Service and VSS service to check if could resolve the issue.
For more detailed information, please refer to the thread below:
Backup SystemState 2008 R2 failed - The RPC server is unavailable.
https://social.technet.microsoft.com/Forums/en-US/f92c0a5b-2cfb-47f9-9ace-6028f5316a03/backup-systemstate-2008-r2-failed-the-rpc-server-is-unavailable
Best Regards,
Mandy
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Windows task scheduler not running

Hi All!
(First of all, sorry for my poor english!)
I have a couple of windows servers 2008 R2 Enterprise SP1 on my company and one of them doesnt work like it should and was instaled from zero last week.
I create a bat file to do some stuff and because it dosnt work, for test porpouses i made a bat file realy simple, that wirtes file
Here is the bat file code:
echo "text_example" > C:\scripts\works.txt
my user has write permisions and the task is configured to run with my user.
If i run my bat manualy works fine.
If this job is set to the task scheduler "run only if user is loged" also works fine
BUT when i set the task to run wheter "the user is logued or not" and I log off and return after the job was triggered, i found that the last run date is the one i set but the last run result is (0xc000142) and the task ovbiusly didnt work.
Im figthing with this problem las 4 days and i cant find why is this appening (its trange that in the other servers in the same group works fine)
Here is the task code:
<?xml version="1.0" encoding="UTF-16"?>
<Task version="1.2" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
<RegistrationInfo>
<Date>2014-11-17T14:07:58.9325949</Date>
<Author>GROUP\rrepetto</Author>
</RegistrationInfo>
<Triggers>
<CalendarTrigger>
<StartBoundary>2014-11-17T17:46:00</StartBoundary>
<Enabled>true</Enabled>
<ScheduleByDay>
<DaysInterval>1</DaysInterval>
</ScheduleByDay>
</CalendarTrigger>
</Triggers>
<Principals>
<Principal id="Author">
<UserId>GROUP\rrepetto</UserId>
<LogonType>Password</LogonType>
<RunLevel>LeastPrivilege</RunLevel>
</Principal>
</Principals>
<Settings>
<MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
<DisallowStartIfOnBatteries>true</DisallowStartIfOnBatteries>
<StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>
<AllowHardTerminate>true</AllowHardTerminate>
<StartWhenAvailable>false</StartWhenAvailable>
<RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
<IdleSettings>
<StopOnIdleEnd>true</StopOnIdleEnd>
<RestartOnIdle>false</RestartOnIdle>
</IdleSettings>
<AllowStartOnDemand>true</AllowStartOnDemand>
<Enabled>true</Enabled>
<Hidden>false</Hidden>
<RunOnlyIfIdle>false</RunOnlyIfIdle>
<WakeToRun>false</WakeToRun>
<ExecutionTimeLimit>P3D</ExecutionTimeLimit>
<Priority>7</Priority>
</Settings>
<Actions Context="Author">
<Exec>
<Command>C:\scripts\test.bat</Command>
</Exec>
</Actions>
</Task>
Any help will be greatly appreciated !
Thanks In advance!
Ramiro

Since batch job can be run manually without error, cmd.exe is not the problem.
I researched and found that the problem may be due to exhausted desktop heap and the solution is to increase the value.
Please try this step:
1. restart the server first and test again (a simple solution that may work)
2. if the first attempt fail, take a full backup first and attempt to increase desktop heap
http://www.symantec.com/business/support/index?page=content&id=TECH48099
Yes THAT WAS THE SOLUTION FOR THE ISSUE. !!
Now its working perfect!!
Why now its working and not before? Because after made the changes to the registry,
RESTART IS NECESSARY to apply the changes and I have done it yesterday night (this server is working 24x7, so its hard to find a moment to restart it).
Thanks for all to help me with this issue!!! I really,really ,really ,really apreciate !!!
THANKS !!!!!

Executing powershell script via task scheduler

Hello,
I am trying to execute powershell script via windows task scheduler which will forcefully delete all email in a mailbox, but I am getting the below errors
Operational Code - 2
Task Category - Action Completed --- Task Scheduler successfully completed task "\IL98" , instance "{2b193375-cbd2-4986-918d-3cfd4027d6b6}" , action "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" with return code 0.
Last Run Result - 0X0
When I am adding additional cmdlets in the script "Set-ExecutionPolicy Unrestricted", I am getting Last Run Result 0X5 rest of the error remains the same.
Powershell version - 3.0
Task Scheduler version - 1.0
If I try to run the script manually via Exchange Powershell the script executes without any errors
Thanks in Advance,
Ankush Shah

I figured out the problem, there wasn't any problem with the script but I had to correct inputs in windows task scheuler
Below is the resolution:
Under Actions:
Program/Script --> ws\System32\WindowsPowerShell\v1.0\powershell.exe
Add Argument --> -noexit -command ". 'C:\Program Files\Microsoft\Exchange Server\V14\bin\RemoteExchange.ps1'; Connect-ExchangeServer -auto
; <filepath>"
Eariler I was writing the filepath after double quote "
Also I have selected the option "Run with Highest Privilages" to avoid
0x5 error

Unable to receive an email by task scheduler on audit failure in windows server 2008 r2 security log

Deal All,
I am sorry in advance if i would be on wrong forum, i have created a task on Server 2008 r2 Domain controller that when an audit failure event triggered in windows security log then an email should reach on my email ID, but unfortunately, nothing happen
on audit failure.i receive no email from task scheduler.
kindly suggest me to resolve the issue. I have created Email task on event ID 4771.
Thanks.
Zeeshan Ibrahim Network Administrator

Hi Zeeshan,
I have found a hotfix against the same error messages, though it applies to Windows Vista and Windows Server 2008, I am not sure if it will work on your machine.
Please refer to this KB article below:
Duplicate triggers are generated incorrectly in scheduled tasks in Windows Vista or in Windows Server 2008
http://support.microsoft.com/kb/2617046
Please feel free to let us know if this hotfix couldn’t help you fix this issue.
Best Regards,
Amy Wang

Backup-GPO cmdlet errors in Task Scheduler

Similar Messages

Maybe you are looking for